CSCts69270 - CCX CTI ports may stuck in out-of-service state when UCM Upgrade/Restart

Unanswered Question
Dec 9th, 2013
User Badges:

Symptom:


CCX CTI ports (RP & IVR) may stuck in out-of-service state during CUCM upgrade or Restart.

Conditions:


During CUCM upgrade the The UCCX CTI ports (RoutePoint Triggers and few IVR ports) went into out-of-service state .

This condition may happen during CUCM upgrade process or CUCM nodes restart. When this happens;

The CUCM sate of down ports is "Registered".

The UCCX state of down ports is "Out of Service"

This was tested on following Release branch;

CUCM Version: 8.6.2.10000-30

UCCX Version: 8.5.1.11001-35

JTAPI Version: 8.6(2.10000)-2

CUCM is a 15 Nodes cluster over the LAN with 10 subscriber nodes.

UCCX is a 2 Nodes-HA Cluster, with one Route point, and 300 ICT IVR ports.

Workaround:


After Upgrade completes, restart of CTIManager service from the CUCM nodes serving the CCX.

Last Modified:

Aug 26,2013

Symptom:
CCX CTI ports (RP & IVR) may stuck in out-of-service state during CUCM upgrade or Restart.


Conditions:


During CUCM upgrade the The UCCX CTI ports (RoutePoint Triggers and few IVR ports) went into out-of-service state .


This condition may happen during CUCM upgrade process or CUCM nodes restart. When this happens;


The CUCM sate of down ports is "Registered".


The UCCX state of down ports is "Out of Service"


This was tested on following Release branch;


CUCM Version: 8.6.2.10000-30


UCCX Version: 8.5.1.11001-35


JTAPI Version: 8.6(2.10000)-2


CUCM is a 15 Nodes cluster over the LAN with 10 subscriber nodes.


UCCX is a 2 Nodes-HA Cluster, with one Route point, and 300 ICT IVR ports.


Workaround:


After Upgrade completes, restart of CTIManager service from the CUCM nodes serving the CCX.


Last Modified:

Aug 26,2013

Known Affected Releases:

(0)



Known Fixed Releases:

(0)

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Wes Sisk Mon, 12/09/2013 - 12:02
User Badges:
  • Cisco Employee,

Hello r.mata, do you have a question about this bug?  Regards, Wes

Actions

This Discussion