[asterisk-bugs] [Asterisk 0013008]: [patch] chan_sip ignores rport and does not reply to source IP:port

noreply at bugs.digium.com noreply at bugs.digium.com
Tue Jul 22 18:07:40 CDT 2008


The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=13008 
====================================================================== 
Reported By:                klaus3000
Assigned To:                bbryant
====================================================================== 
Project:                    Asterisk
Issue ID:                   13008
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.21 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 duplicate
Duplicate:                  8855
Fixed in Version:           
====================================================================== 
Date Submitted:             07-07-2008 08:44 CDT
Last Modified:              07-22-2008 18:07 CDT
====================================================================== 
Summary:                    [patch] chan_sip ignores rport and does not reply to
source IP:port
Description: 
Hi!

I have defined a peer in sip.conf:
[klaus]
type=peer
username=klaus
secret=password
host=dynamic
context=fromklaus

Then I register with eyebeam. Eyebeam sets the "rport" parameter in via
header which should activate symmetric signaling. Further, even if rport is
missing, the RFC 3261 mandates that replies should be sent to the source IP
of the request, not the IP in the Via header (the latter one should only be
used if the first one fails (e.g. ICMP error)).

Bug: Asterisk sends the request back to the IP in the Via header. I know I
can change behavior by setting nat=yes, but even without this setting
Asterisk should be standard conform.

I used Asterisk 1.4.21.1
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0012577 Asterisk MUST add VIA "received&qu...
duplicate of        0008855 nat=no is not RFC 3261 compliant regard...
====================================================================== 

---------------------------------------------------------------------- 
 kpfleming - 07-22-08 18:07  
---------------------------------------------------------------------- 
This also is a duplicate of issue 8855; instead of having multiple
discussions going in different directions, let's keep everything there. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-22-08 18:07  kpfleming      Relationship added       duplicate of 0008855
07-22-08 18:07  kpfleming      Duplicate ID             0 => 8855           
07-22-08 18:07  kpfleming      Status                   assigned => resolved
07-22-08 18:07  kpfleming      Resolution               open => duplicate   
07-22-08 18:07  kpfleming      Note Added: 0090584                          
======================================================================




More information about the asterisk-bugs mailing list