How to verify voice channels on voice gateway

Question

Hello,
I am in the testing phase of deploying a 2921 voice gateway with 2 PRIs. After connecting the T1s, how do I verify if all the channels are up and ready for use? Also, how do I verify if clocking on the T1 interfaces are configured correctly?
This 2921 is a replacement for a 2811 currently being used. When I login to the 2811 via SSH, I see this:
560240: Aug 13 20:37:24.368: %ISDN-6-CONNECT: Interface Serial0/2/0:3 is now connected to 3854143418 N/A
560241: Aug 13 20:37:24.368: %ISDN-6-CONNECT: Interface Serial0/2/0:3 is now connected to 3854143418 N/A
560242: Aug 13 20:37:24.544: %ISDN-6-CONNECT: Interface Serial0/2/0:5 is now connected to 7753428028 N/A
560243: Aug 13 20:37:24.544: %ISDN-6-CONNECT: Interface Serial0/2/0:5 is now connected to 7753428028 N/A
560244: Aug 13 20:37:27.128: %ISDN-6-CONNECT: Interface Serial0/2/0:4 is now connected to 7753296300 N/A
560245: Aug 13 20:37:27.128: %ISDN-6-CONNECT: Interface Serial0/2/0:4 is now connected to 7753296300 N/A
560246: Aug 13 20:37:27.128: %ISDN-6-CONNECT: Interface Serial0/2/0:22 is now connected to 3296300 N/A
560247: Aug 13 20:37:27.128: %ISDN-6-CONNECT: Interface Serial0/2/0:22 is now connected to 3296300 N/A
560248: Aug 13 20:37:27.652: %ISDN-6-CONNECT: Interface Serial0/2/0:20 is now connected to 3525101 N/A
560249: Aug 13 20:37:27.652: %ISDN-6-CONNECT: Interface Serial0/2/0:20 is now connected to 3525101 N/A
560250: Aug 13 20:37:30.320: %ISDN-6-CONNECT: Interface Serial0/2/1:22 is now connected to 3525101 N/A
560251: Aug 13 20:37:30.320: %ISDN-6-CONNECT: Interface Serial0/2/1:22 is now connected to 3525101 N/A
How do I do that with the 2921 in an SSH session? I've enabled "logging monitor" and "term mon" but I still can't see messages like that.
I thank you very much for your time.

Answer 1

Hello,
To check clocking you can use the "show network-clock" command. For example:
SiteA-RTR#show network-clock
Network Clock Configuration
Priority Clock Source Clock State Clock Type
1 T1 0/0/0 GOOD T1
10 Backplane GOOD PLL
Current Primary Clock Source
Priority Clock Source Clock State Clock Type
1 T1 0/0/0 GOOD T1
The above is an example of a "good" configuration, assuming that T1 0/0/0 is the controller terminating the line from your carrier. In your case, it would be T1 0/2/0 or 0/2/1. You can also look at "show controller t1 [interface]" (e.g. show controller t1 0/2/0) and pay particular attention to "Line Code Violations", "Slip Secs", and "Errored Secs" counters. Note that the "Clock Source Line" status in the "show controller t1" command is not enough to verify you have proper clocking. 
Example of a "bad" clock scenario:
SiteA-RTR(config-voiceport)#do sh controller t1 0/0/0
T1 0/0/0 is up.
Applique type is Channelized T1
Cablelength is long 0db
No alarms detected.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Clear
Version info Firmware: 20080918, FPGA: 13, spm_count = 0
Framing is ESF, Line Code is B8ZS, Clock Source is Line.
CRC Threshold is 320. Reported from firmware is 320.
Data in current interval (483 seconds elapsed):
3 Line Code Violations, 4 Path Code Violations
207 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
206 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 109 Unavail Secs
To make sure the clock is set correctly, look at the "network-clock-participate" and the "network-clock-select" commands.
For the ISDN status information, you can use "show isdn status". For example:
SiteA-RTR(config)#do sh isdn stat
Global ISDN Switchtype = primary-ni
%Q.931 is backhauled to CCM MANAGER 0x0003 on DSL 0. Layer 3 output may not apply
ISDN Serial0/0/0:23 interface
dsl 0, interface ISDN Switchtype = primary-ni
L2 Protocol = Q.921 0x0000 L3 Protocol(s) = CCM MANAGER 0x0003
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 0 CCBs = 0
The Free Channel Mask: 0x800000FF
Number of L2 Discards = 0, L2 Session ID = 15
*Note: The above is output from a gateway provisioned to use MGCP.
For all gateways, just make sure that Layer 1 is "ACTIVE" and that Layer 2 has "MULTIPLE_FRAME_ESTABLISHED".
You can also use the "show isdn service" command to look at status for individual B-channels.
SiteA-Rtr#sh isdn service
PRI Channel Statistics:
%Q.931 is backhauled to CCM MANAGER 0x0003 on DSL 0. Layer 3 output may not appl
ISDN Se0/0/0:23, Channel [1-24]
Configured Isdn Interface (dsl) 0
Channel State (0=Idle 1=Proposed 2=Busy 3=Reserved 4=Restart 5=Maint_Pend)
Channel : 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
State : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3
Service State (0=Inservice 1=Maint 2=Outofservice 8=MaintPend 9=OOSPend)
Channel : 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
State : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2
Use the "Channel State" and "Service State" to verify things are what you expect.
HTH.
-Bill (@ucguerrilla)
http://ucguerrilla.com