You are right that this is not very explicit.

Kamailio will cancel automatically once one branch connects but if it failed to cancel (meaning other branches connects)
The originiting UAC will have to disconnect the extra calls.

Which is something that is handled properly by most if not all.


On Mon, Apr 20, 2020, 01:31 Ivan Ribakov <i.ribakov@zaleos.net> wrote:
Hi all,

What I’m trying to achieve is to have Kamailio fork an INVITE to multiple endpoints in parallel but only maintain the branch that responds first (first to respond with 200 OK I guess).

I’ve read the TM module documentation on forking (https://www.kamailio.org/docs/modules/stable/modules/tm.html#tm.serial_forking) and as far as I understood a combination of “seturi()” + “append_branch()” + “t_relay()” command calls will allow me to send multiple forked INVITEs in parallel. 

What I couldn't find information about in the documentation (please point me to it in case I missed it) is what controls (if any) do I have over forked requests. Do I need to keep track of the branches myself and cancel others when first succeeds or does Kamailio have some kind of setting for implementing such behaviour?

Thanks,
Ivan
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users