This is addressed by RFC 5057.
The transaction times out and fails, but neither the dialog nor the
invite dialog usage are affected.
Thanks,
Paul
Iñaki Baz Castillo wrote:
> Hi, an easy scenario:
>
> - A calls C through a B2BUA and the call is established with direct
> audio between A and C.
>
> - A sends an in-dialog OPTIONS but B2BUA replies nothing (ignores the
> request) due to a bad implementation or SIP stack.
>
> - After ~32 seconds A decides that the dialog is dead and terminates
> the call (stops sending RTP).
>
>
> In this case A doesn't require to send a BYE as an in-dialog request
> has not been answered by B2BUA so the dialog is clearly broken.
>
> Well A could generate a BYE with a very high CSeq (at least greater
> than the failed OPTIONS) and send it to B2BUA but it's, for sure, not
> required at all.
>
> My question is: could somebody please point me to the exact point in
> RFC 3261 in which this is explained? I need it to document a failure
> in a SIP device. I have no doubt about that the above is 100% correct
> (A is not required to send such BYE), but I have to document it and
> cannot find the exact specification in RFC 3261.
>
> Any reference in RFC 3261 please? Thanks a lot.
>
>
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
