Fraudulent calls are being made from Cisco Unity Connection. Which action prevents the calls from reaching the PSTN using SCCP integration?

Question

Options

• AChange the configuration of the routing rule.
• BChange the CSS of the voicemail port.
• CChange the Rerouting CSS on the trunk to Cisco Unity Connection.
• DRemove values from restriction table.

• A
  13% (7)
• B
  79% (41)
• C
  6% (3)
• D
  2% (1)

Explanation

In a SCCP integration between Cisco Unity Connection and CUCM, the Voice Mail Ports are registered as SCCP devices. These ports have a Calling Search Space (CSS) assigned in CUCM that determines what destinations they are permitted to dial. If the CSS on the Voice Mail Ports includes partitions that grant access to PSTN routes, fraudulent callers who gain access to Unity Connection's dial-out capability can place external calls. Changing the CSS of the voicemail ports to a restricted CSS - one that only allows internal extensions and not PSTN route patterns - prevents these fraudulent calls from ever reaching the PSTN. Option A (routing rule changes) affects Unity Connection internally but does not block the PSTN trunk at the CUCM level. Option C (Rerouting CSS on the trunk) affects inbound rerouting, not outbound restriction from voicemail ports. Option D (removing restriction table values) would loosen restrictions, making the problem worse.

No community discussion yet for this question.