T1 line configured on different Serial port

[Amafsha1]

Hello, I've noticed something recently that I don't understand.

We use MGCP.

Serial0/0/0:0 is in the below output.  This is where our T1 is configured.

Serial0/0/0:0 is up, line protocol is up
Hardware is DSX1
Description: DS1IT to ISP MPLS
Internet address is 63.x.x.42/30
MTU 1500 bytes, BW 1536 Kbit/sec, DLY 20000 usec,
reliability 255/255, txload 25/255, rxload 60/255
Encapsulation HDLC, crc 16, loopback not set
Keepalive set (10 sec)
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 34385
Queueing strategy: Class-based queueing
Output queue: 6/1000/34385 (size/max total/drops)
5 minute input rate 365000 bits/sec, 67 packets/sec
5 minute output rate 153000 bits/sec, 66 packets/sec
52293166 packets input, 4144144677 bytes, 0 no buffer
Received 197884 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
48430758 packets output, 684817026 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
1 carrier transitions

Yet, why is it that our configurations are on Serial0/0/1:23 ?

interface Serial0/0/1:23
no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn incoming-voice voice
isdn bind-l3 ccm-manager
no cdp enable

When I do show int below on that interface of Serial0/0/1:23, I get empty counters.  why is that?

 Serial0/0/1:23 is down, line protocol is down
Hardware is DSX1
MTU 1500 bytes, BW 64 Kbit/sec, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation HDLC, crc 16, loopback not set
Keepalive set (10 sec)
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions

[R0g22]

Serial0/0/0:0 >> does not look to be like a voice circuit. Even if it is, its NOT CCS. T1 is not necessarily for voice only. Can you send an output for "show run | s contro|voice-port" ?

Serial0/0/1:23 >> is configured for voice BUT the L1/L2 stat is DOWN so this circuit is not functioning currently
Serial0/0/1:23 is down, line protocol is down

[Amafsha1]

You're right it is not a voice circuit, it is used for Data.  Here is the output you asked for

show run | s contro|voice-port

controller T1 0/0/0
clock source line independent
cablelength long 0db
channel-group 0 timeslots 1-24
controller T1 0/0/1
cablelength long 0db
pri-group timeslots 1-24 service mgcp
control-plane
voice-port 0/1/0
trunk-group OUTGOING
echo-cancel coverage 64
timing hookflash-out 50
voice-port 0/1/1
trunk-group OUTGOING
echo-cancel coverage 64
timing hookflash-out 50
voice-port 0/1/2
trunk-group OUTGOING
echo-cancel coverage 64
timing hookflash-out 50
voice-port 0/1/3
trunk-group OUTGOING
echo-cancel coverage 64
timing hookflash-out 50
voice-port 0/0/1:23
!
!
!
!

[R0g22 · Accepted solution]

Yup, it's configured for a "channel-group". That's data ONLY.

controller T1 0/0/0
clock source line independent
cablelength long 0db
channel-group 0 timeslots 1-24

For T1/E1 CCS, you would need a "pri-group" and for T1/E1 CAS you would need a "ds-group". Only with these two there would be "voice-ports" which are important for VOICE.

[Amafsha1]

Thank you, sorry I'm not too familiar with voice.  So where does the voice traffic go than?

[R0g22]

That's fine, no need to apologise. They should be what I believe to be FXO port -

voice-port 0/1/0
trunk-group OUTGOING
echo-cancel coverage 64
timing hookflash-out 50

voice-port 0/1/1
trunk-group OUTGOING
echo-cancel coverage 64
timing hookflash-out 50

voice-port 0/1/2
trunk-group OUTGOING
echo-cancel coverage 64
timing hookflash-out 50

voice-port 0/1/3
trunk-group OUTGOING
echo-cancel coverage 64
timing hookflash-out 50

Do a "show inven" and check the slot/subslot for an FXO port on their. Then match that to the voice-port. The convention is slot/subslot/port (ports are non-canonical from an IOS perspective i.e. right to left and always start at 0).

[Amafsha1]

#sh inv
NAME: "CISCO2911/K9", DESCR: "CISCO2911/K9 chassis, Hw , Hw Revision: 1.0"
PID: CISCO2911/K9 , VID: V07 , SN: FTX1805AL95

NAME: "VWIC3-2MFT-T1/E1 - 2-Port RJ-48 Multiflex Trunk - T1/E1 on Slot 0 SubSlot 0", DESCR: "VWIC3-2MFT-T1/E1 - 2-Port RJ-48 Multiflex Trunk - T1/E1"
PID: VWIC3-2MFT-T1/E1 , VID: V01 , 

NAME: "2nd generation four port FXO voice interface daughtercard on Slot 0 SubSlot 1", DESCR: "2nd generation four port FXO voice interface daughtercard"
PID: VIC2-4FXO , VID: V04 , 

NAME: "PVDM3 DSP DIMM with 16 Channels on Slot 0 SubSlot 4", DESCR: "PVDM3 DSP DIMM with 16 Channels"
PID: PVDM3-16 , VID: V01 , 

NAME: "PVDM3 DSP DIMM with 16 Channels on Slot 0 SubSlot 5", DESCR: "PVDM3 DSP DIMM with 16 Channels"
PID: PVDM3-16 , VID: V01 , 

NAME: "C2911 AC Power Supply", DESCR: "C2911 AC Power Supply"
PID: PWR-2911-AC , VID: V05 , 

So you're saying that the PRI here is being used for data, and we have FXO ports that are being used for voice?

[R0g22]

Correct. You can further confirm that if you see any dial-peers configured and they have a "trunkgroup OUTGOING" configured under them and not shut.
Do a "show run | s -peer".