JTAPI - stopRecording Function?

[Doug.Brinkmeier]

Hi,

We are currently using the ciscoTerminalConnection -> startRecording function to fork a media stream and start a recording to MediaSense through CUCM.  This is all working as expected, and recordings are coming through fine.

However, I'm struggling a bit now, trying to find a way to stop the recording.  We're using Media Sense 8.5, and the MediaSense API is failing for some reason when I call stopRecording - without any detail in the response (it just says "API call failed, please verify the deviceRef...", but inputs are fine. I can query other active recordings and find it on that same deviceRef).  My best guess is that the originator (i.e. CUCM) is the only one allowed to stop the recording.  This seems a bit strange to me, because telling MediaSense to stop recording - since it's actually doing the recording - it should definitely know how to not continue to record - even if the stream is still coming in.

Anyway, assuming this is true, and I need to call JTAPI to stop the recording, any hints at where I should look for this API call?  Intuitively, it seems like it should have been "stopRecording" - or "terminateRecording" on the same ciscoTerminalConnection object.  But I don't see anything like that.  Any advice/help would be very much appreciated.

Thanks in advance!

[Doug.Brinkmeier]

I should also mention that I am using JTAPI 8.6.  I see in version 10.0, this function is available.  Is there an alternative in 8.6?

[Doug.Brinkmeier · Accepted solution]

Well, looks like I found the answer to my own question.  Not sure if I still get "points" for it or not?

I was able to cast the object that was returned from the call event to a MediaTerminalConnection.  It came back as just a TerminalConnection in all of the doc, and I had been casting it to CiscoTerminalConnection in order to startRecording(), but that Interface didn't have a stopRecording() for some reason.  So, to invoke stopRecording, I just cast it to MediaTerminalConnection, and invoked stopRecording from that interface.  I didn't realize the object returned in the event implemented both.