Cannot get pri d channel to synch on Merlin legend r7

[cray27249]

Changed 100d cards
Installed new
Processor
Upgraded power module
Any other suggestions

 

[TouchToneTommy]

Verify settings with carrier. Remember the Legend/Magix are very limited on the protocols that they can accept, and in some cases require the telco to make additional tweaks on their side even with standard protocols.

 

[merlinman]

Curve Balls they Vendors throw are (but are not limited to):

They use NI2 - Our PRI can only be NI1.

They can't change from NI2 - OUR PRI CAN ONLY BE NI1!

They want us to make it do XYZ - We only have Certain, BUT LIMITED protocols we can use (as Tommy said).

They don't use the same SWITCH TYPE that we do.


Curve balls Legend/Magix programmers throw:

T1 is set up wrong. It needs to be ESF & B8ZS.

Wrong switch type.

Again, those are a few of what can go wrong, there are too many to list, but these are the Main "D" Channel affecting ones.

http://home.comcast.net/~merlinman

-merlinmansblog.blogspot.com

 

[mforrence]

Did it work before and stopped, or is this a new PRI?

 

[Telecomboy]

I had a similar issue recently with an ATT IP flex circuit. When it was installed ATT claimed it was set to custom 5ESS. It worked for about a month and then went down. Turned out they had it NI2, then they said they did not have any legacy settings so we tried DMS100 on both ends....failed after 2 days, then 5ESS on both ends....failed after a week....we even tried 4ESS, which failed immediately. Finally I got someone on the phone that said they had a "legacy 5ESS" setting they could choose. Nice since they kept claiming they did not have this for weeks (only NI2, 5ESS, DMS100, and 4ESS I was told over and over again). They set their router to "legacy 5ESS" and the Magix was set to 5ESS. So far so good, been a couple of months with no complaints.

 

[CarGoSki]

exactly. When the soft switches first arrived they were not very good for Merlin PRI. They would work until the system was power cycled then would not sync again. Since then "custom" has improved quite a bit however at this point if it is still an issue then it is a likely carrier issue. Probably set to something other than custom or 5ess