During a season where I worked for a Cisco partner, the support guys affectionately referred to JTAPI as “J-crappy.” While that assessment still holds true, Cisco has come a long way in developing that nuisance of a plugin for integrating CUCM with IP-IVRs, UCCE, and (our favorite…gag me with a wooden spoon) UCCX. Oh joy, could it be? UCCX is on the blueprint for the exam.
Rant: I have no idea why they chose UCCX and not UCCE. If we’re pushing the limits of advanced features, why not use the enterprise-class contact center solution? I digress…
When you check the MIVR logs in UCCX for JTAPI subsystem problems, there are relatively few errors you will find. Here are some of those errors and easy solutions for fixing them. Please note, these errors are described in terms of CRS, which is Cisco IP-IVR solution. However, if you have ever touched a CRS server, you will understand that a UCCX box is essentially a CRS server with contact center capabilities. The software architecture is the same.
