|
|
|
|
Joined: Nov 2008
Posts: 39
Member
|
|
Member
Joined: Nov 2008
Posts: 39 |
positive about the network timing. pardon my ignorance but what does a t3 hitting up mean?
on another note, we've been having some bad weather here for the last 4 days, the whole time these problems have been happening. well today it was clear, until tonight of course, and the phone system hasn't gone down all day. i'm don't really think that the problem disappeared but it does seem a little strange to me. it hasn't gone this long without having an alarm for the last four days. its just weird...
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
|
Joined: May 2002
Posts: 17,726 Likes: 19
Member
|
|
Member
Joined: May 2002
Posts: 17,726 Likes: 19 |
What alarms are you getting? If a T3 bounces it can cause all the T1's on it to loose sync. I don't think that's your problem since there would be 28 other circuits having problems.
Retired phone dude
|
|
|
|
|
Joined: Nov 2008
Posts: 39
Member
|
|
Member
Joined: Nov 2008
Posts: 39 |
well, i think i spoke too soon. there is a massive thunder/lightening storm going on right now and the pbx just showed another alarm. dammit...
|
|
|
|
|
Joined: May 2002
Posts: 17,726 Likes: 19
Member
|
|
Member
Joined: May 2002
Posts: 17,726 Likes: 19 |
I looked at your other post in VoIP, D channel alarm is not a T1 alarm.
Retired phone dude
|
|
|
|
|
Joined: Nov 2008
Posts: 39
Member
|
|
Member
Joined: Nov 2008
Posts: 39 |
i'm not sure if the log message is related to the outages. i am getting them a lot before and after the circuit bounces but i'm not sure if they are the cause of this. they are the only errors in the log though except for the alarms of course.
isn't the d channel used for timing?
|
|
|
|
|
Joined: May 2002
Posts: 17,726 Likes: 19
Member
|
|
Member
Joined: May 2002
Posts: 17,726 Likes: 19 |
No, the D channel is used for signaling. A T1 alarm is going to be yellow red/ais or maybe oof or ses.
If you're loosing the D channel that's a whole differnt trouble.
Retired phone dude
|
|
|
|
|
Joined: Nov 2008
Posts: 39
Member
|
|
Member
Joined: Nov 2008
Posts: 39 |
this is the log from the last outage. let me know what you think.
24 05/25/2009 10:47 PM NOTICE chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
25 05/25/2009 10:47 PM NOTICE chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
26 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 23
27 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 22
28 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 21
29 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 20
30 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 19
31 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 18
32 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 17
33 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 16
34 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 15
35 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 14
36 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 13
37 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 12
38 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 11
39 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 10
40 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 9
41 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 8
42 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 7
43 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 6
44 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 5
45 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 4
46 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 3
47 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 2
48 05/25/2009 10:47 PM NOTICE chan_zap.c: Alarm cleared on channel 1
49 05/25/2009 10:47 PM NOTICE chan_zap.c: PRI got event: No more alarm (5) on Primary D-channel of span 1
50 05/25/2009 10:47 PM WARNING chan_zap.c: No D-channels available! Using Primary channel 24 as D-channel anyway!
50 05/25/2009 10:47 PM WARNING chan_zap.c: No D-channels available! Using Primary channel 24 as D-channel anyway!
51 05/25/2009 10:46 PM WARNING Last Message Repeated 1 times
52 05/25/2009 10:46 PM NOTICE chan_zap.c: PRI got event: Alarm (4) on Primary D-channel of span 1
53 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 23
54 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 23: Red Alarm
55 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 22
56 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 22: Red Alarm
57 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 21
58 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 21: Red Alarm
59 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 20
60 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 20: Red Alarm
61 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 19
62 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 19: Red Alarm
63 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 18
64 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 18: Red Alarm
65 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 17
66 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 17: Red Alarm
67 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 16
68 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 16: Red Alarm
69 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 15
70 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 15: Red Alarm
71 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 14
72 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 14: Red Alarm
73 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 13
74 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 13: Red Alarm
75 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 12
76 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 12: Red Alarm
77 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 11
78 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 11: Red Alarm
79 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 10
80 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 10: Red Alarm
81 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 9
82 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 9: Red Alarm
83 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 8
84 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 8: Red Alarm
85 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 7
86 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 7: Red Alarm
87 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 6
88 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 6: Red Alarm
89 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 5
90 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 5: Red Alarm
91 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 4
92 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 4: Red Alarm
93 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 3
94 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 3: Red Alarm
95 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 2
96 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 2: Red Alarm
97 05/25/2009 10:46 PM WARNING chan_zap.c: Unable to disable echo cancellation on channel 1
98 05/25/2009 10:46 PM WARNING chan_zap.c: Detected alarm on channel 1: Red Alarm
99 05/25/2009 10:45 PM NOTICE chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
|
|
|
|
|
Joined: May 2002
Posts: 17,726 Likes: 19
Member
|
|
Member
Joined: May 2002
Posts: 17,726 Likes: 19 |
I don't know what the channel specific stuff means, as IP uses different terms than Telco. A red alarm at the T1 level means you're not receiveing a signal at the T1 rate. I don't know what your box says it means.
Why the IP world chooses to change terms that have been around for many years is beyond me, you'd have to ask those in that world.
Retired phone dude
|
|
|
|
|
Joined: Nov 2008
Posts: 39
Member
|
|
Member
Joined: Nov 2008
Posts: 39 |
me either, these logs are kind of cryptic. the thing that really sticks is that the log never says anything about timing or frame slips but the verizon tech was easily detecting them. i wish it were a bit clearer.
i'm going to run out and buy a new t1 card tomorrow morning and replace the one that i'm using. hopefully the card is the problem maker and i resolve it with a new one. if it's not then i'm back to the drawing board. thanks for all your help!
|
|
|
|
|
Joined: Jun 2007
Posts: 2,106
Member
|
|
Member
Joined: Jun 2007
Posts: 2,106 |
Ok, so there are a few options here.
1) The RJ48X dongle plugged into the smartjack is fubar'd and shorting out/frayed/etc. If it's plugged in unplug it and directly connect the smartjack to the T1 port. For some reason they like to get corroded and screwed up. Probably all our lovely humidity and salty air.
2) Whatever cables/connectors running between your T1 port and the smartjack is junk. If you have inline couplers, handmade cables, or other such error-prone things then replace it.
3) The T1 port on the PBX is loose/smashed/broken. Get on the phone, then walk over to the PBX and start wiggling the connector. If the calls drop with moderate agitation, then there's your problem.
4) Last is a failed hardware card. If it's an older switchvox then this is where my money is. I've been down this road before with Digium cards and they were notorious for this in their earlier production runs.
So, I'm putting my money on option #4. Given the fact that the card reports red then instantly goes green is a somewhat tell-tale sign of this kind of failure. Problems 1 and 2 usually result in an obscene about of bit errors/etc. We would be talking 6-digit error figures in a 24-hour period or more (depending on the bit error). Problem 3 is easy enough to prove with a little investigation.
Unfortunately you don't have a Sangoma card so you cant get to the real CSU/DSU error stats. If you did you could actually look up and see exactly what KIND or errors you were getting other then just "errors".
|
|
|
|
Forums84
Topics94,428
Posts639,501
Members49,821
| |
Most Online5,661
May 23rd, 2018
|
|
|
|
|
|
