Dialing Plan Logic Sanity Check

Dashrender

Without testing what you have might work, or you might need

Prefix = 8 and match pattern = NXXXXXXXXX because the 8 might already be stripped out by the Prefix column when moving onto the second column of match pattern.

Dashrender

I just tested this on FreePBX

This worked

This failed

As I suspected, the 8 in the match failed because the prefix already stripped that out before sending the remaining digits to the match pattern.

PenguinWrangler

When I read the title of this post I read it as "Dating Plan Logic Sanity Check"

EddieJennings

@dashrender said in Dialing Plan Logic Sanity Check:

I just tested this on FreePBX

This worked

This failed

As I suspected, the 8 in the match failed because the prefix already stripped that out before sending the remaining digits to the match pattern.

I'll try it out tomorrow. Had zero time to work, test, and learn today.

EddieJennings

@dashrender said in Dialing Plan Logic Sanity Check:

I just tested this on FreePBX

This worked

This failed

As I suspected, the 8 in the match failed because the prefix already stripped that out before sending the remaining digits to the match pattern.

I was able to replicate the results. This means (from the Prefix definition) "The dialed number" must mean the prefix number. So perhaps this is what FreePBX does.

User dials 8777705554321
FreePBX checks against first dial pattern (NXXXXXXXXX) - false
FreePBX checks against the second dial pattern.

Checks to see if the prefix number is at the beginning of the dialed number - true
Removes the prefix and checks the resultant number against the match pattern field - true

FreePBX adds the prepend, and sends +17705554321 to the trunk.

JaredBusch

@eddiejennings said in Dialing Plan Logic Sanity Check:

@dashrender said in Dialing Plan Logic Sanity Check:

I just tested this on FreePBX

This worked

This failed

As I suspected, the 8 in the match failed because the prefix already stripped that out before sending the remaining digits to the match pattern.

I was able to replicate the results. This means (from the Prefix definition) "The dialed number" must mean the prefix number. So perhaps this is what FreePBX does.

User dials 8777705554321

FreePBX checks against first dial pattern (NXXXXXXXXX) - false

FreePBX checks against the second dial pattern.

Checks to see if the prefix number is at the beginning of the dialed number - true

Removes the prefix and checks the resultant number against the match pattern field - true

FreePBX adds the prepend, and sends +17705554321 to the trunk.

Correct. How was this hard to understand?

JaredBusch

@eddiejennings said in Dialing Plan Logic Sanity Check:

@dashrender said in Dialing Plan Logic Sanity Check:

I just tested this on FreePBX

This worked

This failed

As I suspected, the 8 in the match failed because the prefix already stripped that out before sending the remaining digits to the match pattern.

I was able to replicate the results. This means (from the Prefix definition) "The dialed number" must mean the prefix number. So perhaps this is what FreePBX does.

User dials 8777705554321

FreePBX checks against first dial pattern (NXXXXXXXXX) - false

FreePBX checks against the second dial pattern.

Checks to see if the prefix number is at the beginning of the dialed number - true

Removes the prefix and checks the resultant number against the match pattern field - true

FreePBX adds the prepend, and sends +17705554321 to the trunk.

Also NXXXXXXXXX is an invalid dial pattern for NANPA. The valid pattern is NXXNXXXXXX.

EddieJennings

@jaredbusch said in Dialing Plan Logic Sanity Check:

@eddiejennings said in Dialing Plan Logic Sanity Check:

@dashrender said in Dialing Plan Logic Sanity Check:

I just tested this on FreePBX

This worked

This failed

As I suspected, the 8 in the match failed because the prefix already stripped that out before sending the remaining digits to the match pattern.

I was able to replicate the results. This means (from the Prefix definition) "The dialed number" must mean the prefix number. So perhaps this is what FreePBX does.

User dials 8777705554321

FreePBX checks against first dial pattern (NXXXXXXXXX) - false

FreePBX checks against the second dial pattern.

Checks to see if the prefix number is at the beginning of the dialed number - true

Removes the prefix and checks the resultant number against the match pattern field - true

FreePBX adds the prepend, and sends +17705554321 to the trunk.

Correct. How was this hard to understand?

It's not, once "dialed number" is defined. First thought was it sees if the match pattern matches, if it does, then it strips the number specified in the prefix, then adds the prepend, but, in fact, it just matches that a number begins with the prefix, strips it, then sees if the number matches the match pattern, then adds the prepend as was discovered.

EddieJennings

@jaredbusch

Also NXXXXXXXXX is an invalid dial pattern for NANPA. The valid pattern is NXXNXXXXXX.

You're right. I've fixed my patterns. While the invalid pattern works, it would be best to follow the standard.

JaredBusch

@eddiejennings said in Dialing Plan Logic Sanity Check:

@jaredbusch

Also NXXXXXXXXX is an invalid dial pattern for NANPA. The valid pattern is NXXNXXXXXX.

You're right. I've fixed my patterns. While the invalid pattern works, it would be best to follow the standard.

It is too loose, so it would never have stopped a real call from processing.

NXX - NPA (Area Code)
NXX - Exchange (ILEC Central Office)
XXXX - Line (Station within the Exchange)

N = 2-9
X = 0-9

So this menas that NPA and Exchange 3 digit numbers can never begin with a 0 or 1.