[asterisk-bugs] [Asterisk 0010677]: [post 1.4] SIP change at r77616 (rizzo) causes all outbound calls to fail authentication with 403 Forbidden

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10677 
====================================================================== 
Reported By:                mensaiq
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10677
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 17616 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             09-09-2007 15:22 CDT
Last Modified:              11-15-2007 06:16 CST
====================================================================== 
Summary:                    [post 1.4] SIP change at r77616 (rizzo) causes all
outbound calls to fail authentication with 403 Forbidden
Description: 
Before r77616, outgoing calls properly send a second INVITE in response to
a 401 Unauthorized response to the initial INVITE. Both INVITE headers
contain the same IP address in Via:.
After r77616, the second INVITE's Via: header has a real IP address in it,
the first contains the internal IP. This difference causes the provider
(Broadvoice) to return a 403 Forbidden in response to the second INVITE.
====================================================================== 

---------------------------------------------------------------------- 
 oej - 11-15-07 06:16  
---------------------------------------------------------------------- 
Yes, that's a bad patch to have mandatory. Some communication badly enough
rely on not sending a public IP/Port, since NAT's may change that. NAT's
are very evil.

We need to implement an option for this, so we can set it on a peer/user
level.

Sorry, I missed this patch earlier. Thanks for reporting this bug. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
11-15-07 06:16  oej            Note Added: 0073702                          
======================================================================