I've seen some partners/customers implement solutions this way where they create line partition for each site without thinking about possible impact/limitations this can have.
I would never recommend this as SIP or JTAPI applications are not partition aware, which means as soon as you start using those apps you'll have issues.
Unless you have a requirement to block siteA users from calling siteB users (never seen anyone wanting to do it), there is no point of creating separate partitions, simply create global partition that all DNs are assigned to.
Typically the reason to do this is to achieve 4 digit dial plan with 4 digit extensions and have a TP that prefixes digits, again the proper way to achieve variable length dial plan is by making the extensions unique (i.e. 8 digits) in global partitions and having site specific TPs that strip the site codes instead of prefixing.
Chris, You hit it on the head. That is why I am reducing it to five partitions instead of one in the event that the last 4 digits are duplicates. and we are not blocking siteA from siteB. I do have two special locations where the public can reach the phones so unless someone logins the phone. The phone lines are in a local calling search space. Thank you! Tom
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...