Extension with Follow Me Failed to Dial External Number

matthewljensen · June 26, 2023, 5:51am

I’ve got a setup on a system that uses a ringgroup (801) to dial an extension (250) with an external number in the follow me as well as another ring group (800). However, for most of Saturday, calls were not ringing through to the external number in the follow me.

I looked at the logs and came across what appears the be the following pertinent section that I’m not sure how to decipher. The only thing I can thing of is that perhaps a user entered a new number into the follow me and failed to add the trailing #. I was troubleshooting on my phone and could have missed this when I was trying to figure out why calls were failing, and then added it back and then testing to find it was working again. Do the following logs support this theory? Would the whole call trace be helpful? I was thinking the NoOp saying “Should never get here” might be indicative of some type of problem, but user error is generally the most likely culprit.

[2023-06-24 14:42:55] VERBOSE[30022][C-000036dd] res_agi.c: Launched AGI Script /var/lib/asterisk/agi-bin/dialparties.agi

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] res_agi.c: dialparties.agi: Starting New Dialparties.agi

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] res_agi.c: dialparties.agi: Caller ID name is ‘Matthew’ number is ‘xxxxxxxxxx’

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] res_agi.c: dialparties.agi: CW Ignore is:

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] res_agi.c: dialparties.agi: CF Ignore is:

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] res_agi.c: dialparties.agi: CW IN_USE/BUSY is: 1

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] res_agi.c: dialparties.agi: Ringgroup confirm is :

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] res_agi.c: dialparties.agi: Methodology of ring is ‘ringall’

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] res_agi.c: dialparties.agi: Filtered ARG3:

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] res_agi.c: dialparties.agi: Setting default NOANSWER DIALSTATUS since no extensions available

[2023-06-24 14:42:55] VERBOSE[30022][C-000036dd] res_agi.c: dialparties.agi: Starting New Dialparties.agi

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] res_agi.c: dialparties.agi: RVOL_MODE ‘’

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] res_agi.c: dialparties.agi: RVOL is:

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] res_agi.c: dialparties.agi: RVOLPARENT is:

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] res_agi.c: <Local/250@from-internal-00002aed;2>AGI Script dialparties.agi completed, returning 0

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] pbx.c: Executing [s@macro-dial:7] GotoIf(“Local/250@from-internal-00002aed;2”, “0?”) in new stack

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] pbx.c: Executing [s@macro-dial:8] NoOp(“Local/250@from-internal-00002aed;2”, “Returned from dialparties with no extensions to call and DIALSTATUS: NOANSWER”) in new stack

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] pbx.c: Executing [s@macro-dial:9] MacroExit(“Local/250@from-internal-00002aed;2”, “”) in new stack

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] pbx.c: Executing [250@followme-sub:40] Goto(“Local/250@from-internal-00002aed;2”, “nextstep”) in new stack

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] pbx_builtins.c: Goto (followme-sub,250,47)

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] pbx.c: Executing [250@followme-sub:47] Set(“Local/250@from-internal-00002aed;2”, “RingGroupMethod=”) in new stack

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] pbx.c: Executing [250@followme-sub:48] GotoIf(“Local/250@from-internal-00002aed;2”, “1?nodest”) in new stack

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] pbx_builtins.c: Goto (followme-sub,250,56)

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] pbx.c: Executing [250@followme-sub:56] NoOp(“Local/250@from-internal-00002aed;2”, “SKIPPING DEST, CALL CAME FROM Q/RG: 801”) in new stack

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] pbx.c: Executing [250@followme-sub:57] Return(“Local/250@from-internal-00002aed;2”, “”) in new stack

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] pbx.c: Executing [250@followme-check:2] NoOp(“Local/250@from-internal-00002aed;2”, “Should never get here”) in new stack

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] pbx.c: Executing [250@followme-check:3] Hangup(“Local/250@from-internal-00002aed;2”, “”) in new stack

[2023-06-24 14:42:55] VERBOSE[30023][C-000036dd] pbx.c: Spawn extension (followme-check, 250, 3) exited non-zero on ‘Local/250@from-internal-00002aed;2’

dobrosavljevic · June 26, 2023, 4:00pm

If you want the follow-me behavior to be followed on an extension that’s part of a ring group you have to include that extension in the ring group with a # at the end of the extension.

Here is the relevant hint text:

Extensions without a ‘#’ will not ring a user’s Follow-Me. To dial Follow-Me, Queues and other numbers that are not extensions, put a ‘#’ at the end.

matthewljensen · June 26, 2023, 11:28pm

Hi @dobrosavljevic. Thank you for your reply. Yes, I understand that the # is necessary. I’m wondering if a user entered the number and forgot to include it. I’ve already changed it at this point, and I don’t have a way to check if it was set improperly. I’m wondering if the logs indicate that this is what happened and we simply need to do some retraining, or if there is something more problematic going on that might happen again.

dobrosavljevic · June 27, 2023, 2:23am

I don’t think you understand. The # goes behind the extension number inside the Ring Group configuration, otherwise the Ring Group ignores the follow me settings completely, no matter how you have them set up.

matthewljensen · June 27, 2023, 2:30am

You’re right, I did misunderstand where you were referring to. However, our users don’t have access to adjust the ring group settings. The extension (250) in the ring group (801) definitely had the suffixed # during the call failures. Since it had been working, and started working again, with the only changes being that I swapped out my phone number in the follow me settings, and then changed it back a few hours later, I figure it either had to be a misconfigured follow me or some type of as asterisk failure. More and more I’m convinced it was user error, I’m just surprised I wouldn’t have seen and realized it immediately. The asterisk logs were confusing enough, especially the noop saying “should never get here” that I had enough concern to post this and seek clarification.

system · July 28, 2023, 2:30am

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