Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PRI/Magix

Status
Not open for further replies.

FoneDude66

Vendor
Apr 22, 2003
170
US
I'm having PRI problems on a Magix 2.2. I programmed it the exact same way that I have always, but something is not correct. The CO says that they can see the Magix sending back a "user busy" whenever a DID is called. When I try to make an outbound call, I get fast busy as soon as I access the PRI pool. I am running clean on my side and they claim to be on theirs as well. I brought a new 100DCD module today and tried that, but still the same result. It is going into a DMS-100 and the protocol is NTNAPRI. I'm not sure what to do on this one. Thanks in advance.
 
Print your PRI Translations and let's see if anything was missed.

ALSO, if they are emulating 5ESS - Make sure they are doing CUSTOM, not NATIONAL.

 
If this is a DMS100 check with the provider to see if the " L1 Flag in the Trunk Sub Group" is set to yes. I believe this is necessary.
 
Certainly sounds like a protocol issue.

Pepperz at newper dot net
 
NTNAPRI is a Nortel custom protocol for Nortel switches, it will not work correctly with a Legend/Magix. Request the carrier to use protocol u-459 (AT&T custom) in the LT-DEF. DO NOT accept any arguments to the contrary. Then change you setup to be AT&T custom, reboot your switch and you should be in business.
 
If the CO switch is a Nortel switch, then the correct setting is to be either DMS-100 or 250 on the Magix side, and have the carrier set their Nortel switch to NTNA protocol.

Pepperz at newper dot net
 
I checked the L1 flags right from the beginning, and we tried all the possible protocol combinations known to man.

After having an Avaya engineer in the switch for an hour, they discovered that the individual channels had busied themselves out. The DCD module had been in the switch for almost two years without being used and apparently busied themselves as a result. The actual module itself was not busied out, but the channels were. Thanks again for all of the input. I have a couple more stumpers and would appreciate any thoughts on them once again.
 
I guess I must ask, if you have access to AVAYA ENGINEERS, why are you on this site?
 
2 Reasons:

1) It was on the customers credit card, and..

2) I have gotten much better information from this site than I have from Avaya.......plus, the people are much nicer here.
 
I have gotten some really good help from here and I appreciate it.....especially since our Tech Support isn't
5-star.
 
Two thing if this is set up as PRI they should be sending you DNIS digits not DID - the second thing is the Vendor has to have this service set up as AT&T custom or it will never work on a Merlin system.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top