There is a DOS tool called PORTQRY out on the internet (google it) that will let you query a particular port using an IP address. If the NSP is responding to ping commands, try a portqry to see if port 59002 is listening for UDP or TCP traffic. Not really a solution, but just a diagnostic tool.
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
I connect to the NSP IP Address of the cabinet on port 59002 and it claims the network card is not responding however in fact does respond to ping and the IP phones are up and running.
The IP phones are not on the NSP card. They would be working on a different IP address than the NSP. Check to make sure you are using the correct IP address for the NSP card. You can use Hyperterm or some other terminal emulator to connect to the NSP. A carrige return should prompt for a password.
One thing you can try before calling TS is go into a command prompt and type : telnet xxx.xxx.xxx.xxx 59002
If the NSP has a session that is stuck it will say something like "NSP currently in use by vvv.vvv.vvv.vvv" if that is what it says, call TS, it will take them 2 min to remove it.
If they issue an NSP reload, be sure to warn any users with VIP that they will need to EXIT Outlook and then come back in once the NSP is cleared.
I am having a problem programming via ESI-Access using the Network option. I connect to the NSP IP Address of the cabinet on port 59002 and it claims the network card is not responding however in fact does respond to ping and the IP phones are up and running. There is no firewall in front of this system and its a direct connection to the DSL modem with a public IP so there are no firewall issues here.
Any ideas?
Re-boot the router, on site where the ESI is installed. Been there done that.
