Outbound Routes Dial Plans not formatting correctly

[jarvisswope (computerguy2907)]

When creating an outbound route and adding in the Dial Patterns I get the following when selecting
anything

• 7 digit
  *10 digit
  *emergency

Upgraded from FreePBX 14 to 15

current version is FreePBX 15.0.16.75

@lgaetz advised me to do the following. Not luck. I even did a backup and restore to a fresh install and had the same outcome.

lgaetzLorne GaetzSangoma

8d

We don’t have any other reports of this issue. You might try reinstalling core and framework:

 fwconsole ma downloadinstall framework core --force

and you might try purging browser cache (ctrl-F5 usually does it) or trying from a different browser.

Outbound Routes

When creating an outbound route and adding in the Dial Patterns I get the following when selecting anything 7 digit *10 digit *emergency Upgraded from FreePBX 14 to 15 current version is FreePBX 15.0.16.75 [image]

[Stewart1 (Stewart)]

Why are you using the Dial patterns wizards at all? For most cases, just type in the patterns you want.

The wizards are useful in two cases:

1. Your provider requires dialing local calls in a format different from other domestic calls. For example, local calls must be dialed as 7 digits; long distance as 11.
2. Your provider has unlimited local calling, but you use a different (cheaper) trunk for long distance.

If either of these apply to you, it’s possible that something is going wrong with the lookup on localcallingguide.com. What NPA and NXX did you enter?

[lgaetz (Lorne Gaetz)]

What is the output of:

fwconsole setting  ENABLEOLDDIALPATTERNS

[jarvisswope (computerguy2907)]

[root@freepbx ~]# fwconsole setting ENABLEOLDDIALPATTERNS
Setting of “ENABLEOLDDIALPATTERNS” is (bool)[true]

[lgaetz (Lorne Gaetz)]

You have enabled “Enable The Old Style FreePBX Dial Patterns Textarea” in Advanced Settings, a non-default setting. It appears that the dialplan rules wizard breaks when combined with this setting. Resetting the value in advanced settings, even if only temporarily, will resolve.

Please file a ticket with your findings, but know it’s like to get a low priority. It’s possible a community coder will submit a PR to resolve.

[jarvisswope (computerguy2907)]

That did it. I am not sure how that got changed it it is working as expected.