[asterisk-dev] [Code Review] 2421: One-way Audio With auto_* NAT Settings When SIP Calls Initiated By PBX

Michael Young reviewboard at asterisk.org
Tue Apr 2 15:04:30 CDT 2013


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/2421/#review8170
-----------------------------------------------------------



/branches/11/channels/chan_sip.c
<https://reviewboard.asterisk.org/r/2421/#comment15764>

    red spots will be eliminated


- Michael Young


On April 2, 2013, 4:03 p.m., Michael Young wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/2421/
> -----------------------------------------------------------
> 
> (Updated April 2, 2013, 4:03 p.m.)
> 
> 
> Review request for Asterisk Developers.
> 
> 
> Bugs: ASTERISK-21374
>     https://issues.asterisk.org/jira/browse/ASTERISK-21374
> 
> 
> Repository: Asterisk
> 
> 
> Description
> -------
> 
> I found another case where the force_rport and comedia flags are not being set automatically when using the new auto_* settings. This time it involves calls initiated by the PBX.
> 
> When we reload asterisk the default flags turned on and off by auto_force_rport (force_rport) and auto_comedia (comedia) go back to the default setting of off. These flags are turned on, as needed, when a peer re-registers or initiates a call. This would apply to even just having the default global setting "nat=auto_force_rport".
> 
> Everything is good except in the following scenario:
> We reload Asterisk and the peer's registration has not expired. We load in the default settings for the peer which turns force_rport and comedia back to off. Since the peer has not re-registered or placed a call yet, they remain off. We then initiate a call to the peer from the PBX. The force_rport and comedia flags stay off. If NAT is involved, we end up with one-way audio since we never checked to see if the peer is behind NAT or not.
> 
> This patch should be applied after the patch for ASTERISK-21225 is committed. (Review - https://reviewboard.asterisk.org/r/2385/)
> 
> 
> Diffs
> -----
> 
>   /branches/11/channels/chan_sip.c 384473 
> 
> Diff: https://reviewboard.asterisk.org/r/2421/diff/
> 
> 
> Testing
> -------
> 
> Tested on machine in production where this problem occurred.
> 
> 
> Thanks,
> 
> Michael Young
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20130402/509b12c4/attachment-0001.htm>


More information about the asterisk-dev mailing list