Hello,

I am trying to understand how WDE communicates with other Genesys applications such as the configuration server and t-server.
We specify the application name, configuration host and port at login.
But we don't do the same for the t-server because it is connected to the application object in CME/GA.

So we can specify the IP route by which it communicates with the configuration server.
Does it then use the same IP route to communicate with the t-server for voice media? 
if not I guess it will do this using the t-server host ip/port ?
Scenario as below:
WDE installed on workstation IP 111.10.11.12 (source)
Configuration server on IP 112.10.11.12, port 2020 (destination 1)
T-Server on IP 113.10.11.12, port 3060 (destination 2)

In the WDE login page, I will specify 80.10.20.30, port 2020.  In the network, the traffic will be configured to route via 112.10.11.12.
Therefore when we reach the second page for voice login in WDE, is it now already using IP route 80.10.20.30 and initiate voice login with the t-server at the backend rather than from the source again.

We are trying to find a way to send the WDE communication traffic via a specific network whilst migrating users from an old softphone to WDE (without impacting the current users by changing the network).  I can do this for the configuration server host/ip as it can be defined in the login page or interactionworkspace.exe.config file.  I cannot see the same for the t-server anyway..

thanks,
#Omni-ChannelDesktop/UserInterface

------------------------------
WA
------------------------------

Hi Wasim,

I believe if your just talking about the TLIB communication from WDE, it goes a little something like this:

• WDE reads the connection application information from Config server
• WDE reads the host information for the connected applications
• WDE for TLIB will create a TCP connection using the host name and then use DNS to determine the IP address

