Hope that you have verified that BYE is received on the correct call-leg of
B2B UA. Suspect that such issue can happen if BYE is given on the other
UAS(INVITE) side of B2BUA.

-Harbhanu

On Mon, Jun 4, 2012 at 12:36 PM, Tarun2 Gupta <tarun2.gu...@aricent.com>wrote:

> Hi All
>
> Consider the following scenario:
>
>
> UA 1                             B2BUA                         UA2
> Invite (From tag F1)
> --------------------------------->
>                                    Invite (From tag F2)
>                                    ---------------------------------->
>                                    200 OK (From tag F2, To tag F2)
>                                    <---------------------------------
> 200 OK (From tag F1,
>              To tag F3)
> <-------------------------------
> ACK (From tag F1,
>          To tag F3)
> ------------------------------->
>                                    ACK (From tag F2,
>                                                 To tag F2)
>                                    ---------------------------------->
>
>                        RTP
> <------------------------------------------------------------------>
>
>                                          BYE (From tag F2, To tag F2,
>                                                To and From headers
> reversed)
>                                    <----------------------------------
>                                            481
>                                    ---------------------------------->
>
>
> As per Section 19.3 of RFC 3261,
> "When a tag is generated by a UA for insertion into a request or response,
> it MUST be globally unique and
> cryptographically random with at least 32 bits of randomness"
>
> Now, is the B2BUA right in rejecting the BYE with a 481. Can the 200 ok
> from UA2 have same To and From tags? What should the B2BUA do:
>
>  1.  On receiving the 200 OK?
>  2.  On receiving the BYE?
>
> Regards,
> Tarun Gupta
> Aricent
>
>
>
>
>
>
> ===============================================================================
> Please refer to http://www.aricent.com/legal/email_disclaimer.html
> for important disclosures regarding this electronic communication.
>
> ===============================================================================
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to