Guest

Preview Tool

Cisco Bug: CSCun14017 - "CTI doesn't report INSERVICE to Application" issue

Last Modified

Feb 25, 2019

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

8.6(2.24103.2)

Description (partial)

Symptom:
If network connectivity goes away then comes back agents are not about to log in and receive calls and LCP/RCP is not recovering on itself.

Conditions:
Happens when there is a network interruption and LCP/RCP ports have active call (Connected/Hold).

Related Community Discussions

12005 - Device is not registered correctly in call manager
Hello All   We have a CUCM single cluster integrated to ICM/UCCE. Everytime we perform any maintenance activities on CUCM/have it rebooted all the agents start receiving error "12005 - Device is not registered correctly in call manager" in the Agent communicator.   To circumvent the issue either we have to remove the extension one by one from the application user(associated with the PG) and associate it back or recycle the PIM process.   Wanted to check if anyone has faced the same error before and ...
Latest activity: Oct 12, 2015
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.