[cisco-voip] Redundant Route Patterns

[Ryan Ratliff]

That's because your SIP trunk is associated to a route pattern.   A  
gateway/trunk an only be in a RG or route pattern, not both.  Remove  
it from the route pattern and you'll see it available to be added to  
the RG.

-Ryan

On Sep 11, 2008, at 11:48 AM, Marcelo Zilio wrote:

Hi Ryan, thanks

I would like to use just one route pattern with separate route groups  
in the same route list as you said, but I didn't find the way to add  
a SIP Trunk to a RG.
Am I missing something? Is that possible ou should it be done in  
another way?

thanks
Marcelo

Ryan Ratliff escreveu:
>
> Only way I can think of to achieve this is in CUCM is using  
> locations-based CAC (or a gatekeeper to control calls to the H.323  
> gw).    Set the bandwidth to the H.323 site so that only the  
> desired number of calls can be up at a given time.
>
> Otherwise if you can have the H.323 gateway reject calls after a  
> certain number CUCM will route to the next member of the RL/RG.
>
> I would encourage you to not use separate route patterns though and  
> make them separate route groups in the same RL.
>
> -Ryan
>
> On Sep 11, 2008, at 10:05 AM, Marcelo Zilio wrote:
>
> Hi,
>
> I have two Route Pattern at Unified CallManager 5.1(3) pointing to  
> the same destination.
> Say 9.123XXXX
> One of them use a SIP Trunk.
> The other one uses a Route List -> Route Group -> H323 Gateway (E1).
>
> Is it possible, for example, the first ten calls use the SIP Trunk  
> to go out and the eleventh, twelfth,... calls use the RL?
>
> thanks
> Marcelo
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.169 / Virus Database: 270.6.19/1664 - Release Date:  
> 10/9/2008 06:00
>
>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080911/fcc2d57d/attachment.html>