McDewey

Conference on Monitored Call Expected result Action Monitoring Request is successful and the Session is started Conference is created with A , C and C1 Line_CallDevSpecific (dwparam1 = DevSpecifcData, dwparam2 = OverallSecurityStatus) will be fired to C1. Call Security Status = Not Authenticated SRTP info will not be available CallAttributeInfo in devspecific part of LineCallInfo of B will contain CFB’s info. CallAttributeTye = CallAttribute_SilentMonitorCall Call Security Status = Not Authenticated SRTP info will not be available Security Indicator = MEDIA_NOT_ENCRYPT 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 = Not Authenticated SRTP info will not be available Security Indicator = MEDIA_NOT_ENCRYPT 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 = Not Authenticated LineInitialize. Device A, B and C is not Secure Device C1 is Secure LineOpen on A,B,C and D A calls B;B answers the Call C issues LineDevSpecific (Start Monitoring) with B’s permanent lineID, silent monitoring mode and NoTone as input C creates conference with C1 LineGetCallInfo on B LineGetCallInfo on C LineGetCallInfo on C1 Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 960 Message Sequence Charts Conference on Monitored Call