Hi Denys and A Happy New Year,
Let me check the pcap you PM'ed me.
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 12/22/21 10:18 AM, Denys Pozniak wrote:
Hello!
Yes, that's right, the documentation did not indicate that TH should
generate different Call-IDs for different incoming branches...
But now there is still an open question about the work of the B2B module.
It just generates separate Call-IDs, but does not forward the SIP CANCEL
message (I
Hi Denys,
Doing TH with dialog does not provide you with different call-ids for
each branch. The TH (or changing) is done between in (caller) and out
(callee) sides. There is no doc stating that each branch will get a
different Call-ID (I hope :D).
Best regards,
Bogdan-Andrei Iancu
Hello!
Any update?
вт, 14 дек. 2021 г. в 14:13, Denys Pozniak :
> Hello!
>
> Bogdan,
> I tested the combination of dialog + TH modules and found out that this
> also does not work correctly if the incoming call was forked.
> Outgoing legs have the same Call-ID and tag, although I would expect
Hello!
Bogdan,
I tested the combination of dialog + TH modules and found out that this
also does not work correctly if the incoming call was forked.
Outgoing legs have the same Call-ID and tag, although I would expect them
to be different.
The configuration is exactly the same as in the
Hi Denys,
Before diving into the B2B dark corners, I would strongly suggest to use
OpenSIPS with dialog + topology hiding modules, rather than B2B. The B2B
is not so friendly with parallel forking.
And as time as you only need TH, dialog + TH is be best way to do it.
Best regards,
Hello!
Sorry, but I need help with this issue.
вт, 7 сент. 2021 г. в 14:14, Denys Pozniak :
> Adding a scheme of the current call-flow scenario maybe it is not
> completely clear from the previous message:
>
> FreeSWITCH --(1-call)--> Fork Proxy --(N-branches)--> SEMS --(N-calls)-->
> Edge Proxy
Adding a scheme of the current call-flow scenario maybe it is not
completely clear from the previous message:
FreeSWITCH --(1-call)--> Fork Proxy --(N-branches)--> SEMS --(N-calls)-->
Edge Proxy > N-devices
вт, 7 сент. 2021 г. в 12:57, Denys Pozniak :
> Hello!
>
> Our service delivery