The billing system should use the callid+from-tag+to-tag to match the
invite with the bye. Relying only on callid can result on other issues
over the times. Forking through a proxy is quite common and specified in
Anyhow, event there is parallel forking to many branches, only one gets
a 200ok -- once one does it, the other branches are cancelled by the proxy.
On 24/02/2017 15:00, Kjeld Flarup wrote:
Thanks for confirming Daniel
My issue is, that the call will pass a system with billing, which uses
the callid, to keep track of the calls.
I can live with running multiple instances in this project.
I also have a Asterisk in my system, which I use to generate new
callid's. I would like to take that one out of the loop, an replace it
with a Kamailio. But if I cannot branch and get different call id's on
the branches with just one kamailio instance, then it may just
introduce more trouble.
Med venlig hilsen / Best regards
Kjeld Flarup (Christensen) M.Sc E.E, Teknisk chef
Viptel ApS, Hammershusvej 16C, DK-7400 Herning
Telefon: +45 46949949, Telefax: +45 46949950,http://viptel.dk
On 2017-02-23 20:54, Daniel-Constantin Mierla wrote:
On 23/02/2017 12:47, Kjeld Flarup wrote:
I ran into the same problem. Just that I may have
more than two
Am I right, that I need a kamailio instance for each fork.
what kind of problem? The next hop is matching on R-URI or it requires
different Call-ID because of other reasons?
And indeed, if you need different call-id, I think you would need
different kamailios with topos and different secret parameter for them.
You can run them on the same system, just using different port.
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list