|
|
|
|
Joined: Jun 2005
Posts: 2,709 Likes: 7
Member
|
Member
Joined: Jun 2005
Posts: 2,709 Likes: 7 |
In the past here is what I have seen to cause a failure to connect:
Wrong IP
Incorrectly IP or subnet settings on admin PC
Duplicate IP
(since recieving a ping reply while directly connected, I would assume the above don't apply)
Bad NIC (usually I have seen on older ACTU1A processors)
Admin locked up (typically when using a Stratagy ES voicemail, and corrected by a cycling power)
Network emanager pre-install requirements not installed (But they are now installed with the emanager installation)
Broken NEM install (usually results in html, ASP, or other IIS type errors.)
Wrong community name, or default was changed on the CIX.
|
|
|
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.
|
|
|
Forums84
Topics94,298
Posts638,868
Members49,769
| |
Most Online5,661
May 23rd, 2018
|
|
|
1 members (KRRath),
138
guests, and
303
robots. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|
|
