Magix PRI down 2

[thephonelady]

Hi all- my customer has a Granite PRI that went down on Wednesday- I was out there yesterday and the circuit seems to be up- no major alarms in the Magix- no incoming or outgoing calls. Granite says they see no issues on their end but seeing call rejection on the channels coming from the Magix. no programming changes have been made and I know that 9 times out of 10 it is a provider issue. I'm going to attach the the errors I'm finding. My vendor is shipping out a replacement DS1 just in case. Any thoughts on a possible cause. Thanks in advance.
Last 99 System Errors:

Message ss/pp Cnt First Last Code
PRI SVC AUDIT TIMEOUT 08/01 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/02 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/03 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/04 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/05 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/06 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/07 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/08 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/09 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/10 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/11 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/12 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/13 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/14 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/15 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/16 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/17 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/18 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/19 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/20 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/21 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/22 - - 04/14 14:21:57 7001
PRI SVC AUDIT TIMEOUT 08/23 - - 04/14 14:21:57 7001
PRI SVC STATE INCONSIST 08/23 - - 04/14 14:25:38 7002
PRI SVC STATE INCONSIST 08/23 - - 04/14 14:25:40 7002
DS1 SLIP ALARM 08/00 - - 04/14 14:30:43 6C0A

Slot 8 Switch: 5ESS

System: By line

BchnlGrp #: Slot: TestTelNum: NtwkServ: Incoming Routing:
1 8 CallbyCall By Dial Plan

Channel ID: 23 22 21 20 19 18 17 16 15 14
13 12 11 10 9 8 7 6 5 4
3 2 1

Line PhoneNumber NumberToSend
813 9443281
814 9443281
815 9443281
816 9443281
817 9443281
818 9443281
819 9443281
820 9443281
821 9443281
822 9443281
823 9443281
824 9443281
825 9443281
826 9443281
827 9443281
828 9443281
829 9443281
830 9443281
831 9443281
832 9443281
833 9443281
834 9443281
835 9443281

Network Selection Table

Entry Number: 0 1 2 3
Pattern to Match: 101**** 10***

Special Service Table

Entry Number: 0 1 2 3 4 5 6 7
Pattern to Match: 011 010 01 00 0 1
Operator: none none none none none none none none
Type of Number: N N N N N N N N
Digits to Delete: 0 0 0 0 0 0 0 0

Call-By-Call Service Table

Entry Number: 0 1 2 3 4
Pattern 0: 0
Pattern 1: 1
PRI INFORMATION


Pattern 2: 2
Pattern 3: 3
Pattern 4: 4
Pattern 5: 5
Pattern 6: 6
Pattern 7: 7
Pattern 8: 8
Pattern 9: 9
Call Type: BOTH BOTH BOTH BOTH BOTH
NtwkServ: No Service
DeleteDigits: 0 0 0 0 0

Entry Number: 5 6 7 8 9
Call Type: BOTH BOTH BOTH BOTH BOTH
NtwkServ:
DeleteDigits: 0 0 0 0 0

Dial Plan Routing Table

Entry Number: 0 1 2 3
NtwkServ: Any service Any service
Expected Digits: 4 4 0 0
Pattern to Match: 3281
Digits to Delete: 0 4 0 0
Digits to Add: 3000

Entry Number: 4 5 6 7
NtwkServ:
Expected Digits: 0 0 0 0
Pattern to Match:
Digits to Delete: 0 0 0 0
Digits to Add:

Entry Number: 8 9 10 11
NtwkServ:
Expected Digits: 0 0 0 0
Pattern to Match:
Digits to Delete: 0 0 0 0
Digits to Add:

Entry Number: 12 13 14 15
NtwkServ:
Expected Digits: 0 0 0 0
Pattern to Match:
Digits to Delete: 0 0 0 0
Digits to Add:

 

[merlinman]

Well this doesn't look very good.

Is the RED LIGHT on the T1 (AT THE PROVIDERS EQUIPMENT) on?

Has the PROVIDER done an "UPGRADE" or "UPDATE" Recently?

A lot of times, what happens is the PROVIDER decides to update the Circuit and it ends up getting CHANGED to NI-2.

MAGIX/LEGEND MUST ALWAYS BE NI-1

http://merlinmanswebpage.yolasite.com

 

[thephonelady]

Merlinman- it took Granite Communications 5 days to finally find one of their engineers to check the switch type and protocol in their Adtran. Once they finally set the switch type back to 5ESS the PRI magically started working again. It took all of 5 minutes to change the setting. Customer is PO'd and I don't blame them one bit.
I spoke to 4 different people between Friday and Sunday and nothing ever got done. It took the customer to call their account manager yesterday and have him light a fire under someone's rear end.

 

[merlinman]

I am not surprised in the least.

http://merlinmanswebpage.yolasite.com