We require broadened access to provide for our future developments in terms of protocols and network infrastructure, and to avoid you having to systematically change your configuration at each change on our side.
1/ Ports and Protocol
Opening ports 80 and 443 is essential (ideally on all protocols).
Currently, we use the protocols https, wss, xmpp, and bosh. Please be sure these protocols are open on your network.
WARNING : From now, we are using dynamic IP ranges. Please refer to domain name exclusively if you need to apply filtering. cf. Infrastructure migration to AWS
It is essential not to filter requests between your agents and our servers.
We therefore ask you a bypass *.iadvize.com on your network equipment (proxy, firewall, etc.).
Be sure to open this domain on all protocols used by iAdvize solution :
Bypassing *.twilio.com is also mandatory if you are using:
- the video channel
- the call channel, only if your agent are answering the calls from the iAdvize discussion panel (without using a phone)
Be sure to open this domain on all protocols used by Twilio solution :
Bypassing *.googleapis.com is necessary if you need to use the automatic translation feature on the discussion panel.
Bypassing *.amazonaws.com is also necessary if you need to use the send a file feature on the discussion panel.
The proxy timeout should be above 70 seconds to not disturb the "long polling" request.
These 3 parameters (ports, domain, timeout) have to be verified on each layer impacting the agents' connection (VPN / Proxy / Firewall / Antivirus).