Connecting to the Instant Connect Docker Repository
In this section you will log in to the Instant Connect private Docker repository to pull and run the required Docker container for ICE Telephony support. This requires the creation of a .env file.
To connect the Instant Connect Docker repository
1. Log into Docker with the following command:
docker \
login docker.io \
-u iccustomeraccess \
-p 7dcb7799-f418-4651-ab65-66feec2a4234
8. Verify you can pull the ICE Telephony container by executing the following:
docker pull instantconnect/gateway:3.5.7732
Note: For now, you will have to manually enter the IP addresses of the Arcus cluster you are connecting to and the public IP address of the node you're using to host ICE-Telephony into the file env.
9. Pass in environment variables by creating an env file to feed into docker. It is easiest to build this from your workstation, then upload it to your telephony node. The structure of the file is as follows:
ICE_TEL_PLATFORM_URL=https://chicago.icnow.app
CLIENT_BRIDGE_ADDRESS=https://chicago.icnow.app
SERVER_BRIDGE_ADDRESS=https://chicago.icnow.app/server-bridge
INGRESS_IP=your telephony node ip
GATEWAY_PLATFORM_LOGIN_TOKEN=<token from your ICE Server>
GATEWAY_TYPE=telephony
ICEGW_ARCUS_RELOGIN_ATTEMPTS_COUNT=10
ICEGW_ARCUS_WAIT_INTERVAL_BETWEEN_RELOGIN_ATTEMPTS=60
ICEGW_ARCUS_MAX_ATTEMPTS_TO_DOWNLOAD_CONFIG=10
Note: The ICE Server environment variables must include https:// or http:// at the beginning, but the INGRESS_IP variable does not. For server without certificates or FQDN, use http://\<Your Server IP>
10. Obtain the GATEWAY_PLATFORM_LOGIN_TOKEN value.
For the ICE Telephony to register to ICE Server, you must populate the GATEWAY_PLATFORM_LOGIN_TOKEN value with a Kubernetes secret. If you have kubectl access on your ICE Server cluster, you can obtain the token value (jq 1.6 or newer is required).
For the ICE Telephony to register to ICE Server, you must populate the GATEWAY_PLATFORM_LOGIN_TOKEN value with a Kubernetes secret. If you have kubectl access on your ICE Server cluster, you can obtain the token value (jq 1.6 or newer is required).
A. Run the following command:
kubectl -n ice-arcus get secrets gateway-auth-token -o json
B. Copy the sip value from the output. For example, if the output were this...
"data": {"dfsig":
"bWh4ZnVmNWlwMHJueTYwcGdxdmJwbTA1NWt5MjNxYmdnaXIxejJwM2JoaTMyanp0aXc
0bGQwNTE1c3M5NHI0Zg==","sip":
"aGJ3enF2ZmwxdGc4Nm01a2FjNnA2Z3F5MTM1NHBtdGhoYmhiNXdxYmtyZW54YjkzZjd
2NmdrMXlraG43azd2aQ=="},
...then you would copy the sip value:
aGJ3enF2ZmwxdGc4Nm01a2FjNnA2Z3F5MTM1NHBtdGhoYmhiNXdxYmtyZW54YjkzZjd2Nm
drMXlraG43azd2aQ==
C. Using the above example, run the following command:
echo aGJ3enF2ZmwxdGc4Nm01a2FjNnA2Z3F5MTM1NHBtdGhoYmhiNXdxYmtyZW54YjkzZjd
2NmdrMXlraG43azd2aQ== | base64 -d
D. The output is the token value, for example:
hbwzqvfl1tg86m5kac6p6gqy1354pmthhbhb5wqbkrenxb93f7v6gk1ykhn7k7vi
E. Copy the token value and use it for GATEWAY_PLATFORM_LOGIN_TOKEN in env. In our example, the env file on the ICE Telephony node would have following information:
ICE_TEL_PLATFORM_URL=https://chicago.icnow.app
CLIENT_BRIDGE_ADDRESS=https://chicago.icnow.app
SERVER_BRIDGE_ADDRESS=https://chicago.icnow.app/server-bridge
INGRESS_IP=your telephony node ip
GATEWAY_PLATFORM_LOGIN_TOKEN=hbwzqvfl1tg86m5kac6p6gqy1354pmthhbhb5wqbkrenxb93f7v6gk1ykhn7k7vi
GATEWAY_TYPE=telephony
Note: If your cluster is not using certificate, replace https with http. Ensure the token does not include double-quotation marks.
11. Proceed to the next step (Running the Container).