To be able to communicate with ONEiO, end systems need to have ALL of the following communication channels open
Production
Inbound: End System > ONEiO
Static IP(s)
- 54.77.75.179:443
- 54.77.137.161:443
(Address: https://rest-receiver.service-flow.com/api OR https://soap-receiver.service-flow.com/api )
Outbound: ONEiO > End System
Static IP(s)
- 54.77.247.222:443 / case specific
- 54.77.250.26:443 / case specific
QA (Test)
Inbound: End System > ONEiO
Static IP(s)
- 54.171.0.42:443
- 54.171.36.116:443
(Address: https://rest-receiver-test.service-flow.com/api OR https://soap-receiver-test.service-flow.com/api)
Outbound: ONEiO > End System
Static IP(s)
- 54.171.68.212:443 / case specific
- 54.171.121.41:443 / case specific
How to test connectivity from your system to ONEiO?
The easiest way to check if there is a network connection to ONEiO is to use a command-line tool like curl or telnet from the server where your system is running. Remember to test both the INBOUND IP addresses. Here's an example with curl:
curl https://prod-inbound-1.service-flow.com curl https://prod-inbound-2.service-flow.com curl https://test-inbound-1.service-flow.com curl https://test-inbound-2.service-flow.com |
If you get a HTML page as a result, connectivity is ok.
Here's how you test with telnet:
telnet prod-inbound-1.service-flow.com 443 telnet prod-inbound-2.service-flow.com 443
telnet test-inbound-1.service-flow.com 443 telnet test-inbound-2.service-flow.com 443 |
You will just get a blank screen if the connection succeeds.
Comments
Please sign in to leave a comment.