[cisco-voip] Local Route Group with redundancy

Joel Perez tman701 at gmail.com
Mon May 3 17:23:38 EDT 2010 

I replied to a similar thread a while back regarding this.
I currently have several customers running this scenario. It started with
just one customer where we did it as a sort of experiment.
These customers are all running SIP to their providers on multiple GW's with
multiple sites, no local PRI's exist for PSTN.
The LRG for each site is its own local GW that itself has usually more than
one T1 in this case. We also added another sites GW as a backup to the RG.
So it will try the LRG first then move on to the other GW included in the
RG.
For 911 services we have FXO's as backup at each site for this same
scenario.

Hopefully I didnt get my Groups mixed up here, too many similar acronyms
thrown out in one email.

Joel P

On Mon, May 3, 2010 at 8:57 AM, Ryan Ratliff <rratliff at cisco.com> wrote:

> As Phil mentioned the rerouting behavior depends on the disconnect cause we
> get back from the gateway.  For SIP we actually convert its disconnect cause
> to a q931-like cause before the RouteList decides whether to reroute the
> call or not.
>
> If your calls are not rerouting you need to look at the SIP messages to
> determine what cause is coming back.
>
> -Ryan
>
> On May 3, 2010, at 7:08 AM, Ahmed Elnagar wrote:
>
> > I had to configure this parameter in order to run for two different RG
> each one contain one gateway...it wasn't working without that
> parameter...that is strange!!!
> > Any other opinions here??
> >
> >
> >  Best Regards;
> >   Ahmed Elnagar
> >   Senior Network PS Engineer
> >   Mob: +2019-0016211
> >
> >
> >
> > -----Original Message-----
> > From: Phil G [mailto:pgciscovoip at gmx.net]
> > Sent: Monday, May 03, 2010 1:51 PM
> > To: Ahmed Elnagar
> > Cc: cisco-voip at puck.nether.net
> > Subject: Re: [cisco-voip] Local Route Group with redundancy
> >
> > I have 2 E1 on different Gateways, both in the same RG. If one of the E1
> > is not working, then all calls leave the other E1. If both are failing,
> > then it continues to route on the next RG in the RL.
> >
> > The only thing you have to deal with is, if you are using H323 (or as
> > this is a dial-peer issue i think also with SIP), the service parameter
> > "Stop routing on unallocted number".
> >
> > Ahmed Elnagar wrote:
> >> No I am using SIP...but let's say that you have two E1 added to RG if
> one fail the calls never come out of it "regardless it is circular or top
> down?"
> >>
> >> Best Regards;
> >>  Ahmed Elnagar
> >>  Senior Network PS Engineer
> >>  Mob: +2019-0016211
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: Phil G [mailto:pgciscovoip at gmx.net]
> >> Sent: Monday, May 03, 2010 12:34 PM
> >> To: Ahmed Elnagar
> >> Cc: cisco-voip at puck.nether.net
> >> Subject: Re: [cisco-voip] Local Route Group with redundancy
> >>
> >> If one of the E1's is down then it routes the call to the other one, i
> >> have implemented this at several customers, no problems so far. Why
> >> should i use "Circular" algorithm if not for load balancing or for
> >> redundancy?
> >>
> >> Are you using H323-GWs?
> >>
> >>
> >>
> >> Ahmed Elnagar wrote:
> >>> If one of them is down and the algorithm is circular the calls will
> fail...CallManager doesn't provide RG component to be backup to each
> other...that is what accomplished in RL.
> >>>
> >>> Best Regards;
> >>>  Ahmed Elnagar
> >>>  Senior Network PS Engineer
> >>>  Mob: +2019-0016211
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: Phil G [mailto:pgciscovoip at gmx.net]
> >>> Sent: Monday, May 03, 2010 12:08 PM
> >>> To: Ahmed Elnagar
> >>> Cc: cisco-voip at puck.nether.net
> >>> Subject: Re: [cisco-voip] Local Route Group with redundancy
> >>>
> >>> What about putting the 2 E1's in the same route group (which is the
> LRG)?
> >>>
> >>> Ahmed Elnagar wrote:
> >>>> No, the idea is that you make a generic Route list that point to a
> >>>> “system” generated route group then you point your RP to that RL and
> by
> >>>> doing so the CUCM take the local route group that is configured in the
> >>>> Device pool of the calling party. Actually I am not talking about
> >>>> redundancy in the manner if site A GW is down use site B…no…I am
> talking
> >>>> about two site A GWs that has redundant E1’s and they should be
> working
> >>>> together and in case one fail the other should be handling the calls
> >>>> normally…I couldn’t achieve this using Local route group.
> >>>>
> >>>>
> >>>>
> >>>> Best Regards;
> >>>>
> >>>>  Ahmed Elnagar
> >>>>
> >>>>  Senior Network PS Engineer
> >>>>
> >>>>  Mob: +2019-0016211
> >>>>
> >>>> ccie_voice_large.gifccvp_voice_large.gif
> >>>>
> >>>>
> >>>>
> >>>> *From:* Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
> >>>> *Sent:* Sunday, May 02, 2010 3:26 PM
> >>>> *To:* Ahmed Elnagar
> >>>> *Cc:* cisco-voip at puck.nether.net
> >>>> *Subject:* Re: [cisco-voip] Local Route Group with redundancy
> >>>>
> >>>>
> >>>>
> >>>> I have not read the full thread, but from what I understand, the local
> >>>> route group is for routing calls that only should be routed to the
> local
> >>>> gateways and nothing else.
> >>>>
> >>>> Calls like 911 should only go out the local gateway. If a 911 call
> gets
> >>>> routed out a remote gateway, chances are they will not know where to
> >>>> send the service.
> >>>>
> >>>> But it does seem a bit strange that redundancy is not available.
> >>>>
> >>>> Are you sure you can't add the local route group to a route list?
> >>>>
> >>>> ---
> >>>> Lelio Fulgenzi, B.A.
> >>>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> >>>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> >>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >>>> Cooking with unix is easy. You just sed it and forget it.
> >>>>                              - LFJ (with apologies to Mr. Popeil)
> >>>>
> >>>>
> >>>> ----- Original Message -----
> >>>> From: "Ahmed Elnagar" <ahmed_elnagar at rayacorp.com>
> >>>> To: cisco-voip at puck.nether.net
> >>>> Sent: Sunday, May 2, 2010 5:27:17 AM GMT -05:00 US/Canada Eastern
> >>>> Subject: [cisco-voip] Local Route Group with redundancy
> >>>>
> >>>>
> >>>> Dear all;
> >>>>
> >>>>
> >>>>
> >>>> Anyone know any info if Cisco is going to solve the below problem…or
> >>>> maybe any workaround?
> >>>>
> >>>>
> >>>>
> >>>> https://supportforums.cisco.com/message/1169001#1169001
> >>>>
> >>>>
> >>>>
> >>>>  Best Regards;
> >>>>
> >>>>  Ahmed Elnagar
> >>>>
> >>>>  Senior Network PS Engineer
> >>>>
> >>>>
> >>>>
> >>>> raya_corp_logoIT Line of Business
> >>>>
> >>>>  RAYA Building El Motamiez District, 6th of October, Egypt
> >>>>
> >>>>
> >>>>
> >>>>  Mob: +2019-0016211
> >>>>
> >>>>  Phone: +202 3827 6000 Ext.2475
> >>>>
> >>>>  Website: www.rayacorp.com <http://www.rayacorp.com/>
> >>>>
> >>>>  E-mail: ahmed_elnagar at rayacorp.com <mailto:
> ahmed_elnagar at rayacorp.com>
> >>>>
> >>>> ccie_voice_large.gifccvp_voice_large.gif
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> Disclaimer: NOTICE The information contained in this message is
> >>>> confidential and is intended for the addressee(s) only. If you have
> >>>> received this message in error or there are any problems please notify
> >>>> the originator immediately. The unauthorized use, disclosure, copying
> or
> >>>> alteration of this message is strictly forbidden. Raya will not be
> >>>> liable for direct, special, indirect or consequential damages arising
> >>>> from alteration of the contents of this message by a third party or as
> a
> >>>> result of any malicious code or virus being passed on. Views expressed
> >>>> in this communication are not necessarily those of Raya.If you have
> >>>> received this message in error, please notify the sender immediately
> by
> >>>> email, facsimile or telephone and return and/or destroy the original
> >>>> message.
> >>>> _______________________________________________ cisco-voip mailing
> list
> >>>> cisco-voip at puck.nether.net
> >>>> https://puck.nether.net/mailman/listinfo/cisco-voip
> >>>>
> >>>>
> >>>> Disclaimer: NOTICE The information contained in this message is
> >>>> confidential and is intended for the addressee(s) only. If you have
> >>>> received this message in error or there are any problems please notify
> >>>> the originator immediately. The unauthorized use, disclosure, copying
> or
> >>>> alteration of this message is strictly forbidden. Raya will not be
> >>>> liable for direct, special, indirect or consequential damages arising
> >>>> from alteration of the contents of this message by a third party or as
> a
> >>>> result of any malicious code or virus being passed on. Views expressed
> >>>> in this communication are not necessarily those of Raya.If you have
> >>>> received this message in error, please notify the sender immediately
> by
> >>>> email, facsimile or telephone and return and/or destroy the original
> >>>> message.
> >>>>
> >>>>
> >>>>
> ------------------------------------------------------------------------
> >>>>
> >>>> _______________________________________________
> >>>> cisco-voip mailing list
> >>>> cisco-voip at puck.nether.net
> >>>> https://puck.nether.net/mailman/listinfo/cisco-voip
> >>> Disclaimer: NOTICE The information contained in this message is
> confidential and is intended for the addressee(s) only. If you have received
> this message in error or there are any problems please notify the originator
> immediately. The unauthorized use, disclosure, copying or alteration of this
> message is strictly forbidden. Raya will not be liable for direct, special,
> indirect or consequential damages arising from alteration of the contents of
> this message by a third party or as a result of any malicious code or virus
> being passed on. Views expressed in this communication are not necessarily
> those of Raya.If you have received this message in error, please notify the
> sender immediately by email, facsimile or telephone and return and/or
> destroy the original message.
> >>
> >> Disclaimer: NOTICE The information contained in this message is
> confidential and is intended for the addressee(s) only. If you have received
> this message in error or there are any problems please notify the originator
> immediately. The unauthorized use, disclosure, copying or alteration of this
> message is strictly forbidden. Raya will not be liable for direct, special,
> indirect or consequential damages arising from alteration of the contents of
> this message by a third party or as a result of any malicious code or virus
> being passed on. Views expressed in this communication are not necessarily
> those of Raya.If you have received this message in error, please notify the
> sender immediately by email, facsimile or telephone and return and/or
> destroy the original message.
> >
> > Disclaimer: NOTICE The information contained in this message is
> confidential and is intended for the addressee(s) only. If you have received
> this message in error or there are any problems please notify the originator
> immediately. The unauthorized use, disclosure, copying or alteration of this
> message is strictly forbidden. Raya will not be liable for direct, special,
> indirect or consequential damages arising from alteration of the contents of
> this message by a third party or as a result of any malicious code or virus
> being passed on. Views expressed in this communication are not necessarily
> those of Raya.If you have received this message in error, please notify the
> sender immediately by email, facsimile or telephone and return and/or
> destroy the original message.
> >
> > _______________________________________________
> > 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/20100503/a826035e/attachment.html>

More information about the cisco-voip mailing list