Guest

Preview Tool

Cisco Bug: CSCur75764 - MCID does not work on STCAPP integration with CUCM

Last Modified

Feb 06, 2016

Products (1)

  • Cisco VG Series Gateways

Known Affected Releases

15.1(1.2)

Description (partial)

Symptom:
MCID(Malicious Call Identification) feature is not working for VG224 which has SCCP integration with the CUCM.
Even though we see the GW generate the MCID as follows:
*Mar  1 00:28:38.163: STCAPP:MCID feature is activated, *fid=9
*Mar  1 00:28:38.163: 2/0   : stcapp_handle_feature_id
*Mar  1 00:28:38.163: 2/0   :     Sending MCID softkeyevent (27)
*Mar  1 00:28:38.163: 2/0   : stcapp_send_softkey_event
*Mar  1 00:28:38.163: 2/0   :     Sending dcDeviceSoftKeyEvent(MaliciousCallID: event=27) for device id: 3, call_ref: 20605481

CUCM does not recognize the MCID because we see the following in the CUCM traces:
1.    Incoming call from 0293527000 to 6165. Here 6165 is an SCCP endpoint for CCM with device name as ANB7487A4241402.
2.    6165 answers the call and media is established.
3.    Incoming Transfer request from 6165 and media is disconnected.
4.    CUCM waits for digits for the new call (second leg of transfer).
5.    Incoming MCID event from 6165.
-      Here CUCM ignores this MCID event since this event was triggered from a call which is not active and there is no destination side and the calling party is 6165 which had initiated MCID event. Ideally CUCM expects MCID event on the active call (the first call).
6.    Second call is dropped.
7.    First call is dropped.
It seems like the hook flash initiated transfer event and due to that the MCID event was notified on second call leg which is ignored by CUCM. For MCID to work, CUCM would need the MCID event on the active call without involving transfer.

This is a limitation of the GW(VG224).

Conditions:
Inbound call to Analog phone on VG224 should be able to do the following:
1.       When a phone (let's just say it's user A) receives an incoming call (from user B), and answers it. The user A is in an active basic call now.
2.       The user A presses hookflash, and "hears dialtone".
3.       Then user A dials "***".
4.       The MCID SK event will be sent.
5.       Then user A presses hookflash again to come back to the original basic call with user B.

This should generate the MCID even as follows:
*Mar  1 00:28:38.163: STCAPP:MCID feature is activated, *fid=9
*Mar  1 00:28:38.163: 2/0   : stcapp_handle_feature_id
*Mar  1 00:28:38.163: 2/0   :     Sending MCID softkeyevent (27)
*Mar  1 00:28:38.163: 2/0   : stcapp_send_softkey_event
*Mar  1 00:28:38.163: 2/0   :     Sending dcDeviceSoftKeyEvent(MaliciousCallID: event=27) for device id: 3, call_ref: 20605481
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.