> -----Original Message-----
> From: Sunil Kumar T [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 12, 2001 11:11 AM
> To: Vovida - SIP; SIP implementors
> Subject: [Sip-implementors] need help on Client and Server FSMs
>
>
> Hi,
>
> please consider bis-03.
>
> When the transport is UDP,
>
> a) pg 78, fig 11 - why should the server wait for 32 sec before moving
> to COMPLETED state from CONFIRMED state.
This enables it to recognize incoming ACKs as retransmissions, and to
discard them. After going into the completed state (which then destroys the
FSM), any ACKs that are received would not match an existing transaction,
and might cause some kind of error processing which is not appropriate.
>
> When the transport is TCP,
>
> a) how long a client waits for the response after sending a request
Its up to the client. Its not different than how long a client waits after
sending an INVITE, and then receiving a 1xx.
>
> b) how long a server waits after sending a response to non-INVITE
Since requests are not retransmitted over TCP, the server can destroy
transaction state immediately after sending the response.
-Jonathan R.
---
Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave.
Chief Scientist First Floor
dynamicsoft East Hanover, NJ 07936
[EMAIL PROTECTED] FAX: (973) 952-5050
http://www.jdrosen.net PHONE: (973) 952-5000
http://www.dynamicsoft.com
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
