McDewey

Basic Silent Monitoring Scenario in Secure Mode Expected result Action Silent Monitored Call is created in Secure Mode Line_CallDevSpecific (dwparam1 = MonitoringStarted) will be fired for B. New call will be fired on C Line_CallDevSpecific(dwparam1 = DevSpecifcData, dwparam2 = CallAttributeInfo) will be fired to B and C Line_CallDevSpecific(dwparam1 = DevSpecificData, dwparam2 = SLDST_SRTP_INFO, dwParam3 = MEDIA_ENCRYPT_KEYS_AVAILABLE) will be fired for the call on C. SRTP info will be available CallAttributeInfo in devspecific part of LineCallInfo of B will contain C’s info. CallAttributeTye = ‘CallAttribute_SilentMonitorCall’ Address = C’s DN, Partition = C’s Partition Device Name = C’s Device Name Transaction ID = XXXX Call Security Status = Encrypted SRTP info will be available CallAttributeInfo in devspecific part of LineCallInfo of C will contain B’s info CallAttributeTye = CallAttribute_SilentMonitorCall_Target Address = B’s DN, Partition = B’s Partition Device Name = B’s Device Name Transaction ID = XXXX CallSecurityStatus = Encrypted LineInitialize. Device A,B and C is Secure LineOpen on A,B and C A calls B;B answers the Call A to B call is Secure C issues LineDevSpecific (Start Monitoring) with B’s permanent lineID, silent monitoring mode and NoTone as input. LineGetCallInfo on B LineGetCallInfo on C Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 953 Message Sequence Charts Basic Silent Monitoring Scenario in Secure Mode