|
|
Joined: Nov 2006
Posts: 9
Member
|
OP
Member
Joined: Nov 2006
Posts: 9 |
Question: Will a disconnect tear down a t1/pri? The timeing is set to the co, the trunks are programmed in reverse in the trunk group?
How can i interpret the meaning of Log# 32? The logs are from the maint logs of the pri card. :p
LOG# 32 | INFO GW | 07/04/25 09:22:37 | asn_decode: possible disconnect glare for prim:0x133 aei:0x5BB3 pei:0x5BA3 pln:0xF2 [asn.cpp @ 343] | 1234 LOG# 33 | INFO GW | 07/04/25 23:58:58 | DATETIME: Received time-change from PBX: 2007/4/26 0:0:0 [mtc.cpp @ 1006] | 1234 LOG# 34 | INFO GW | 07/04/26 00:00:00 | time changed to -> 07/04/26 00:00:00 [osmisc.cpp @ 330] | 1234 LOG# 35 | INFO GW | 07/04/26 00:00:00 | DATETIME: Time changed to -> 07/04/26 00:00:00 [mtc.cpp @ 1022] | 1234 LOG# 36 | WARN GW | 07/04/26 09:33:58 | asn decoder called asi manager REQUEST - REJECTED [asn.cpp @ 338] | 1234 LOG# 37 | INFO GW | 07/04/26 09:33:58 | asn_decode: possible disconnect glare for prim:0x133 aei:0x5DC0 pei:0x5DB0 pln:0xF2 [asn.cpp @ 343] | 1234 LOG# 38 | WARN GW | 07/04/26 13:03:24 | asn decoder called asi manager REQUEST - REJECTED [asn.cpp @ 338] | 1234 LOG# 39 | INFO GW | 07/04/26 13:03:24 | asn_decode: possible disconnect glare for prim:0x133 aei:0x5E56 pei:0x5E46 pln:0xF2 [asn.cpp @ 343] | 1234 LOG# 40 | INFO GW | 07/04/26 13:19:07 | DATETIME: Received time-change from PBX: 2007/4/26 1:22:59 [mtc.cpp @ 1006] | 1234 LOG# 41 | INFO GW | 07/04/26 01:22:59 | time changed to -> 07/04/26 01:22:59 [osmisc.cpp @ 330] | 1234 LOG# 42 | INFO GW | 07/04/26 01:22:59 | DATETIME: Time changed to -> 07/04/26 01:22:59 [mtc.cpp @ 1022] | 1234 LOG# 43 | warn AFC | 07/04/26 05:30:53 | layer 1 RED alarm ACTIVE for link 0 | 6 LOG# 44 | warn AFC | 07/04/26 05:30:53 | D-channel is forced DOWN for link 0 | 6 LOG# 45 | info AFC | 07/04/26 05:30:53 | Link 0 down due to PRI | 2 LOG# 46 | WARN GW | 07/04/26 05:30:54 | D-channel DOWN on AFC link 0 [dch.cpp @ 1340] | 1234 LOG# 47 | warn AFC | 07/04/26 05:31:24 | layer 1 YELLOW alarm ACTIVE for link 0 | 6 LOG# 48 | warn AFC | 07/04/26 05:31:24 | layer 1 RED alarm clear for link 0 | 6 LOG# 49 | warn AFC | 07/04/26 05:31:32 | layer 1 YELLOW alarm clear for link 0 | 6 LOG# 50 | WARN GW | 07/04/26 05:31:34 | D-channel UP on AFC link 0 [dch.cpp @ 1340] | 1234 LOG# 51 | warn AFC | 07/04/26 05:31:35 | D-channel is up on link 0 | 6 LOG# 52 | info AFC | 07/04/26 05:31:38 | Link 0 up (PRI) | 2 LOG# 53 | info AFC | 07/04/26 05:32:26 | MTNETSNC switching to long term accumulator mode for link 0 | 8 LOG# 54 | warn AFC | 07/04/26 05:34:46 | layer 1 RED alarm ACTIVE for link 0 | 6 LOG# 55 | warn AFC | 07/04/26 05:34:46 | D-channel is forced DOWN for link 0 | 6 LOG# 56 | info AFC | 07/04/26 05:34:46 | Link 0 down due to PRI | 2 LOG# 57 | WARN GW | 07/04/26 05:34:47 | D-channel DOWN on AFC link 0 [dch.cpp @ 1340] | 1234 LOG# 58 | warn AFC | 07/04/26 05:35:32 | layer 1 YELLOW alarm ACTIVE for link 0 | 6 LOG# 59 | warn AFC | 07/04/26 05:35:32 | layer 1 RED alarm clear for link 0 | 6 LOG# 60 | warn AFC | 07/04/26 05:35:41 | layer 1 YELLOW alarm clear for link 0 | 6 LOG# 61 | WARN GW | 07/04/26 05:35:43 | D-channel UP on AFC link 0 [dch.cpp @ 1340] | 1234 LOG# 62 | warn AFC | 07/04/26 05:35:44 | D-channel is up on link 0 | 6 LOG# 63 | info AFC | 07/04/26 05:35:47 | Link 0 up (PRI) | 2 LOG# 64 | info AFC | 07/04/26 05:36:10 | MTNETSNC switching to long term accumulator mode for link 0 | 8 LOG# 65 | WARN GW | 07/04/26 05:40:11 | asn decoder called asi manager REQUEST - REJECTED [asn.cpp @ 338] | 1234 LOG# 66 | INFO GW | 07/04/26 05:40:11 | asn_decode: possible disconnect glare for prim:0x133 aei:0x5F1F pei:0x5F0F pln:0xF2 [asn.cpp @ 343] | 1234 LOG# 67 | INFO GW | 07/04/27 00:00:01 | DATETIME: Received time-change from PBX: 2007/4/27 0:0:0 [mtc.cpp @ 1006] | 1234 LOG# 68 | INFO GW | 07/04/27 00:00:00 | time changed to -> 07/04/27 00:00:00 [osmisc.cpp @ 330] | 1234 LOG# 69 | INFO GW | 07/04/27 00:00:00 | DATETIME: Time changed to -> 07/04/27 00:00:00 [mtc.cpp @ 1022] | 1234 LOG# 70 | WARN GW | 07/04/27 02:58:49 | asn decoder called asi manager REQUEST - REJECTED [asn.cpp @ 338] | 1234 LOG# 71 | INFO GW | 07/04/27 02:58:49 | asn_decode: possible disconnect glare for prim:0x133 aei:0x6090 pei:0x6080 pln:0xF2 [asn.cpp @ 343] | 1234 LOG# 72 | INFO GW | 07/04/27 23:58:58 | DATETIME: Received time-change from PBX: 2007/4/28 0:0:0 [mtc.cpp @ 1006] | 1234 LOG# 73 | INFO GW | 07/04/28 00:00:00 | time changed to -> 07/04/28 00:00:00 [osmisc.cpp @ 330] | 1234 LOG# 74 | INFO GW | 07/04/28 00:00:00 | DATETIME: Time changed to -> 07/04/28 00:00:00 [mtc.cpp @ 1022] | 1234 LOG# 75 | INFO GW | 07/04/28 23:58:58 | DATETIME: Received time-change from PBX: 2007/4/29 0:0:0 [mtc.cpp @ 1006] | 1234
Steve McCoy
|
|
|
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 2005
Posts: 1,006
Member
|
Member
Joined: May 2005
Posts: 1,006 |
Steve, is this a new install of the T-1? Let's start there.
|
|
|
|
Joined: May 2005
Posts: 1,006
Member
|
Member
Joined: May 2005
Posts: 1,006 |
At first glance, it looks like a clock problem. Check data descripter programming for internal.
|
|
|
|
Joined: Oct 2004
Posts: 1,057
Member
|
Member
Joined: Oct 2004
Posts: 1,057 |
I'd double check your d-channel programming (dms-100, Ni2, etc). It looks like your data streams aren't quite in "synch". Is the card installed in the main cabinet, or are you using a FIM interface? I also can't help but ask why your dates are so far off?
|
|
|
|
Joined: Nov 2006
Posts: 9
Member
|
OP
Member
Joined: Nov 2006
Posts: 9 |
The pri card is using a FIMM, so it is its own cabinet. The dates are from early on in the maintenance log. The log # in questions possible is the glare disconnect. I have three sx200 the encouter the same problem (T1/PRi is from the same CO. Twin Falls. The Telco is running NI2.
I have been around and aroung with the telco at T1 level and the PRI. The telco finds the timing correct with their T-Bird. The telco does not have remote testing on these sites.
Steve McCoy
|
|
|
Forums84
Topics94,291
Posts638,807
Members49,767
|
Most Online5,661 May 23rd, 2018
|
|
2 members (Keyset6, justbill),
136
guests, and
395
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|