2010/3/12 Paul Kyzivat :
> This is addressed by RFC 5057.
> The transaction times out and fails, but neither the dialog nor the invite
> dialog usage are affected.
Thanks!
--
Iñaki Baz Castillo
___
Sip-implementors mailing list
Sip-implementors@lists
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 bet
2010/3/12 Saúl Ibarra :
> Hi Iñaki,
>
> On Fri, Mar 12, 2010 at 5:39 PM, Iñaki Baz Castillo wrote:
>> 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 somebod
Iñaki Baz Castillo wrote:
> Any reference in RFC 3261 please? Thanks a lot.
This could help:
12.2.1.2 Processing the Responses
... A UAC SHOULD also terminate a dialog if no response at all is
received for the request (the client transaction would inform the TU
about the timeout.)
For INVITE in
Hi Iñaki,
On Fri, Mar 12, 2010 at 5:39 PM, 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 implement
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 term
