/mcpDescription Max Min Default Jtapi.ini fields This field specifies internal CTICLIENT implementation trace NA NA 0 CTIIMPL_DEBUGGING This field specifies full CTI protocol decoding NA NA 0 PROTOCOL_DEBUGGING This field specifies miscellaneous low-level debug trace NA NA 0 MISC_DEBUGGING This field specifies how often, in seconds, the connection between JTAPI and the Cisco Unified Communications Manager cluster will be verified. If JTAPI fails to receive heartbeats, it will establish a connection via the second CTIManager that is specified in the provider open request. Not Present (NP)
0 30 DesiredServerHeartbeatInterval This field specifies the path name to which the trace files are written. When the path is not specified, JTAPI makes the application path as the default. NA NA . TracePath This field specifies a numerical index that is appended to the file base name to indicate the order in which the files are created. For example, if you enter jtapiTrace in the File Name Base field and log in the File Name Extension field, the trace files would rotate between jtapiTrace01.log, jtapiTrace02.log, and jtapiTrace10.log. If the File Name Base and File Name Extension fields are left blank, Cisco Unified JTAPI picks the trace files names as CiscoJtapi01.log, CiscoJtapi02.log, and so on. NA NA log FileNameExtension This field specifies you to direct the traces to a specific path and folder in the system. No fewer than two log files and no more than 99 files can exist. Cisco Unified JTAPI rotates through the log files in numerical order, and returns to the first log file after filling the last. Log files increase in size in 1-megabyte increments. NA NA FALSE SyslogCollector This field allows you to specify the maximum size of log files to be written. NP 1048576 1048576 TraceFileSize Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 242 Cisco Unified JTAPI Installation Fields in the jtapi.ini File