That was my initial thought as well, but I could only see how to setup a route group with H.323/QSIG,MGCP, etc, not SIP.
I’ll look again. Matthew Huff | Director of Technical Operations | OTA Management LLC Office: 914-460-4039 mh...@ox.com<mailto:mh...@ox.com> | www.ox.com<http://www.ox.com> ........................................................................................................................................... From: NateCCIE <natec...@gmail.com> Sent: Thursday, March 10, 2022 10:29 AM To: Matthew Huff <mh...@ox.com> Cc: cisco-voip@puck.nether.net Subject: Re: [cisco-voip] CUCM SIP trunk redundancy with multiple CUBES Split it to two different trunks and add them both to a route group that is configured for round robin to the route list. On Mar 10, 2022, at 8:13 AM, Matthew Huff <mh...@ox.com<mailto:mh...@ox.com>> wrote: We have two cisco ISR 4331 Cube gateways in two different locations. I want to be able to route calls to both devices (preferably round-robin). I have the router pattern going to a trunk with both cubes defined (with sip options keep-alive configured). The issue we are having is that if the call is made to CUBE1 and the associated outbound dial-peer in in busyout, the CUBE returns 503 Service unavailable and CUCM doesn’t try CUBE2. What am I missing? Matthew Huff | Director of Technical Operations | OTA Management LLC Office: 914-460-4039 mh...@ox.com<mailto:mh...@ox.com> | www.ox.com<http://www.ox.com> ........................................................................................................................................... _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
