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
RFC 3261.
Anyhow, event there is parallel forking to many branches, only one gets
a
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 t
Hello,
On 23/02/2017 12:47, Kjeld Flarup wrote:
> I ran into the same problem. Just that I may have more than two parallel
> forks.
> 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 ot
I ran into the same problem. Just that I may have more than two parallel
forks.
Am I right, that I need a kamailio instance for each fork.
--
View this message in context:
http://sip-router.1086192.n5.nabble.com/Parallel-Forking-with-Different-Call-Id-tp150146p156310.html
Sent from the Users ma
Thanks Daniel,
Both are good ideas and I will try and see how it goes. I just wanted to
confirm that there is no way we can modify CallID of branches via script.
This is fine too.
Thanks again,
Best Regards,
Sammy
On Jul 6, 2016 06:11, "Daniel-Constantin Mierla" wrote:
> Hello,
>
> maybe you ca
Hello,
maybe you can loop through a 2nd instance of kamailio (can be same
server, different port) that has topoh enabled.
Otherwise, if the gateway is matching on full r-uri, you can try to add
some extra uri params, which are not relevant for target number.
Cheers,
Daniel
On 05/07/16 21:54, S
