Differences

This shows you the differences between two versions of the page.

--- developers:fixapi:start [2025/09/25 18:46] – rob
+++ developers:fixapi:start [2026/06/11 03:59] (current) – [FIX Session Lifecycle] chad
@@ Line 10: / Line 10: @@
 ^ System              ^ URL                          ^ Port  ^
-| Simulator           | fix-sim.t4login.com          | 10443 |
+| Simulator           | uhfix-sim.t4login.com          | 10443 |
-| Live                | fix.t4login.com              | 10443 |
+| Live                | uhfix.t4login.com              | 10443 |
-We have the following IP address ranges:
-  * **Internap - EQ-CER**
-    Range: 74.201.6.0 /24
-    Mask: 255.255.255.0
-  * **CenturyLink - EQ-CER**
-    Range: 69.44.110.0 /24
-    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.
@@ Line 52: / Line 23: @@
 Optional: Multiple [[developers:fixapi:traderlogon|Trader Logons]] per physical connection
+<WRAP center round warning 100%>
+The T4 FIX API does not support session recovery. All sessions begin with a sequence number of 1. A full account snapshot will be sent upon account subscription.
+[[https://docs.t4login.com/doku.php?id=developers:fixapi:logon#notes|More Info]]
+</WRAP>
 ===== Message Integrity Requirements =====
   * SOH delimiter (ASCII 001) between fields