Malicious Call Identification works by setting a specific flag in the CDR records. These flagged calls can be reported on, attaining whatever information is necessary to take action. This document cover the configuration procedure to Identify the Malicious Calls using CDR (Call detail record).
What is Malicious Call Identification?
Whenever a User receives a disturbing call, malicious call identification (MCID) feature allows a user to report a call of a malicious nature by requesting that Cisco Unified Communications Manager identify and register the source of an incoming call in the network.
Malicious call identification (MCID), an internetwork service, allows users to initiate a sequence of events when they receive calls with a malicious intent. The user who receives a disturbing call can invoke the MCID feature by using a softkey or feature button while the user is connected to the call. The MCID service immediately flags the call as a malicious call with an alarm notification to the Cisco Unified Communications Manager administrator. The MCID service flags the call detail record (CDR) with the MCID notice and sends a notification to the off-net PSTN that a malicious call is in progress.
Below Configuration procedures tested on Cisco Unified Communications Manager 8.5(1)
1. Navigate to the Service Parameters configuration page (System | Service Parameters).
2. Select -> Server
3. Select -> Cisco CallManager Service
4. Under the System section, select True for CDR Enabled Flag:
5. Click -> Save
6. Next navigate to the Serviceability page by clicking on Cisco Unified Serviceability
7. Click -> Go
8. Navigate to the Alarm configuration page (Alarm | Configuration)
9. Select -> Server
10. From the Service Group drop-down select -> CM Services:
11. From the Service drop-down, select -> Cisco CallManager
12. Click -> Go
13. Check Enable Alarm under the Local Syslog section.
14. Under the same section, select Informational from the Alarm Event Level drop-down.
15. If using multiple nodes, check Apply to All Nodes
16. Click -> Save
Now the service has been enabled, we can configure a softkey template with the appropriate button and assign it to a device.
1. Navigate back to the Unified CM Administration page
2. Navigate to the Softkey Template configuration page (Device | Device Settings | Softkey Template).
3. Click -> Add New
4. Select Standard User from the Create a softkey template based on drop-down.
5. Click -> Copy
6. Specify a Name
7. Specify a Description
8. Click -> Save
9. From the Related Links drop-down, select Configure Softkey Layout:
10. Click -> Go
11. From the Select a call state to configure drop-down, select Connected
12. Move the Toggle Malicious Call Trace (MCID) to the Selected Softkeys field, in the desired position:
13. Click -> Save
At this point we can assign the softkey template we just created to the appropriate devices. After selecting the MCID softkey from the phone, a CDR flag is set for malicious calls. After the button has been selected, we can search the CDR logs for the flag, and determine and provide the information necessary for the authorities to take appropriate action.
I'd like my C40 on 7.3.3 to load a camera preset when it starts up. I've got a startup script that works when I click Run in the web interface startup scripts page. Unfortunately, application.log seems to show that it runs the script right before pairing ...
hi, we have a cucm and CMS on the central site and we have sx 80 on the central site and 9 other sites , other sites have 6 or 2 mbps, the problem is that the video quality isn't good with a 3 way video, so i'm pretty sure if it's a 10 way video...
Call flow:Ingress GW -> CVP -> Label 20480(in routing script) -> CVP -> CUBE If i send call asis, then CUBE answer "486 Busy here" but CVP send to IngressGW "302 Moved Temporarily"If i modify Remote-Party-ID to "--CVP <sip:aaa@bbb>"...
Hi,I have just upgraded an 11.5 deployment of CUCM, IM & P and Unity Connection servers from 11.5 to 12.5.The operating system used by the virtual machines changes from Red Hat Linux to CentOS 7.I have tried to change the guest operating system on the...
If a remote destination is calling in to another desk phone on the same cluster (PBX) the caller ID from the attached directory number. If you call to another cluster it will just show "WIRELESS CALLER". I am wondering if there is any solution so all clus...