McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 1479

↗ View in doc context
page
1479
source
cucm/v15/jtapi-dev-guide/jtapi-dev-guide.md
chunk_id
cucm::v15::jtapi-dev-guide::jtapi-dev-guide::1483

Events and Call Info Setup and Action Step 4- Check auto recording started on RD1. Check RD1 get CiscoTermConnRecordingStartedEv and CiscoTermConnRecordingTargetInfoEv. Check RD1 TermConnection.getCiscoRecorderInfo(): .getRecordingType() = CALL_RECORDING_TYPE_AUTOMATIC .getTerminalName() = central recorder device name .getAddress() = Recording profile (DN 2000) .getMediaForkingDeviceType() = CALL_RECORDING_MEDIA_FORKING_ DEVICE_TYPE_GW .getMediaForkingDeviceName() = SIP trunk device name - SIP GW .getProtocolReferenceGUID() = .getMediaForkingClusterID() = name of cluster1 Step 6- Recording retriggered on RD1. Check RD1 get CiscoTermConnRecordingEndedEv , CiscoTermConnRecordingStartedEv and CiscoTermConnRecordingTargetInfoEv. Check RD1 TermConnection.getCiscoRecorderInfo(): .getRecordingType() = CALL_RECORDING_TYPE_AUTOMATIC .getTerminalName() = central recorder device name .getAddress() = Recording profile (DN 2000) .getMediaForkingDeviceType() = CALL_RECORDING_MEDIA_FORKING_ DEVICE_TYPE_GW .getMediaForkingDeviceName() = SIP trunk device name - SIP GW .getProtocolReferenceGUID() = .getMediaForkingClusterID() = name of cluster1 Step 7- Check RD1 CiscoTermConnRecordingTargetInfoEv. Check RD1 TermConnection.getCiscoRecorderInfo(): .getRecordingType() = CALL_RECORDING_TYPE_AUTOMATIC .getTerminalName() = central recorder device name .getAddress() = Recording profile (DN 2000) .getMediaForkingDeviceType() = CALL_RECORDING_MEDIA_FORKING_ DEVICE_TYPE_GW .getMediaForkingDeviceName() = SIP trunk device name - SIP GW .getProtocolReferenceGUID() = Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1415 Message Sequence Charts Message Sequence Charts

Page 1479 diagram