Prime Collaboration | afterthenumber

The later version (11.0 – 11.2) of PCP have a fairly painful caveat when it comes to Unity Connection. CUC is currently afflicted by a(nother) horrid Informix problem that will cause subscriber sync failures.

The defect is below:

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCux67499/?referring_site=bugquickviewclick

Unfortunately, there’s no workaround available as per the bug description:

Symptom:
User Sync of Unity Connection fails on Prime Collaboration Tool (PCP).
NullPointerException exception is seen in Nice log (PCP).

System or internal error java.lang.NullPointerException
java.sql.SQLException: System or internal error java.lang.NullPointerException
at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:488)
at com.informix.jdbc.IfxSqli.a(IfxSqli.java:9547)
at com.informix.jdbc.IfxSqli.receiveMessage(IfxSqli.java:2634)
at com.informix.jdbc.IfxSqli.a(IfxSqli.java:1830)
at com.informix.jdbc.IfxSqli.executeStatementQuery(IfxSqli.java:1768)
at com.informix.jdbc.IfxSqli.executeStatementQuery(IfxSqli.java:1699)
at com.informix.jdbc.IfxResultSet.a(IfxResultSet.java:210)
at com.informix.jdbc.IfxStatement.executeQueryImpl(IfxStatement.java:1237)
at com.informix.jdbc.IfxPreparedStatement.executeQuery(IfxPreparedStatement.java:382)
at dfc.ipt.cisco.unity.util.UMPUtil.executeQuery(UMPUtil.java:247)

Conditions:
1) PCP User Sync in executed for Unity Connection
2) Having 5K or 20K End Users record in CUC11.x or 10.x

Workaround:
None

Please take note of the following, as this does affect planned PCP upgrades:

http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/collaboration/11-2/provisioning/install_upgrade/guide/cpco_b_Cisco_Prime_Collaboration_Provisioning_Install_and_Upgrade_Guide_11_2/cpco_b_Cisco_Prime_Collaboration_Provisioning_Install_and_Upgrade_Guide_11_2_chapter_0110.html

Nice work from the technical documentation team in listing out the caveat in the upgrade guide!

Before upgrading, you need to install an engineering special in Cisco Unity Connection(10.5.x & 11.0) for successful subscriber synchronization. Contact TAC to obtain the Cisco Unity Connection engineering special for the bug (CSCux67499). If you are using Cisco Unity Connection release below 10.5, then you must upgrade to Cisco Unity Connection version 10.5.x and then apply the engineering special.

A call to TAC to request an ES is going to be required (as of the date of this blog post). Cross-reference the bug “Fixed In” details and check if this has been included in a later Unity Connection SU. If in doubt, call TAC for assistance.

Leave a comment

cucm, expressway, im and presence, mra, Prime Collaboration, telepresence, UC Applications

Cisco Support Community Collaboration Videos

Thanks to Java for sharing this – can’t believe I’ve never come across this!

A really, really awesome resource for a number of Collab-related support topics. Some excellent videos on topics such as:

CUOS certificates
Self-Provisioning
Conference Now
PCD
TelePresence
VCS
Service Discovry and UDS
Various phone model factory reset procedures

Enjoy! 🙂

Tagged certificates, conferencing, cucm, cuos, im and presence, pcd, Prime Collaboration, self-provisioning, telepresence, uds, vcs

2016-04-05

2 Comments

cucm, Prime Collaboration, scripting, UC Applications

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 auto-provisioning, cucm, pcp, provisioning, scripting, self-provisioning, sql

2016-04-05

1 Comment

cucm, Prime Collaboration, UC Applications

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 auto-provisioning, cucm, prime, provisioning, self-provisioning

2016-03-16

Leave a comment

Prime Collaboration, UC Applications

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:

http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/collaboration/11-0/Provisioning/Guide/Cisco_Prime_Collaboration_Provisioning_Guide_11/Cisco_Prime_Collaboration_Provisioning_Guide_11_chapter_0111.html#ID1503

Tagged cuc, pcp, prime, provisioning, unity

2016-02-16

Leave a comment

Prime Collaboration, scripting, UC Applications

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 linux, pcp, prime, provisioning, scripting

	jonathan on Implementing Loop Prevention o…
	Anil on Implementing Loop Prevention o…
	jonathan on Implementing Loop Prevention o…
	Jim on Implementing Loop Prevention o…
	jonathan on ExpressWay DMZ and NAT Design…

afterthenumber

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

Category Archives: Prime Collaboration

CSCux67499 – SQL NullPointer Exception causes CUC Subscriber Sync Failures

Cisco Support Community Collaboration Videos

Active Unassigned DN’s – Updating with SQL

Prime Collaboration Provisioning and the Unassigned DN

Prime Collaboration Provisioning Business Rules

Prime Collaboration Provisioning – Aborting Failed Orders