[asterisk-bugs] [JIRA] (ASTERISK-20756) Asterisk sippeers.sql columns place error cause peer to be without codecs when setting disallow=all under MySQL
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Mon Jan 14 13:57:46 CST 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Jordan updated ASTERISK-20756:
-----------------------------------
Target Release Version/s: 11.2.0
10.12.0-digiumphones
10.12.0
1.8.20.0
> Asterisk sippeers.sql columns place error cause peer to be without codecs when setting disallow=all under MySQL
> ---------------------------------------------------------------------------------------------------------------
>
> Key: ASTERISK-20756
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-20756
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Contrib/General
> Affects Versions: 11.0.1
> Environment: Ubuntu 12.04.01 LTS 386
> Asterisk 11.0.1 LTS compiled from source
> Dahdi 2.6.1
> Libipri 1.4.13
> Reporter: Andre Luis
> Assignee: Richard Mudgett
> Severity: Minor
> Target Release: 1.8.20.0, 10.12.0, 10.12.0-digiumphones, 11.2.0
>
> Attachments: sippeers.patch
>
>
> Creating the sippeers table from the sippeers.sql found in
> asterisk-11.0.1/contrib/realtime/mysql/ source folder, and
> set the parameter "disallow" to "all" will make peers with this configuration to be without codecs, therefore not being able to place calls.
> Explanation:
> The "disallow" parameter comes after the "allow" parameter in file
> sippeers.sql as showed below:
> ...
> `allow` varchar(40) DEFAULT NULL,
> `disallow` varchar(40) DEFAULT NULL,
> ...
> Peers set with disallow=all won't be able to place calls.
> How to fix:
> Put the "disallow" column before "allow" as showed below
> in file sippeers.sql
> ...
> `disallow` varchar(40) DEFAULT NULL,
> `allow` varchar(40) DEFAULT NULL,
> ...
> This way will work as supposed to be just like sip.conf .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list