MAGIX PRI can receive, but not place calls HELP!

[broody81]

Hi All, We are putting in a T1 from XO which is PRI ATTCUSTOM, and I have 3 others at three other sites, same carrier, same system. This one will not place outbound calls. I dial 9, get the system dial tone, dial and there is a 3 second pause before fast busy. They never see it hit the switch on their end.

I have Group 1 B channs, pool 892 , lines 837-859, CBC, patterns 00=0 thru 09=9, Dial Plan Routing > Service > 0 > Misc > Any Service and ARS programmed, 4ess as with the other sites, I mirrored everything I have done in the past and I gave them the other accounts to look at and compare on their end. They say all is exact. The only odd thing on this one is that they wrote the order incorrectly for NI1 and fixed it that morning. Once fixed, we had no issue receiving calls. Still could not place. No red light on 100D, I have restarted the system, looked at outgoing table closely, tried dialing with 1 and no 1. Not happening.

Anything I can try or tell them to look at??

Thanks!

 

[TouchToneTommy]

Give an extension pool dial out access to 892, and dial that instead of 9. You'll be dialing directly on a channel. Make sure ARS and tables are not an issue.

 

[broody81]

Hi, I added DIAL OUTCD 892 to 2 phones. When they dial 892 they get a dial tone, but when they dial with or without a 1 they get a fast busy still. Is that our dial tone or theirs???

 

[dagwoodsystems]

I ran into this problem once with SBC/PacBell. Inbound calls worked fine, but I was getting busies on the outbound.

Turned out that the telco's "AT&T Custom" profile needed some tweaking. This old protocol is the one Achilles Heel of the Legend/Magix, but fortunately there's a great deal of info on the topic in these threads.

In my case, it took me a little over an hour to convince SBC to revisit their config. The telco tech that I was working with had a nearly unshakable belief that the PRI couldn't possibly be up and running with inbound calls if the protocol wasn't correct.

 

[kwing112000]

I have had the same thing. THey had NI2 and we could get incoming but no outgoing. Forced them to check and they found it and it came right up.

 

[TravelingTom]

I had the same problem and could not dial out. I missed a step in the setup
Set Network Service.
Ntwk Svc=>Misc=>No=>Enter.

Good luck

 

[broody81]

Thanks to all for your replies so far. I am assured it is not NI1 or NI2, but will ask them to check again. What are L1 flags and should I be asking about them? Also, I had an old PRI document written by a guru in Denver years ago stating that the 100D mod had to be a certain rev or higher. I just wanted to mention that I satisfied that reqquirement as well. Thanks! I will go at it again on Monday and see what happens.

 

[dagwoodsystems]

I believe the L1 Flag (which should be set to Yes) only applies to DMS switches. Other parameters relevant to the Nortel DMS can be read in thread689-929943. Check out the last entry, which was written by mountain52.

Also, thread689-809750 reminds us to status the B-channels after any significant change or anytime your trunks go into a busy state. If they have been busied out, you'll have to restore them one at a time.

Most of all, hold your ground. Make sure your programming is correct, but then hold your ground. Suffice it to say that some carriers uh...have a better handle on these problems than others do. In this case, I'm especially suspicious that something was missed on the telco side because it was incorrectly provisioned in the first place. Experience has shown that changing the protocol piece of the circuit's "personality" offers a great deal of opportunity for further mistakes on the telco end.