McDewey

Silent Monitoring Scenario on Non-Secure Call From Supervisor Which Is Secure Expected result Action Call between B and C will be Non-Secure No SRTP Events will be fired CallAttributeInfo in devspecific part of LineCallInfo of C will contain B’s info security Indicator = MEDIA_NOT_ENCRYPTED CallAttributeTye = CallAttribute_SilentMonitorCall_Target Address = B’s DN, Partition = B’s Partition Device Name = B’s Device Name Transaction ID = XXXX CallSecurityStatus = Not Authenticated LineInitialize. Device A and B is not Secure Device C is Secure LineOpen on A,B and C A calls B;B answers the Call A to B call is non Secure C issues LineDevSpecific (Start Monitoring) with B’s permanent lineID, silent monitoring mode and NoTone as input. LineGetCallInfo on C Silent Monitoring Scenario on Secure Call From Supervisor Which Is Non-Secure Expected result Action • New Call will be Fired on C. • Call on C will go to Disconnected State • Request fails with new Error Code LINEERR_SECURITY_CAPABILITIES_MISMATCH. Note Request fails as the Supervisor Security Capabilities doesn’t meet or exceed the Security status of Agent (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 C issues LineDevSpecific (Start Monitoring) with B’s permanent lineID, silent monitoring mode and NoTone as input. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 955 Message Sequence Charts Silent Monitoring Scenario on Non-Secure Call From Supervisor Which Is Secure