MAGIX PRI Incoming Problem

[dholmes45431]

Have a Legend R7 on a PRI with rock steady performance for years, about half of the system is comprised of Magix modules in clam shells, including the the processor as a result of office growth.

Moving to a new building and using the opportunity to upgrade to Magix carriers, 100 DCD, 016, more MLX-16 etc. Have setup a Magix carrier with a seprate new processor, 100DCD and MLX-16 to initially configure the new system. Testing involves just moving the incoming PRI from the Legend/external-CSU to directly to the Magix 100DCD.

Have used the print out from the orginial system to program the new system exactly, even matched both printouts. Magix of course has the internal CSU activated.

Outgoing local and long distance calls works as expected. Incoming to the office number (via cell phone), gets a fast busy and "network busy" message on my cell phone. Return the PRI to the Legend and the old system (which still supports the office works perfectly). Sounds like a dial plan table problem in the new system, but everything (all the PRI settings including the dial plan table, extensions, etc.) are exactly as in the Legend. Is there something unique to the Magix that I'm missing??

BTW, have also done a Frigid start and used the FAQ checklist to program with no change to incoming calls status on the new system...

Thanks!

 

[SYQUEST]

Phonesrus,

When using CSUs in that fashion, I hope you are using REAL T1 cable! 'Cause CAT 5e isn't! And cable shields are for grounding!

A flexible CSU should be transparent to format and protocol, etc. That is why I suggested disabling the CSU and/or changing modules.

I remember reading a QPPCN about a CSU problem on the 100DCD awhile ago and one of the suggestions was to disable the CSU.

The telling item is the fact that the Legend works but the Magix doesn't work on the same PRI.

....JIM....

 

[phonesrus]

SYQUEST,
Actually it was OLD Cat 2 House cable, 50Pair underground Jelly, but Hey, it worked!

Issue could be a hardware problem, but I am still thinking some sort of a protocol issue on the Magix with the "D" up and "B's" confused based on the ability to call out, but not in. We really need a "D" trace with cause codes, and a look at the PRI config.
It would be helpful to know what kind of CO Switch we are dealing with, too.
It might be something that just got missed, dholmes said and showed that the settings have been changed several times. Heck, we have all done that at least once!

 

[SYQUEST]

According to the printout posted for this thread the CO switch is a DMS100. Now since dholmes said he moved the system from one location to a new location, he never mentioned whether the CO was the same or not and what type of switch he is served from.

So this being the situation, my next question is: dholmes what switch is serving your Magix and what protocol is specified on the order from the service provider?

With all the history on this forum about the Legend/Magix with PRI ISDN it boils down to two protocol options:

5ESS = AT&T CUSTOM

DMS100 = NTNAPRI & "L1 flags" in the "Trunk Sub Group" table must
be YES.


Because of firmware differences between DS1 modules in the Legend series and the "newer" Magix series, protocol can be a critical factor as to whether the module will function properly.

dholmes we await your response.

Phonesrus, one comment about the T1 cable. Cat 2 is OK. The key is NOT to have adjacent pairs when using multipair cable, especially on long runs. So use a pair from each binder. This way you can minimize crosstalk problems. The ideal situation is for the TX & RX to be separately shielded and grounded.
This also helps the T1 wave form integrity. The Quabbin Cable website has some excellent tech notes about this subject if you want more info.

....JIM....

 

[phonesrus]

With all the posts I missed the DMS-100, dholmes also said he is running the two systems side by side, just moving the T-1 between them for testing. That alone is one of the major reasons I forsee a protocol issue somewhere in the Magix, or worst case, a hardware issue.

BTW: On a DMS-100/250 the equivalent Emulation package for "Custom" is called U-459.

We shall have to wait until dholmes pops back in to find out how he is progressing, and catch up on his reading.

 

[dholmes45431]

Update...phonesrus' last post correctly states the setup. Currently verifing protocol setup with the CO.

Thanks for the replys

 

[dholmes45431]

Update, Working with CO (SBC-who does not/will not support 5ESS emulation on the DMS) on PRI settings to resolve why my 100D-Legend card works and my 100DCD-Magix does not support incoming call but outgoing is fine.

Currently have NTNAPRI protocol, and the L1 flags are set to yes (SBC claims L1Flags are normally set to Yes (Y) with a DMS Custom protocol PRI when the CPE is Non-Nortel)

There is another setting in the same LTDEF Table that was unaware of. "The option of PROFNAME can be set to NIL or SL1PROFL. This must be specified by the CPE vendor with the DMS Custom option. If set incorrectly, the B Channels will not go into service."

Anyone know what the meaning of the two setting are and/or more importantly what is the correct setting for a new 100DCD?

Thanks for the help!!

 

[merlinman]

Well, back to basics here.

The LEGEND/MAGIX ONLY USES CUSTOM Protocol, not NATIONAL.

I don't know what SBC's Settings are supposed to be, but I would be willing to bet they have some LEGENDS/MAGIXS that DOE WORK and should be able to make sure that your customers' service is set that way.

 

[phonesrus]

The AT&T Custom protocol in a DMS switch is U-459 in the LTDEF. If they refuse to use it start asking for managers names (escallate by stepping on toes)until you get one to agree. SBC does support AT&T custom, because I have many customers on DMS switches around Texas. The most likely reason is the Tech doesn't know how to set it up, I've seen that before. Also, if memory serves, you want the SL1profile (PROFNAME). I will double check that with a friend at SBC ISDN group.

 

[SYQUEST]

Dholmes,

I just wondered if you ever tried swapping the DS1 cards between the Legend and the Magix to see if the problem followed or stayed?

Also, I guess the Texas SBC people are very different from the California ones. The tester I worked with in the Pasadena,CA TRCO was very cooperative. I was able to do all my testing before the cut. This was a Supertrunk to PRI conversion and I had a second DS1 module to play with prior to cutover so regular service was not disturbed.

....JIM....