So I can and have installed the Desktop Suite on the users who want it, after squaring away the settings in 10-20. All of the features work fine except if I enable Shared Services in the desktop configuration, This stands to reason because I can not get Shared Services to install back on my Phone Server box that has the ACD/MIS server suite installed. I go through the install, it sets up the Telephony Driver first and asks for the PBX IP, the CTI port(in 10-20-01), and the server address (127.0.0.1). But that's for the telephony driver. That installs fine. Now the Shared Services install starts, but there's no prompt for any information(this may be OK), and the install completes NEC installer says all is well. When I go to run the NEC Services Configuration i get a CTI Communications error "Unable to connect to the telephone system".


I've been over the config too many times now...it should be working. I have tried using both the 3rdParty CTI (8181) and 3rd Party (8282)

I got my licenses ... dunno here.

NEC Highly recommends not having any other applications on the PC running the MIS/ACD software.

Is this on a UX500 or a SV8100?

If on a UX5000 you have to have the shared services License.

I may be wrong but i think on the 8100 You have to be at 4.0 or higher to have shared services license

Yes, sv8100

Main Software 04.00 with Licenses for both Shared Services and Desktop Clients.

my above post should have read:

I have tried using both the 3rdParty CTI (8181) and 1st* Party (8282)

Try telneting the phone ssytem using the port you are using to verify that you can get into that port. ie: telnet 192.168.0.10 8181
You should get a blinking cursor if it conects and hit enter a couple times to see if you get a reply.
If not try changing ports in 10-20
I would try to install it on your Laptop if all else fails, I am assuming you can ping and enter the phone system from the PC.
Have you tryed to reset the PBX.

on 8181, I just get a cursor, and get booted upon pressing enter.

on 8282 I get the following 'ack'

►☻♥p☻►♥


I really don't see any reason why this wouldn't be communicating. Yes I've reset the PBX recently due to a faulty CF.

That sounds normal for telnet, just get a blank DOS box.. On several sites we have had to change to CTI port to 8182 to get it to work.. Our office system is setup with this port.. We've had real grief with this stuff down here and try to avoid selling it if possible..

which did you change to 8182

10-20-01 (CTI Server)
or
10-20-09 (First Party CTI)

Ok, start with basics here:

1.Can you ping the shared services Ip address from the client and vice versa?

2. Can you ping the domain name of the shared services machine from the client and vice versa?

When you open the Desktop Config (close desktop first) make sure the 8282 port is defined as the CTI port, make sure that O&M user port is set to 8010 and user= USER1 password=1111

Make sure Shared Services is check-marked with the server IP address in the fields below.

Check program 10-20 in the PBX.

Make sure 01=8282, 09=8181, and 11=8010

Make sure you are running 3.6.3 (latest for now, 3.6.9 is due out soon)


All I can think of of the top of my head....

10.20.01

@doghart

1. Yes
2. Yes
3. 8282/8010 is defined on the clients

"Check program 10-20 in the PBX.
Make sure 01=8282, 09=8181, and 11=8010"

according to the Docs, 01 should be 8181 and 09 should be 8282 (I have left the defaults in the Desktop setup, and Desktop works without Shared Services.)

My issue is that the Shared Services Server itself is unable to connect to the PBX. From the Desktop clients I can telnet to 192.168.1.250 8888 so the service is listening, but since the service itself can't connect to the phone switch, neither can the Desktop clients.

Telnetting from the Shared Services Server, I can reach both 8181 and 8282.

The following image shows the steps and result of a clean Shared Services install.

https://junkfiles.org/grrr.jpg

Wow. That did the trick. Trip out. So is this a bug somewhere, I did a scan on my network and nothing else is listening on 8181 either inside or outside to conflict with Shared Services.

@doghart - have you run into this in 3.6.3 or the one you're beta'ing? I'm still on 3.6.2

No, we are using 3.6.3 at two locations and 3.6.9 in our office. All are using the default ports 8181, 8282 and 8888.

I can get you 3.6.3, it's officially released but I would wait for 3.7 which is in beta now under 3.6.9.67 version.

Email me if you have an ftp site I can upload 3.6.3 to if you want it. You would have to replace the Shared Services and each of the desktop clients. Can't mix/match.

Chuck