+1 to what Bob says.
In addition, I suggest you read:
* RFC 5057 Multiple Dialog Usages in the Session Initiation Protocol
* RFC 5407 Example Call Flows of Race Conditions in the
Session Initiation Protocol
Thanks,
Paul
On 8/3/11 3:37 PM, Bob Penfield wrote:
> It may
It may just be part of your implementation, but Transactions are independent of
dialogs. There is nothing in RFC 3261 that associates transactions and dialogs
together in a way that the state of the dialog would affect the state of a
pending transaction.
The main point is that the reception of
Hi, Paul,
There is something missing here, please explain it to me.
>They BYE does *not* "terminate all transactions"!
>Every transaction must follow its own state machine, independent of any
>other transaction.
>You MUST attempt to send some final response to any outstanding
>transactions ev
2011/8/3 Brett Tate :
> For reference, RFC 3261 section 15.1.2 recommends sending 487.
>
> "The UAS MUST still respond to any pending requests received for that
> dialog. It is RECOMMENDED that a 487 (Request Terminated) response
> be generated to those pending requests."
Thanks.
--
Iñaki
On 8/3/11 1:48 PM, Iñaki Baz Castillo wrote:
> 2011/8/3 Paul Kyzivat:
>> They BYE does *not* "terminate all transactions"!
>> Every transaction must follow its own state machine, independent of any
>> other transaction.
>>
>> You MUST attempt to send some final response to any outstanding
>> transa
For reference, RFC 3261 section 15.1.2 recommends sending 487.
"The UAS MUST still respond to any pending requests received for that
dialog. It is RECOMMENDED that a 487 (Request Terminated) response
be generated to those pending requests."
> -Original Message-
> From: sip-impl
2011/8/3 Paul Kyzivat :
> They BYE does *not* "terminate all transactions"!
> Every transaction must follow its own state machine, independent of any
> other transaction.
>
> You MUST attempt to send some final response to any outstanding
> transactions even if a BYE transaction has been completed.
On 7/27/11 8:29 AM, Leo Leo wrote:
>>> Interesting, never thought about it. So, if I send a re-INVITE for
>>> which I have no final reply yet and then I send a BYE, should the UAS
>>> reply 200 for the BYE and terminate the remaining re-INVITE
>>> transasction without sending a final response?
>
>>
