Hello,

I was wondering if anyone has this issues and found a solution.

two days ago our network eManager for our Toshiba strata CIX 670 stop working. when trying to open the icon it gives this error " the remote device or resource won't accept the connection" when checking the details of the error I get "The device or resource (localhost) is not set up to accept connections on port "The World Wide Web service (HTTP)".

I have rebooted the phone system, check all network connectivity, look online for any troubleshooting for that issue applied. no luck.

Any ideas?

also, the data collector stop working as well after rebooting the system. It opens up but it doesn't not record any calls. "waiting for data" is showed on the screen.

any help about either of this two problems would be greatly appreciate it.

Thanks,

Can you ping the processor?

I have little experience with phones systems. I don't know exactly what you mean by the processor. I ping all the IP we have documented related to the phone system and I was getting a response.

We have dedicated computer that runs the network eManager, the call collector and the voicemail system. I have done different trouble shooting to that pc. Everything looks ok.


I rebooted the phone system, it came back up fine. I can ping all cards in the system.

Thanks for the help.

Pm'd you

any ideas.. anyone?

Did you PM "phonemeister" ?

yes, we have been talking. I have been answering his questions and following what he says.
Still working with him but no solution yet. This is a rare problem.

I was just wondering if anyone else have had this problem before.

Is the call collector doing this via RS232 or LAN capturing?
Have you tried deleting the I/O SMDR device and re-creating it again?
Has the IP address of the processor changed or been defaulted?
Do you have any remote access to the CIX670?

He has more than one issue at hand and they may be network, OS, or hardware related. Not sure at this point but I've suggested that he calls out a Toshiba tech to troubleshoot his issues on site.

OK thanks for the heads up

Sorry for the delay.

I got a hold of Toshiba. There were some windows corrupt files. only solution was to reinstall Windows.
So I ended up leaving the other programs on that PC and install the eManager in another windows 10 PC.

it work for 3 days, now it gives me the "Service Unavailable" error 503.

any ideas?

I have restart every service need. uninstall and reinstall the eManager.


Thanks,

is the win 10 pc on a domain? did you check you popup blocker? Are you using IE not one of the other browsers? Did you use the correct Network Emanager for Win 10?

"It worked for 3 days..."

You didn't install or update Anti-Virus did you?

Different circumstances, but I was recently using remote desktop on a PC with a free anti-virus and succumbed to their repeated requests to upgrade to the paid version. Long story short, the RDP connection dropped in the middle of the install. I couldn't even ping the local IP address, so I figured the PC needed rebooted.After finally getting to the machine, the local console was working fine, but only after a couple re-boots and a lot of hair-pulling I discovered that the AV had added it's own firewall that was locked down tight. I didn't have emanager to worry about, but I was running several remote services in addition to RDP and never did get everything running. I finally disable the AV firewall and went back to Windows Firewall and everything is mostly back to normal.

My suggestion is install Network eManager onto a Windows 7 operating system as it is much more stable then Windows 10

Thanks for your replies.

I removed the PC from the domain. I was using IE. I got the correct network eManager for windows 10. Nothing was being blocked.
I didn't install anything to PC. Actually it work from Wednesday to Friday. PC was off during the weekend. Turn it on on Monday, didn't work. No updates or anything.

it was installed on a windows 7 machine but some files got corrupted and the solution was to reinstall windows. and then the we have do installed callwhere system, call collector, etc. it seemed worst than just installing it on Win 10.
And we don't have another win 7 spear since all does go to production to run their batching software etc.

but after the 3rd time restoring the PC to a earlier date. reinstalling the eManager, going through every service and feature that need to be running.

It finally started working. Biggest Pain in the A...... lets see how long it lasts

we are going to be getting a new phone system soon This is just a temporary solution.

Thanks again.

Oh the joys of Network EManager

Can I help with the above. I have a great solution.