[asterisk-dev] [Code Review] 2524: Fix The Crash Caused By The Fix For One-way Audio With auto_* NAT Settings When SIP Calls Are Initiated By PBX
Mark Michelson
reviewboard at asterisk.org
Thu May 9 09:04:36 CDT 2013
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/2524/#review8533
-----------------------------------------------------------
Ship it!
Ship It!
- Mark Michelson
On May 9, 2013, 4:38 a.m., Michael Young wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/2524/
> -----------------------------------------------------------
>
> (Updated May 9, 2013, 4:38 a.m.)
>
>
> Review request for Asterisk Developers.
>
>
> Bugs: ASTERISK-21374
> https://issues.asterisk.org/jira/browse/ASTERISK-21374
>
>
> Repository: Asterisk
>
>
> Description
> -------
>
> Okay... so... I created a crash problem which will not make many people very happy.
>
> The code that was submitted failed to take into consideration that not all outgoing calls will be to a peer. Shame on me.
>
> This patch checks if there is a related peer involved. If there is, then go about checking its NAT settings to see if it is using the new auto_* NAT settings and then handle the call accordingly.
>
> Also, I discovered an issue with real time peers. If the global setting has auto_force_rport set and we issued a "sip reload" while a peer is still registered, which, resets the flags for the NAT settings on the peer to off (and we haven't had a chance to check if the peer might be behind NAT in order to turn the force_rport flag on for the peer), we were always setting the contact address of the peer to that of the full contact. This patch corrects that condition as well.
>
>
> Diffs
> -----
>
> /branches/11/channels/chan_sip.c 388111
>
> Diff: https://reviewboard.asterisk.org/r/2524/diff/
>
>
> Testing
> -------
>
> Tested on a production machine for some days now and on a couple of dev machines.
>
>
> Thanks,
>
> Michael Young
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20130509/6a9603ba/attachment.htm>
More information about the asterisk-dev
mailing list