Has anyone experienced any issues with handling "Call Park" test using JTAPI ?

I have a CUCM 6.0 - where Call Park works.

The system got upgraded to CUCM 6.1.2 and now Call Park tests are failing. I see the CiscoProvCallParkEv coming in but I don't see the call being disconnected from the Orig and re-establish with the Retriever.

Arvind

[Attached the CTI logs from the CUCM]

Call Setup info:

Target DN - 1002
Terminator DN - 1004
Park Retriever - 1005

Edited by: Arvind Sharma on Oct 28, 2008 4:22 PM

Attachments:

Just attached the CUCM CTI log files and some other info.

Arvind

Yes, the userid is associated with CTI permissions.

Other CTI related operation (Call Transfer) for the same user does work.

Arvind

Yes, application is Observing all the three parties.

I know I can use JTAPI Prefs tool to setup the Debug.

Where do I keep the jtapi.ini file so that log files gets generated in the dir I mentioned there ? Same place where I have the jtapi.jar or some other place.

Arvind

OK I see the jtapi.ini file.

All the settings looks correct.

I also changed the location where the output file should go (c:\temp)....BUT I still don't see any trace files coming out to c:/temp....

I also checked c:\WINDOWS\java area - no trace files there either.

Question: - Does the jtapi.ini file need to be where the jtapi.jar file is ?

My JTAPI application which is interfacing with the CUCM is installed in some other directory.

Arvind

I should have stated it more clearly, my fault.

I have the JTAPI Pref tool installed and I can setup the debuggin information using the tool.

I can also see the JTAPI debug statements coming out when I run the sample appliaction "makecall". All the trace goes to, in my case, c:\temp\

What I am not able to do is - when I run my application (which is installed some place else on the same Windows machine) the JTAPI related calls don't generate any debug statements in the c:\temp\ area.

I have the jtapi.ini file in the CLASSPATH (which was done when I installed the JTAP Pref tool). It has all the information about the CUCM with which my application is interacting with.

I have tried putting the jtapi.ini file in various different directory locations (JRE, TOMCAT, even in the directory where my application JARS are) - but still no luck.

What gives?

Thanks!
Arvind

I have an alternate solution for that: I never liked having to install jtapi on any machine.. I have a bunch of jtapi.jar files from various CCM versions and use the one matching the CCM version I'm developing against.

In order to have the possiblity to get debug information anyway, I'm using code during my initialization routines:

private void setJtapiPreferences(CiscoJtapiPeer peer)
{
CiscoJtapiProperties props = peer.getJtapiProperties();
props.setDebuggingValue("JTAPI_DEBUGGING", config.jtapiConfig.jtapiDebugJtapi);
props.setDebuggingValue("JTAPIIMPL_DEBUGGING", config.jtapiConfig.jtapiDebugJtapiImpl);
props.setDebuggingValue("CTI_DEBUGGING", config.jtapiConfig.jtapiDebugCti);
props.setDebuggingValue("CTIIMPL_DEBUGGING", config.jtapiConfig.jtapiDebugCtiImpl);
props.setDebuggingValue("PROTOCOL_DEBUGGING", config.jtapiConfig.jtapiDebugProtocol);
props.setDebuggingValue("MISC_DEBUGGING", config.jtapiConfig.jtapiDebugMisc);
props.setTraceValue("WARNING", config.jtapiConfig.jtapiTraceWarning);
props.setTraceValue("INFORMATIONAL", config.jtapiConfig.jtapiTraceInfo);
props.setTraceValue("DEBUG", config.jtapiConfig.jtapiTraceDebug);
props.setTraceDirectory(config.jtapiConfig.jtapiLogPath);
props.setTraceFileSize(config.jtapiConfig.jtapiLogFileSize);
props.setTracePath(config.jtapiConfig.jtapiDirectoryBaseName);
props.setUseFileTrace(config.jtapiConfig.jtapiUseTraceFiles);
props.setUseSameDir(config.jtapiConfig.jtapiUseSameDirectory);
props.setUseSyslog(config.jtapiConfig.jtapiUseSyslog);
if (config.jtapiConfig.jtapiUseSyslog)
{
props.setSyslogCollector(config.jtapiConfig.jtapiSyslogHost);
props.setSyslogCollectorUDPPort(config.jtapiConfig.jtapiSyslogPort);
}
props.setUseJavaConsoleTrace(config.jtapiConfig.jtapiUseJavaConsole);
}

(config is a class representing the configuration file of my app).

That way, you can programmatically do what jtapiprefs does, and it works on every machine, not only those where you have installed jtapi.

Sorry - forgot to mention another observation (which kind of ties my other Posting in the "Cisco JTAPI" forum titled "CUCM 7.0 verfication"

If I point to the CTI Manager on the subscriber (currently it was pointing to the Publisher) then I see Call Park work (7 out of 10 times though)

If I keep it pointing to the Publisher then it fails every time.

I am confused now :-(

Arvind

Also ensure that the file system permissions for the log target location allow writing by the user under which the application is running. If the java app can't write to the disk due to permissions, then logs cannot be created.