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
