FollowMe issues with external calls

We do have a dial plan for it, follow me does not work with/without the leading country code. Lucky me need it or not… although I use land lines so little now I could probably just toss the 1 all together. Neither here nor there I suppose.

We also setup an outbound prefix 9 and still no luck. We are quickly approaching completely stumped on our end… =\

Here’s another log… several things seem strange and I wish we could get a third set of eyes looking at it. To my untrained eye it looks like it doensn’t realize the 714326XXXX number is external??

[2012-06-22 09:26:10] VERBOSE[30904] res_agi.c: -- dialparties.agi: Added extension 218 to extension map [2012-06-22 09:26:10] VERBOSE[30904] res_agi.c: -- dialparties.agi: Added extension 1714326XXXX0# to extension map [2012-06-22 09:26:10] VERBOSE[30904] res_agi.c: -- dialparties.agi: Extension 218 cf is disabled [2012-06-22 09:26:10] VERBOSE[30904] res_agi.c: -- dialparties.agi: Extension 1714326XXXX0# cf is disabled [2012-06-22 09:26:10] VERBOSE[30904] res_agi.c: -- dialparties.agi: Extension 218 do not disturb is disabled [2012-06-22 09:26:10] VERBOSE[30904] res_agi.c: -- dialparties.agi: dbset CALLTRACE/218 to 714310XXXX [2012-06-22 09:26:10] VERBOSE[30904] res_agi.c: -- dialparties.agi: Filtered ARG3: 218-1714326XXXX0 [2012-06-22 09:26:10] VERBOSE[30904] res_agi.c: -- <DAHDI/i1/714310XXXX-43c>AGI Script dialparties.agi completed, returning 0 [2012-06-22 09:26:10] VERBOSE[30904] pbx.c: -- Executing [s@macro-dial:7] Dial("DAHDI/i1/714310XXXX-43c", "SIP/218&Local/1714326XXXX0@from-internal/n,60,trIM(auto-blkvm)") in new stack [2012-06-22 09:26:10] VERBOSE[30904] netsock2.c: == Using SIP RTP TOS bits 184 [2012-06-22 09:26:10] VERBOSE[30904] netsock2.c: == Using SIP RTP CoS mark 5 [2012-06-22 09:26:10] VERBOSE[30904] app_dial.c: -- Called SIP/218 [2012-06-22 09:26:10] VERBOSE[30904] app_dial.c: -- Called Local/1714326XXXX0@from-internal/n [2012-06-22 09:26:10] VERBOSE[30904] app_dial.c: -- Connected line update to DAHDI/i1/714310XXXX-43c prevented. [2012-06-22 09:26:10] VERBOSE[30906] pbx.c: -- Executing [1714326XXXX0@from-internal:1] ResetCDR("Local/1714326XXXX0@from-internal-b79f;2", "") in new stack [2012-06-22 09:26:10] VERBOSE[30906] pbx.c: -- Executing [1714326XXXX0@from-internal:2] NoCDR("Local/1714326XXXX0@from-internal-b79f;2", "") in new stack [2012-06-22 09:26:10] VERBOSE[30906] pbx.c: -- Executing [1714326XXXX0@from-internal:3] Progress("Local/1714326XXXX0@from-internal-b79f;2", "") in new stack [2012-06-22 09:26:10] VERBOSE[30904] app_dial.c: -- Local/1714326XXXX0@from-internal-b79f;1 is making progress passing it to DAHDI/i1/714310XXXX-43c [2012-06-22 09:26:10] VERBOSE[30906] pbx.c: -- Executing [1714326XXXX0@from-internal:4] Wait("Local/1714326XXXX0@from-internal-b79f;2", "1") in new stack [2012-06-22 09:26:10] VERBOSE[30904] app_dial.c: -- SIP/218-00000a80 is ringing [2012-06-22 09:26:11] VERBOSE[30906] pbx.c: -- Executing [1714326XXXX0@from-internal:5] Progress("Local/1714326XXXX0@from-internal-b79f;2", "") in new stack [2012-06-22 09:26:11] VERBOSE[30906] pbx.c: -- Executing [1714326XXXX0@from-internal:6] Playback("Local/1714326XXXX0@from-internal-b79f;2", "silence/1&cannot-complete-as-dialed&check-number-dial-again,noanswer") in new stack [2012-06-22 09:26:11] VERBOSE[30906] file.c: -- <Local/1714326XXXX0@from-internal-b79f;2> Playing 'silence/1.slin' (language 'en')

