Hi Deepak,
In the scenario mentioned the proxy has already responded to CANCEL request with a 200 OK. Ideally it should initiate a CANCEL request downstream before processing reponse for original INVITE. Now if we consider that server is not behaving as expected and is proxying the 2XX response to UAC, UAC should ignore the response and wait for 487. I am not sure about the forked responsequestion. In case forking is initiated by UAC itself it can very well judege from branch parameter of topmost via header.
regards
Rayees
[EMAIL PROTECTED] wrote: -----
To: [email protected]
From: Deepak Kumar Mawandia/BLR/[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
Date: 07/07/2006 10:42AM
Subject: [Sip-implementors] Forked Response or Not?
Hi,
Please refer to the Scenario and answer my query.
NOTE: No 18x response from UAS.
Where Px - Proxy.
UAC <------------->Px<-------------->UAS
F1. ------->INV |
F2<-------100 Trying | ---------->F3 (INVITE)
|<---------F4 (100 Trying)
F5(CANCEL)-------------> |
<-----------F6(2xx for cancel)|
|<----------F7(2xx for Invite)
<----------F8(2xx For Invite)
In the above scenario, when 2xx for Invite (F8), received after 2xx for cancel (F6), at UAC,will it treat as Forked Response.
How will it be handled?Please reply.
Regards,
Deepak
*********************** FSS-Private ***********************
"DISCLAIMER: This message is proprietary to Flextronics Software Systems (FSS) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSS accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
*****FSS-Private *****" DISCLAIMER: This message is proprietary to Flextronics Software Systems Limited (FSS) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSS accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
"DISCLAIMER: This message is proprietary to Flextronics Software
Systems Limited (FSS) and is intended solely for the use of the
individual to whom it is addressed. It may contain privileged or
confidential information and should not be circulated or used for
any purpose other than for what it is intended. If you have received
this message in error, please notify the originator immediately.
If you are not the intended recipient, you are notified that you are
strictly prohibited from using, copying, altering, or disclosing
the contents of this message. FSS accepts no responsibility for
loss or damage arising from the use of the information transmitted
by this email including damage from virus."
_______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
