Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

Call Manager PIM not getting activated.

Getting the follwoing error in JGW1 Log

15:05:18 pg1A-jgw1 Trace: Configuring JTAPI Object
15:05:18 pg1A-jgw1 Trace: Calling getJtapiPeer for peer: com.cisco.jtapi.CiscoJtapiPeerImpl
15:05:18 pg1A-jgw1 Trace: getJtapiPeer returned successfully.  JTapiPeer class name: com.cisco.jtapi.CiscoJtapiPeerImpl
15:05:18 pg1A-jgw1 Trace: CiscoJtapiVersion: Cisco Jtapi version 6.1(2.1000)-12 Release
15:05:18 pg1A-jgw1 Trace: BuildDescription: Release BuildNumber: 1000 RevisionNumber: 2 MajorVersion: 6 MinorVersion: 1 ExtendedBuildNumber: 12
15:05:18 pg1A-jgw1 Trace: Use icmJavaLib.jar to support CallManager 5.0 or higher release.
15:05:18 pg1A-jgw1 Trace: Not using CiscoSynchronousObserver interface.
15:05:18 pg1A-jgw1 Trace: disableAll() TraceManager for CTICLIENT
15:05:18 pg1A-jgw1 Trace: Calling getProvider() 16.138.43.119;login=ccmadmin;passwd=<***edited***>
15:05:35 pg1A-jgw1 Trace: JtapiPeer.getProvider(): caught PlatformException(com.cisco.jtapi.PlatformExceptionImpl: Unable to create provider -- directory login timeout)  Provider could not be created.
15:05:35 pg1A-jgw1 Trace: Message: Unable to create provider -- directory login timeout
15:05:53 pg1A-jgw1 Trace: Node Manager thread received shutdown message
15:05:53 pg1A-jgw1 Trace: Node Manager thread sending NM_MSG_SHUTDOWN_REPLY_OK to Node Manager.
15:05:53 pg1A-jgw1 Trace: Node Manager thread completed clean shutdown dialog with Node Manager.  Exiting process.
15:11:45 pg1A-jgw1 Initializing Event Management System (EMS) Library.
15:11:45 pg1A-jgw1 Trace: EMS Server pipe gdic\PG1A\jgw1EMSPipe enabled for gdic\PG1A\jgw1
15:11:45 pg1A-jgw1 Trace: [Thread-3]ThreadAddressManager starts
15:11:45 pg1A-jgw1 Trace: ThreadAddressManager::Waiting for next retry
15:11:45 pg1A-jgw1 Trace: Monitor Server pipe gdic\PG1A\jgw1CmdPipe enabled for gdic\PG1A\jgw1
15:11:45 pg1A-jgw1 Trace: JVM Total Memory: 33357824 JVM Free Memory: 33017520 JVM Heap in Use: 340304 JVM has 98.979836% free memory
15:11:45 pg1A-jgw1 Trace: Configuring JTAPI Object

PIM Logs

15:05:53 pg1A-pim1 Trace: [  7220]Node Manager thread received shutdown message
15:05:53 pg1A-pim1 NodeManagerHandler received shutdown message
15:05:53 pg1A-pim1 Requesting normal MDS termination.
15:05:53 pg1A-pim1 Connection to MDS process closed.
15:05:54 pg1A-pim1 Trace: [  7220]Node Manager thread sending NM_MSG_SHUTDOWN_REPLY_OK to Node Manager.
15:05:54 pg1A-pim1 Trace: [  7220]Node Manager thread completed clean shutdown dialog with Node Manager.  Exiting process.
15:11:42 pg1A-pim1 Initializing Event Management System (EMS) Library.
15:11:42 pg1A-pim1 Trace: EMS Server pipe gdic\PG1A\pim1EMSPipe enabled for gdic\PG1A\pim1
15:11:42 pg1A-pim1 Trace: Monitor Server pipe gdic\PG1A\pim1CmdPipe enabled for gdic\PG1A\pim1
15:11:42 pg1A-pim1 Initializing Node Manager Library.
15:11:42 pg1A-pim1 EAGTPIM Release 7.5.1.0 , Build 23684
15:11:42 pg1A-pim1 Failed to read AutoCfgErrorFileMaxBytes value in the SOFTWARE\CISCO SYSTEMS, INC.\ICM\gdic\PG1A\PG\CurrentVersion\PIMS\pim1\EAgentData\Dynamic key in the registry.
15:11:42 pg1A-pim1 Failed to read AutoCfgErrorFileName value in the SOFTWARE\CISCO SYSTEMS, INC.\ICM\gdic\PG1A\PG\CurrentVersion\PIMS\pim1\EAgentData\Dynamic key in the registry.
15:11:42 pg1A-pim1 Trace: PimConfig::TPServices: ChkDdLck=1 TrkLck=1 Grp=0 Ord=10 MxHldTcks=3000

15:11:42 pg1A-pim1 Trace: [  5504]DeskLinkDeviceTarget::SetNumExtensionDigits: Number of extension digits set to 7
15:11:42 pg1A-pim1 Trace: [  5504]EMT I/O completion ports: max threads=2, concurent threads=0
15:11:44 pg1A-pim1 Connection to MDS process established.
15:11:44 pg1A-pim1 MDS now in service.
15:12:31 pg1A-pim1 ProcessPIMSetIdleReq: Peripheral 5001 going idle.

Followinf are checked

1. CTI service is active

2. JTAPI user is created

3. re-installed the JTAPI client

Please let me know what can be done

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: Call Manager PIM not getting activated.

Check if jtajpi user is application user with CTI enabled permissions in CUCM. Directory login timeout usually indicates incorrect jtapi user permissions

5 REPLIES

Re: Call Manager PIM not getting activated.

Please check JTAPI username & password what you have mentioned in CCM & in PG setup must match .

secondly have you downloaded JTAPI plugin from CCM on CCMPG machine & installed on it.

Re: Call Manager PIM not getting activated.

Hi Irfan

thanks for the reply

yes i did have the same Jtapi user ID and password in CCM and PG setup. I installed the JTAPI client from the call manager admin page.

Cisco Employee

Re: Call Manager PIM not getting activated.

Check if jtajpi user is application user with CTI enabled permissions in CUCM. Directory login timeout usually indicates incorrect jtapi user permissions

Re: Call Manager PIM not getting activated.

Thanks Nebojsa

I gave the CTI permissions to the Jtapi user and it worked. Thanks for the reply.

Thanks to cndilip123 as well for giving the information.

Re: Call Manager PIM not getting activated.

One more question you have created icmsuer as an application user in ccm , and assigned required groups to it.

1915
Views
0
Helpful
5
Replies