McDewey

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

Page 789

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

TSP Message to App Data Party CallerID = D / CalledID = A / ConnectedID = A mod Calling = D / mod Called = A / mod Connected = A C1: LINE_DEVSPECIFIC(SLDSMT_RECORDING_STARTED, 0, 0) LINE_DEVSPECIFIC(SLDSMT_LINECALLINFO_ DEVSPECIFICDATA, SLDST_CALL_ATTRIBUTE_INFO, 0) CallAttributeTye = ‘Recording’ C1’s CCMCallId Address = R’s DN, Partition = R’s Partition, DeviceName = R’s DeviceName Chaperone C1 starts recording to recording device R Forced Authorization and Client Matter Code Scenarios Manual Call to a Destination That Requires an FAC The following table describes the message sequences for the Forced Authorization and Client Matter Code scenario of Manual Call to a Destination that requires an FAC. Preconditions Party A is Idle. Party B requires an FAC. The scenario remains similar if Party B requires a CMC instead of an FAC. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 757 Message Sequence Charts Forced Authorization and Client Matter Code Scenarios

Page 789 diagram