07-23-2023 08:11 AM
Hello,
So we have two gateways at our main office that are feed from our NOC provider for VOIP services. Both Gateway 1 and 2 are 4331.
We started getting wierd issue with some of our DID at our building locations were not recieving calls. However dialing out was fine. Over night we lost complete incoming calls. I was poking around our gateways to see if I can find out what may be the issue this is what I found from our GW1 at our main office.
T1 0/1/0 is down
Applique type is Channelized T1
Cablelength is long gain36 0db
Description: -=-=- In from Service Provider -=-=-
Transmitter is sending remote alarm.
Receiver has loss of frame.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Failure
Framing is ESF, Line Code is B8ZS, Clock Source is Line.
BER thresholds: SF = 10e-3 SD = 10e-6
Data in current interval (773 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, 773 Unavail Secs
Data in Interval 1:
1 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 1 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 900 Unavail Secs
Total Data (last 1 15 minute intervals):
1 Line Code Violations, 0 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 1 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 900 Unavail Secs
Here what are GW2
T1 0/1/0 is down
Applique type is Channelized T1
Cablelength is long gain36 0db
Description: -=-=- In from Service Provider -=-=-
Transmitter is sending remote alarm.
Receiver has loss of frame.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Failure
Framing is ESF, Line Code is B8ZS, Clock Source is Line.
BER thresholds: SF = 10e-3 SD = 10e-6
Data in current interval (236 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, 236 Unavail Secs
Data in Interval 1:
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, 900 Unavail Secs
Data in Interval 2:
2 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 1 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 900 Unavail Secs
Total Data (last 2 15 minute intervals):
2 Line Code Violations, 0 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 1 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 1800 Unavail Secs
I'm trying to see if something is up with telecom provider or our gateways.
07-23-2023 09:50 AM
issue identified the ONT for our incoming T1s was the issue panel needed restart. telecom issue
07-23-2023 06:51 PM
From the output i can see line code violations. show isdn status will also help you in such situations.
07-24-2023 04:11 AM
In such situations, after checking the isdn status, we can also collect debug isdn q931 for any failed call. Since you had incoming call issue, in the debugs we would be able to see if we are receiving the isdn setup or not from provider.
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