McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 72

↗ View in doc context
page
72
source
voice-quality/troubleshooting/cisco-ios-vs-iosxe/cisco-ios-vs-iosxe.md
chunk_id
voice-quality::troubleshooting::cisco-ios-vs-iosxe::cisco-ios-vs-iosxe::97

Two-Stage Dialing If the incoming POTS dial-peer is configured with no direct-inward-dial, the router or gateway enters the digit collection mode (digits are collected inband). Outbound dial-peer matching is done on a digit-by-digit basis. The router or gateway checks for dial-peer matches after the device has received each digit, and then routes the call when a full match is made.

Configuration Example

! dial-peer voice 1 pots incoming called-number 8675309 voice-port 0/0/0 no direct-inward-dial !

Blocking Calls Each protocol handles call blocking a bit different. Most protocols can make use of the translation-rule reject pattern which blocks based on a digit string. If an administrator wants to still apply an inbound translation- profile for normal digit manipulation, but not block any numbers within, there is an option of implementing a call-block using the call-block translation-profile command.

! voice translation-rule 164 rule 1 reject /8675309/ ! voice translation-profile CALLBLOCK translate calling 164 ! dial-peer voice 1 pots desc INCOMING VOICE-PORT with BLOCK translation-profile incoming ANOTHER call-block translation-profile incoming CALLBLOCK call-block disconnect-cause incoming invalid-number incoming called-number . port 0/0/0:23 !

Gateway#test voice translation-rule 164 8675309 8675309 blocked on rule 1

Within E1 R2 there exists the ability for an administrator to block Collect Calls. This is mainly seen and employed in Brazil deployments, but can be configured via any cas-custom group. The two options are: