No ring back on follow me calls

[Doug Mattingly]

I have set up follow-me call routing which includes external cell phone numbers on some extensions. An external caller does not hear any ring back while the phones are ringing when follow-me is enabled. When calling direct to the extension from another extension on the same system, the caller can hear the ring back. Any idea how to fix this?
Thank you in advance.

 

[hailthemelody]

Can you send a trace? Likely "early media" is not being sent.

 

[Doug Mattingly]

I haven't set up any way to do an external sip trace yet although I'm planning to set up homer. In the meantime, is there something instrinsic in fusionpbx that would help? My research indicated an early media issue as well. Are there any specific settings I should check regarding early media?

 

[hailthemelody]

Let us know. You could also try tshark (terminal-based wireshark), it's fairly easy to get going with that (apt-get install tshark on Debian family)

 

[Doug Mattingly]

I realized I can take a packet capture from my router and view on wireshark. I found that the internal calls produce a sip status 180 ringing whereas the external calls produce a sip status 183 session progress. Does this help?

 

[c0reM]

It's easiest if you post the full SIP trace so we can see the call flow. The best utility for this is sngrep on the server. Google sngrep as you need to add the sources in sources.list then you can do apt update and apt install sngrep.

Run that and post the full trace and somebody can probably tell you more from that.

 

[Doug Mattingly]

Here is the full trace from the packet capture with public ip addresses redacted. The fusionpbx is behind nat and has private ip 192.168.97.201. The extension 1411 is being called and is routing the call to an external cell phone and another extension on a different network. Everything works except that the caller does not hear ring back during the ringing process.

 

[KonradSC]

I'm a little late to the party, but I just ran across the same thing. I inserted this into the dialplan to fix the issue.

<action application="set" data="ringback=%(2000,4000,440.0,480.0)" />

You can insert it in the public context under inbound routes and that will cover all domains. Or you can insert it under dialplan manager for each domain that is broken. I put mine under the "variables" step for the particular domain that had the issue. My ring back broke when I enabled Fax Detection.

 

[DigitalDaz]

One thing I noticed in that trace was UDP was getting fragged, this would likely be happening on the 183 because that would be carrying an SDP. I have definitely had this myself before when the 183 gets fragged and you get no ringback. So reduce the codecs or switch to TCP

 

[Koketso Mabuse]

Hi there, I am a newbie and need a bit of clarity on where to insert that. Tried Advanced, Variable ... could not find where to insert that.

Regards

I'm a little late to the party, but I just ran across the same thing. I inserted this into the dialplan to fix the issue.

<action application="set" data="ringback=%(2000,4000,440.0,480.0)" />

You can insert it in the public context under inbound routes and that will cover all domains. Or you can insert it under dialplan manager for each domain that is broken. I put mine under the "variables" step for the particular domain that had the issue. My ring back broke when I enabled Fax Detection.

 

[KonradSC]

Go to Dialplan -> Dialplan Manager.
Edit Variables (order #20)

Tag: action
Type: set
Data: ringback=%(2000,4000,440.0,480.0)
Inline: true

 

[s2svoip]

this is interesting, I had to add this today because I noticed if I enabled follow me with 2 extensions in destination then nether would ring when I called the extension, when I ended the call both ext in the destinations would show a missed call - very odd - why I would need to add this now i've no idea, can anyone explain why this would suddenly be needed ? what does the additional dialplan entry do ?