The MCT deactivation call flow on Avaya Aura® is similar to the call flow on CS 1000. The difference is that CS 1000 does not use Flexible Feature Codes (CS 1000 FAC).
-
The MCT controller dials the FAC configured for MCT deactivation.
Deactivation frees any blocked resources that were used for MCT.
-
When all parties left the call, the system disconnects the MCT call recorder.
When using a SIP endpoint, an agent does not need to remain on the call for the monitoring and recording to continue.
If the MCT controller does not deactivate MCT the call recorder keeps recording the call.
An agent cannot make a second MCT or, if using Device Adapter, an emergency call until the controller releases the resources that are used for MCT.
A Communication Manager MCT controller cannot be a SIP device. Therefore, SIP devices does not have keys to activate or deactivate MCT. An MCT controller must use a H.323 endpoint. The activation and deactivation functionality can be configured on that endpoint using the H.323 attendant console.
