[asterisk-bugs] [Asterisk 0015283]: [patch] CLI NOTIFY always tries to use UDP, even if the peer is connected via TCP
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Jun 9 15:47:59 CDT 2009
The following issue has been RESOLVED.
======================================================================
https://issues.asterisk.org/view.php?id=15283
======================================================================
Reported By: jthurman
Assigned To: dvossel
======================================================================
Project: Asterisk
Issue ID: 15283
Category: Channels/chan_sip/General
Reproducibility: always
Severity: minor
Priority: normal
Status: resolved
Asterisk Version: SVN
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 199478
Request Review:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 2009-06-07 02:51 CDT
Last Modified: 2009-06-09 15:47 CDT
======================================================================
Summary: [patch] CLI NOTIFY always tries to use UDP, even if
the peer is connected via TCP
Description:
When sending a notification from the console to a sip peer using
transport=tcp, only a TCP notification is attempted.
Here is the error on the console:
ERROR[11426]: chan_sip.c:4963 create_addr_from_peer: 'UDP' is not a valid
transport for '1000'. we only use 'TCP'! ending call.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2009-06-09 15:47 svnbot Status assigned => resolved
2009-06-09 15:47 svnbot Resolution open => fixed
======================================================================
More information about the asterisk-bugs
mailing list