[asterisk-bugs] [Asterisk 0015679]: Registration fails when the packe contains 'transport=udp"

Asterisk Bug Tracker noreply at bugs.digium.com
Sat Aug 8 09:27:37 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15679 
====================================================================== 
Reported By:                falves11
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15679
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.2 
SVN Revision (number only!): 211122 
Request Review:              
====================================================================== 
Date Submitted:             2009-08-08 06:36 CDT
Last Modified:              2009-08-08 09:27 CDT
====================================================================== 
Summary:                    Registration fails when the packe contains
'transport=udp"
Description: 
As you can see below, the registration packet from a very popular SIP
Phone, the Eyebeam, includes "transport=udp". The Asterisk fails to accept
the registration with a message that says "only Unknown transport is
accepted". This is wrong. Registration should never be denied if the
transport is udp.

This issue should be fixed also in 1.4 ad Business Edition 3.0.4, coming
out next week. I am a user of all of them. 
====================================================================== 

---------------------------------------------------------------------- 
 (0108805) kpfleming (administrator) - 2009-08-08 09:27
 https://issues.asterisk.org/view.php?id=15679#c108805 
---------------------------------------------------------------------- 
This bug does not exist in any version of Asterisk prior to 1.6.0, or in
ABE, since there is no transport parsing prior to those versions (they only
supported UDP so any provided transport parameter was ignored). 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-08 09:27 kpfleming      Note Added: 0108805                          
======================================================================




More information about the asterisk-bugs mailing list