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

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Apr 30 09:54:50 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14446 
====================================================================== 
Reported By:                frawd
Assigned To:                oej
====================================================================== 
Project:                    Asterisk
Issue ID:                   14446
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
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-04-30 09:54 CDT
====================================================================== 
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
====================================================================== 

---------------------------------------------------------------------- 
 (0104005) frawd (reporter) - 2009-04-30 09:54
 http://bugs.digium.com/view.php?id=14446#c104005 
---------------------------------------------------------------------- 
Agreed, but isn't the behaviour of Asterisk also wrong without it?

I would love to see the issue resolved, but simply do not have the skills
or time to do more than just pointing out the issue and sending a dirty fix
that works for me. Sorry!

Mr. oej, is there anything planned for this issue, I can help with testing
if needed. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-30 09:54 frawd          Note Added: 0104005                          
======================================================================




More information about the asterisk-bugs mailing list