08-18-2019 11:05 AM
I am very new to telephony troubleshooting. We are having call quality issues. Here is a sampling from my logging and my the controller that seems to be resetting. Any thoughts would be great.
T1-GWY-2921#sh controller T1 0/0/1
T1 0/0/1 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: 20100222, 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.
Total Data (last 24 hours)
10409200 Line Code Violations, 8116530 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 86400 Line Err Secs, 1440 Degraded Mins,
86400 Errored Secs, 86400 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
044999: Aug 16 11:35:26.214: %CONTROLLER-5-UPDOWN: Controller T1 0/0/1, changed state to down (10 SES)
045000: Aug 16 11:35:27.214: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:0, changed state to down
045001: Aug 16 11:35:27.214: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:3, changed state to down
045002: Aug 16 11:35:28.214: %LINK-3-UPDOWN: Interface Serial0/0/1:23, changed state to down
045003: Aug 16 11:35:48.554: %VOICE_IEC-3-GW: SIP: Internal Error (Socket error): IEC=1.1.186.7.7.4 on callID 193913 GUID=BCC40545BF7A11E9B6A84C4E35DCA050
045004: Aug 16 11:35:55.290: %VOICE_IEC-3-GW: SIP: Internal Error (Socket error): IEC=1.1.186.7.7.4 on callID 193916 GUID=C0C7DBB3BF7A11E9B6A94C4E35DCA050
045005: Aug 16 11:35:57.850: %VOICE_IEC-3-GW: SIP: Internal Error (Socket error): IEC=1.1.186.7.7.4 on callID 193921 GUID=C24E7B12BF7A11E9B6AB4C4E35DCA050
045006: Aug 16 11:35:57.998: %VOICE_IEC-3-GW: SIP: Internal Error (Socket error): IEC=1.1.186.7.7.4 on callID 193919 GUID=C23CC790BF7A11E9B6AA4C4E35DCA050
045007: Aug 16 11:36:17.655: %VOICE_IEC-3-GW: SIP: Internal Error (Socket error): IEC=1.1.186.7.7.4 on callID 193927 GUID=CE1C5709BF7A11E9B6AC4C4E35DCA050
045008: Aug 16 11:36:24.683: %VOICE_IEC-3-GW: SIP: Internal Error (Socket error): IEC=1.1.186.7.7.4 on callID 193930 GUID=D24CBAD2BF7A11E9B6AD4C4E35DCA050
045009: Aug 16 11:36:32.879: %VOICE_IEC-3-GW: SIP: Internal Error (Socket error): IEC=1.1.186.7.7.4 on callID 193933 GUID=D72F57D5BF7A11E9B6AE4C4E35DCA050
045010: Aug 16 11:36:42.847: %VOICE_IEC-3-GW: SIP: Internal Error (Socket error): IEC=1.1.186.7.7.4 on callID 193936 GUID=DD205796BF7A11E9B6AF4C4E35DCA050
Solved! Go to Solution.
08-19-2019 01:59 AM
Hello Stacia,
your T1 has problems on the line
>> 10409200 Line Code Violations, 8116530 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 86400 Line Err Secs, 1440 Degraded Mins,
86400 Errored Secs, 86400 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
86400 Errored Secs means you have had events of errors every second in the last 24 hours.
>> Framing is ESF, Line Code is B8ZS, Clock Source is Line.
check with the other side ( ISDN provider I suppose ) what are the settings expected for your T1 regarding framing and line code.
Or you can have clocking issues. Or you may need to change the cable length parameter.
Use a reference the following troubleshooting documents
https://www.cisco.com/c/en/us/support/docs/wan/t1-e1-t3-e3/10205-t1-flchrt-main.html
https://www.cisco.com/c/en/us/support/docs/wan/t1-e1-t3-e3/8131-T1-pri.html
Hope to help
Giuseppe
08-18-2019 11:42 AM
Hello,
how are your dial peers configured ? Post, if possible, the running configuration of your 2921...
08-19-2019 05:14 AM
Here you go!
dial-peer cor custom
name inbound
name outbound
!
!
dial-peer cor list Inbound
member inbound
!
dial-peer cor list Outbound
member outbound
!
!
dial-peer voice 100 pots
trunkgroup LOCAL
corlist incoming Inbound
corlist outgoing Outbound
translation-profile outgoing INTERNATIONAL
destination-pattern .T
incoming called-number .
no digit-strip
direct-inward-dial
no sip-register
!
dial-peer voice 101 pots
trunkgroup LOCAL
corlist outgoing Outbound
destination-pattern 18[0,4,8,7,6,5]+.T
no digit-strip
no sip-register
!
dial-peer voice 110 pots
trunkgroup LD
corlist outgoing Outbound
destination-pattern 1.T
no digit-strip
no sip-register
!
dial-peer voice 111 pots
corlist outgoing Outbound
translation-profile outgoing INTERNATIONAL
destination-pattern 011.T
no digit-strip
port 0/0/1:23
no sip-register
!
dial-peer voice 200 voip
corlist incoming Outbound
session protocol sipv2
session transport tcp
incoming called-number .
dtmf-relay rtp-nte digit-drop
codec g711ulaw
fax-relay ecm disable
no vad
!dial-peer voice 201 voip
corlist outgoing Inbound
preference 1
destination-pattern .T
session protocol sipv2
session target ipv4:10.10.300.4:5060
session transport tcp
dtmf-relay rtp-nte digit-drop
codec g711ulaw
no vad
!
dial-peer voice 202 voip
corlist outgoing Inbound
preference 2
destination-pattern .T
session protocol sipv2
session target ipv4:10.10.300.5:5060
session transport tcp
dtmf-relay rtp-nte digit-drop
codec g711ulaw
no vad
!
dial-peer voice 112 pots
trunkgroup LD
corlist incoming Inbound
service app_cas_ani_dnis
incoming called-number ^[*][0-9]+[*][0-9]+[*]$
direct-inward-dial
no sip-register
!
dial-peer voice 301 voip
session target ipv4:10.10.300.4:5060
08-19-2019 01:59 AM
Hello Stacia,
your T1 has problems on the line
>> 10409200 Line Code Violations, 8116530 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 86400 Line Err Secs, 1440 Degraded Mins,
86400 Errored Secs, 86400 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
86400 Errored Secs means you have had events of errors every second in the last 24 hours.
>> Framing is ESF, Line Code is B8ZS, Clock Source is Line.
check with the other side ( ISDN provider I suppose ) what are the settings expected for your T1 regarding framing and line code.
Or you can have clocking issues. Or you may need to change the cable length parameter.
Use a reference the following troubleshooting documents
https://www.cisco.com/c/en/us/support/docs/wan/t1-e1-t3-e3/10205-t1-flchrt-main.html
https://www.cisco.com/c/en/us/support/docs/wan/t1-e1-t3-e3/8131-T1-pri.html
Hope to help
Giuseppe
08-19-2019 05:08 AM
>>check with the other side ( ISDN provider I suppose ) what are the settings expected for your T1 regarding framing and line code.
Or you can have clocking issues. Or you may need to change the cable length parameter.
According to the historical documents that I have it has been programmed this way for at least the last couple of years. That being said I am going to get a hold of the ISP today to verify the configuration and line.
The documents that you attached were very helpful and I will save them for the future.
08-19-2019 02:14 PM
Definitely T1 issues, or whatever device is plugged into that port. It's not timing slips.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide