Guest

Preview Tool

Cisco Bug: CSCuo88424 - TCD shows Wrong InstrumentPortNumber for CUCM Ext. beginning with a Zero

Last Modified

Dec 29, 2016

Products (1)

  • Cisco Unified Contact Center Enterprise

Known Affected Releases

8.5(4) 9.0(1) 9.0(4)

Description (partial)

Symptom:
In the t_Termination_Call_Detail table, the InstrumentPortNumber is showing the wrong extensions for CUCM agents.

For example, the following query returns this:

SELECT InstrumentPortNumber, COUNT(*)
FROM t_Termination_Call_Detail TCD
WHERE TCD.DateTime > getdate() -10
         AND PrecisionQueueID IS NOT NULL
GROUP BY InstrumentPortNumber
ORDER BY COUNT(*) DESC

InstrumentPortNumber               Count
NULL      135
104977  78
69696    74
69640    74
104970  72
69647    69

These extensions show starting with a 69 or 10 however the agents' real CUCM extensions start with 02xxxxx (e.g. 0210055).

69xxx actually looks more like Avaya extensions.

When I look at real-time data (e.g. t_Agent_Real_Time), their extensions show up correctly.

Conditions:
We were able to validate with BU lab as well as the customers LAB,

That this only occurs when the CUCM extension begins with a Zero

Exp.    0210060

the TCD is actually writing the decimal number format and not the octal number format that it should be.

0210060  is the valid CUCM extension.

When converted to Decimal It's the 69680 number we are seeing in the Instrument Port Number
That is not happening when a CUCM extension begins with any other number.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.