Hello,
as frequently mentioned, Kamailio is a SIP proxy and not a B2BUA in its core. There are some modules that implement limited B2BUA functions, like rtp_media_server. But I think if you want to go that route you should look into another B2BUA, or as suggested before use one of the other strategies.
Cheers,
Henning
-----Original Message----- From: Benoit Panizzon via sr-users sr-users@lists.kamailio.org Sent: Tuesday, October 15, 2024 2:54 PM To: Benoit Panizzon via sr-users sr-users@lists.kamailio.org Cc: Benoit Panizzon benoit.panizzon@imp.ch Subject: [SR-Users] Re: parallel forking: how to fix 183 g711 then 200 ok g722?
Hi
Parallel forking situation.
Btw, exactly same issue also happens with serial forking.
A => B => C
A invites with g711/g722 B generates early 'ringback' audio g711 durcing 183 B times out, serial forking to C with inital SDP from A B answers with g722
I agree with Daniel, that messages from C contain a different to tag than the ones from B, so one could argue, this is not the same session.
But I doubt the companies building SBC takes such details into account.
In fact, I traced the issue again, our commercial SBC, operating in B2BUA mode is using a different set of ToTag,FromTag on each leg and the ToTag on the A leg are the same despite the ToTag on the B leg being different after forking. So from A's point of view, an additional SDP answer is receivedin the same session, which shall be dropped.
So, still wondering, is there a way so issue a Re-Invite or Update from Kamailio?
Mit freundlichen Grüssen
-Benoît Panizzon-