Hi Jeff, You are right, phones at the roaming location will get the LRG configuration from the roaming DP, we cannot avoid this.
However, a workaround to your scenario may be to implement + dialing, in which you globalize the caller input (translation patterns) depending on his/her dialing habits and localize it for the outgoing gateway (cd xform patterns), in that way, a US user roaming to UK will be allowed to use the LRG route patterns (using US dialing habits) therefore using local UK resources. The drawback here is that this won't be a cost effective solution, in which case you will have to implement teho/location specific route patterns to route calls out and save costs, Hope this make sense, On Fri, Feb 19, 2010 at 6:23 PM, Jeff Cotter <[email protected]> wrote: > Having trouble understanding how this is supposed to function without > Site Specific Route Patterns and Route List/Group. If using only non-site > specific route patterns pointed to local route group I see no value in this. > Of course I am probably mistaken…hence this message. Scenario below > > > > > > No location specific Route Patterns exist…all route patterns point to local > route group. > > > > Device roams from HQ to BR1 DMG is US for both. (CSS for both home and > Roaming device pool is CSS-LD). Roaming sensitive settings are applied as > well as Mobility Settings. which means device will use local route group > defined in BRI device pool for all calls based on CSS-LD. User dials > 95551212..No problem here since calls will now be sent out BR1-GW as > expected with correct digits assuming predot is applied via Called > Transformation. > > > > However take the same scenario above except the DMG is now changed to UK > for roaming phone. Mobility settings are no longer applied meaning CSS does > not change. The purpose for this is supposed to be that user does not want > to have to dial differently when in a new country. However Local Route Group > is still obtained from roaming Device Pool. Since all Route Patterns point > to local route group and local route group is now UK…. ALL calls will now be > directed to UK gw. Call will fail as digits PSTN is expecting will be > incorrect. > > > > What is the excepted way to get calls to NOT route out local gateway but > traverse the WAN and go out US gateway. I can’t think of how to do this > without using location specific Route Patterns and Route Lists which now > defeats the purpose of the Local Route Group concept. ARRRGGGGH > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > -- Regards, Otto Sanchez CCIE #25592 (Voice) Support Engineer - IPexpert, Inc. URL: http://www.IPexpert.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
