I think that will work, yes.
On Jan 12, 2015, at 10:22 AM, John Nash <john.nash778@gmail.com> wrote:
Looks like a good work around. But if we have only one instance of freeswitch, can different profile be used (Listening on different port)?
On Mon, Jan 12, 2015 at 8:22 PM, Grant Bagdasarian <gb@cm.nl <mailto:gb@cm.nl>> wrote: I’ve fought with the 482 Request merged response for a long time in Freeswitch, and lost.
I ended up sending any subsequent INVITEs to another instance of Freeswitch.
From: freeswitch-users-bounces@lists.freeswitch.org <mailto:freeswitch-users-bounces@lists.freeswitch.org> [mailto:freeswitch-users-bounces@lists.freeswitch.org <mailto:freeswitch-users-bounces@lists.freeswitch.org>] On Behalf Of John Nash Sent: Monday, January 12, 2015 1:10 PM To: freeswitch-users@lists.freeswitch.org <mailto:freeswitch-users@lists.freeswitch.org> Subject: [Freeswitch-users] Freeswitch + serial forking at opensips
Hello,
I am facing an issue when using opensips to serial fork Invites to some SIP gateways and using freeswitch in the middle as b2bua to send calls. That means if first Invite fails opensips will pick next available gateway and append branch to send this again to freeswitch.
But I have noticed when first gateway sends a failed response (and freeswitch log shows call destroyed) and second invite is sent (Same call id, cseq but different branch tag) , freeswitch seem to have old transaction alive and sends 482 Request merged response.
I saw in mail archives that it was discussed few years back but there was no conclusion.
Is there a reason freeswitch keeps transaction alive (for 4 seconds I think) even if it received "ACK" for failed response?
Regards
John