Change in follow-me behavior

Hi everyone

I’m using freepbx 16

I used to have follow me list for an extension with one external number and the extension itself to ring, so when someone call the extension for example 102, the ip phone will ring AND the external number “Mobile phone for the same person” will ring simultaneously … And whichever been answered the other one will hangup

The external number will be in follow-me list ending with #… So it use one of the trunks to ring that number

This help us to reach the one who we call faster either they are in the office or outside the office

Couple of weeks ago, I upgraded all the modules, including core, follow-me module… And discovered a really annoying issues

1- if we call an extension, the call will forward to the external number only! Even though the actual extension is included in the follow-me list! I have to enable call confirmation so that both the extension and the external number will ring in the same time, the problem now is they have to press 1 to answer the call! Answering the call from an external number will not stop the ip phone from ringing and will not actually answer the call, the receiver should press 1 to receive it… Which is it not fast and make the process one step longer

2- if I don’t enable “call confirmation” the music on hold will not work as the call will be forwarded to the external number only and the caller will hear the normal ringing sound from the trunk. Before the update, the caller can hear the music on hold until the receiver answer the phone, whether it’s an internal sip phone or external #.

3- if a call came from internal extension to another extension with follow-me list and call confirmation enabled, the receiver will hear the call confirmation anouncement normally, but when an external call received and goes to an extension with follow-me enabled and contains external number, the receiver will receive the call but can’t hear the call confirmation anouncement, whether it’s the default or any other anouncement… The receiver should press 1 to answer the call, and there is no anouncement tell them to do so.

I need help by downgrade the required modules, or maybe the developers with all thanks can provide a solution

I tried to install Freepbx 17 in Debian system, and it acts the same as 16, I guess it’s an update issue or something

Thank you everyone for the great work

My guess is that something is forcing an ‘ANSWER’ on the outbound channel before the call is actually answered by the mobile user. A call trace will show it, but I can’t think of what might cause it. I wouldn’t expect a simple module upgrade to have made that change. Share a call trace of a problem call via pastebin
https://sangomakb.atlassian.net/wiki/spaces/SS/pages/31162494/Providing+Great+Debug#Asterisk-Logs---Part-II

2 Likes

As @lgaetz says, but before making the test call, turn on pjsip logger so we can see the responses from the trunking provider. To do this, at the Asterisk command prompt type
pjsip set logger on
assuming it’s a pjsip trunk. Otherwise, please provide info about the outbound trunk.

https://pastebin.freepbx.org/view/d94f2088

here is a call trace for a call from internal extension to 102

Thank you

On line 604, the trunk 0571312333 ‘answered’ the call within the same second it was placed.
Possibly, pjsip logger will show more info.

Hi Stewart1,

I set the logger on as you said in the last replay

pjsip set logger on

before I get the call trace

is there another way to get pjsip logger than this ?

When you typed that command, you should have seen
pjsip logging enabled
Note that this gets turned off by Apply Config or any other reload or restart.

1 Like

I found the problem, as you said, there is ‘answered’ signal sent from the trunk immediately after placing a call

I’m using LTE to VoIP module, apparently there is settings changed and let it send an answer signal soon as receive the request, I changed that and it’s fixed now

Thank you Stewart, and Lorne Gaetz :rose::rose:

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.