350-801 · Question #284
A company has an excessive number of call transfers to local and long-distance PSTN from Cisco Unity Connection voicemail. Which action in the Cisco Unity Connection restriction table resolves this…
The correct answer is B. Block PSTN patterns on Default Transfer, Default Outdial, and Default System Transfer. To prevent excessive call transfers to the PSTN from Cisco Unity Connection voicemail, configure restriction tables to block PSTN dialing patterns for transfer and outdial features.
Question
A company has an excessive number of call transfers to local and long-distance PSTN from Cisco Unity Connection voicemail. Which action in the Cisco Unity Connection restriction table resolves this issue?
Options
- AImplement password complexity on voicemail boxes to prevent accounts from being
- BBlock PSTN patterns on Default Transfer, Default Outdial, and Default System Transfer.
- CCreate a custom restriction table *********** and block it.
- DCreate a custom restriction table ??????????? and block it.
How the community answered
(26 responses)- B85% (22)
- C4% (1)
- D12% (3)
Why each option
To prevent excessive call transfers to the PSTN from Cisco Unity Connection voicemail, configure restriction tables to block PSTN dialing patterns for transfer and outdial features.
Implementing password complexity enhances security by preventing unauthorized access to voicemail boxes but does not directly restrict legitimate users or attackers who gain access from using transfer/outdial features to call the PSTN.
Cisco Unity Connection uses restriction tables to control which phone numbers can be dialed for call transfers and outdialing from voicemail. By configuring the 'Default Transfer', 'Default Outdial', and 'Default System Transfer' restriction tables to block local and long-distance PSTN patterns, administrators can effectively prevent unauthorized or excessive calls to the PSTN originating from voicemail boxes.
Creating a custom restriction table with `***********` and blocking it is overly broad and does not specify which call handlers or features it applies to; also, `*` can have different wildcard meanings, making it ambiguous.
Creating a custom restriction table with `???????????` and blocking it, while blocking 11-digit numbers, is still too general and does not specify application to the relevant transfer/outdial features, making it less precise than targeting PSTN patterns on default tables.
Concept tested: Cisco Unity Connection restriction tables for call transfer
Source: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/15/call_handler_guide/b_15cuc_call_handler_guide/b_15cuc_call_handler_guide_chapter_010.html#concept_D62C92C3D32F42D59492190A5F0C2C82
Topics
Community Discussion
No community discussion yet for this question.