McDewey

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

Page 46

↗ View in doc context
page
46
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::60

Numbering Type With ISDN Q.931 integrations there exists the ability to match a dial-peer based on the calling or called number as well as the specific ITU number type from the Q.931 SETUP messaging. This is configurable via the numbering-type command on a VOIP or POTS dial-peer. Numbering-type cannot be used alone and must be used in conjunction with destination-pattern, answer-address, or incoming called- number. This means both the condition of the inbound / outbound matching statement and the number type must match to be a success for the dial-peer to be considered for inbound and outbound call routing. Numbering-match can be thought of as a dial-peer filtering mechanism rather than a matching mechanism. This is because a dial-peer with and without a numbering type command applied are considered the same default preference weight if no administrator preference is applied. This is unlike carrier-id which, when applied to a dial-peer along side other matching mechanism, adds preference to that dial-peer over others if both conditions are true. Numbering Type matching was added in Cisco IOS 12.0(7)XR1 and is present in all Cisco IOS XE releases. With the decline of traditional POTS ISDN lines being deployed in collaboration networks the use of numbering-type is rarely seen in modern deployments. Command Syntax: Cisco IOS Voice Command Reference - K through R Configuration Example This dial-peer can match 4085150000 through 4085159999 only if the ISDN number type is National.