[asterisk-bugs] [Asterisk 0013117]: [patch] multiple 'transport' on peer doesn't work, tcp port still open

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13117 
====================================================================== 
Reported By:                pj
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13117
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 132312 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-07-20 15:28 CDT
Last Modified:              2008-11-20 09:17 CST
====================================================================== 
Summary:                    [patch] multiple 'transport' on peer doesn't work,
tcp port still open
Description: 
When I specify eg. 'transport=udp,tcp,tls' in peer configuration, in effect
is only first transport type. 
Currently, I can't specify multiple transport for peers.
Separate to more rows, doesn't solve this, ie:
transport=udp
transport=tcp
transport=tls
still only first is used.

Second issue is, that even if 'sip show settings' displays tcp port
disabled (default), asterisk still have tcp/5060 open.
====================================================================== 

---------------------------------------------------------------------- 
 (0095177) blitzrage (administrator) - 2008-11-20 09:17
 http://bugs.digium.com/view.php?id=13117#c95177 
---------------------------------------------------------------------- 
Ping(status)?

I'm dropping this down to Confirmed status as it appears there is an issue
here, but the attached patch(es) to resolve the issue seem to have no
effect. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-20 09:17 blitzrage      Note Added: 0095177                          
======================================================================