Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
| developers:fixapi:start [2025/09/25 18:46] – rob | developers:fixapi:start [2025/09/25 19:52] (current) – rob | ||
|---|---|---|---|
| Line 12: | Line 12: | ||
| | Simulator | | Simulator | ||
| | Live | fix.t4login.com | | Live | fix.t4login.com | ||
| - | |||
| - | |||
| - | |||
| - | We have the following IP address ranges: | ||
| - | |||
| - | * **Internap - EQ-CER** | ||
| - | Range: 74.201.6.0 / | ||
| - | Mask: 255.255.255.0 | ||
| - | |||
| - | * **CenturyLink - EQ-CER** | ||
| - | Range: 69.44.110.0 / | ||
| - | Mask: 255.255.255.0 | ||
| - | |||
| - | |||
| - | Our applications use port **80** & **443** on any of those IP’s. | ||
| - | From a domain name perspective then you need: | ||
| - | * *.t4login.com | ||
| - | * *.sim.t4login.com | ||
| - | * www.ctsfutures.com open. | ||
| - | |||
| - | If your proxy requires authentication then you will need to allow T4 to bypass it as the Microsoft .Net Framework we use doesn’t support authenticating proxy servers. | ||
| - | |||
| - | If your proxy doesn’t require authentication then T4 should work fine, but if it doesn’t then the simplest solution would be to bypass the proxy if that is possible. | ||
| - | |||
| - | |||
| - | ===== PING ===== | ||
| - | We don’t enable ping or tracert across our entire system. | ||
| - | You can ping **64.74.232.69**. It is a device on the edge of our network. | ||
| - | |||