[cisco-voip] e164 dialplan conversion

Fri Sep 22 11:44:35 EDT 2017

This is the link to the page that contains all the PA and CVD documents published so far:


De: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] En nombre de Anthony Holloway
Enviado el: viernes, 22 de septiembre de 2017 02:15 a.m.
Para: Ben Amick <bamick at humanarc.com>
CC: cisco-voip voyp list <cisco-voip at puck.nether.net>
Asunto: Re: [cisco-voip] e164 dialplan conversion

You remember the big Y2K scare of the late 90s?

Storing only the last 4 digits of an E.164 number is like storing the last two digits of the Year.

It's not like moving to more digits prevents users from keeping their existing dialing habits.

I would also recommend you read the Dial Plan section of the Preferred Architecture (PA) for Collaboration.  It's a quick read, like less than 10 minutes.


If that excited you, then move on the the PA Cisco Validated Design (CVD) section on End Point Addressing, and Routing and Normalization.  It's pretty great.


On Thu, Sep 21, 2017 at 9:24 AM Ben Amick <bamick at humanarc.com<mailto:bamick at humanarc.com>> wrote:
Inexperienced person here chiming in with a question:
What advantage/purpose does switching to an e164 dial plan afford you? Is it just more of a flexibility to mate dial plan/DNs to DIDs?
More importantly, how would an e164 dial plan mesh with a system where the majority of users do not have DIDs or DIDs that do not match their extension plan?
Is any additional overhead generated by going to an e164 dial plan?
Also, from what I understand, 4-5digit dialing is made possible only by having proper CSS per site with a translation pattern, not through any function of the DN configuration, correct?

Ben Amick
Unified Communications Analyst

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Bernhard Albler
Sent: Thursday, September 21, 2017 10:04 AM
To: Florian Kroessbacher <florian.kroessbacher at gmail.com<mailto:florian.kroessbacher at gmail.com>>
Cc: cisco-voip voyp list <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] e164 dialplan conversion

What Florian says is the correct way to do it.
You can also run a sql update against the numplan table which will do 2 things:
1.)I you typoed you are in for a lot of pain
2.)Ucm will load up on change notification (assuming lots of DNs) and might come to halt before recovering

Agent DNs in my experience will reflect automatically. Routepoints and CTI ports you will need to change manually.

Personally i suggest the SQL route as the adrenaline rush is just incredible once you realize you made a mistake.

On Thu, Sep 21, 2017 at 3:20 PM, Florian Kroessbacher <florian.kroessbacher at gmail.com<mailto:florian.kroessbacher at gmail.com>> wrote:
Hy out there,

throug updateLine this is working

use old pattern & partition
and set newpattern

we have done this for 12000 Lines

Am 21. Sep. 2017, 15:13 +0200 schrieb Bill Talley <btalley at gmail.com<mailto:btalley at gmail.com>>:
I know there have been some conversations around this in the past, but I’m hoping there are new methods for converting from a 4-digit to full e164 dialplan.

Is there a way to change dialplan entries on CUCM and UCCX without having to either individually touch each dialplan pattern or without deleting and reimporting/recreating? Has anyone seen or used AXL/SOAP to automate modification of dialplan patterns, or used PCP or some third party product to accomplish this?

Thanks for any feedback.


Sent from a mobile device with very tiny touchscreen input keys. Please excude my typtos.
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>

cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>

Bernhard Albler, +4369917207384<tel:+43%20699%2017207384>
"Was Nachwelt! Wie komm' ich dazu was für die Nachwelt zu tun? Was hat denn die Nachwelt für mich getan?"
--Carl Friedrich Zelter

Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you _______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170922/f5a47d96/attachment.html>

More information about the cisco-voip mailing list