atcomsystems.ca/forum Forums TDM Business Telephone Systems Avaya - Lucent Telephones & Systems Magix T1 PRI

:bang: Have Magix Rel.4.0, Rev.4.7
Configuration:
Four 412 cards( slots 1-4)
T1 PRI, 100DS1(slot 5)
Merlin Messaging Rel.3.5 in second cabinet.
Can not get PRI to work with Provider(Verizon).
Can not change provider. Not my account.
Shows D-channel lucked. Loop back from switch to Verizon through Smart Jack - no problem. Loop back from patch to T1 doesn't work. Red alarm stays on. Reset, Restor is not helping.

B-channels: 0501-0523, Group 1
Lines: 817-839, Group 1.
PRI, ESF, B8ZS, Custom(5ESS), Any Servise.
Clock is Slot 5, external Loop.

Forced Verizon changed switch at their end. The same problem - D-channel lucked.
Ordered replacement for Processor and cabinet but afraid would be the same problem, unless there is some problem with Prcessor. Yes, I forget to mention that I already changed T1 card with the same result. Used to be T1 DCD and I replaced for 100DS1. Red light stays on no metter what I do. Maintenance shows: Ron, Yoff, Goff. Doing Reset and Restore Red light goes away for a while and then coming back up.
If I request verizon tech with T-bird come on site and they find that tere is aproblem with my T1 - charge $500 would apply.I know all my program is OK, but I don't understand why I can not loopback to my switch.
Changed PR! to DS1 - no problems. Loop back is fine. !!!!!!!!!!

The biggest obstacle in getting a PRI to work on a Magix is convincing the telco to use and correctly implement the "AT&T Custom" protocol. If someone put a gun to my head and asked me to guess what the problem with THIS circuit is, that's what I'd say.

A metallic loopback to the Magix won't do squat because there isn't a way to emulate the D-Channel, so you'll always get that red light until you're sync'd with the carrier. Yes the light will go out for a bit after doing a busy/restore and clearing of the alarms. But don't be fooled; the absence of the red light doesn't mean that it's somehow working for any length of time.

I'll send you my cheater if you wanna double-check your programming. Otherwise, I guarantee that it's the protocol.

I was sure it is a protocol but they moved my circute to one which is working based on what they said and still would not get D-channel sinchronisation.
You can send me your cheater and I am sure it would be helpfull but in the mean time I am positive I've done program right. It is not the first time and is not a second. I've done PRI on Magix dosen of times and never a problem. But never with Verizon.

Thanks, Dagwoodsystems

just went though this with verizon last week,after a couple of hours it turn out to be the D channel, ask them to reinstall at their end, turns out now even verizon is contracting out their co work

also just check your error log , should say PRI D channel inoperative,

Did you remember to activate your CSU in Lines\Trunks???

The CSU isn't a deal-breaker, but it's definately good advice. The Verizon subcontracting bit is a real eye opener, though.

Some days I really pray for Ma Bell to come back so that the finger pointing can stop.

dagwoodsystems, yeah , had a customer that took verizon up last year in the desert on a fractional t-1 , didn't tell me, this year started to have problems with flashing, because they had 8 lines, tried getting to go either Telpacific or patec, 3000 to get out of contract, so i told them to change it to a PRI, morning of cut ,800 call conf Verizon csr in Florida, DS1 tech in LA, first thing out of her mouth, boy's this is my first PRI

Well, my advice is first:

Check all of your settings, especially the BASIC B8ZS & ESF.

Then, Double check them and then TRIPLE CHECK THEM as well.

After that, ask this simple question of the PROVIDER:

Is this set for NI2?

When they say "Well OF COURSE IT IS!"

Then politely remind then that WE NEED NI1, CUSTOM, NOT NI2 National.

Good luck!

Checked my setings 100 of times. Ask Verizon few times what is the protocol. All suppose to match. But I still have fillings that they are not at the switch and setings they read to me from the paper. I am positive that somthing screw uo at the switch but can not force them to take actual look. I am going to replace Processor and if problem would continue ask for technician on site.
Thanks all of you for quick respond.