[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
Mon Jun 8 20:04:27 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15283 
====================================================================== 
Reported By:                jthurman
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15283
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 199478 
Request Review:              
====================================================================== 
Date Submitted:             2009-06-07 02:51 CDT
Last Modified:              2009-06-08 20:04 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0106148) jthurman (reporter) - 2009-06-08 20:04
 https://issues.asterisk.org/view.php?id=15283#c106148 
---------------------------------------------------------------------- 
Set the socket.type = 0 before the call to create_addr in sip_cli_notify
and the issue went away.  Similar to the MWI notification fix.

Tested with peers configured for TCP only and UDP only. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-08 20:04 jthurman       Note Added: 0106148                          
======================================================================




More information about the asterisk-bugs mailing list