Attendant Console or Desktop CTI clients rel. 2018.6.1 and above, regardless the UC Suite version.
This article explains how to enable the DNS mechanism that allows the Imagicle Attendant Console to automatically discover the list of the eligible UC Suite servers.
This mechanism allows to manage the scenarios having the Imagicle Attendant servers behind a NAT, that is a common scenario when clients need to reach the Imagicle UC Suite nodes on the Internet, without a VPN.
It also allows to expose on the Internet the Attendant Console Service of several Imagicle nodes using only one public IP address, as described below.
Suppose you want to manage a scenario where:
Please find below how to manage such scenario with DNS discovery mechanism:
1) In the datacenter create two NAT rules to expose the internal TCP port 51234 (default port used by Attendant Console) of each Imagicle server into a different port of the same public IP address, for instance:
2) In the DNS server used by the Attendant Console client workstations*, create the 2 following DNS SRV rules:
_service._proto.name. | TTL | class | SRV | priority | weight | port | target |
_iac._tcp.acme.com. | 86400 | IN | SRV | 10 | 100 | 28101 | acme.com |
_iac._tcp.acme.com. | 86400 | IN | SRV | 8 | 80 | 28102 | acme.com |
* this can be either the internal organization DNS (for clients running inside the organization) or a public DNS server.
These entries will allow the client to discover the weighted list of hostnames and TCP port number of available UC Suite servers. Please notice that the prefix _iac._tcp cannot be changed.
3) The end-user runs the Attendant Console client on his workstation and specifies as server hostname: acme.com
4) The client will run a SRV query _iac._tcp.acme.com, getting from the DNS server the weighted list of Imagicle servers and related TCP ports.
The client tries to connect to the first SRV entry acme.com at tcp port 28101 (routed to the internal port 51234 of the first Imagicle server). In order to do that, the client will run a DNS "A" query to its DNS server, to solve the hostname acme.com.
5) If failing, it will automatically try to the second SRV entry acme.com at tcp port 28102 (routed to the internal port 51234 of the second Imagicle server).
1) In the datacenter create two NAT rules to expose the internal TCP port 51235 (default port used by Attendant Console) of each Imagicle server into a different port of the same public IP address, for instance:
2) In the DNS server used by the Attendant Console client workstations*, create the 2 following DNS SRV rules:
_service._proto.name. | TTL | class | SRV | priority | weight | port | target |
_iacsec._tcp.acme.com. | 86400 | IN | SRV | 10 | 100 | 28101 | acme.com |
_iacsec._tcp.acme.com. | 86400 | IN | SRV | 8 | 80 | 28102 | acme.com |
* this can be either the internal organization DNS (for clients running inside the organization) or a public DNS server.
These entries will allow the client to discover the weighted list of hostnames and TCP port number of available UC Suite servers. Please notice that the prefix _iacsec._tcp cannot be changed.
3) The end-user runs the Attendant Console client on his workstation and specifies as server hostname: acme.com
4) The client will run a SRV query _iacsec._tcp.acme.com, getting from the DNS server the weighted list of Imagicle servers and related TCP ports.
The client tries to connect to the first SRV entry acme.com at tcp port 28101 (routed to the internal port 51235 of the first Imagicle server). In order to do that, the client will run a DNS "A" query to its DNS server, to solve the hostname acme.com.
5) If failing, it will automatically try to the second SRV entry acme.com at tcp port 28102 (routed to the internal port 51235 of the second Imagicle server).
Suppose you want to manage a scenario where:
Here how to manage such scenario with DNS discovery mechanism:
1) In each datacenter create a NAT rule to expose the internal TCP port 51234 (or 51235 in case of encrypted connection) of each Imagicle server into a TCP port of the corresponding public IP address, for instance:
Please, notice that the 2 public TCP ports can be different on the 2 datacenters.
2) In the DNS server used by the Attendant Console client workstations*, create the 2 following DNS SRV rules:
_service._proto.name. | TTL | class | SRV | priority | weight | port | target |
_iac._tcp.acme.com. | 86400 | IN | SRV | 10 | 100 | 21234 | dc1.acme.com |
_iac._tcp.acme.com. | 86400 | IN | SRV | 8 | 80 | 21234 | dc2.acme.com |
_service._proto.name. | TTL | class | SRV | priority | weight | port | target |
_iacsec._tcp.acme.com. | 86400 | IN | SRV | 10 | 100 | 21234 | dc1.acme.com |
_iacsec._tcp.acme.com. | 86400 | IN | SRV | 8 | 80 | 21234 | dc2.acme.com |
* this can be either the internal organization DNS (for clients running inside the organization) or a public DNS server.
These entries will allow the client to discover the weighted list of hostnames and TCP port number of available UC Suite servers. Please notice that the prefix "_iac._tcp" cannot be changed.
3) The end-user runs the Attendant Console client on his workstation and specifies as server hostname: acme.com
4) The client will run a SRV query _iac._tcp.acme.com (or _iacsec._tcp.acme.com for TLS connection), getting from the DNS server the weighted list of Imagicle servers and related TCP ports.
The client tries to connect to the first SRV entry acme.com at tcp port 21234 (routed to the internal port 51234 or 51235 of the first Imagicle server). In order to do that, the client will run a DNS "A" query to its DNS server, to solve the hostname dc1.acme.com.
5) If failing, it will automatically try to reach the second SRV entry dc2.acme.com at tcp port 21234 (routed to the internal port 51234 or 51235 of the second Imagicle server). In order to do that, the client will run a DNS "A" query to its DNS server, to solve the hostname dc2.acme.com.