[Home]

Summary:ASTERISK-28398: Column order of contrib realtime MySQL config for sippeers causes issues with NAT
Reporter:Bart Bergman (bbergman)Labels:sip
Date Opened:2019-04-26 05:41:39Date Closed:
Priority:MinorRegression?
Status:Open/NewComponents:Channels/chan_sip/General
Versions:16.3.0 Frequency of
Occurrence
Constant
Related
Issues:
Environment:Attachments:
Description: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)
Comments:By: Asterisk Team (asteriskteam) 2019-04-26 05:41:40.842-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

By: Kevin Harwell (kharwell) 2019-04-30 11:15:56.801-0500

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