OpenUI 126.96.36.199: @ClientHostName @ClientIP Not Working Through LoadBalancer, CTI Hoteling Not Working
(Doc ID 1926737.1)
Last updated on JULY 06, 2017
Applies to:Siebel CTI - Version 188.8.131.52  to 184.108.40.206.17 [IP2013] [Release V8]
Information in this document applies to any platform.
The customer is using a loadbalancer or other network intermediate devices the information returned by the Communications Configuration macros
is not correct, it contains the LoadBalancer information of the network device instead of the workstation hostname. Basically CTI Hoteling is not working properly.
The solution AutoLoadDriver =FALSE where the user enters the Workstation name manually does not work for our business requirements:
"How to use Siebel CTI Hoteling feature with Siebel OpenUI when there is a proxy between IE and Web Servers (Doc ID 1578061.1)"
What we need is detailed information on how Siebel determines the hostname of the user workstation, this will allow us to investigate what could be done at the network level to solve the issue. Or if Siebel has a solution for this scenario please inform us how to solve. Previously we used a ActiveX control on Siebel 8.0 HI in order to pass the hostname information to a Siebel ProfileAttr, this is not a solution since the upgrade to OpenUI
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document