nerdexam
Cisco

300-070 · Question #111

Which CUCM default global conference setting should be changed to ensure fraud prevention?

The correct answer is D. Drop Ad Hoc Conference. Enabling 'Drop Ad Hoc Conference' in CUCM closes a critical default gap that allows toll fraud via orphaned PSTN connections after the conference initiator disconnects.

Cisco Unified Communications Manager (CUCM)

Question

Which CUCM default global conference setting should be changed to ensure fraud prevention?

Options

  • AAdvanced Ad Hoc Conference Enabled.
  • BBlock OffNet to OnNet Transfer.
  • CMCU Conference Bridge Custom Layout Index.
  • DDrop Ad Hoc Conference.
  • EEnable Click-to-Conference for Third-Party Applications.

How the community answered

(47 responses)
  • A
    4% (2)
  • B
    2% (1)
  • C
    11% (5)
  • D
    83% (39)

Why each option

Enabling 'Drop Ad Hoc Conference' in CUCM closes a critical default gap that allows toll fraud via orphaned PSTN connections after the conference initiator disconnects.

AAdvanced Ad Hoc Conference Enabled.

Advanced Ad Hoc Conference Enabled controls whether users can expand an ad hoc conference by adding more parties, but does not address the orphaned PSTN connection fraud scenario.

BBlock OffNet to OnNet Transfer.

Block OffNet to OnNet Transfer prevents an external caller from being transferred back out to the PSTN, which is a separate fraud control unrelated to ad hoc conference behavior.

CMCU Conference Bridge Custom Layout Index.

MCU Conference Bridge Custom Layout Index is a cosmetic display configuration for MCU video conferences and has no security or fraud prevention relevance.

DDrop Ad Hoc Conference.Correct

By default, CUCM leaves an ad hoc conference active even after the initiating party hangs up, which allows a bad actor to bridge an expensive offnet PSTN number into a conference, disconnect, and leave the two parties connected at the organization's cost - a classic toll fraud scenario. Enabling 'Drop Ad Hoc Conference' ensures the conference is terminated when the controller disconnects, eliminating this fraud vector. Changing this from its default disabled state is a well-documented CUCM security hardening requirement.

EEnable Click-to-Conference for Third-Party Applications.

Enable Click-to-Conference for Third-Party Applications governs external application integration for conference initiation and does not relate to the ad hoc conference toll fraud scenario.

Concept tested: CUCM ad hoc conference toll fraud prevention default setting

Source: https://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-callmanager/200614-Toll-Fraud-Prevention-in-Cisco-Unified.html

Topics

#conference settings#fraud prevention#ad hoc conference#CUCM security

Community Discussion

No community discussion yet for this question.

Full 300-070 Practice