Overlapping dial-plan support

Overview

The following table resumes the list of UC Suite applications that support overlapping dial plan, with possible limitations and requirements.

Please, notice that it applies to a single CUCM cluster. In a multi-cluster scenario, further requirements and limitations (not indicated here) apply.

In the next paragraph you can find some additional details about the different applications.

Application  Support
(Full/Partial/No)
Requirements Limitations
Call Recording PARTIAL

Users should record using Built-in Bridge or Network Based recording technologies.

The Numeric User/Partition Id mechanism must be used to distinguish users having the same directory number.

SIPREC recording is not supported. 

DIAL-IN reocrding is not supported.

Advanced Queuing & Auto Attendant

NO

Too many requirements apply but, normally, this is out of our control, so we prefer it is not supported at all.

Actual requirements:

  • Agents phone numbers must be unique across the cluster (and the IAS)
  • ACD queue numbers must be unique ((not overlapping with any other QME/IVR number).
  • IVR service numbers must be unique (not overlapping with any other QME/IVR number).

-

Attendant Console YES

If using the console with Advanced Queuing, above mentioned constraints apply.

The preferred devicename of UC Suite user must be populated for Att.Console users.

-
Call Analytics FULL

Call Analytics for Cisco UC includes a Partition-aware driver, to support overlapping extensions on different Partitions. Remember that the partition field can be synchronized only when synchronizing with CUCM, using the Primary-Line number of the CUCM end-user. For all other cases, it must be manually populated (CSV import).

Staring from Summer 2021 release, each user can be associated to a specific PBX "SITE", allowing overlapping extensions on different platforms/gateways, independently from Partition ID.

If Partition-aware driver is used, extension numbers in reports and filters appears in the composite format:
<DN>.<PartitionName> 
(i.e. 2501.PT_Rome_IPPhones)
Phone Lock YES

Phones must be TAPI controlled.

The MAC address and/or the partition field must be valued for each IAS user.

CURRI is not supported.
Budget Control YES Both the Billy Blue's and the Stonelock requirements (mentioned above) apply. Both the Billy Blue's and the Stonelock limitations (mentioned above) apply.
Digital Fax PARTIAL Fax numbers must be unique (the E.164 numbering is recommended!). -
Contact Manager PARTIAL If Caller Lookup is needed, it must be done using TAPI.

CURRI Caller Lookup is not supported.

Smart Numbers are not supported.

VoiceMail PARTIAL Users having the same DN must have different voice mail numbers. VoiceMail IVR cannot be used.
Hotel Services NO The phones numbering plan must be flat (not overlapping). 
Only room numbers can overlap in a multi-property scenario, we distinguish them using the property prefix number.
-

Technical details

Assumptions

Call Analytics:

Advanced Queuing and Attendant Console

Phone lock and Budget Control:

Contact Manager:

Call Recording:

Digital Fax

VoiceMail

VoiceMail could work with the following requirements and limitations that normally are not acceptable in a real-world scenario:



Article ID: 787
Last updated: 25 Jun, 2021
Revision: 2
Imagicle UC Suite for Cisco UC -> FAQ and Solutions -> Overlapping dial-plan support
https://kbp.imagicle.com/kb/entry/787/