Can someone tell me why POTS dial-peer 1 has been matched here on the Inbound call leg? This call is an inbound call from the PSTN onto the FXO port (0/0/0) of this voice gateway router. The calling number as per dial-peer debugging below is 07974266928. The called number is 7950. The dial-peer 1 config is below.
dial-peer voice 1 pots
supervisory disconnect dualtone mid-call
supervisory custom-cptone gb-custom
output attenuation 0
playout-delay maximum 100
timeouts initial 5
timeouts call-disconnect 1
timeouts ringing infinity
timeouts wait-release 1
timing percentbreak 50
timing guard-out 1000
timing sup-disconnect 90
timing pulse-inter-digit 500
connection plar opx 7950
caller-id alerting dsp-pre-allocate
Rule 1 ^.% 9
Feb 7 10:24:55.822 GMT: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=07974266928, Called Number=, Voice-Interface=0x653BCBC0,
When the Cisco IOS router or gateway receives a call setup request, a dial peer match is made for the incoming call in order to facilitate routing the call to different session applications. This is not a digit-by-digit match, rather the full digit string received in the setup request is used to match against configured dial peers.
Note: The maximum number of dial peers that can be configured on a Cisco IOS gateway depends on the available memory (DRAM). Each dial peer consumes approximately 6KB of memory. Make sure that you have at least 20% of the total memory reserved for other CPU processes. If the dial peers are used for call routing, a larger number of dial peers will add to the delay to route a call. This will be significant as the Cisco IOS voice stack looks through dial peers from the top down, similar to an Acess Control List.
The router or gateway matches the information elements in the setup message with the dial peer attributes to select an inbound dial peer. The router or gateway matches these items in this order:
Called number (DNIS) with the incoming called-number command
First, the router or gateway attempts to match the called number of the call setup request with the configured incoming called-number of each dial peer. Because call setups always include DNIS information, it is recommended to use the incoming called-number command for inbound dial peer matching. This attribute has matching priority over the answer-address and destination-pattern commands.
Calling Number (ANI) with the answer-address command
If no match is found in step 1, the router or gateway attempts to match the calling number of the call setup request with the answer-address of each dial peer. This attribute can be useful in situations where you want to match calls based on the calling number (originating).
Calling Number (ANI) with the destination-pattern command
If no match is found in step 2, the router or gateway attempts to match the calling number of the call setup request to the destination-pattern of each dial peer. For more information about this, see the first bullet in the Dial Peer Additional Information section of this document.
Voice-port (associated with the incoming call setup request) with configured dial peer port (applicable for inbound POTS call legs)
If no match is found in the step 3, the router or gateway attempts to match the configured dial peer port to the voice-port associated with the incoming call. If multiple dial peers have the same port configured, the dial peer first added in the configuration is matched.
If no match is found in the first four steps, then the default dial peer 0 (pid:0) command is used.
The Cisco IOS router or gateway matches only one of these conditions. It is not necessary for all the attributes to be configured in the dial peer or that every attribute match the call setup information. Only one condition must be met for the router or gateway to select a dial peer. The router or gateway stop to search as soon as one dial peer is matched.
The longest prefix matching criteria applies while each step is performed. At each step, if multiple matches are found, the one with the longest explicit match is chosen. This example helps clarify this concept:
Assume the incoming called number (DNIS) is "81690". Dial peer 2 is matched.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.