Help with NEAX 2000 IVS "restricted" call

[bwilch]

Greetings! I'm working on an NEAX 2000 IVS site. There is a primary and remote site. The primary site is not having any problems, but when we go to the remote site to make a (317) 90x-xxxx call we are seeing "restricted" on the display. We've looked through every piece of programming we can find on the remote site and have not found any restrictions out of the ordaniry. And nothing specific to restricting a xxx-90x number.

I'm not sure where to go from here. We looked at the Trunk Data, the LCR table, the Trunk Route, and everything in between we could see on the remote site. We're using the MatWorx program to interface for programming. Is there something we're missing? Any help is GREATLY appreicated... my forehead and the wall will thank you.

 

[3DNet]

From the remote site (I'm assuming you're talking about CCIS), are calls to 317-90x-xxxx routed through the primary site? If so, are you adding a 9 in the Digit Addition Pattern (CM 8A9xxx)?

If you are sending the call straight out of the remote PBX over a local route (PRI/Copper/etc) and other calls are going through, the problem is most likely in LCR (8A405).

 

[bwilch]

The calls are being routed back via CCIS to the Primary site, then sent outbound. We are not adding an additional "9" from what we can tell. The end users are dialing "990xxxxx".

When dialed, there is a delay, the display then flashes once "Busy" then the word "Restricted" is replaces it.

Thanks for the response and any other help you can offer kodiak22.

 

[3DNet]

What do the users at the primary site dial? In other words, are you dialing 7 digits from both locations or 7 digits from the remote site and 10 digits from the primary site? I'm trying to determine what digits need to be added to the route.

 

[3DNet]

Also, are calls to the 317 NPA the only calls that need routed through the primary PBX over CCIS?

 

[bwilch]

Both sites are using 7 digits (This is a local call we're attempting to make). Additionally, I'm not sure if indicating it was a 317 call was necessarily on my part. This is a local number they can dial 7 digits from the primary site, but come up "restricted" via the remote site. All other local numbers from the remote site outbound appear to be just fine (using 7 digits as should be).

There is a point to point circuit that connects the remote and primary sites together, there is then 2 in/out circuits that allow the actual calls to be placed to the LEC's. So all the calls from the remote site are crossing a point to point circuit then processed in the main switch for outbound.

 

[3DNet]

I Gotcha. Double check that 90x-xxxx is in the same route pattern in 8a405 as other local calls in the remote PBX. If so, the problem must be in the primary switch. Since you are getting a pause before the restrict tone, we know the PBX is taking all 7 digits.

Is the primary PBX a 2000 IVS as well, or is it a 2400?

 

[bwilch]

The primary PBX is a 2000 IVS as well. We're attempting to look up the data in the mux script editor and seem to be hitting a brick wall. Is there a simpler way to view/edit the data in the command line? Sorry to be asking so many questions, and thank you for your patience and assistance.

Additionally we looked at the Toll Restrictions and found them set to "none" on both systems.

 

[3DNet]

I prefer the MOC Terminal in MWS or to program through the phone. It's just faster than using the built in MATWorX commands.

Connect to the PBX and go into MOC Terminal (under tools in MWS).
Press F9. Type 8A405 and then hit F8.
Now enter 9 (as in 90x-xxxx) and then hit F8.
If you get an error msg (NONE/WRONG/etc), press F3 and try 90+F8.
You should see a 3 digit number (the route pattern no.) once you enter the NXX and hit F8.
If so, check another nxx that you know is working (7 or 71 or something). You'll have to press F3 in order to enter another NXX.
The route pattern should be the same for both.
If not, take note of the route pattern of the number with IS working, pull up the 90x-xxxx, enter the correct route pattern and hit F2.

If you want, I'd be happy to dial in to take a look. My E-mail is dwillis@aumgt.com.

 

[bwilch]

The primary switch shows 000 in the 2nd data field for the 9 and other numbers. The remote site is having problems with remote access so we are going to the site tomorrow. I will touch base with you via email with a status and perhaps we can contact you once we are on site if we have questions. Thanks for helping us on this. It has been quite an interesting experience! Programming on these system is a bit different than Avaya's ! Thanks again and talk to you tomorrow!

 

[3DNet]

Trouble has been resolved. Had to break out 9s in Area Code Development table (8A405) in remote PBX. Then set the maximum digits in 855. Test calls were completed from remote site.