Routers don't, I believe, have settings that determine other host transit traffic TCP timers. Also believe, many hosts might not allow easy or any modification of such timers.
If TCP connections are failing on your new p-2-p T1, I would check for excessive latency and/or errors. Both, I believe, can cause a host to consider a TCP session so bad the TCP session is reset or dropped.
PS:
If you're using FIFO on the WAN interfaces, you might want to switch to FQ. The latter tends to make multiple flow performance more predicable which can assist host TCP session monitoring since part of its operation is based on tracking RTT.