[asterisk-bugs] [JIRA] (ASTERISK-20756) Asterisk sippeers.sql columns place error cause peer to be without codecs when setting disallow=all under MySQL

[Andre Luis (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Luis updated ASTERISK-20756:
----------------------------------

    Attachment: sippeers.patch

Patch for sippeers.sql
                
> 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: . I did not set the category correctly.
>    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
>            Severity: Minor
>         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