When a user activates the mct-act button, the system notifies the potential MCT controllers. A potential MCT controller is a station or an attendant that has an mct-contr button.
Note:
The mct-contr button can only be administered on H.323 or DCP stations or attendants. This functionality is not SIP compatible. If no mct-controller is administered, then the SNMP trap is generated to record the MCT activation.
To notify the potential MCT controllers, the system:
The user who presses the mct-contr button first becomes the MCT controller of the call. The system stops alerting other potential MCT controllers.
The user of the MCT controller must continue to press the mct-contr button to see the entire MCT information.
Depending on the origin of the call, the system displays:
The calling number if the call originates inside the system or on the same node within a Distributed Communications System (DCS) network.
The calling number if the call originates outside the system and an Integrated Services Digital Network (ISDN) or SIP calling number identification is available on the incoming trunk.
The location of the incoming trunk for all other calls. In this case, the user must call the connecting server to get more information about the malicious call.