Tag Archives: pcp

CSCux67499 – SQL NullPointer Exception causes CUC Subscriber Sync Failures

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:

 

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:

 

 

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.

 

 

Tagged , , ,

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 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

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.