I think you're overstating a bit there. in the lab. of course it's meaningless... do not even use local route groups unless specifically asked for!!! use specific gateways.
In real life! well it's different story. say you have the following design: client with 1 HQ site, and 10 smaller sites. Local GW in smaller sites where all calls should go out from local sites. failover to secondary GW in HQ if Local GW is not working. 1) standard approach every site will have it's own ROUTE LIST -> 1 choice - local site gw, 2 choice HQ gw. so this is 10 ROUTE LISTS already. and now RP: RP local 9XXXXXXX -> PT-LOCAL -> RL-LOCAL-HQ-siteX if call goes out of local gw, then it needs one kind of treatment. if goes out of HQ gateway it needs to go as national and needs different treatment. Here you would have to define the different treatments for every single site every time you create route lists and etc. 2) Local RG approach: Only one ROUTE LIST!!! 1 choice LRG , 2 choice HQ gw. no need for anything else. and now TP: RP local 9XXXXXXX -> PT-LOCAL-siteX -> translatees go E164 standard and points to CSS-GLOBAL -> PT-GLOBAL this is the only place where you have to duplicate things. and now RP: RP: \+! -> PT-GLOBAL -> RL-LRG-HQ only one RP!!! in my example we only had 10 sites... and saved on ROUTE-LISTS configurations. now imagine a client with 10.000 locations!!! read this guide: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/7_0_1/ccmfeat/fslrg.pdf Especially the part: "Routing with Local Route Groups" Regards, On Wed, Dec 28, 2011 at 11:23 AM, datucha123 datucha123 < datucha...@gmail.com> wrote: > If I use separate Partitions for each site, then the idea of Local Route > Groups is meaningless. > > > > > On Wed, Dec 28, 2011 at 3:07 PM, George Goglidze <gogli...@gmail.com>wrote: > >> Hi, >> >> You have to create two different partitions with two different TP-s. >> There is no other way around it. >> PT_PSTN_sa >> PT_PSTN_sb >> >> I would suggest you never try to use same pattern, even RP for two >> different sites in a lab, unless it's stricktly necessary by task >> requirement. >> Don't try to save space, and use less partitions/css. It will only cause >> you trouble. use different one for every single task and every single site. >> >> Regards, >> >> >> On Wed, Dec 28, 2011 at 10:50 AM, datucha123 datucha123 < >> datucha...@gmail.com> wrote: >> >>> Hello, >>> >>> I am very confused with the Called Party Globalization along with Local >>> Route Groups. >>> >>> Let's take a look at the following example. >>> >>> We have two site in USA: >>> >>> Site A with Area Code of 202 >>> Site B with Area Code of 512 >>> >>> So, now we create the Local Route Groups - each Site Gateway is >>> assinged in its own Route Group, then DP is assigned the Local Route Group >>> and etc. Just the standard way, nothing hard here. >>> >>> But now we have to create the Translation Patterns for PSTN Dialplan >>> where the + signs along with Area Codes and etc will be added, so that the >>> called number will become full E164. The Route Pattern is configured as >>> "\+!" and the Called Party Transformation at the GWs will stripp >>> uneccessary digits from the Called Number, and if necessary will add digits >>> for PSTN to route them properly - Like 011 for International, 1 for >>> National and etc. >>> >>> Well here is no problem. >>> >>> But now look, we have to create only one instance of Translation >>> Patterns as we are using Local Route Groups - for instance, >>> one International pattern, one National and etc, so that when the Site A >>> phone will make call to this Patterns it will go out through its Local >>> Route Group (GW), while when the Site B will make call to the same Pattern, >>> the call will be routed through its Local Route Group (GW). >>> >>> Adding the + sign and digit 1 for International and National calls >>> respectavley to Called Number is not a problem. >>> >>> The problem arrise when I am configuring the Local Area Pattern: >>> >>> [2-9]XXXXXX >>> >>> For this pattern to Globalize the Called Number I have to add the Area >>> Code as well, but how do I know which Area Code to add, when I have two >>> Site Phones,each Site having its own Area Code? >>> >>> For insatance, when Site A Phone is calling through this pattern to its >>> local Area, then the 202 has to be added as the Area Code to Globalize the >>> Called Number, but when the Site B Phone makes call through this patterm I >>> have to add 512 as the Area Code to Globalize the Called Number. >>> >>> How this situation is solved? >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> For more information regarding industry leading CCIE Lab training, >>> please visit www.ipexpert.com >>> >>> Are you a CCNP or CCIE and looking for a job? Check out >>> www.PlatinumPlacement.com <http://www.platinumplacement.com/> >>> >> >> >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
