McDewey

Recording Scenario on Non-Secure Call Using Secure Recording Profile/Device Expected result Action Recording Request will Fail with existing error code LINEERR_OPERATIONFAILED Note Recording Failed as the Recording Device Security Capabilities doesn’t meet or exceed the Security status of B LineInitialize Device A and B is Secure Device C is Not Secure LineOpen on A,B and C A calls B;B answers the Call A to B call is Secure B issues LineDevSpecific (Start Recording, BothLocalAndRemote) for A-B call Recording Scenario When Agent Holds the Call Expected result Action Recording Session is started Line_CallDevSpecific (dwparam1 = RecordingStarted) will be fired for B Call between B and C will be Non-Secure Media between B and C is ended Line_CallDevSpecific (dwparam1 = RecordingEnded) will be fired for B Recording Session will be started Media between B and C is started Line_CallDevSpecific (dwparam1 = RecordingStarted) will be fired for B Recording Session will be started LineInitialize Device A and B is not Secure Device C is Secure LineOpen on A and B A calls B;B answers the Call A to B call is non Secure B issues LineDevSpecific (Start Recording, BothLocalAndRemote) for A-B call LineHold on Call on B B resumes the Call Note Recording option – Automatic Call Recording Enabled B Resumes the Call Recording and Monitoring This section describes Silent Monitoring and Recording on Agent Call in Secure Mode. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 964 Message Sequence Charts Recording Scenario on Non-Secure Call Using Secure Recording Profile/Device