sundance-communications.com Forums Telephony Discussion Phone & VoIP Systems Toshiba Telephones & Systems CIX100 eManager Access ("The Nightmare")

Im trying to access a CIX100 via dial up (as I have just plain given up on accessing it via IP) but my modem never responds to the eManager program in IE. (Known working modem)

-I have the RemoteCTX1 network built. (No telephone number)
-Pop-up blocker off.
-Using available IP addess of 192.168.255.2 in the Internet Protocol Version 4 for RemoteCTX1
-All Firewall settings off
-https://localhost listed in exceptions under the Intranet
-Communnity Name is correct
-2 seperate modems used
-I am using V5.20B21 with IE 8.0 on Windows 7 32 bit.

Can someone suggest anything to get a modem connection to the CIX100 please?

I guess first, why isn't it connecting with direct IP? Are you sure the processor IP is correct and that you are using a crossover cable if the laptop is old enough that it doesn't have an auto negotiating NIC. I would check the IP in programming to make sure.

As for the dial-up connection the only thing I don't see in your check list is the telephone number entered in the dial-up section of emanager?

Also, have you verified that the processor has a remote modem installed?

What software are you running? In older software the NIC locks up and you cannot access the system via direct connection or modem until you reset the system. Checking program 916 on the phone when the system is in this state will also give a nasty surprise since it reboots the system.

If there is an IES or ES VM there will not be soft keys either.

On the older processors MK063 reliably addresses this issue.

So I finally found the issue. When my PC was removed off the domain and the software installed, it created a local admin account on the PC and the software was installing within that admin account named "eManagerUser". Unknown to me, this account was being erased via the workstation policy when placed back on the domain. With IT's help, we had to create a new container in AD which would allow a local admin account called "eManagerUser" to remain on the machine.

This is why both the IP and the Dial-up weren't working.