I tried to translate the picture in notepad. I hope, it is received as
intended. Please find below.

A
side
B side
                                    ______________
---------------------------------> |     B       |
Invite                             |
|-------------------------------> Invite
                                   |
|<------------------------------ 100 Trying
<--------------------------------- |             |     18x without contact
header
100 Trying                         |     2
|<------------------------------
                                   |             |
<--------------------------------- |             |
18x with contact                   |             |
---------------------------------->|     B
|---------------------------------> ????????
BYE                                |             |


18x from B side received without contact header. 18x response has "To tag"
and without Record Route.

Thanks,
kumar



On Mon, Aug 17, 2009 at 11:24 PM, Vikram Chhibber <[email protected]
> wrote:

> We can not see the attachment. A UAC should have no problem processing
> a unreliable 18x response without Contact as it is optional.
> It is definitely needed in a reliable 18x as without it, a UAC can not
> construct a PRACK request. In this case, 18x will timeout and the
> early dialog will be terminated.
> On Wed, Aug 12, 2009 at 3:03 AM, raikkme rrrrr<[email protected]>
> wrote:
> > What should be the behaviour, in case 18X response is received with no
> > Contact header for the below case?
> >
> > Please refer the attached document for sample scenario.
> >
> > The entity is behaving as a B2B, where BYE is received from one side.
> >
> > Thanks,
> > kumar
> >
> > _______________________________________________
> > 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

Reply via email to