cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1603
Views
0
Helpful
2
Replies

CUEAC - Call Park Issue / Call Parking Devices Field

comms
Level 1
Level 1

Hope someone can assist.

I've running CUEAC v8.0.3.9 and client version is OPR.8.0.3.562. I've got 9 call parking devices setup and when I run the CUCM Sync Report on the server is says the sync to my Park Devices are is "completed". The CUCM I'm running is v7.1.5.30000-1

When I use the AC client, Call Park doesn't work - instead it disconnects the call. If I use the phone (the DN is associated with the AC) to park the call it works fine.

All that shows on the Call Park area on the AC is where the last call was parked at.

All other call handling such as answering, hold and transfer through the AC works fine.

I've searched through all the threads but without success.

Any ideas?

2 Replies 2

Jonathan Schulenberg
Hall of Fame
Hall of Fame

The CUEAC call park is *not* the same as the CUCM call park numbers. You need to put in new/unique extension numbers which CUEAC will create as additional CTI ports.

Tommer Catlin
VIP Alumni
VIP Alumni

There seems to be a few bugs in CUEAC and how it syncs.  It does not seem to fix the auto add in all the devices the AC application user is to control.  You need to make sure that the CTI application user you are using for CUEAC has control of ALL of the devices it wants to, or the ports for Park, Hold, etc will not register.

So check your configurations in the Sync process that CUEAC did in fact create the Park CTI Ports.  If it did and they are not registered, you will need to check the following:

- The CTI Ports for Park are controlled by the Application End user used for CUEAC (not the AXL user)

- Check to make sure your TSPs are setup correctly on the CUEAC server.  This means that you have 255 set, and the time is at 300.   If the ports are still not registering, try uninstall the TSP, unistall the wav drive, then reboot, reinstall TSP, do the settings for 255 and 300, then install the WAV driver and then reboot.