VOICE TROUBLESHOOTING GUIDE

Commands
sh version
sh ip int brief
sh int s0/0.1
sh voice port
sh voice port sum
sh controller t1
sh controller e1
sh voice call
sh voice call sum
sh call active voice
sh call active voice brief
sh call history voice brief
sh dialer-peer voice sum
sh isdn stat
sh run | beg voice-port [controller]
sh access list
sh frame-relay map
sh frame-relap pvc [dlci]
sh frame-relay fragement [dlci]


If all connectivity looks good on both the remote and local routers and customers voice is not working at all, I would suggest an extended ping between Loopback 323's on both routers and then try pinging the primary Gatekeeper from the local router.


PBLR160# sh ver (shows voice hardware)

Cisco Internetwork Operating System Software
IOS (tm) 3700 Software (C3725-IS-M), Version 12.2(15)T5, RELEASE SOFTWARE (fc1)
TAC Support: http://www.cisco.com/tac
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Wed 11-Jun-03 23:51 by eaarmas
Image text-base: 0x60008954, data-base: 0x61B0C000

ROM: System Bootstrap, Version 12.2(8r)T2, RELEASE SOFTWARE (fc1)

pblr160 uptime is 3 weeks, 1 day, 8 hours, 20 minutes
System returned to ROM by reload
System restarted at 23:04:23 UTC Wed Jun 23 2004
System image file is "flash:c3725-is-mz.122-15.T5"

cisco 3725 (R7000) processor (revision 0.1) with 98304K/32768K bytes of memory.
Processor board ID JPE075210BP
R7000 CPU at 240Mhz, Implementation 39, Rev 3.3, 256KB L2 Cache
Channelized E1, Version 1.0.
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
Primary Rate ISDN software, Version 1.1.
2 FastEthernet/IEEE 802.3 interface(s)
1 Serial network interface(s)
2 Channelized E1/PRI port(s) <<<==========Command shows what voice hardware is on router
DRAM configuration is 64 bits wide with parity disabled.
55K bytes of non-volatile configuration memory.
62720K bytes of ATA System CompactFlash (Read/Write)

Configuration register is 0x2102


PBLR160# sh voice port sum (shows current status of Voice ports)

PORT CH SIG-TYPE ADMIN OPER STATUS STATUS EC
========= == ============ ===== ==== ======== ======== ==
1/0:0 01 e&m-imd up dorm idle idle y
1/0:0 02 e&m-imd up dorm idle idle y
1/0:0 03 e&m-imd up dorm idle idle y
1/0:0 04 e&m-imd up up seized seized y
<<<=Port is being used for call, oper is up and both in and out status is set to seized

1/0:0 05 e&m-imd up up seized seized y
1/0:0 06 e&m-imd up dorm idle idle y
1/0:0 07 e&m-imd up dorm idle idle y
1/0:0 08 e&m-imd up up siezed idle y
<<<= You will often see this when call is either starting of finishing, it only means one of the users has put down the
phone. You should do the command again and you will either see the state change to idle/idle for end of call or
seized/seized for call in progress. If this state remains for a period of time then you do have a problem. In this
example the local user has picked up the phone but it is not getting picked up at the other end.
1/0:0 09 e&m-imd up dorm idle idle y
1/0:0 10 e&m-imd up dorm idle idle y
1/0:0 11 e&m-imd up dorm idle idle y
1/0:0 12 e&m-imd up dorm idle idle y
1/0:0 13 e&m-imd up dorm idle idle y
1/0:0 14 e&m-imd up dorm idle idle y
1/0:0 15 e&m-imd up dorm idle idle y
<<<=This is normal state for a port that is waiting to be used, dorm stands for dormant

1/0:0 17 e&m-imd up dorm idle idle y
1/0:0 18 e&m-imd up dorm idle idle y
1/0:0 19 e&m-imd up dorm idle idle y
1/0:0 20 e&m-imd up dorm idle idle y
1/0:0 21 e&m-imd up dorm idle idle y
1/0:0 22 e&m-imd up dorm idle idle y
2/0:0 01 e&m-imd down down
<<<=Port has been administratively shutdown

2/0:0 02 e&m-imd up dorm idle idle y
2/0:0 03 e&m-imd up dorm idle idle y
2/0:0 04 e&m-imd up down
<<<=Problem, port is adminstratively up but physically down

2/0:0 05 e&m-imd up dorm idle idle y
2/0:0 06 e&m-imd up dorm idle idle y
2/0:0 07 e&m-imd up up seized seized y
2/0:0 08 e&m-imd up up seized seized y
2/0:0 09 e&m-imd up up seized seized y



PBLR160# sh contr e1 (if customer is using digital from router to pbx)

E1 1/0 is up.
Applique type is Channelized E1 - balanced
No alarms detected.
alarm-trigger is not set
Version info Firmware: 20020812, FPGA: 11
Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.
Data in current interval (588 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
<<<========================Errors running on line - remember this is inhouse cabling at customer site

0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 24 hours)
0 Line Code Violations, 0 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
E1 2/0 is up.
Applique type is Channelized E1 - balanced
No alarms detected.
alarm-trigger is not set
Version info Firmware: 20020812, FPGA: 11
Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.
Data in current interval (590 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 24 hours)
0 Line Code Violations, 0 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs



