[sr-dev] new dialog module design: tm trigger for dialog management

[Timo Reimann]

Iñaki Baz Castillo wrote:
> 2010/4/14 Timo Reimann <timo.reimann at 1und1.de>:
>>> It sounds Ok, but for this we must be really sure that, upon receipt
>>> of the first 200, the other pending branches are not immediately
>>> removed so the second 200 (after less than 1-2 seconds) would match an
>>> entry in dialog_out.
>> Agreed. Does the SIP standard specify the time interval for which
>> another branch's 200 response must still conclude another (concurrently
>> confirmed) call? Or is this time interval naturally bound to some
>> standard-provided timer?
>>
>> I've tried to figure that out from RFC 3261 but couldn't find anything.
> 
> 
> Theorically (just RFC 3261) an INVITE transaction is terminated in the
> exact moment a 200 arrives. See RFC 3261 page 128 (figure 5):

[snap]


> However all this text is fixed in this draft:
> 
>   http://tools.ietf.org/html/draft-sparks-sip-invfix-03
> now:
>   http://tools.ietf.org/html/draft-sparks-sipcore-invfix-01
> 
> A new state "Accepted" is added for client and server transaction
> diagram. We care now about the client transaction:

[snap]

> So, TM client transaction should wait for 64xT1 seconds before
> destroying the client transaction after receiving a 200 OK.
> IMHO this should also be the time the entries in dialog_out should
> remain. Do you agree?

Agreed as discussed on the developer meeting on IRC before.


Cheers,

--Timo