[asterisk-bugs] [Asterisk 0015679]: Registration fails when the packe contains 'transport=udp"
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Aug 10 09:10:31 CDT 2009
The following issue requires your FEEDBACK.
======================================================================
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: feedback
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-10 09:10 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.
======================================================================
----------------------------------------------------------------------
(0108840) mmichelson (administrator) - 2009-08-10 09:10
https://issues.asterisk.org/view.php?id=15679#c108840
----------------------------------------------------------------------
I cannot reproduce this issue using rev 211346 of 1.6.2. The Polycom phone
I use has in its Contact header:
Contact: <sip:666 at 10.24.19.242;transport=udp>;methods="INVITE, ACK, BYE,
CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER"
As you can see, it also includes "transport=udp" in the registration, but
Asterisk responds with a 200 OK. So, it's not the presence of the transport
parameter which is causing the problem, it must be something else. To help
me figure this out, could you post your sip.conf file so that I may try
using a similar configuration to reproduce the problem? Thank you.
Issue History
Date Modified Username Field Change
======================================================================
2009-08-10 09:10 mmichelson Note Added: 0108840
2009-08-10 09:10 mmichelson Status new => feedback
======================================================================
More information about the asterisk-bugs
mailing list