Hi,
In this case there will be no early dialog formation at UAC side,
since proxy doesn't forward the response till it gets 200 OK or 6xx
response.
Hence there is no question of UAC terminating early dialogs.
Rgds,
Manju
****************************************************************************
***********
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: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sigrid Thijs
Sent: Tuesday, April 04, 2006 3:53 PM
To: [email protected]
Subject: [Sip-implementors] Forking: early dialog termination
Hi,
I'm sorry if this has been asked before, but I haven't found a real
answer to this question.
According to RFC 3261:
If the forwarded response was a final response, the proxy MUST
generate a CANCEL request for all pending client transactions
associated with this response context.
What is the desired behavior for the UAC?
- non-2xx response: all early dialogs are considered terminated
- 2xx response: early dialogs are terminated 64*T1 seconds after the
reception of the first 2xx response
Does the UAC need to terminate these early dialogs by sending a BYE
request, or should it just discard the early dialogs?
--
kind regards,
Sigrid Thijs
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
