Tag Archives: provisioning

Active Unassigned DN’s – Updating with SQL

Update to a previous post

Disclaimer :

Provided as is – you break your box all on your own buddy!  Lab this first.

 The offending DNs can be queried using:

select n.dnorpattern from numplan n
left outer join devicenumplanmap m on m.fkdevice = n.pkid
where m.fkdevice is null
and n.tkpatternusage = ‘2’
and n.iscallable = ‘t’

  • m.fkdevice is null assures the Route Plan element is unassigned
  • tkpatternusage = ‘2’ matches DNs only
  • iscallable=’t’ defines the “Active” checkbox on the DN page – and our offending behaviour.

Some help came from here.

Construct your own UPDATE SQL statement to fix it!  As assistance – start here, it’s not too difficult.

#dontcalltac

Tagged , , , , , ,

Prime Collaboration Provisioning and the Unassigned DN

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.

Tagged , , , ,

Prime Collaboration Provisioning Business Rules

Prime Collaboration Provision has an excellent centralized management of a set of “Business Rules” that really identify a level of system configuration that can be applied to a cluster.

In this example below (using PCP 10.6), the default Unity Connection PIN is set to a trivial value of 123456.

rules

Note:

System-level considerations still apply!   For the example of Unity Connection, one would need to modify the Authentication Rules to accommodate trivial passwords.  This param is called DefaultUnitySubscriberPassword.

This is in fact also referenced in the online documentation:

The DefaultUnitySubscriberPassword rule does not validate the length of the default password entered in the data field. Cisco Unity Connection may have different credential policies configured.

 

Another VERY USEFUL param is LineDisplayString – great for batch provisioning off templates and avoiding messy template updates for a single cluster-wide standard!

Again, from the documentation:

Template string used to construct the Internal Caller ID display format for the phone line. If disabled, the system defaults to FIRSTNAME LASTNAME. This rule does not apply if the Service Area has a Cisco Unified Communications Manager Express as a Call Processor.

The default value for the Display (Internal Caller ID) provisioning attribute is applied from this rule. If you specify CUPM_BLANK or an empty value in batch provisioning or through the Prime Collaboration Provisioning user interface, the value for the Display (Internal Caller ID) provisioning attribute comes from this rule.

Therefore, if you want to set an empty value for the Display (Internal Caller ID) provisioning attribute, you must enable this rule and make sure its value is empty.

Useful Links:

Tagged , , , ,

Prime Collaboration Provisioning – Aborting Failed Orders

If you’ve worked with Prime Collaboration Provisioning, you will be accustomed to this ongoing headache when using Batch Provisioning:

pcp

 

The queuing architecture is atrocious, and is very prone to failure.  Also, validation is pretty much non-existent, so this is a pretty common issue.  Delightfully, there is no way to resolve failed orders other than from root.

 

[root@myhostame01 ~]# cd /opt/cupm/sep/ipt/bin/
[root@myhostame01 bin]# ./AbortOrders.sh globaladmin <password> <order_number> -forced

[root@myhostame01 ~]# cd /opt/cupm/sep/ipt/bin/
[root@myhostame01 bin]# ./AbortOrders.sh globaladmin myp@ssw0rd 164 -forced
===========================================================================
AbortOrders.sh

—————————————————————————

Copyright (c) 2009 Cisco Systems, Inc.
All rights reserved.
===========================================================================
—————————————————————————–
Aborting orders with id: 164
—————————————————————————–

Stopped Provision
Stopped VoIPBatch
Stopped AddLine
Stopped AddLineBatch
Number of rows updated = 1
—————————————————————————–
Order with Id 164 is aborted successfully
—————————————————————————–

[root@myhostame01 bin]#

 

Had to hunt to find this:

 

https://supportforums.cisco.com/discussion/12576731/prime-collaboration-provisioning-105-abort-orders

 

 

UPDATE:

During a call this week [02/2016] with the PCP Product Manager and TME this week has confirmed that this (as well as many other) features will be added to the UI to remove the need to access root.  This work is being done to meet FIPS requirements – great news functionally as well! 🙂

Tagged , , , ,
Collaboration Engineer

All things Collaboration - Posts to save for when you need them

Gerry Keleghan's Blog

A Blog about Cisco Unified Communications

ccieme

my personal journey to ccie collaboration

Striving for greatness

Thoughts on emerging tech, open source, and life

Network Experts Blog

“Knowledge comes by eyes always open and working hands.”

SIP Adventures

A unified communications blog by Andrew Prokop

The Cloverhound Blog

Cloverhound Employees Talk Unified Communications and Contact Center

Warcop

Fog navigator. Get out of the clouds. Down to earth solutions. @Warcop

Cisco Collab Engineering Tips

Michael White - CCIE #26626

Darkroomstory

Photography by Manos,

afterthenumber

Thoughts and experiences of a Cisco Collaboration engineer after clearing the CCIE lab...

Longreads

The best longform stories on the web

The Daily Post

The Art and Craft of Blogging

The WordPress.com Blog

The latest news on WordPress.com and the WordPress community.