[asterisk-bugs] [Asterisk 0014446]: [patch] chan_sip does not support the maddr attribute in Via headers

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14446 
====================================================================== 
Reported By:                frawd
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14446
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.23 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-02-10 04:12 CST
Last Modified:              2009-02-10 11:23 CST
====================================================================== 
Summary:                    [patch] chan_sip does not support the maddr
attribute in Via headers
Description: 
I recently connected Asterisk with a badly configured Nortel CS2K, which
sends me the following Via header:

Via: SIP/2.0/UDP
CS2KSSTEMAG:5060;maddr=213.60.204.48;branch=z9hG4bK-142abd7-ec6f41f2-4aeebdaf

CS2KSSTEMAG not being a valid DNS entry, the reply is never sent (Asterisk
blocks trying to resolve the name). Even tho it is a configuration error,
maddr should be used as reply address.

The attached patch fixes the issue in 1.4.23.1
====================================================================== 

---------------------------------------------------------------------- 
 (0099807) oej (manager) - 2009-02-10 11:23
 http://bugs.digium.com/view.php?id=14446#c99807 
---------------------------------------------------------------------- 
This is related to a few other bug reports on how to send replies. We
should propably just send the reply to whatever address we got it from. Via
headers is not really for UAS, more for proxy routing. But that is under
discussion.

But following the way we currently send replies, I guess this is something
to look into. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-10 11:23 oej            Note Added: 0099807                          
======================================================================