So assuming the above is correct, you'll need to use DNS to point to a different IP. 
If you up logging on WDE to Debug you'll see something like the following:
19-12-02 11:25:28.252 [ 32] DEBUG bur_a_p.HAConnection - Connection HA[1]: [StateOpening<tcp://sgcca1nasip02.pam03-dev01.iams.cba:3000>]:[StateNotAvailable] is changing state from Closed to Opening
19-12-02 11:25:28.253 [ 32] DEBUG lService.sip_bur_a_p - [DuplexChannel.OpenConnection.Commit] Wait for complete. Timeout: 29987 ms
19-12-02 11:25:28.254 [ 33] DEBUG xy1.CommonConnection - [CommonConnection.SetConnectionSequenceState]: Commit
19-12-02 11:25:28.254 [ 33] DEBUG xy1.CommonConnection - [OpenInitAction] started commit
19-12-02 11:25:28.254 [ 33] DEBUG xy1.CommonConnection - Connection tcp://sgcca1nasip02.pam03-dev01.iams.cba:3000 is changing state from Closed to Opening
19-12-02 11:25:28.254 [ 33] DEBUG xy1.CommonConnection - [OpenInitAction] Connecting to tcp://sgcca1nasip02.pam03-dev01.iams.cba:3000 ...
19-12-02 11:25:28.254 [ 33] DEBUG xy1.CommonConnection - [DnsResolveAction] started commit
19-12-02 11:25:28.254 [ 33] DEBUG xy1.CommonConnection - [DnsResolveAction] [CommonConnection.ConnectSocket] Used address family: InterNetwork
19-12-02 11:25:28.255 [ 33] DEBUG xy1.CommonConnection - [DnsResolveAction] DNS has resolved address list:
InterNetwork:10.23.177.153

19-12-02 11:25:28.255 [ 33] DEBUG xy1.CommonConnection - [ConnectSocketAction] started commit
19-12-02 11:25:28.255 [ 33] DEBUG xy1.CommonConnection - [ConnectSocketAction] [ConnectSocketAction.SelectAddress] Use address: InterNetwork: 10.23.177.153
19-12-02 11:25:28.256 [ 33] DEBUG xy1.CommonConnection - [ConnectSocketAction] [CommonConnection.ConnectSocket] Socket uses: InterNetwork
19-12-02 11:25:28.256 [ 33] DEBUG xy1.CommonConnection - Socket#4468: Trying to connect to 10.23.177.153:3000



------------------------------
Jason McLennan
Commonwealth Bank of Australia
------------------------------

Original Message:
Sent: 01-16-2020 10:01
From: Wasim Altaf
Subject: WDE Communication with Genesys Servers

Hello,

I am trying to understand how WDE communicates with other Genesys applications such as the configuration server and t-server.
We specify the application name, configuration host and port at login.
But we don't do the same for the t-server because it is connected to the application object in CME/GA.

So we can specify the IP route by which it communicates with the configuration server.
Does it then use the same IP route to communicate with the t-server for voice media?
if not I guess it will do this using the t-server host ip/port ?
Scenario as below:
WDE installed on workstation IP 111.10.11.12 (source)
Configuration server on IP 112.10.11.12, port 2020 (destination 1)
T-Server on IP 113.10.11.12, port 3060 (destination 2)

In the WDE login page, I will specify 80.10.20.30, port 2020.  In the network, the traffic will be configured to route via 112.10.11.12.
Therefore when we reach the second page for voice login in WDE, is it now already using IP route 80.10.20.30 and initiate voice login with the t-server at the backend rather than from the source again.

We are trying to find a way to send the WDE communication traffic via a specific network whilst migrating users from an old softphone to WDE (without impacting the current users by changing the network).  I can do this for the configuration server host/ip as it can be defined in the login page or interactionworkspace.exe.config file.  I cannot see the same for the t-server anyway..

thanks,
#Omni-ChannelDesktop/UserInterface

------------------------------
WA
------------------------------

Hello

May i just talk about this again based on an existing problem.
So when we login (WDE), i use a NAT ip under host (72.x.x.x), port of CS Proxy (2050).  This initially works and i can proceed to the second stage (select Place), but we cannot proceed from this point.

As we are using a citrix environment, we are being told WDE is using real IP for the voice media authentication (they allow NAT ip only).  I dont think it is possible to change this in WDE, or Genesys configuration as a whole?  could be that a DNS entry is required to translate host name/ip to nat ip.
Also when closing and reopening WDE, rather than use the defined NAT ip (72.x.x.x), it is now trying the real IP for Cs Proxy.  Is this a cache in WDE ? if so is it controlled in WDE/Genesys?

thanks,

------------------------------

Original Message:
Sent: 01-16-2020 16:32
From: Jason McLennan
Subject: WDE Communication with Genesys Servers

Hi Wasim,

I believe if your just talking about the TLIB communication from WDE, it goes a little something like this:

• WDE reads the connection application information from Config server
• WDE reads the host information for the connected applications
• WDE for TLIB will create a TCP connection using the host name and then use DNS to determine the IP address

So assuming the above is correct, you'll need to use DNS to point to a different IP.
If you up logging on WDE to Debug you'll see something like the following:
19-12-02 11:25:28.252 [ 32] DEBUG bur_a_p.HAConnection - Connection HA[1]: [StateOpening<tcp://sgcca1nasip02.pam03-dev01.iams.cba:3000>]:[StateNotAvailable] is changing state from Closed to Opening
19-12-02 11:25:28.253 [ 32] DEBUG lService.sip_bur_a_p - [DuplexChannel.OpenConnection.Commit] Wait for complete. Timeout: 29987 ms
19-12-02 11:25:28.254 [ 33] DEBUG xy1.CommonConnection - [CommonConnection.SetConnectionSequenceState]: Commit
19-12-02 11:25:28.254 [ 33] DEBUG xy1.CommonConnection - [OpenInitAction] started commit
19-12-02 11:25:28.254 [ 33] DEBUG xy1.CommonConnection - Connection tcp://sgcca1nasip02.pam03-dev01.iams.cba:3000 is changing state from Closed to Opening
19-12-02 11:25:28.254 [ 33] DEBUG xy1.CommonConnection - [OpenInitAction] Connecting to tcp://sgcca1nasip02.pam03-dev01.iams.cba:3000 ...
19-12-02 11:25:28.254 [ 33] DEBUG xy1.CommonConnection - [DnsResolveAction] started commit
19-12-02 11:25:28.254 [ 33] DEBUG xy1.CommonConnection - [DnsResolveAction] [CommonConnection.ConnectSocket] Used address family: InterNetwork
19-12-02 11:25:28.255 [ 33] DEBUG xy1.CommonConnection - [DnsResolveAction] DNS has resolved address list:
InterNetwork:10.23.177.153

19-12-02 11:25:28.255 [ 33] DEBUG xy1.CommonConnection - [ConnectSocketAction] started commit
19-12-02 11:25:28.255 [ 33] DEBUG xy1.CommonConnection - [ConnectSocketAction] [ConnectSocketAction.SelectAddress] Use address: InterNetwork: 10.23.177.153
19-12-02 11:25:28.256 [ 33] DEBUG xy1.CommonConnection - [ConnectSocketAction] [CommonConnection.ConnectSocket] Socket uses: InterNetwork
19-12-02 11:25:28.256 [ 33] DEBUG xy1.CommonConnection - Socket#4468: Trying to connect to 10.23.177.153:3000



------------------------------
Jason McLennan
Commonwealth Bank of Australia

Original Message:
Sent: 01-16-2020 10:01
From: Wasim Altaf
Subject: WDE Communication with Genesys Servers

Hello,

I am trying to understand how WDE communicates with other Genesys applications such as the configuration server and t-server.
We specify the application name, configuration host and port at login.
But we don't do the same for the t-server because it is connected to the application object in CME/GA.

So we can specify the IP route by which it communicates with the configuration server.
Does it then use the same IP route to communicate with the t-server for voice media?
if not I guess it will do this using the t-server host ip/port ?
Scenario as below:
WDE installed on workstation IP 111.10.11.12 (source)
Configuration server on IP 112.10.11.12, port 2020 (destination 1)
T-Server on IP 113.10.11.12, port 3060 (destination 2)

In the WDE login page, I will specify 80.10.20.30, port 2020.  In the network, the traffic will be configured to route via 112.10.11.12.
Therefore when we reach the second page for voice login in WDE, is it now already using IP route 80.10.20.30 and initiate voice login with the t-server at the backend rather than from the source again.

We are trying to find a way to send the WDE communication traffic via a specific network whilst migrating users from an old softphone to WDE (without impacting the current users by changing the network).  I can do this for the configuration server host/ip as it can be defined in the login page or interactionworkspace.exe.config file.  I cannot see the same for the t-server anyway..

thanks,
#Omni-ChannelDesktop/UserInterface

------------------------------
WA
------------------------------