topic Re: What JTAPI logging levels are required for diagnosing problems? in Call Control

What JTAPI logging levels are required for diagnosing problems?

derrickgunter — Wed, 18 May 2016 14:20:05 GMT

We have a customer that is attempting to reduce jtapi logging in high call flow environment. If they need to reduce JTAPI log volumes, what is the minimum output values required for debugging, and which ones can be safely turned off?

Thank you.

Re: What JTAPI logging levels are required for diagnosing problems?

derrickgunter — Wed, 18 May 2016 14:29:00 GMT

That is, which of these can be eliminated:

INFORMATIONAL

DEBUG

WARNING

JTAPI_DEBUGGING

JTAPIIMPL_DEBUGGING

CTI_DEBUGGING

CTIIMPL_DEBUGGING

PROTOCOL_DEBUGGING

MISC_DEBUGGING

Re: What JTAPI logging levels are required for diagnosing problems?

mpotluri — Wed, 18 May 2016 15:46:10 GMT

If we have corresponding CTIManager logs we could potentially turn off the following

CTI_DEBUGGING

CTIIMPL_DEBUGGING

PROTOCOL_DEBUGGING

Re: What JTAPI logging levels are required for diagnosing problems?

derrickgunter — Wed, 18 May 2016 16:38:07 GMT

Thanks Mohan. Are there any that could be turned of even without CTIManager logs?

Re: What JTAPI logging levels are required for diagnosing problems?

mpotluri — Wed, 18 May 2016 17:01:55 GMT

PROTOCOL_DEBUGGING is one that takes up space and can be turned off if we have CTI logs to tell us what events are sent out. Without CTI logs and PROTOCOL_DEBUGGING we will loose debugging capability for some scenarios.

Only combination we had success is with CTIManager logs with JTAPI PROTOCOL_DEBUGGING turned off.

Re: What JTAPI logging levels are required for diagnosing problems?

derrickgunter — Wed, 18 May 2016 17:09:48 GMT

Thanks Mohan.