/mcpCause code Cause code name 0XA3000000 + CAUSE_UNALLOCATEDNUMBER CAUSE_CTICCMSIP604DOESNOTEXISTANYWHERE 0XA4000000 + CAUSE_NORMALUNSPECIFIED CAUSE_CTICCMSIP606NOTACCEPTABLE 0xA5000000 + NORMALUNSPECIFIED CAUSE_CTICCMSIP200CALLCOMPLETEDELSEWHERE 0xA7000000 + SERVNOTAVAILUNSPECIFIED CAUSE_CTICCMSIP503SERVICENOTAVAILABLE Additional Troubleshooting Information Viewing JTAPI Debug Output To view JTAPI debug output, use the JTPREFS application to change the trace settings. The JTPREFS application allows you to enable or disable various kinds of tracing. JTPREFS is installed in the %SystemRoot%\java\lib directory along with the JTAPI classes. Cisco JTAPI Preferences is installed by default in Program Files\JTAPITools. To open the Cisco JTAPI Preferences utility, choose Start > Programs > Cisco JTAPI > JTAPI Preferences. The following trace levels are defined: • WARNING - warning events • INFORMATIONAL - status events • DEBUG - debugging events If DEBUG is enabled, JTPREFS allows you to enable or disable various debugging levels. The following debugging levels are defined: • TAPI_DEBUGGING - to trace JTAPI methods and events • TAPI_IMPLDEBUGGING - internal JTAPI implementation trace • CTI_DEBUGGING - to trace Cisco Unified Communications Manager events that are sent to the JTAPI implementation • CTIIMPL_DEBUGGING - internal CTICLIENT implementation trace • PROTOCOL_DEBUGGING - full CTI protocol decoding • MISC_DEBUGGING - miscellaneous low-level debug trace Traces can be directed to a specific path and folder rather than to the application directory by default. The same trace folder could be used for successive or more than one simultaneous launch of JTAPI. Different launches of JTAPI would also send the traces to different folders. This allows simultaneous JTAPI instances to maintain independent trace destinations Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1651 Troubleshooting Cisco Unified JTAPI Additional Troubleshooting Information