[asterisk-bugs] [JIRA] (ASTERISK-28398) Column order of contrib realtime MySQL config for sippeers causes issues with NAT

[Kevin Harwell (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247055#comment-247055 ] 

Kevin Harwell commented on ASTERISK-28398:
------------------------------------------

The chan_sip channel driver is in 'extended' support status and is supported only by community members.  Your issue is in the queue. Your patience is appreciated as a community developer may work the issue when time and resources become available.

Asterisk is an open source project and community members work the issues on a voluntary basis. You are welcome to develop your own patches and submit them to the project.[1]

If you are not a programmer and you are in a hurry to see a patch provided then you might try rallying support on the Asterisk users mailing list or forums.[2] Another alternative is offering a bug bounty on the asterisk-dev mailing list.[3] Often a little incentive can go a long way.

[1]: https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process
[2]: http://www.asterisk.org/community/discuss
[3]: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Bug+Bounties



> Column order of contrib realtime MySQL config for sippeers causes issues with NAT
> ---------------------------------------------------------------------------------
>
>                 Key: ASTERISK-28398
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28398
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Contrib/General
>    Affects Versions: 16.3.0
>            Reporter: Bart Bergman
>            Severity: Minor
>
> In the create table SQL definition for the sippeers table there are some issues with the column order.
> The columns are read into config in the order they appear in the database.
> `host` before `ipaddr` causes peers to subscribe with their local IP when behind NAT and a `sip reload` is issued.
> `permit` and `deny` might also cause issues (not confirmed)



--
This message was sent by Atlassian JIRA
(v6.2#6252)