Thanks Cristobal - must engage my brain next time I post! On Mon, Jun 6, 2011 at 9:17 PM, Cristobal Priego <[email protected]>wrote:
> you're not "roaming" when you use extension mobility because the DP never > changes > > if we need to localize the dialing for the user, then i will use the CSS > of the device profile. > > > > > 2011/6/6 Brian Mulgrew <[email protected]> > >> Guys - just on this topic; if we had a question which required extension >> mobility be configured on an HQ phone (with no mention of roaming between >> sites) would we still be expected to update the dial plan to support HQ >> localised dialling from a BR1 phone? >> >> any thoughts appreciated. >> >> thks >> On Mon, Jun 6, 2011 at 8:30 PM, Cristobal Priego < >> [email protected]> wrote: >> >>> if you have your calling/called party transformation you can also use >>> globalized dialing >>> >>> when you you log in with EM the only change on the phone is going to be >>> the settings assigned to the line, those settings will be overwritten by the >>> device profile. >>> >>> >>> >>> 2011/6/6 Qq Ccie <[email protected]> >>> >>>> Thanks Cristobal. So Globalized dialing is a prerequisite as well? >>>> >>>> ------------------------------ >>>> *From:* Cristobal Priego <[email protected]> >>>> >>>> *To:* Qq Ccie <[email protected]> >>>> *Cc:* Brian <[email protected]>; "[email protected]" < >>>> [email protected]> >>>> *Sent:* Mon, June 6, 2011 3:00:42 PM >>>> >>>> *Subject:* Re: [OSL | CCIE_Voice] Extension Mobility and Local Route >>>> Group >>>> >>>> if you have local route groups >>>> when the user logs in to a phone using EM it will use the LRG of the DP >>>> that yo associated to the device. because on the device profile you can't >>>> assign a device pool. >>>> >>>> you can indeed use the line device approach >>>> >>>> where you allow on the device calling search space and block on the line >>>> and if you share the same dialplan between sites you shouldn't have any >>>> problems >>>> >>>> i have used EM and LRG on real life for a few customers and it works >>>> pretty well >>>> >>>> 2011/6/6 Qq Ccie <[email protected]> >>>> >>>>> I though the CSS on device pool mean for Device Mobility only, not for >>>>> Extension Mobility? >>>>> >>>>> >>>>> ------------------------------ >>>>> *From:* Brian <[email protected]> >>>>> >>>>> *To:* Qq Ccie >>>>> <ccieqqhttps://mail.google.com/mail/?hl=en&shva=1#inbox/13060d89e4fd6644if >>>>> [email protected] <[email protected]>> >>>>> *Cc:* "[email protected]" < >>>>> [email protected]> >>>>> *Sent:* Mon, June 6, 2011 1:06:09 PM >>>>> >>>>> *Subject:* Re: [OSL | CCIE_Voice] Extension Mobility and Local Route >>>>> Group >>>>> >>>>> hi - re EM call routing path: we can use device mobility to flip to the >>>>> roaming device pool to support this. >>>>> >>>>> hth. >>>>> Brian >>>>> >>>>> >>>>> Sent from my iPad >>>>> >>>>> On 6 Jun 2011, at 15:05, Qq Ccie <[email protected]> wrote: >>>>> >>>>> >>>>> Thanks Kiwi. On a side note, calling number transformation has to be >>>>> handled at RL level in order to different calling number requirements >>>>> (local, ld and intl)? >>>>> >>>>> Also, two RPs (\+1919.XXXXXXX placed in two different partitions) have >>>>> to be configured if Site B has a requirement of TEHO for 919 area code? >>>>> >>>>> >>>>> *From:* Ki Wi <[email protected]> >>>>> *To:* Qq Ccie <[email protected]> >>>>> *Cc:* <[email protected]>[email protected] >>>>> *Sent:* Sun, June 5, 2011 11:39:36 PM >>>>> *Subject:* Re: [OSL | CCIE_Voice] Extension Mobility and Local Route >>>>> Group >>>>> >>>>> In that case, you have a great time of converting everything to e164. >>>>> =P >>>>> >>>>> Use called party transformation to strip them into the correct digits >>>>> at the gateway level. >>>>> >>>>> Example : Site A ( local area code 919) ---> calls to local number is >>>>> 8123123 >>>>> >>>>> Converted the dialed number to +19198123123 >>>>> >>>>> Use a route pattern +.! and send to local route group >>>>> >>>>> >>>>> At each gateway, use called party transformation. >>>>> Match +1.919! , called transformation mask XXXXXXX for Site A gateway >>>>> >>>>> At Site B, you will strip predot for the other called party >>>>> transformation. >>>>> >>>>> >>>>> >>>>> On Mon, Jun 6, 2011 at 9:54 AM, Qq Ccie < <[email protected]> >>>>> [email protected]> wrote: >>>>> >>>>>> >>>>>> Thanks Ahmed for your help. Yes, I agree that CSS has to be at the >>>>>> line level. >>>>>> >>>>>> However, the assumption is that HQ and BR1 have configured call >>>>>> routing via Standard Local Route Group. When logged in to EM service, >>>>>> the >>>>>> user would not be able to use his original local gateway because the >>>>>> current >>>>>> local gateway is based on Device Pool settings. As a result, his >>>>>> local/long >>>>>> distance call might not be correct. Any suggestion? >>>>>> >>>>>> Thanks, >>>>>> >>>>>> ------------------------------ >>>>>> *From:* Ahmed Ellboudy < <[email protected]> >>>>>> [email protected]> >>>>>> *To:* Qq Ccie < <[email protected]>[email protected]>; >>>>>> <[email protected]>[email protected] >>>>>> *Sent:* Sun, June 5, 2011 1:53:46 PM >>>>>> *Subject:* RE: [OSL | CCIE_Voice] Extension Mobility and Local Route >>>>>> Group >>>>>> >>>>>> Hi, >>>>>> I think you need to use Line device approach rule which will solve it >>>>>> by open every calls types local/national and international and makes the >>>>>> EM >>>>>> to limit your access,refer to the SRND in this point >>>>>> >>>>>> >>>>>> Thanks & Regards; >>>>>> Ahmed Mahmoud Ellboudy >>>>>> ------------------------------ >>>>>> *From:* <[email protected]> >>>>>> [email protected] on behalf of Qq Ccie >>>>>> *Sent:* Sun 6/5/2011 6:31 PM >>>>>> *To:* <[email protected]>[email protected] >>>>>> *Subject:* [OSL | CCIE_Voice] Extension Mobility and Local Route >>>>>> Group >>>>>> >>>>>> >>>>>> Anyone has any thoughts of the interaction between Extension >>>>>> Mobility and Local Route Group? Assuming HQ and BR1 have configured call >>>>>> routing via Local Route Group. Any suggestions? >>>>>> >>>>>> 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. >>>>>> >>>>>> _______________________________________________ >>>>>> For more information regarding industry leading CCIE Lab training, >>>>>> please visit <http://www.ipexpert.com>www.ipexpert.com >>>>>> >>>>>> Are you a CCNP or CCIE and looking for a job? Check out >>>>>> <http://www.PlatinumPlacement.com>www.PlatinumPlacement.com >>>>>> >>>>> >>>>> _______________________________________________ >>>>> For more information regarding industry leading CCIE Lab training, >>>>> please visit <http://www.ipexpert.com>www.ipexpert.com >>>>> >>>>> Are you a CCNP or CCIE and looking for a job? Check out >>>>> <http://www.PlatinumPlacement.com>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 >>>>> >>>> >>>> >>> >> >
_______________________________________________ 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
