|
Joined: Dec 2004
Posts: 31
Member
|
Member
Joined: Dec 2004
Posts: 31 |
The switch Cox is using is DMS500. What should the Magix be set to for this? Right now we're set at DMS100.
|
|
|
|
Joined: Dec 2005
Posts: 9,181 Likes: 9
Spam Hunter
|
Spam Hunter
Joined: Dec 2005
Posts: 9,181 Likes: 9 |
The DMS-500 does offer 5ESS protocol. You can give it a try and see how things work out.
I Love FEATURE 00
|
|
|
|
Joined: Feb 2007
Posts: 2,473
Member
|
Member
Joined: Feb 2007
Posts: 2,473 |
Pattern 8 has to be deleted because it's using 2 digits(72) instead of 4 and striping 1, which is 7 from that entry. You left with #2. What that digit supposed to represent? Somebody made a mistake but that Pattern might create a problems for incoming calls. Ask your provider set you up for 5ESS, go To Maintenance > System > Error logs > Permanent and then Transient. Use assigned Drop 44XX button to clear all logs(Drop with SPM) then go to your slot where T1 is and do Reset and Restore. You should be good to go.
|
|
|
|
Joined: Dec 2004
Posts: 31
Member
|
Member
Joined: Dec 2004
Posts: 31 |
I put the CSU back. I know Cox said they could do NI1. I'll check to see if they can do 5ESS. I'll also check with my local guy about those dialing patterns.
|
|
|
|
Joined: Mar 2002
Posts: 3,630
Moderator-Avaya, Nortel
|
Moderator-Avaya, Nortel
Joined: Mar 2002
Posts: 3,630 |
What are your extension nubmers? 200-299? I would get Cox to send you three digits instead of 4. I would change the protocol the 5ESS. I would then completely rebuild the PRI programming from scratch to make sure you don't have any corruption on the PRI side of the switch programming. I have had it happen before. If you do those three things, and your still getting dropped calls...you can bet its an issue at the carrier.
|
|
|
|
Joined: Jan 2007
Posts: 1,951 Likes: 2
RIP
|
RIP
Joined: Jan 2007
Posts: 1,951 Likes: 2 |
I strongly agree with the suggestion made by upstateny. The alarms you're seeing indicate a problem with the physical layer (wiring) and not protocol.
Forget about making changes to your Route By Dial Plan patterns. None of those entries have a thing to do with whether your PRI stays up or not. And if there were any mismatched, undefined or otherwise senselessly patterened DID calls, they would automatically be sent to the Operator.
Also note that NI2 is not a protocol that the Legend/Magix understands. While it's true that NI2 "is pretty standard", I'm willing to bet that's NOT what's running on your circuit. No matter. I've seen these errors reported soooooo many times, and the problem is neither the CSU, nor the processor or T1 card. There is a problem with the copper pairs on which the PRI is delivered, which means that you should check your patch cord (from the T1 card to the demarc) as well.
"Press play and record at the same time" -- Tim Alberstein
|
|
|
|
Joined: Dec 2004
Posts: 31
Member
|
Member
Joined: Dec 2004
Posts: 31 |
It's fiber optic cable coming into our building. Does that make a difference?
|
|
|
|
Joined: Dec 2004
Posts: 31
Member
|
Member
Joined: Dec 2004
Posts: 31 |
CSU is back and I had Cox switch to NI1 this morning (02/26). I will watch for a day to two to see how it goes. Z-man, is there a way to wipe out and reprogram just the PRI info?
|
|
|
|
Joined: Feb 2007
Posts: 2,473
Member
|
Member
Joined: Feb 2007
Posts: 2,473 |
If you familiar with Magix it's takes 5 minutes to reprogram PRI.
|
|
|
|
Joined: Dec 2004
Posts: 31
Member
|
Member
Joined: Dec 2004
Posts: 31 |
After the switch to NI1, the constant "PRI SVC AUDIT TIMEOUT 07/02" errors we were seeing have gone away. Have not had any complaints about dropped calls either. I'll keep my fingers crossed. I appreciate everyone's help on this.
Tom Kerschen Southwest Paper
|
|
|
Forums84
Topics94,521
Posts639,995
Members49,851
|
Most Online5,661 May 23rd, 2018
|
|
|
|