Warning: Undefined array key "kkmods_kkpostslider" in /home/clients/bb1b7c38f63c1b363aa0114be7911e68/web/collaboration/wp-content/plugins/kk-divi-mods/kk_divi_mods.php on line 67
IPCC Troubleshooting | Cisco Collaboration

As in Call Manager, you can specify the level of traces that you want to enable but we will not cover this now. Let’s see the common issues.

Most of the times , issues are due of a mistake with the JTAPI. You can find easily the root cause with the Control Center as it will give you a status of the engine. Then with these status, you can see in which direction you have to go.

  • In-Service : Indicates a full operational mode (all CTI ports, CTI route points and associated applications are successfully initialized)
  • Initializing : Indicates that the subsystem is initializing the CTI route points, ports and associated applications
  • Partial Service : Indicates that the JTAPI subsystem was unable to initialize one or more CTI route points or ports. Most of the time, it is due to a misconfiguration, so check that route points/ports exist , are correctly configured and associated with the JTAPI on Call Manager
  • Out-Of-Service : Indicates that none of the CTI route points and ports were correctly initialized. It can occur for a number of reasons as follows:
    • JTAPI Provider on Call Manager down
    • No CTI ports or route points configured
    • Username/password incorrect
    • CRS is unable to resolve the Call Manager’s DNS name
    • No connectivity between the CRS and Call Manager