Something to watch out for!
When using Prime Collaboration for auto-provisioning of users/lines for Self-Provisioning in CUCM, the DNs will be added as “Active” by default.
Active Check Box
The Active check box, which only displays for unassigned directory numbers, determines whether the directory number gets loaded and used by Cisco Unified Communications Manager. By checking the check box, the directory number gets loaded and used by Cisco Unified Communications Manager. For example, the directory number belonged to an employee who left the company. The directory number had certain settings that were configured, such as call forwarding to voice-messaging system. By leaving the directory number active, a call that is intended for the directory number will get forwarded. This eliminates the need to reconfigure another employee to have the same call-forwarding options. If the check box is not checked, the directory number will not get loaded by Cisco Unified Communications Manager, which results in settings that are configured for that DN to not be used (for example, call forward destinations), and callers will not get their call forwarded properly.
Please see the CUCM System Guide. My links for 8.6, but still 100% relevant.
The impact is that when doing site migrations, sites already deployed onto the new cluster will fail to dial users that, although pre-provisioned in CUCM, have not yet Self-Provisioned their endpoints. Nice way to create an outage, sending all calls a VM box that hasn’t even been set up!
I haven’t found a Prime-driven solution for this. Sadly, we’re back to BAT tools to get the working with Export/Import… Or SQL.
One thought on “Prime Collaboration Provisioning and the Unassigned DN”