Avoiding connection timeout on accepting a large volume of change sets with distributed SCM

We've recently configured distributed SCM between 2 RTC servers so that we can flow code from a stream in the source RTC to a stream in the target RTC.  I can create a workspace in the target RTC and "accept" code to it from the source RTC stream at a component level for small components.

Attempting to accept code for a (much) larger component times out after about 3 hours which happens to be the maximum timeout value of 9999 seconds.  Obviously, we don't want to have to reorganize the source stream just to be able to flow change sets from the source RTC stream to the target RTC stream.  Is there any other way to get around this problem?  Can we accept a limited number of change sets in batches until we're up-to-date on the target stream?  Any way to have a larger timeout value than 9999 seconds?

Alternatively, if this is not possible could we load the code as-is in the source and start accepting change sets from this point forward (obviously that is not ideal, but better than nothing).

Thanks in advance for the help!