[OpenSIPS-Devel] Limitations of dialog module

[Bogdan-Andrei Iancu]

Iñaki Baz Castillo wrote:
> 2009/8/4 Bogdan-Andrei Iancu <bogdan at voice-system.ro>:
>   
>>> That makes sense but, what would occur in the exotice RFC3261 case in
>>> which  two (or more) 200 OK replies are received at the same time?
>>> AFAIK for now OpenSIPS terminates the INVITE transaction (not 100%
>>> true since it matches the following ACK) when the first 200 arrives,
>>> so the second 200 is bypassed stateless to the UAC.
>>>
>>>       
>> Not true.
>>
>> After the first 200 OK, the transaction is completed and moved in wait state
>> to catch any other delayed replies. If more 200 OK are  received in the mean
>> while, all of them will be forwarded statefully  to the caller and let the
>> caller to decide which to accept and which to deny.
>>     
>
> Ok, I expected this behaviour since OpenSIPS doesn't implement the RFC
> 3261 strictly (when the 200 arrives it doesn't terminate the
> transaction, instead the next ACK is matched against the same *but
> different* transaction).
>
>
>   
>> Of course, if there is a very late 200 OK and the transaction was already
>> deleted (the wait state is by default 5 secs) the stateless 200 OK will be
>> dropped.
>>     
>
> Dropped? or stateless forwarded?
>   
In 1.5 there was a stateless / statefull checking add - if you do not 
statefully relay any requests (based on auto script detection), the core 
will drop all stateless replies also. See 
http://www.opensips.org/Main/Ver150#toc4

Regards,
Bogdan