FusionPBX never receives the BYE about dsiprouter HOT 8 CLOSED

I'm not getting a proper bye / ok from Freepbx / Asterisk in Dsip 0.51
After the Bye I get the following:
SIP/2.0 481 Call leg/transaction does not exist

One of the callers line stays connected as a result (depends on who hangs up first.

This does not happen when routing calls directly to FRreePBX, only when routing through dSip then FreePBX.

from dsiprouter.

Do you get this when the pbx extension hangs up first?

Mat

from dsiprouter.

Hey @marc8lange I just tested it with FreePBX 14 / Asterisk 13.22 and the BYE worked without an issue when the carrier sent the BYE.

But, the BYE doesn't happen when the SIP client send it. I just fixed it...actually it was commented out for testing another use case and we didn't catch it during our final testing. I will fix it and rebuild 0.51. But, you can fix your install by doing the following

1. login to the host
2. vi /etc/kamailio/kamailio.cfg
3. Goto line 726 and remove the # sign
4. Save the file
5. Execute systemctl restart kamailio
6. Try the call again

from dsiprouter.

Hello,

Applied the very clear instructions to amend kamailio.cfg (thank you).

Now, when the carried goes bye, the ack, bye, and 200ok sequence works well. However when the PBX extensions hangs up first, I still get the ack - bye - 403 Forbidden - Bye - and 481 Call leg does not exist.

Again tried to bypass dsip and hangups occur as predicted no matter who hangs up first.

I confirmed the changed stuck in kamailio.cfg, and restarted kamailio a few times for good measure.

You'll notice in the sngrep, the carrier stayed connected to dsip for another 20 seconds after the 403 forbidden...until I hung up manually the carrier. Sorry...purposely not showing IPs and details here.

from dsiprouter.

Side note, Add this to bottom of .bashrc in /root
export NCURSES_NO_UTF8_ACS=1

from dsiprouter.

Side note, Add this to bottom of .bashrc in /root
export NCURSES_NO_UTF8_ACS=1

done after googling it...but still not entirely sure that I've achieved a different display in putty?

from dsiprouter.

from dsiprouter.

@marc8lange

It looks like your carrier doesn't like how dSIPRouter forwards the BYE. Some carriers are picky. We are using Flowroute without an issue. What carrier are you using?

In regards to export NCURSES_NO_UTF8_ACS=1, I will create an issue and add that into the build. I've always wondered people get letters when using putty :-)

from dsiprouter.