If the REFER is sent within the dialog of the INVITE then the Contact of
the refer should be the contact address for the dialog. If it is
different, then I believe the effect is to change the contact address
for the dialog.
Thanks,
Paul
SHIV SINGH wrote:
> Hi All,
> I have one query about REFER request.
>
> The Request-URI of a NOTIFY for a REFER, all sent within an established
> INVITE dialog, becomes the Contact header from the REFER instead of remote
> target of the INVITE dialog.
>
> <---INVITE/200/ACK ---> (INVITE contains Contact: X)
> --- REFER---> (REFER contains Contact: Y)
> <--- 202 ---
> <--- NOTIFY --- (Request-URI = Y)
>
> X and Y differ in port number and URI-parameters.
>
>
> RFC 3515
> “2. The REFER Method
> ...
> A REFER request MAY be placed outside the scope of a dialog created
> with an INVITE. REFER creates a dialog, and MAY be Record-Routed,
> hence MUST contain a single Contact header field value. REFERs
> occurring inside an existing dialog MUST follow the Route/Record-
> Route logic of that dialog.”
>
>
> Is there a way to make the Request-URI of the NOTIFY follow the remote
> target of the dialog state?
>
>
>
> Thanks & Regards,
> Shiv
>
>
>
> ---------------------------------
> Bring your gang together. Do your thing. Find your favourite Yahoo! Group.
> _______________________________________________
> 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
