Upgrading/Downgrading Asterisk: Difference between revisions

From MiRTA PBX documentation
Jump to navigation Jump to search
(Created page with "Upgrading or downgrading Asterisk should be done only if really needed. Asterisk relies on a series of libraries and different Asterisk versions may need different library ver...")
 
No edit summary
Line 8: Line 8:


From Asterisk 13.10.0, the nasty ODBC lock bug is solved, but the SIP lock bug was still in place. It is needed to upgrade unixODBC to at least version 2.3.4-1. A link to upgrade it is provided in the script. If installing a previous asterisk version, upgrading unixODBC can lead to unexpected instabilities.
From Asterisk 13.10.0, the nasty ODBC lock bug is solved, but the SIP lock bug was still in place. It is needed to upgrade unixODBC to at least version 2.3.4-1. A link to upgrade it is provided in the script. If installing a previous asterisk version, upgrading unixODBC can lead to unexpected instabilities.
If you upgrade to unixODBC 2.3.4-1, then you need to add the max_connections parameters to /etc/asterisk/res_odbc.conf. A good value can be 100.
<pre>
[asteriskcdrdb1]
enabled => yes
dsn => asteriskcdrdb1
pre-connect => yes
sanitysql => select 1
idlecheck => 28000
max_connections => 100
[asteriskcdrdb2]
enabled => yes
dsn => asteriskcdrdb2
pre-connect => yes
sanitysql => select 1
idlecheck => 28000
max_connections => 100
[asterisk1]
enabled => yes
dsn => asterisk1
pre-connect => yes
sanitysql => select 1
idlecheck => 28000
max_connections => 100
[asterisk2]
enabled => yes
dsn => asterisk2
pre-connect => yes
sanitysql => select 1
idlecheck => 28000
max_connections => 100
</pre>


From Asterisk 13.12.0 the nasty SIP lock bug seems gone.
From Asterisk 13.12.0 the nasty SIP lock bug seems gone.

Revision as of 08:06, 26 October 2016

Upgrading or downgrading Asterisk should be done only if really needed. Asterisk relies on a series of libraries and different Asterisk versions may need different library versions.

A sample script to upgrade Asterisk is provided as protected/installAsterisk.sh

Asterisk version up to 13.4.0 (included) are known to work pretty well.

From Asterisk 13.5.0 to 13.9.0 there is a nasty ODBC lock bug and a nasty SIP lock bug

From Asterisk 13.10.0, the nasty ODBC lock bug is solved, but the SIP lock bug was still in place. It is needed to upgrade unixODBC to at least version 2.3.4-1. A link to upgrade it is provided in the script. If installing a previous asterisk version, upgrading unixODBC can lead to unexpected instabilities.

If you upgrade to unixODBC 2.3.4-1, then you need to add the max_connections parameters to /etc/asterisk/res_odbc.conf. A good value can be 100.

[asteriskcdrdb1]
enabled => yes
dsn => asteriskcdrdb1
pre-connect => yes
sanitysql => select 1
idlecheck => 28000
max_connections => 100

[asteriskcdrdb2]
enabled => yes
dsn => asteriskcdrdb2
pre-connect => yes
sanitysql => select 1
idlecheck => 28000
max_connections => 100

[asterisk1]
enabled => yes
dsn => asterisk1
pre-connect => yes
sanitysql => select 1
idlecheck => 28000
max_connections => 100

[asterisk2]
enabled => yes
dsn => asterisk2
pre-connect => yes
sanitysql => select 1
idlecheck => 28000
max_connections => 100

From Asterisk 13.12.0 the nasty SIP lock bug seems gone.