>> However note that in draft-invfix (sipcore) theserver transaction is
>> not terminated when sending a 200, instead a new state "Accepted" is
>> entered.

Please correct me if I am wrong but as per my understanding of draft-invfix,
the change in server transaction's lifetime (state machine) has nothing to
do with basic 2xx handling (i.e. generation + retransmission).

>> However, such retransmission should not delay or alter any timer 
>> belonging to the dialog status (as Session Timers).
Please share the rationale behind this statement? 
Also, does retran-2xx not able to serve the purpose for which session timer
is originally introduced?

****************************************************************************
***********
This e-mail and attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed
above. Any use of the information contained herein in any way (including,
but not limited to, total or partial disclosure, reproduction, or
dissemination) by persons other than the intended recipient's) is
prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!

-----Original Message-----
From: Iñaki Baz Castillo [mailto:[email protected]] 
Sent: Thursday, July 01, 2010 2:35 PM
To: Harbhanu
Cc: [email protected]
Subject: Re: [Sip-implementors] Retrans 2xx handilng - RFC-4028

2010/7/1 Harbhanu <[email protected]>:
> Please elaborate your point, since I got a bit confused from your answer.
>
> Do you mean 'INVITE transaction' here, since ACK anyways doesn't form its
> part (incase of a 2xx response)?

Yes.


> Also, 2xx terminates the server transaction and subsequent retransmissions
> are then handled by TU (or UAS to be precise).

You are right, I meant the TU (the TU handles the retransmissions).
However note that in draft-invfix (sipcore) theserver transaction is
not terminated when sending a 200, instead a new state "Accepted" is
entered.


> Thus, Is it wrong to infer that the 'peer-is-alive' when we get a 2xx
> retransmission of INVITE?

The peer is alive, obviously, as its TU is generating the response
retransmission. However, such retransmission should not delay or alter
any timer belonging to the dialog status (as Session Timers).


-- 
Iñaki Baz Castillo
<[email protected]>


_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to