Extension Numbers

[Joe Archibald]

Hi,
I am upgrading from FreePBX to 3CX and I am looking to avoid a problem that I currently have.

We have 3 digit extensions 200-260, we have had these extensions for years, but a new area code has been added to our local area that is in the same range as our extensions.
When someone starts dialing the area code, our dial pattern sees it as a local extension and tries to call the area code as an extension.

I have told the users to dial the number, and then choose a line to dial it.
We are thinking of moving to 4 digit extensions to get around these issues like 4200-4260.

Is there a BestPractise to extension numbers these days?
Anyone else having these issues?

THanks
Joe

 

[leejor]

Changing the digit length requires a re-install.

https://www.3cx.com/community/threads/v16-change-length-of-extensions.68896/

If you are talking about the internal (set) dialplan, recognising the area code as an extension, then change the dialplan to require the full number, before sending the call to 3CX. Most dialplans are pretty flexible. The other, extreme measure, would be to require the use of an access digit, say "9", for outside calls.

 

[Joe Archibald]

Right now on my FreePBX, I have the dialplan recognizing 2xx,so when users dial an extension like 217, it immediately dials. But there is a local area code in that range.
As I am setting up 3CX, I am trying to avoid issues like this and looking for input.

Thanks

 

[leejor]

Unfortunately, this is not a PBX issue, it is a set dialplan (conflict) issue. With SIP, the digits are sent all at once, so if the dialplan in the set is not able to diferenciate between an extension number, and the area code of an outside call, the extension gets called after 3 digits. The only things you could do, is remove the set dialplan altogether, and require that a dial: button, or # (depending on the set), be pressed after dialling (or wait for the digit collection timeout), or, require the use of a prefix for outbound calls.