Equias IP (CMS) Addresses

Equias IP (CMS) Addresses

  UAT (User Acceptance Test System)
GUI, URL https://www.cms- test.equias.org
GUI, IP address 83.138.133.129
Inbound Messenger URL https://msg.cms- test.equias.org/pontonxp/SoapListener
Inbound Messenger IP 83.138.133.130
Outbound Messenger IP 83.138.133.140


Live
GUI, URL https://www.cms.equias.org
GUI, IP address 94.236.4.20
Inbound Messenger URL https://msg.cms.equias.org/pontonxp/SoapListener
Inbound Messenger IP 94.236.4.21
Outbound Messenger IP 94.236.4.29


DR (Disaster Recovery System)
GUI, URL https://www.cms.equias.org
GUI, IP address 89.234.49.170
Inbound Messenger URL https://msg.cms.equias.org/pontonxp/SoapListener
Inbound Messenger IP 89.234.49.171
Outbound Messenger IP 89.234.49.175


New GUI information:


Production GUI, URL:   www.cms.equias.org

IP address 104.74.84.176 for both Production and UAT (routing is performed internally, the outward facing IP is the same)

Please note: It is not possible to provide GUI IP information for the new GUI as the URL is resolved to different IPs from varying IP ranges, depending on where you are located.

The CMS GUI is served by AKAMAI and is using local Servers nearest to you.

Since AKAMAI is always using the nearest server and adding servers regularly, its not possible to tell which server is actually in use.

AKAMAI has whole range of IP's that could be used to serve the GUI, you should probably allow the Akamai ranges.


Table definitions:

GUI, IP address is the IP address behind the GUI URL.

Inbound Messenger URL is the address the client’s Messenger will send documents to.

Inbound Messenger IP is the IP behind the Inbound Messenger URL, it is the same principle as for the CMS GUI: you can either use the IP address to reach a webpage or the URL.

Outbound Messenger IP is the address that the client’s Messenger can expect to receive documents from. This is an important IP as clients need to whitelist this IP in their firewall.