The Session should keep track of the ACK receipt.
200 Should be retransmitted by session layer (Session to Transport bypassing Transaction layer) starting with T1 interval and doubling with each retransmission until T2 or until the ACK is received.
If ACK is not received after all the retransmissions, the dialog is considered to be Confirmed but it should be terminated immediately by sending a BYE.
Also, the UAS session should be able to identify the retransmitted INVITES based on the missing "To tag" as well as the same remote seq number and retransmit the 200 if an ACK is not yet received.
Have fun,
NC
KrishnaKanthT 70508 <[EMAIL PROTECTED]> wrote:
KrishnaKanthT 70508 <[EMAIL PROTECTED]> wrote:
Hi,
I need one clarification on INVITE server transaction.
After UAS gets INVITE, when TU sends 2xx response, then UAS immediately transits to "Terminated" state and gets deleted. From then onwards, TU will handle the retransmissions of 2xx response and its corresponding ACK.
Now, if we assume that, after UAS receives INVITE, the 100 sent by it is dropped in the network. Similarly when UAS sends 2xx, lets assume that 2xx is also dropped. Since 2xx is sent, UAS transaction is deleted. Since UAC has not received any response, it will again retransmit INVITE. Now, when this retransmitted INVITE comes to the destination, will a new server transaction be created. If so, how is this retransmitted INVITE handled??
Thanks & Regards
Krishna
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
