Troubleshooting Secure JTAPI Connection

This section lists the possible errors along with the recommended actions to troubleshoot secure JTAPI connection.

Troubleshooting Secure JTAPI Connection

  1. Possible errors with setup of CUCM for Secure JTAPI.

    1. Ensure to move CUCM to Mixed mode for Secure JTAPI connection to work.

    2. Application User on CUCM do not have “Standard CTI Secure Connection” role associated.


      Note

      For non-secure connection “Standard CTI Secure Connection” role should not be present.

    3. Application User CAPF profile do not have “Certificate Operation as Install/Upgrade”.

    4. CTI service/ Call Manager service/ CAPF service/ TFTP service is down on CUCM.

    5. When CUCM/CAPF certificates are regenerated, make sure the CTL file is regenerated and all the required services are restarted, new CAPF Profile is created before CUCM rediscovery on Cisco Prime Collaboration Assurance.

  2. Possible errors while using Cisco Prime Collaboration Assurance with Secure JTAPI in Session Monitoring.

    Issue:

    Sessions not coming up on Conference Diagnostics

    Possible Reasons:

    1. Access level for JTAPI may not be RO (read-only).

    2. Endpoints may not have full visibility.

    3. Endpoints may not be controlled by the JTAPI User.