It should achieve the desired effect. We have a similar use case, and don't see calls hit the second trunk when configuring the routes as sequential. From the documentation:
Select Sequential to route outgoing calls to each trunk in succession beginning with the first trunk.
(If the first trunk has reached its capacity or the call is rejected, then outgoing calls are routed to the second trunk and so on.)
------------------------------
Paul McGurn
Manager, Telecom Services
GoTo
------------------------------
Original Message:
Sent: 03-04-2023 07:28
From: Charaf Eddine Chemlal
Subject: BYOC Cloud Load Balancing
Hi Paul,
I appreciate your suggestion to add both trunks to the outbound routes, which would result in either a sequential or random distribution pattern.
However, for my specific situation, I would prefer to use only one trunk and have the secondary trunk serve as a backup in the event of any issues.
I am unsure if the sequential option would enable me to achieve my desired outcome. I'll run some tests :)
Thank you again,
Kind regards,
Charaf
------------------------------
Charaf Eddine Chemlal
Mentat Conseil SAS
------------------------------
Original Message:
Sent: 03-04-2023 01:35
From: Paul McGurn
Subject: BYOC Cloud Load Balancing
What we do to force this is set up each as its own BYOC trunk, instead of putting both on the same trunk configuration. Then we add both trunks to the Outbound Routes section of the Site(s) that will use them. In there, you can set the Distribution Pattern to Sequential to achieve what you want. I believe the default if putting multiple outbound IP's/FQDN's on the single trunk configuration, it uses round robin.
------------------------------
Paul McGurn
GoTo Technologies USA, Inc