NEAX IPS 2000 Busy issue

[Steika]

We have a NEAX IPS 200 at a remote site that we have linked via a Cisco VPN to our main site.

Right now, it will not accept inbound calls from anywhere and almost all outbound calls result in a busy. The almost is because it seems to route 1-800 calls to the POTS line that we have installed at the site. The POTS line can also still accept inbound calls. Also, the inside extensions work from phone to phone. The modem that is on the outside of the NEAX box has dial tone and will call out properly.

I only have Matworx currently installed at our Main site and so am accessing it from here. Whenever I connect to the remote NEAX box via IP, the task bar reads R-SURVIVAL:01. I have read some information on survival mode, but am not sure if this would be causing the issue.

I have already done a full restart of the system with no results so far.

Any ideas on what is causing this issue or tests that I should run?

 

[belevedere]

If programmed properly while in survival mode it will use the local trunks. If a reset down not synch it back up then you need to lookinto the connection between the main site and the remote. Try pinging from site to site. Check into the VPN for proper connectivity.

 

[Steika]

Good idea, but it does not seem to be the issue to me. I have ping response from both cards at the remote site from my main site. VPN is up and our IP card seems to be perfectly unaffected by the issues. Our internet there has full connectivity. Only the phones seem to have the issue.

 

[OzzieGeorge]

If it worked previously but won't now then it was obviously programmed correctly originally. If you haven't changed anything in the system then it is time to break out wireshark and see what is wrong in your network.

 

[cayres1003]

I had a similar problem a couple of years ago. The customer had changed out the network switch that the remote cabinet was connected to. The switch before was dumb and they replaced it with a managed switch that a lot of settings turned on. That turned out to be the problem. It was blocking my pbx. If there is anyway possible, I would try to connect the remote pim to the cisco router directly, just to make sure nothing else is blocking it.
have you tried to update the remote pim? EC8.... Curious if it updates

 

[Steika]

I was finally able to contact my PBX tech and we took care of this issue. Seems like the issue was the trunk/card. The 800 numbers were grabbing the POTS line for the free long distance, so they could connect. Otherwise, nothing was going out of the main ISDN trunk.

Thanks for the help, I was researching the connections with wireshark for awhile before I heard from him on specifics.