McDewey

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

Page 34

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

Configuration Example With this example, the called number is 8675309. This matches dial-peer 1234 based on the incoming called-number statement. This dial-peer is configured with a dial-peer group that states the call can now route out dial-peers 2, then 3, and finally 1 if dial-peer 2 fails. This the gateway so now try to route the call out dial-peer 2 as it has been explicitly told via the dial-peer group that is what it can do. Note: The destination-pattern on dial-peer 1, 2, and 3, is not the called number of 8675309. This is fine and the call still routes without an issue. Remember, as discussed in the dial-peer states section, you need something/anything configured as an outbound matching statement. In this case, destination pattern is only to bring the dial-peer into an Up operational state, and the digit-string of that command is never evaluated. It is recommended to configure a pattern like destination-pattern AAAA as this is a valid destination-pattern. Since this is technically a valid dial-peer, other calls could match it. Thus the AAAA digit-string means that you can never use it for anything other than a specific scenario involving a dial-peer group as the likelihood of a call coming in for AAAA is very, very low.

Image 1 from page 34