Malicious Call Trace feature operation

Last Updated : Jun 06, 2019 |
Prolog information
During an active call, if the user presses the MCT key, Device Adapter generates the corresponding SIP FNU for the malicious call trace feature. The FAC is processed at Communication Manager by using transfer handling.
To specify the MCT deactivation FAC and release all MCT resources, at least one non-SIP endpoint is required as an MCT controller. This non-SIP endpoint can be a Communication Manager H.323 or digital endpoint. For more information about the configuration and operation of the H.323 or digital endpoint, see the Avaya Aura® Communication Manager Feature Description and Implementation guide.
MCT deactivation FAC is mandatory.