[OpenSIPS-Users] serialize_branches() and timeouts

[Alexander Kogan]

Hello,

I've got such a call flow:

Client      OpenSIPS
|--INVITE-->|
|<--100-----| Vendor1
|           |--INVITE-->|
|           |--INVITE-->|
|           |--INVITE-->|
|           |           |           Vendor2
| |--INVITE------------- >|
| |<--100-----------------|
| |<--180-----------------|
|<--180-----|                       |
|           |<--200-----------------|
|<--200-----|                       |
|           |                       |
|           |<--200-----|           |
|<--200-----|        |
|           |           |           |

The first branch was timed out and we switched up to the next one. A bit 
later we received 200 OK from the first one. The question is - how to 
avoid passing 200 to the first leg? drop() doesn't work for final 
responses. I also can't use t_cancel_branches() because it works in 
onreply_route only which is not called in case of timeout....

-- 

Best regards,
Alexander Kogan,
Director of R&D
5g Future
http://5gfuture.com