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. And see here for current known issues.

New Member

CRS 302 and CCM 3.3.3 JTAPI Problem

I've ICD 3(0)2 and CCM 3.3.3. JTAPI updated to lastest from CCM3.3.3 But the JTAPI Subsystem remains OUT_OF_SERVICE.

Defined the JTAPI user in CCM, Route Point and CTI ports and added devices to user.

Defined the JTAPI Provider, but because the Subsystem will not come up cannot define the CTI Port Groups.

Trace Files from starting the Engine show:

206: Sep 19 16:36:47.625 BST %MIVR-SS_TEL-7-UNK:JTAPI Login Str: 135.136.17.38;login=jtapi;passwd=****;appinfo=Cisco IP IVR

207: Sep 19 16:36:47.656 BST %MIVR-SS_TEL-7-UNK:Initial UDP Port: 16384

208: Sep 19 16:36:47.671 BST %MIVR-SS_TEL-6-CTIPORT_RECOV_THR_START:Starting CTI Port Recovery Thread: Recovery Thread id=CTIPortRecovery-0

209: Sep 19 16:36:48.468 BST %MIVR-SS_TEL-1-SS_OUT_OF_SERVICE:JTAPI subsystem in out of service: Failure reason=A number of route points are OOS - all routes; A number of CTI ports are OOS - all ports

210: Sep 19 16:36:48.578 BST %MIVR-SS_TEL-7-UNK:Number of CTI ports = 0

...

...

248: Sep 19 16:36:49.531 BST %MIVR-SS_TEL-7-UNK:Got JTAPI provider. JTAPI version: Cisco JTAPI version 1.4(3.12) Release

249: Sep 19 16:36:49.531 BST %MIVR-SS_TEL-6-JTAPI_PROVIDER_EVENT:JTAPI Provider state is changed: JTAPI provider name=135.136.17.38,Event=ProvOutOfServiceEv received

250: Sep 19 16:36:49.531 BST %MIVR-SS_TEL-6-JTAPI_PROVIDER_EVENT:JTAPI Provider state is changed: JTAPI provider name=135.136.17.38,Event=ProvInServiceEv received

251: Sep 19 16:36:49.593 BST %MIVR-SS_TEL-5-NO_CTIPG_LDAP:No CTI Port Group in LDAP:

252: Sep 19 16:36:49.593 BST %MIVR-SS_TEL-7-UNK:Number of CTI ports = 0

253: Sep 19 16:36:49.593 BST %MIVR-SS_TEL-7-UNK:calculateSubsystemState

254: Sep 19 16:36:49.593 BST %MIVR-SS_TEL-7-UNK:calculateSubsystemState -> Groups: ISV = 0, OOS = 0, PARTIAL/OTHERS = 0

255: Sep 19 16:36:49.593 BST %MIVR-SS_TEL-7-UNK:calculateSubsystemState -> subsystem out of service

256: Sep 19 16:36:49.593 BST %MIVR-SS_TEL-1-SS_OUT_OF_SERVICE:JTAPI subsystem in out of service: Failure reason=

Adding a couple of 7960s to the device association of the JTAPI user, the JTAPITool,

Jview makecall <server name> <login> <password> 1000 <phone1> <phone2>

works fine so the TAPI interface is working.

Any clues?

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: CRS 302 and CCM 3.3.3 JTAPI Problem

CRS 3.0(2) is not compatible with CM 3.3(3). You need 3.0(3a) minimum. Please checkout the CM compatibility page:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm

HTH

Kev

3 REPLIES
Cisco Employee

Re: CRS 302 and CCM 3.3.3 JTAPI Problem

CRS 3.0(2) is not compatible with CM 3.3(3). You need 3.0(3a) minimum. Please checkout the CM compatibility page:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm

HTH

Kev

New Member

Re: CRS 302 and CCM 3.3.3 JTAPI Problem

If I read this correctly 3.0(3a) does not appear to be an upgrade from the software centre - all thats posted is the Service Packs, not a 3.0(3) upgrade. If that is so, does that mean I need to talk to my Cisco SE?

I'm running the Not for Resale CRS 3.0(2)

Cisco Employee

Re: CRS 302 and CCM 3.3.3 JTAPI Problem

Yes, it would be best to talk to your SE about this.

Kev

176
Views
0
Helpful
3
Replies
CreatePlease login to create content