[asterisk-bugs] [Asterisk 0012282]: [patch] Asterisk sends SIP-over-TCP INVITE to wrong port number
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu May 14 10:34:19 CDT 2009
The following issue requires your FEEDBACK.
======================================================================
https://issues.asterisk.org/view.php?id=12282
======================================================================
Reported By: rjain
Assigned To: dvossel
======================================================================
Project: Asterisk
Issue ID: 12282
Category: Channels/chan_sip/TCP-TLS
Reproducibility: always
Severity: minor
Priority: normal
Status: feedback
Asterisk Version: SVN
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 110578
Request Review:
======================================================================
Date Submitted: 2008-03-23 08:28 CDT
Last Modified: 2009-05-14 10:34 CDT
======================================================================
Summary: [patch] Asterisk sends SIP-over-TCP INVITE to wrong
port number
Description:
The scenario is that a SIP UA registers with Asterisk using TCP transport.
The UA puts its IP address, port number and transport=tcp parameter in the
REGISTER's Conact: header. Asterisk stores these contact parameters
correctly in its registration table. However, when it comes to sending an
INVITE to this UA, Asterisk puts a wrong port number in the destination
port number field of the TCP header. Due to this, the UA never receives the
INVITE. The TCP port number is actually correct in the SIP payload
including the Request-URI and the To: header in the INVITE, but it's not
correct in the TCP header.
Asterisk log file and wireshark trace are attached.
======================================================================
----------------------------------------------------------------------
(0104733) dvossel (administrator) - 2009-05-14 10:34
https://issues.asterisk.org/view.php?id=12282#c104733
----------------------------------------------------------------------
take a look at reg_patch_1.diff. It changes the way the Contact header is
parsed during a Registration. Let me know if it fixes your problem.
Issue History
Date Modified Username Field Change
======================================================================
2009-05-14 10:34 dvossel Note Added: 0104733
2009-05-14 10:34 dvossel Status assigned => feedback
======================================================================
More information about the asterisk-bugs
mailing list