Service Taps doesn't start

[f.gouger]

Hi,

I have a CCM 3.3.2(c) with BAT 4.4(2),CRS 3.0(3a) and JTAPI 1.4(2.3) My Subsystem are IN SERVICE but when I try to start the service TAPS in the services he start for 5 seconde and return to stop. I try to erase and re install the CRS and BAT but that didn't help. Did somebody have a answer for me.

[mowour · Accepted solution]

Hi,

It looks like you are running into CSCeb20345 -- TAPS service fails to start

There's a workaround detailed in the Release Notes.

Regards,

Mike.

[f.gouger]

thanks , the workaround resolved my problem

[nmaharaj2]

I cannot access bug CSCeb20345 from the bug toolkit

Can someone post the release notes

[dugrant]

Symptom:

TAPS service failed to start due to problem with JRE version.

if java.exe is run from the JRE Version 1.3.1 taps will not start.

if JRE 1.4.1 is used then it runs fine.

Condition:

Running ES 2.2.5 with CCM 3.3.2 or CCM 3.1.4b

or

Running CM 3.3.3Sr1 with CRS 3.1.1Sr1

Workaround:

Modify the wrapper.propertie file under: C:\Ciscowebs\bat\TAPS\TapsService\

change the java path from:

wrapper.javabin=$(wrapper.taps_home)\bin\java.exe

to:

wrapper.javabin=C:\Progra~1\Cisco\JRE\j2re1.4.0_01\bin\java.exe

# ABOVE PATH SHOULD POINT TO THE JRE INSTALLED BY CALLMANAGER

# IF JRE IS INSTALLED IN A PATH, OTHER THAN THAT INDICATED ABOVE

# THEN REPLACE ABOVE PATH WITH ACTUAL JRE INSTALL LOCATION

Or simply replace the wrapper.properties

under C:\Ciscowebs\bat\TAPS\TapsService\

with following:

#THIS FILE IS REQUIRED TO RUN TAPS SERVICE.

#DO NOT MODIFY OR DELETE CONTENTS.

wrapper.bat_home=c:\ciscowebs\bat

wrapper.taps_home=$(wrapper.bat_home)\taps

wrapper.tomcat_home=$(wrapper.taps_home)

wrapper.server_xml=$(wrapper.taps_home)

wrapper.window_home=C:

wrapper.stdout=$(wrapper.taps_home)\TAPSService\TAPSSrvOutPut.log

wrapper.stderr=$(wrapper.taps_home)\TAPSService\TAPSSrvError.log

#wrapper.javabin=$(wrapper.taps_home)\bin\java.exe

wrapper.javabin=C:\Progra~1\Cisco\JRE\j2re1.4.0_01\bin\java.exe

wrapper.class_path=$(wrapper.taps_home)

wrapper.class_path=$(wrapper.taps_home)\bat.jar

wrapper.class_path=$(wrapper.window_home)\winnt\java\lib\DirUser.jar

wrapper.class_path=$(wrapper.window_home)\winnt\java\lib

wrapper.startup_class=TAPS

wrapper.cmd_line=$(wrapper.javabin) -classpath $(wrapper.class_path)

$(wrapper.startup_class)

[nmaharaj2]

thanks, this seems to work

[simon.machielse]

Hi,

I'm running into the same problem. All my Services are running except the JTAPI Subsystem.

the NT CRA Engine and the TAPS Services are started.

I've changed the wrapper.properties settings.

CCM 3.3.3sr2

BAT 4.4.3

ES 3.1.1

JTAPI 1.4.3.16

Any suggestions anyone?

Simon

[jeff.hillman]

In order for the JTAPI subsystem to start you need to confirm the following:

1) You have a JTAPI user created that is marked to run CTI Apps, and has been associated with the CTI Route Point and CTI Ports you created in CallManager.

2) The CTI Ports have consecutive extensions (2001, 2002, 2003, etc)

3) The user account and its correct password have been entered into the JTAPI configuration screen on the CRA along with the IP Address(es) of the CallManager(s)

4) In CRA, you have created a CTI Port Group and associated the CTI ports you created. This is under the JTAPI Subsystem menu.

5) In CRA, you have created a JTAPI trigger, associated it with the TAPS application, the CTI Route Point you created, and the Port Group you created. You also select the language and the number of sessions here.

To see why the JTAPI service is failing, you can set the traces to report any errors by going to Engine-->Trace Configuration and checking the 'Debugging' box next to SS_TEL. Then stop and start the engine and look at the logs.

Hope this helps.

Jeff.

[simon.machielse]

Hi Jeff,

Thanx for the reply. Well I've got the Service running, it was a configu mismatch somewhere.

But now when I dial into my CTI Route Point the call is hung up after 2 or 3 seconds. I've created 2 CTI Ports 1001 & 1002 they register normally also the CTI Route Point 1000 is registered.

I can see the following in the trace of the CRA:

295: okt 31 11:22:51.890 CET %MIVR-APP_MGR-3-TASK_ABORTED:Application task aborted: Application=App[name=taps,type=Cisco Script Application,id=1,desc=taps,enabled=true,max=1,valid=true,optional=[script=TAPS.aef,last.modified=1067594807538]],Application Trigger=ContactApplicationTrigger[time=1067595771843,contact=JTAPICallContact[id=1,type=Cisco JTAPI Call,implId=12/1,active=true,state=CALL_ANSWERED,inbound=true,handled=false,locale=en_US,aborting=false,app=App[name=taps,type=Cisco Script Application,id=1,desc=taps,enabled=true,max=1,valid=true,optional=[script=TAPS.aef,last.modified=1067594807538]],task=19000000002,session=Session[id=0x60db88402,parent=null,active=true,state=SESSION_IN_USE,time=1067595771796],seqNum=0,time=1067595771796,cn=1000,dn=1000,cgn=91450,ani=null,dnis=null,clid=null,atype=DIRECT,lrd=null,ocn=1000,odn=null,uui=null,aniii=null,ced=null,route=TR[num=1000],port=TP[type=Cisco CTI Port,id=0,implId=1001,active=true,state=IN_USE],aborting=false,transferring=false,disconnecting=false]],Task id=19.000.000.002,Task Class=class com.cisco.app.impl.WFWorkflowAppDebugTaskWrapper,Exception=com.cisco.channel.ChannelUnsupportedException: com.cisco.dialog.PlayPromptDialog is not supported

Does this say anything to you?

thanx in advance,

Simon

[mdeloach]

You need to add a dialog group and assign it to the JTAPI trigger.

I ran into the same error while moving TAPS to a different server to resolve a delay during the 'Welcome to TAPS' greeting.