/mcpConference on Monitored Call Expected result Action Monitoring Request is successful and the Session is started Monitoring Session is ended and C and C1 will be in direct simple call. Line_CallDevSpecific will be fired for B. dwparam1 = SLDSMT_MONITORING_ENDED, dwparam2 = LINEDISCONNECTMODE_INCOMPATIBLE Line_DevSpecific (dwparam1 = SLDSMT_MONITORING_TERMINATED, dwparam2 = TransactionID – xxxx, Dwparam3 = LINEDISCONNECTMODE_INCOMPATIBLE) will be fired for C LineInitialize Device A, B and C is Secure Device C1 is not Secure LineOpen on A,B,C and C1 A calls B;B answers the Call C issues LineDevSpecific (Start Monitoring) with B’s permanent lineID, silent monitoring mode and NoTone as input lineDevSpecifc (CCiscoLineDevSpecificSetStatusMsgs) with DevSpecificStatusMsgsFlag = DEVSPECIFIC_SILENT_MONITORING_TERMINATED on C C creates and Completes conference with C1 Supervisor Holds the Call Expected result Action Monitoring session is started Media will be stopped Media is started.Call on C will be INACTIVE (RIU Call) Monitoring session is Terminated. Line_CallDevSpecific will be fired for B dwparam1 = SLDSMT_MONITORING_ENDED, dwparam2 = LINEDISCONNECTMODE_INCOMPATIBLE Call on C1 will be Disconnected with new Cause Code LINEDISCONNECTMODE_INCOMPATIBLE Line_DevSpecific (dwparam1 = SLDSMT_MONITORING_TERMINATED, dwparam2 = TransactionID – xxxx, dwparam3 = LINEDISCONNECTMODE_INCOMPATIBLE) will be fired for C LineInitialize Device A, B and C is Secure Device C1 is Secure LineOpen on A,B,C and C1 C and C1 are shared lines A calls B; B answers the Call C issues LineDevSpecific (Start Monitoring) with A’s permanent lineID, silent monitoring mode and NoTone as input C holds the call C1 resumes the call Variant: C1 is not Secure and DEVSPECIFIC_SILENT_MONITORING_TERMINATED filter is enabled on C Recording Set up User is in Allow Recording group A is Customer Device Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 961 Message Sequence Charts Conference on Monitored Call