UCID causing Tserver lockup

[Marc Brenowitz]

Hi. I�fm hopeful that you may be able to provide us with some help. We have been using Genesys Tserver/CTI for some of our call center groups. We have just added Avaya Tserver for another group. In order to use Avaya Tserver, the phone switch was configured to send the UCID field. When the UCID is sent, Genesys Tserver errors out, the UCID transmission must be disabled, and the server hardware must be rebooted in order for Genesys Tserver to function again. Is there any way to prevent Genesys Tserver from locking up when the UCID is sent? Please excuse my poor understanding of this; my team owns Genesys Tserver for historical reasons, but we are not a telecomm support group. Thanks for your help.

[Superglide]

Hello,

Why are you using UCID? We have an Avaya G3 but have set the "matchcallsy" field to UUI, which is working perfectly. Note that UCID must be enabled at both the switch and TServer ends so that both systems are in Sync.

What do the TServer Logs show when the error occurs?

Plus read the TServerG3 reference manual page 85 for further information on these settings.

Graeme

[Vic]

Hi,

what version of TServer do you have?

By the way, could someone tell me the benefit of using UUI over UCID for multisite configurations?

what is wrong with UCID? Why would people consider using UUI instead of UCID?

[macca]

Hi,

According to the manual you need to use UCID for predictive dialing.

Also with UCID enabled you can use the call-cleanup functionality of the T-Server to remove those pesky stuck calls.

However you only need to set 'enable-ucid-swap' set to Yes for this to work. You can leave the 'match-calls-by' set as UUI.

If the primary reason for using UCID is the call-cleanup functionality maybe you should test out using uui?