Also note this interesting bit which came right after the above:

[2012-06-22 09:26:11] VERBOSE[30904] app_dial.c: -- Local/1714326XXXX@from-internal-b79f;1 is making progress passing it to DAHDI/i1/714310XXXX-43c [2012-06-22 09:26:12] VERBOSE[30906] file.c: -- <Local/1714326XXXX@from-internal-b79f;2> Playing 'cannot-complete-as-dialed.gsm' (language 'en') [2012-06-22 09:26:14] VERBOSE[30906] file.c: -- <Local/1714326XXXX@from-internal-b79f;2> Playing 'check-number-dial-again.gsm' (language 'en')

I’m out of my league here… I see CF is disabled for the extension. The Follow Me box is check marked in the user panel correct? And the Call Forward Ring time is set to Default?

Yeah my IT director and I are past the point of scratching heads. He tested call forwarding on another line and had no success. Can you post your SIP settings since yours is working? I’m at a loss and think it’s time to go no-fun style and just compare side by side functional to not, you know?

I really appreciate your help by the way.

Well I figured it out finally many thanks to Jerry for keeping me looking and helping out!

I found out by reading tons of posts that there’s a setting to force/not force the CID on outbound calls, everyone was saying to check it and change it one or another. Well on the particular version of FreePBX (2.10.0.8) we’re running it would seem that setting isn’t where most people suggested but I did find it!

Under the individual follow-me settings is a group “Change External CID Configuration” I changed the Mode to Fixed CID value and set that to our main phone # listed as the outbound CID on our trunk.

Calls are forwarding fine and follow me is working now. Hope this helps anyone who has a similar issue to what I’ve had the fun of wading through!

That setting works in combination with the Trunk. In my case I left the Change External CID Configuration set to Default the I Allow any CID on the CID Options in the truck (needed because not all of our extensions have the same CID). Just curious, what is your trunk set to since you fixed it by forcing the caller ID on the other screen?

The trunk CID? 7148292600. I forced the CID on the individual follow-me entries to match that.

Perhaps the difference. On mine I allowed the truck to accept the caller ID being passed by the other settings rather than forced.

(you may want to edit your phone number out of your post)

Nah it’s our forward facing number anyway you can see it on any company website.

Thanks for keeping an eye out though. =D

Yeah I’m thinking there’s probably a setting on the individual follow-me to not try to use their own and just inherit the trunks but as far as I’m concerned it works and if it ain’t broke don’t fix it, lol.

I have the same exact issue you described early on in your posts digitalbravo, and I followed what you wrote as part of your solution, but no dice. If I dial an extension from another extension, the follow-me works as advertised. If, however, an external call comes into my extension, after the number or rings prescribed in the settings it goes right to voicemail.

Not really sure how to read the logs, so I won’t bore you with posting the whole thing here, but I did see two lines worth posting:

[2012-08-16 12:29:01] VERBOSE[-1] res_agi.c: – dialparties.agi: Extension 602 cf is disabled
[2012-08-16 12:29:01] VERBOSE[-1] res_agi.c: – dialparties.agi: Extension 1951xxxxxxx# cf is disabled

I get from those two lines that Call Forwarding is disabled. Not really sure what I’m missing. If anyone has any insight, I’d really appreciate it.

Thanks!

– Ed

Ok,

The reason I was not able to make the calls coming in from the outside call forward to any of the setup methods (ring group, follow-me, *72 call fwd, etc.) was because ALL of my outbound routes had a qualifier attached to them specifying certain extension and/or patterns could only dial on those outbound routes.

When the external call tried to call, it didn’t match any of the patterns, so the call could not be completed as dialed.

I created a new outbound route with no matching pattern requirement, and I put it at the very end of the outbound routes - a route of last resort, if you will.

Voila! Call forwarding of external calls works just as advertised. I hope this might help anyone who’s been stuck for a few days like me.

– Ed

digitalbravo thank you a lot you saved my life :slight_smile: it take so long to read all your post but i found the solution finally :slight_smile: