cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
227
Views
0
Helpful
0
Comments
cdnadmin
Community Member
This document was generated from CDN thread

Created by: Dan Coffey on 16-11-2009 01:32:29 PM
During the testing of a JTAPI application the CiscoRTPOutputStartedEv event intermittendly does not arrives.
 
This CiscoRTPOutputStartedEv event delivery failure happens intermittendly, once in 10-15 outbound calls.


When the remote phone answers the incoming call, the CUCM does send the CiscoRTPInputStartedEv event but the CUCM does not send the CiscoRTPOutputStartedEv event.
 
If the application fails to get the initial CiscoRTPOutputStartedEv event and I put the IP Communicator on hold, the application does receive the CiscoRTPOutputStoppedEv event and when I select the Resume button on the IP Communicator the application gets a CiscoRTPOutputStartedEv event and the RTP stream can be established.
 
JTAPI application places a call to a IP Communicator
CUCM: System version: 7.0.1.11000-2
Platform: XP SP3
Java: JRE 1.6.0_17
 
Any idea what's wrong?
 
Thanks,
 
Dan

Subject: RE: intermittend missing CiscoRTPOutputStartedEv event -
Replied by: David Staudt on 16-11-2009 03:23:44 PM
Are you counting on the event coming in a particular order (say, after Established?)  Note, the media events may not come in any particular order with the signaling events.
 
You can attach the JTAPI logs (set detailed level, all-types) here, and we can take a look.

Subject: RE: intermittend missing CiscoRTPOutputStartedEv event -
Replied by: Dan Coffey on 16-11-2009 04:22:12 PM
I've not done that before.
I've look at the docs.
I see a jtapi.ini file, do I need that?
I also see the com.cisco.services.tracing.* do I setup the LogFileTraceWriter
 
Can you point me at the right doc's.
 
Thanks,
 
Dan


Subject: RE: intermittend missing CiscoRTPOutputStartedEv event -
Replied by: David Staudt on 16-11-2009 06:44:03 PM
The easy way is to run the 'jtprefs' utility provided with the JTAPI install.  This file creates a jtapi.ini for you; then just make sure the jtapi.ini is in the path for your jtapi app.
 
LogFileTraceWriter is available for managing tracing within your application, but takes a bit more to implement - most just use the jtapi.ini settings.

Subject: RE: intermittend missing CiscoRTPOutputStartedEv event -
Replied by: Dan Coffey on 16-11-2009 07:13:31 PM
Do I have a bad installation?
 
Microsoft Windows XP [Version 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.

C:\Program Files\JTAPITools>jtprefs.bat

C:\Program Files\JTAPITools>cd C:\Program Files\JTAPITools\

C:\Program Files\JTAPITools>.\_jvm\bin\java com.cisco.services.jtprefs.jtprefsFrame

Exception in thread "main" java.lang.NoClassDefFoundError: com/cisco/services/jtprefs/jtprefsFrame

C:\Program Files\JTAPITools>

Subject: RE: intermittend missing CiscoRTPOutputStartedEv event -
Replied by: Mohan Potluri on 16-11-2009 10:17:05 PM
It seems like classpath is not setup correctly. Check the classpath by running - set CLASSPATH. You should see CLASSPATH=c:\windows\java\lib\jtapi.jar;
You can setup classpath manually by running 'set CLASSPATH=c:\windows\java\lib\jtapi.jar;.
 

Subject: RE: intermittend missing CiscoRTPOutputStartedEv event -
Replied by: Dan Coffey on 16-11-2009 11:29:51 PM
Thanks, I missed that.
 
Now I'm getting the application to startup with this error.
I can ping the CUCM.

C:\Program Files\JTAPITools>set CLASSPATH=c:\windows\java\lib\jtapi.jar;
C:\Program Files\JTAPITools>jtprefs.bat
C:\Program Files\JTAPITools>cd C:\Program Files\JTAPITools\
C:\Program Files\JTAPITools>.\_jvm\bin\java com.cisco.services.jtprefs.jtprefsFrame
getting setung enabled setting setting=false
 Update locale caught exception : java.io.FileNotFoundException: http://192.168.5.58:6970/jtapilocalechecksum

C:\Documents and Settings\Dan Coffey>ping 192.168.5.58
Pinging 192.168.5.58 with 32 bytes of data:
Reply from 192.168.5.58: bytes=32 time=19ms TTL=63
Reply from 192.168.5.58: bytes=32 time=19ms TTL=63
Reply from 192.168.5.58: bytes=32 time=18ms TTL=63
Reply from 192.168.5.58: bytes=32 time=20ms TTL=63
Ping statistics for 192.168.5.58:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 20ms, Average = 19ms
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Quick Links