[cisco-voip] CUCM SIP trunk redundancy with multiple CUBES

Kent Roberts dvxkid at gmail.com
Thu Mar 10 21:17:57 EST 2022


You can create multiple lists, and add different groups to them with different trunks….  To accomplish the same goal


> On Mar 10, 2022, at 6:58 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
> 
> 
> For some reason this irks me.  
> 
> I like to create special test patterns to test all my gateways.  
> 
> I had to create individual groups and lists to accomplish this.  
> 
> Because, as you say, they disappear when assigned to a specific pattern directly.  :(
> 
> Sent from my iPhone
> 
>> On Mar 10, 2022, at 10:58 AM, russon81 via cisco-voip <cisco-voip at puck.nether.net> wrote:
>> 
>> 
>> 
>> CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to IThelp at uoguelph.ca
>> 
>> 
>> I think if you have the SIP trunk assigned to a route pattern, it won't show up as an option in the route groups.  You can definitely assign them to a RG though.  Try creating the RG, point your pattern to that, then you should be able to assign the trunk to the RG.
>> 
>> 
>> 
>> Sent from my T-Mobile 5G Device
>> 
>> 
>> -------- Original message --------
>> From: Matthew Huff <mhuff at ox.com>
>> Date: 3/10/22 7:46 AM (GMT-08:00)
>> To: NateCCIE <nateccie at gmail.com>
>> Cc: cisco-voip at puck.nether.net
>> Subject: Re: [cisco-voip] CUCM SIP trunk redundancy with multiple CUBES
>> 
>> 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
>> 
>> mhuff at ox.com <mailto:mhuff at ox.com> | www.ox.com <http://www.ox.com/>
>> ...........................................................................................................................................
>> 
>>  
>> From: NateCCIE <nateccie at gmail.com> 
>> Sent: Thursday, March 10, 2022 10:29 AM
>> To: Matthew Huff <mhuff at ox.com>
>> Cc: cisco-voip at 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 <mhuff at ox.com <mailto:mhuff at 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
>> 
>> mhuff at ox.com <mailto:mhuff at ox.com> | www.ox.com <http://www.ox.com/>
>> ...........................................................................................................................................
>> 
>>  
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>> https://puck.nether.net/mailman/listinfo/cisco-voip <https://puck.nether.net/mailman/listinfo/cisco-voip>_______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20220310/8d41e42b/attachment.htm>


More information about the cisco-voip mailing list