Calls to voicemail ( * + ext numb) returing "Your call cannot be completed as dialed.." with Routes module

Commercial Modules
1

How do I know this?

Started getting complaints on this maybe one-two weeks ago.

On the extensions which had already routes selected, they are affected, but with newer extensions which have not had any routes picked for them, they can dial * + extension number.

On one extension, I started testing, and selecting routes. That is when it could no longer dial to voicemail. Selecting 1, all, or none selected, it results in being able to no longer to dial to voicemail.

Is this a reported bug?

2

Need a call trace:
https://wiki.freepbx.org/display/SUP/Providing+Great+Debug#ProvidingGreatDebug-AsteriskLogs

3

This is all I see:

Executing [*103@from-internal:3] GotoIf(“SIP/299-0000020b”, “0?from-internal,1”) in new stack

-- Executing [*103@from-internal:4] Goto("SIP/299-0000020b", "bad-number,s,1") in new stack

-- Goto (bad-number,s,1)

-- Executing [s@bad-number:1] Goto("SIP/299-0000020b", "11,1") in new stack

-- Goto (bad-number,11,1)

-- Executing [11@bad-number:1] ResetCDR("SIP/299-0000020b", "") in new stack

-- Executing [11@bad-number:2] NoCDR("SIP/299-0000020b", "") in new stack

-- Executing [11@bad-number:3] Progress("SIP/299-0000020b", "") in new stack

-- Executing [11@bad-number:4] Wait("SIP/299-0000020b", "1") in new stack

-- Executing [11@bad-number:5] Playback("SIP/299-0000020b", "silence/1&cannot-complete-as-dialed&check-number-dial-again,noanswer") in new stack

-- <SIP/299-0000020b> Playing 'silence/1.ulaw' (language 'en')

-- <SIP/299-0000020b> Playing 'cannot-complete-as-dialed.ulaw' (language 'en')

– <SIP/299-0000020b> Playing ‘check-number-dial-again.ulaw’ (language ‘en’)

4

Forgot to mention version of FreePBX: FreePBX 13.0.195.12 , and Extension Routes 13.0.10.7

5

Your direct dial to vm feature code is conflicting with the Contact Manger speed dial feature code. I usually change the speed dial feature code to **10

1 Like
6

Thanks for that, and super fast response. Maybe that is worth a caveat/warning in the Wiki?

7

Not to rain on the parade, because the idea is good, but would **10 interfere with any extensions that are 10X. with call pickup?

Probably need to just change it to something that won’t conflict with other feature codes and possible extension ranges.

Ran into the same issue when I had a 21X extension with *2111, for example, because instead of dialing directly to voicemail it attempted to toggle FollowMe for extension 11 because *21 is the FollowMe toggle by default.

2 Likes
8

You’re right, there are prob better choices to fix.

9

Well it’s the right path. Just like with any deployment, you have to make sure the feature codes and special dial codes don’t interfere with each other and the extensions. In my case I made the voicemail feature *5.

10

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