[Sip] TCP timeout

["James Ford" <james_s_ford@hotmail.com>]

Hi,

I was wondering how to handle TCP timeouts with SIP.
If a connection is opened to a _non existing_ destination, the TCP stack 
(using non-blocking sockets and select) will only inform about an error 
after a TCP timeout (that can be considerably long on some systems).
(Existing destination with no listening port usually facilitates ICMP and 
"tells" that there is no listener).

My understanding is that SIP handles that by implementing invite timeout 
that is T1*64 (which is also quite long).

Here are the issues I'm struggling with:
1 - Does SIP has any other mechanism to handle such scenarios (H323 
facilitates a 4 seconds timeout on every outgoing call)?
2 - Doesn't this scenario compromises part of rfc3263 - locating sip 
servers, because the user is not likely to wait that long until a second 
server is reached.

Thanks,
James.

_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online 
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip