[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sip-implementors
Subject:    Re: [Sip-implementors] Request URI, FROM , TO headers in case of Call forwarding
From:       <sunilkumar.verma () wipro ! com>
Date:       2010-08-02 9:48:30
Message-ID: B967EC1195898E499CC20A68744650070BDA061F () BLR-EC-MBX02 ! wipro ! com
[Download RAW message or body]

Hi Vivek,

Only the initial Request should have Request URI and To URI same.
Any modification to the same request can have it different.

It depends upon how the scenario is.
For user A the call is still to User B and user B has forwarded the same
call to User C.
Hence any response coming from User C will be forwarded to User A. 
Hence for user A to understand that the response is for the same call
but is currently inging at some other endpoint the Tag parameter in "To"
header will differ. Hence user A will maintaing two call legs, till cal
is answered.

Modifying the To header will requite Node B to revert back the headers
fro Node A to recognize the call leg.(RFC 2543 compatible).


Regards 
Sunil Verma 
Ph: +919731245000 


-----Original Message-----
From: sip-implementors-bounces@lists.cs.columbia.edu
[mailto:sip-implementors-bounces@lists.cs.columbia.edu] On Behalf Of
Vivek Singla
Sent: Friday, July 30, 2010 9:41 PM
To: sip-implementors@lists.cs.columbia.edu
Subject: [Sip-implementors] Request URI, FROM ,TO headers in case of
Call forwarding

Hi,

In case of call forwarding, I have a question on Request URI and FROM
and TO headers.

When A calls B and B forwards the call to C.

The Invite from A has Request URI of B and FROM of A and TO of B.

Now when B forwards the call to C.

The Invite from B has the Request URI of C but it has the FROM of A and
TO of B.

My question is : The Invite to C, should it have the TO of B here? Is
that correct?


Vivek.
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to this \
message are intended for the exclusive use of the addressee(s) and may contain \
proprietary, confidential or privileged information. If you are not the intended \
recipient, you should not disseminate, distribute or copy this e-mail. Please notify \
the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check \
this email and any attachments for the presence of viruses. The company accepts no \
liability for any damage caused by any virus transmitted by this email. 

www.wipro.com


[prev in list] [next in list] [prev in thread] [next in thread]