PBLR160# sh voice call sum (shows compression and ports connected)


PORT CODEC VAD VTSP STATE VPM STATE
============ ======== === ==================== ======================
1/0:0.1 - - - EM_ONHOOK
1/0:0.2 g729r8 n S_CONNECT EM_CONNECT <<<=compression used by Equant
1/0:0.3 - - - EM_ONHOOK
1/0:0.4 - - - EM_ONHOOK
1/0:0.5 - - - EM_ONHOOK
1/0:0.6 - - - EM_ONHOOK <<<= port not being used
1/0:0.7 - - - EM_ONHOOK
1/0:0.8 g729r8 n S_CONNECT EM_CONNECT <<<= port is being used - call up
1/0:0.9 g729r8 n S_CONNECT EM_CONNECT



PBLR160# sh dial-peer voice sum (shows the mapping/routing calls will take)

AD PRE PASS
TAG TYPE MIN OPER PREFIX DEST-PATTERN FER THRU SESS-TARGET PORT
20010- voip up up .T 1 syst pv4:57.210.105.204 <<< =see point 2
1
20010- voip up up .T 3 syst pv4:57.210.105.236
2
11001- pots up up 791 1 1/0:0=====see point 1
01
11001- pots up up 791 2 2/0:0
02
11001- pots up up 792 1 1/0:0
11
11001- pots up up 792 2 2/0:0
12



1. The bottom 4 entries are very similiar....The highlighted line means that if the router gets anything that starts with 791 it will send it down port 1/0:0 as the first preference, the line below states that as a 2nd preference use port 2/0:0. The following 2 lines state a similiar thing except this is for phone numbers starting with 792. What we can ascertain from these four lines is that the local numbers for this site start with 791 and 792.

2. The .T states that for anything other that 791 or 792 then the router will need to get more information from the Gatekeepers.The 2 IP addresses are the Gatekeepers. The Gatekeepers keep dial plans for all customers. More information on the Gatekeepers below.





PBLR160# sh frame-relay pvc 402 (shows COS details and drops)

PVC Statistics for interface Serial0/0 (Frame Relay DTE)

DLCI = 402, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0.1

input pkts 126813911 output pkts 129009489 in bytes 2167487187
out bytes 2361377576 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
<<<=These figures are for all Class Of Services(COS) on this DLCI


out bcast pkts 0 out bcast bytes 0
5 minute input rate 1000 bits/sec, 11 packets/sec
5 minute output rate 3000 bits/sec, 12 packets/sec
pvc create time 3w4d, last time pvc status changed 5d23h
fragment type end-to-end fragment size 1280
cir 972800 bc 9728 be 0 limit 1216 interval 10
mincir 972800 byte increment 1216 BECN response no IF_CONG no
frags 129009490 bytes 2361378156 frags delayed 1670 bytes delayed 748148
shaping inactive
traffic shaping drops 0
service policy COS-OUT-S0/0.1
Serial0/0.1: DLCI 402 -

Service-policy output: COS-OUT-S0/0.1

Class-map: DSCP-OUT-RT (match-any)
<<<=RT means Real Time - voice is RT and as such gets priority over all other traffic

127800899 packets, 10821772847 bytes
<<<=This section is for just RT COS

5 minute offered rate 1000 bps, drop rate 0 bps
Match: access-group name DSCP-OUT-RT
127800899 packets, 10821773099 bytes
5 minute rate 1000 bps
Queueing
Strict Priority
Output Queue: Conversation 72
Bandwidth 756 (kbps) Burst 94500 (Bytes)
<<<=756K has been allocated for voice, RT is the only COS parameter that has bandwidth hard configured

(pkts matched/bytes matched) 127800900/10821773435
(total drops/bytes drops) 0/0
<<<=No voice packets have been dropped
police:
cir 756000 bps, bc 94500 bytes
conformed 127800900 packets, 10821773435 bytes; actions:
set-dscp-transmit ef
exceeded 0 packets, 0 bytes; actions:
set-dscp-transmit ef
conformed 1000 bps, exceed 0 bps




GATEKEEPERS

The Gatekeepers keep a list of all numbers for each customer. When a customer router receives a request for a call and it is mapped to ".T" it will request more information from the Gatekeeper. The Gatekeeper translates a telephone number prefix to an Ip address and advises the router, the router will then route the traffic as per normal and the Gatekeepers participation is finished for that call.

There are 2 Gatekeepers

Paris 57.210.105.204
Reston 57.210.105.236

If you want to ping to Gatekeepers then you need to use the Loopback 323 address of the router as the source

The following website will take give you the information that the GK's use

http://57.210.105.230/voipvpnMgt/index.html
Login: gcsc
P/W: gcsc#gen

1. Go to VPN data and find your customer - click on the customer
2. Click on VPN site data and this will list all the voice routers for that customer.
3. Click on the router you require
4. You can now go through the tabs to find out more information.

Best info is under the "Site Gateway Group" which shows the max amount of calls allowed at one time, and the IP address of Loopback323 (voice loopback). This other good tab is "Site Extensions".