« Back to Cisco JTAPI Questions

CUCM JTapi not dispatching CiscoTermConnRecording* events on call recording

Combination View Flat View Tree View
Threads [ Previous | Next ]
CUCM JTapi not dispatching CiscoTermConnRecording* events on call recording
bib communications manager silent monitoring and recording recording
Answer
5/3/12 8:23 AM
hello,
 
When one is using Cisco BiB recording JTapi dispatches three events (or multiple of these three events) for each call which is recorded: CiscoTermConnRecordingStartEv, CiscoTermConnRecordingTargetInfoEv, CiscoTermConnRecordingEndEv.

I have found that CUCM JTapi sometimes doesn't dispatch all CiscoTermConnRecording* events as described in documents "Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager Release 7.1(3)" and "Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager Release 8.5(1)".

This behaviour has been observed in CUCM 7.1.x and 8.5.x.
 
Has anybody encountered this problem?
 
Is there a workaround for this problem?
 

I've put together a ZIP archive which includes the following logs: 
1. Our internal log with JTapi events - InternalLogWithCucmJTapiEvents.log,
2. JTapi logs with messages for the following log levels: DEBUG, INFORMATIONAL, WARNING - jtapi-logs/*.
 
ZIP archive is rather large (11M) so i've put it on a seperate server: http://161.53.58.103/CUCM-Recording-JTapiBug/CUCM-JTapiBug-Missing_CiscoTermConnRecording_Events.zip
 
Flag

RE: CUCM JTapi not dispatching CiscoTermConnRecording* events on call recor
Answer
5/3/12 8:51 AM as a reply to Vedran Zeljeznak.
I looked at the first 2 calls ( 526374/1, 8136328/10 ) and in both cases there is an active call and recording session active when call observer is added. Since recording started before call observer
is added you will not see a recording start event. CiscoTermConnRecordingTargetInfoEv indicates that this is an active recording session and you see a recording end event.
Recording start event will be seen if recording starts after the call observer is added. 
 
it seems that you are adding observer on the call. This is in addition to the call observer on the address/terminal. Call events will be delivered to all the call observers, so application may see multiple events depending on how the call observers are handled. I did not see any issues with the events.
Flag

RE: CUCM JTapi not dispatching CiscoTermConnRecording* events on call recor
Answer
5/3/12 9:27 AM as a reply to Mohan Potluri.
I looked at the first 2 calls ( 526374/1, 8136328/10 ) and in both cases there is an active call and recording session active when call observer is added. Since recording started before call observer is added you will not see a recording start event.


 
OK.
I'm curious, where in the log files can you tell that i've added an observer after the recording start event?


CiscoTermConnRecordingTargetInfoEv indicates that this is an active recording session and you see a recording end event.


 
I didn't recieve CiscoTermConnRecordingTargetInfoEv from JTapi emoticon for calls in question (526374/1, 8136328/10),
in InternalLogWithCucmJTapiEvents.log you can see which events i did recieve.
 

Recording start event will be seen if recording starts after the call observer is added. 
 
it seems that you are adding observer on the call. This is in addition to the call observer on the address/terminal. Call events will be delivered to all the call observers, so application may see multiple events depending on how the call observers are handled. I did not see any issues with the events.


 
OK.

Thanks for the quick reply.
Flag