Hi @Jeff Greenburg ,
Does this issue happened in your internal or external network?
Our environment has not done such a deployment due to the limitation. But According to your description, this issue happened when call passed to Mediation pool B. As you said, you could try to change the routing in the SBC directly to Pool A to see if this issue can be fixed.
If this issue occurs from external network, we also recommend you check your proxy server’s time out setting and change it to 600 seconds. For more details, you can refer to:
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.