McDewey

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

Page 100

↗ View in doc context
page
100
source
cucm/v15/tapi-dev-guide/tapi-dev-guide.md
chunk_id
cucm::v15::tapi-dev-guide::tapi-dev-guide::87

However, for call scenarios where the devices involved do not directly register with Unified Communications Manager, phone-based recording is not possible. This situation excludes the calls handled by the mobile agents from being recorded. In addition, the recording of mobile calls becomes increasingly mandatory by regulations in different jurisdictions, or becomes the essential business requirement for call centers or enterprises. These requirements call for a recording solution that does not rely on media forking from the endpoints. The enhancements for the recording solution allow an external call that goes through a Cisco voice gateway to be recorded by having the voice gateway direct the two media streams to a voice recorder. This solution uses the existing CCiscoLineDevSpecificStartCallRecording and CCiscoLineDevSpecificStopCallRecording APIs to start and stop a user control recording session. Automatic recording is also configured on the line. There is an additional option to specify the voice gateway, or the IP phone as the prefered recording resource on a particular line. In addition, the CTI Remote Device that was introduced in Unified Communications Manager Release 9.0 now supports recording through a gateway enabled for recording. If there is a recording gateway between the CTI Remote Device and the remote-destination where the call was routed, the recording can be started at the CTI Remote Device. If there is a recording gateway between the caller and the CTI Remote Device, the recording can also be started at the CTI Remote Device. You can also configure the line(s) on the CTI Remote Device to support Automatic or Selective Recording. The CTI Remote Device can only use a gateway to route the media. CTI port calls can be captured using the Network Recording feature available in Unified Communications Manager Release 10.0(1). The call media must pass through at least one recording-enabled gateway to be recorded. A typical use case: An external call to a CTI Port softphone. The Recording Media Source for the CTI Port is always gateway-preferred. Interface Changes • Recording Failure Event, on page 416 • LINECALLINFO, on page 324 • LINEDEVCAPS, on page 321 Message Sequences Gateway Recording, on page 769 Backward Compatibility Due to a design change to support Gateway Recording, the same recording may be stopped and restarted due to a feature invocation that was not seen in prior releases. Previously, this stop and start of the recording was only seen when the call being recorded is put on hold and then resume. In this release, this can happen when the party on the other end of the call being recorded changes. Take the following example: 10.0 Pre-10.0 Action A calls B and B answers App receives SLDSMT_RECORDING_STARTED event at A App receives SLDSMT_RECORDING_STARTED event at A TSP application issues CCiscoLineDevSpecificStartCallRecording at A. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 68 Features Supported by TSP Gateway Recording