Hi Rahul,
I feel the timeout is implementation dependent. So u cannout expect RFC to
specify one. But the standard way is
to specify a timeout of -1 for infinte wait and a timeout of 0 for
asynchronous events.
Any comments??
Regards
Ranjit
Mascon Communication Technologies
http://www.masconit.com
----- Original Message -----
From: rahul pande <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, May 22, 2001 6:17 AM
Subject: [Sip-implementors] Clarity required regarding timeouts...
The section 10.3.1 in SIP RFC states ::
"A SIP client using an unreliable transport protocol SHOULD retransmit a SIP
INVITE request with an interval that starts at T1 seconds, and doubles after
each packet transmission. The client ceases retransmissions if it receives a
provisional or definitive response, or once it has sent a total of seven
request packets."
When a provisional response for an INVITE reaches the Client , it will stop
having any timeouts, then there is a chance that the application might hang
if the server is malacious and does not follow the standard. Shouldn't the
RFC specify what is that timeout value as in the case of section 10.2.1 for
other Requests other than INVITE.
Please advise me on the same.
Thanking you,
rahul
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
