[asterisk-bugs] [Asterisk 0016425]: SIP qualify fails unless NAT is enabled

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16425 
====================================================================== 
Reported By:                hevad
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16425
Category:                   Channels/chan_sip/TCP-TLS
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!): 233730 
Request Review:              
====================================================================== 
Date Submitted:             2009-12-10 13:33 CST
Last Modified:              2009-12-17 12:51 CST
====================================================================== 
Summary:                    SIP qualify fails unless NAT is enabled
Description: 
Using a SIP device on the same subnet as asterisk fails to qualify unless
nat option is enabled. The device will register fine and can make outgoing
calls but will not receive calls.
====================================================================== 

---------------------------------------------------------------------- 
 (0115399) ebroad (manager) - 2009-12-17 12:51
 https://issues.asterisk.org/view.php?id=16425#c115399 
---------------------------------------------------------------------- 
That is correct, and that's probably why it logged like that. Basically,
nat=yes, Asterisk will use the rport header, if rport is not equal to
anything then Asterisk will use the port that the UA sent from. When
nat=no, Asterisk uses whatever is in the Contact header. AFAIK, I believe
this is correct operation per the RFC(s). Can you check to see if X-Lite is
indeed listening on the port that is specifies in the Contact header when
NAT is disabled(both is Asterisk and in the UA)? Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-12-17 12:51 ebroad         Note Added: 0115399                          
======================================================================