[asterisk-dev] SIP transport type configuration

Russell Bryant russell at digium.com
Fri May 8 18:50:23 CDT 2009

On May 8, 2009, at 5:51 PM, David Vossel wrote:

> In sip.conf the transport option allows for the configuration of  
> what transport types (udp, tcp, and tls) a peer will accept, but  
> only the first type listed is used for outbound connections.
> Example:
> transport = tcp, udp (peer will accept tcp or udp inbound, but will  
> only make outbound requests using tcp)
> If a peer registers using UDP and specifies UDP in the Contact  
> header, why should Asterisk force outbound connections to use TCP?

It shouldn't.  This is an area where we are not currently RFC  
compliant.  If the registered Contact said TCP, that is what we should  

> I purpose a change.  What if we make the first transport type only  
> the default type.  Meaning that is what is used unless the peer  
> registers using a different transport type that is also supported.   
> If the peer does register with a transport other than the default,  
> Asterisk should continue to use the peer's specified transport type  
> over the default type for all outbound connections to that peer  
> until the registration expires or a different transport is specified.

That sounds reasonable to me.

Russell Bryant
Digium, Inc. | Senior Software Engineer, Open Source Team Lead
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www.digium.com & www.asterisk.org

More information about the asterisk-dev mailing list