Important testing commands on the router

-
To simulate test outbound call on the router-
R1#show dialplan number <test number>

This command will show you which dialpeer will be hit if this number is dialed. Example-
RTR1#show dialplan number 911
Macro Exp.: 911

VoiceOverIpPeer15400
peer type = voice, system default peer = FALSE, information type = voice,
description = `CME1-TO-CME2-911',
tag = 15400, destination-pattern = `911$',
voice reg type = 0, corresponding tag = 0,
allow watch = FALSE
answer-address = `', preference=1,


To test translation rules-
R1#test voice translation-rule <rule#> <number to translate>

Example
voice translation-rule 1
 rule 4 /^914102850417/ /DEAD/
 rule 5 /^91410915..../ /DEAD/
 rule 36 /9011204/ /000204/
 rule 37 /9011226/ /000226/

RTR1#test voice translation-rule 1 914102850417  
Matched with rule 4
Original number: 914102850417 Translated number: DEAD
Original number type: none Translated number type: none
Original number plan: none Translated number plan: none

Comments

Post a Comment

Popular posts from this blog

Status: Local Agent is not responding. This may be due to Master or Local Agent being down.

-
If you have read my previous post , you would understand why LA and MA services are important for such a scenario and no component has backed-up, rather you get the above error message. Symptoms -   All Disaster Recovery Framework (DRF) services are down, and no new devices, schedules, or statuses can be viewed from the DRF console. Also, when you access the DRF admin pages, the above error message is received. Affected CM releases 6.1.5 and later. Resolution In order to resolve it, first, verify if the Certificate Serial Number in the keystore of Publisher is present in the Truststore of all Subscribers. Complete these steps: Log on to CUCM OS Administration page of Publisher server of the cluster setup. Choose Security > Certificate Management . The Certificate List window displays. You can use the Find controls in order to filter the certificate. Click on the ipsec.pem file and check the serial number of the certificate. Log on to CUCM OS Admin...
Read more

Understanding code yellow

-
Understanding sample code yellow alert- Oct 3 01:00:10, cms01, Error, Cisco CallManager, ccm: 147896: Oct 03 05:00:10.616 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowEntry: CodeYellowEntry Expected Average Delay:362 Entry Latency:20 Exit Latency:8 Sample Size:10 Total Code Yellow Entry:14 High Priority Queue Depth:2 Normal Priority Queue Depth:12 Low Priority Queue Depth:70 Cluster ID:StandAloneCluster Node ID:cms01, 3652 The above alert is about code yellow entry, it shows the time when server enters code yellow state. There are no specifications to note at this alert, CM enters code yellow when it achieves the mentioned conditions for code yellow state as mentioned in service parameters. Oct 3 01:00:12, cms01, Error, Cisco CallManager, ccm: 147897: Oct 03 05:00:12.268 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowExit: CodeYellowExit Expected Average Delay:0 Entry Latency:20 Exit Latency:8 Sample Size:10 Time Spent in Code Yellow:2 Number of Calls Rejected Due to C...
Read more