12-19-2019 05:37 PM
Hello,
I have a question about e.164 dial plans. I've done a bunch of searching but haven't quite found the answer.How do you get around non-did extensions. For example i have courtesy phones, logged out hotelling phones, unity connection pilot etc. Is it acceptable in an e.164 dial plan to have 4 digit extensions (or i guess non\+ extension) for phones without DIDs?
Thank you in advance.
Solved! Go to Solution.
12-20-2019 05:20 AM
Technically you can have variable length extensions on the cluster, but recommend sticking with +e164 for everything including non DIDs. What I do for non-DIDs is create a range that would never exist for that country, so for example for North America dial plan I usually use +1000XXXXXXX as there never will be area code 000.
12-20-2019 07:30 AM - edited 01-18-2020 06:47 AM
The approach we used for non DIDs in our global deployment with 160+ sites in more countries than I care to count is to format them as \+0 <country code> <area code> <subscriber number> as there will never be any real country code that start with a 0 (zero). For short abbreviated dialing we build them as this <country code> <site code> <last 4 digits of the DN>.
To give an example for a site with made up numbers.
DID range +464055XXXX
DN +4640556677 abbreviated number 4616677
Non DID range
DID range +0464055XXXX
DN +04640558877 abbreviated number 4618877
Our abbreviated dialing is visible in the entire system, so we make sure to keep these from overlapping.
12-20-2019 05:20 AM
Technically you can have variable length extensions on the cluster, but recommend sticking with +e164 for everything including non DIDs. What I do for non-DIDs is create a range that would never exist for that country, so for example for North America dial plan I usually use +1000XXXXXXX as there never will be area code 000.
12-20-2019 05:32 AM
Awesome. Thank you so much for the reply.
One other question, to avoid 4 digit overlaps on translation patterns, i'm guessing it's best to segment the translation pattern partitions by area code/country code? NY Offices have access to NY xlate patterns, CA offices have access to CA xlate patterns, UK etc etc and then do site to site access codes?
Again, thanks for the quick reply.
12-20-2019 06:06 AM
Correct, if you decide to use translation patterns for abbreviated dialing then they have to built in proper partitions to avoid any potential for overlaps. This can be done per site, per county, or whatever the breakdown is.
12-20-2019 07:30 AM - edited 01-18-2020 06:47 AM
The approach we used for non DIDs in our global deployment with 160+ sites in more countries than I care to count is to format them as \+0 <country code> <area code> <subscriber number> as there will never be any real country code that start with a 0 (zero). For short abbreviated dialing we build them as this <country code> <site code> <last 4 digits of the DN>.
To give an example for a site with made up numbers.
DID range +464055XXXX
DN +4640556677 abbreviated number 4616677
Non DID range
DID range +0464055XXXX
DN +04640558877 abbreviated number 4618877
Our abbreviated dialing is visible in the entire system, so we make sure to keep these from overlapping.
12-20-2019 08:23 AM
Thank you both. Clears things up for me.
Happy Holidays!
Cheers.
12-20-2019 08:57 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide