[asterisk-bugs] [Asterisk 0015283]: [patch] CLI NOTIFY always tries to use UDP, even if the peer is connected via TCP

[Asterisk Bug Tracker]

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-09 00:42 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0106150) jthurman (reporter) - 2009-06-09 00:42
 https://issues.asterisk.org/view.php?id=15283#c106150 
---------------------------------------------------------------------- 
After looking at 13865, I think this could be rolled into that patch.  The
patch as it exists does not correct this issue.  However, it appears as if
a single change in that patch could resolve this issue.  Posted the change
to the review. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-09 00:42 jthurman       Note Added: 0106150                          
======================================================================