If you want to make sure that IP-s are still given out when the phones reset, you must have DHCP locally in remote site. Normally it's not the best to have DHCP on Call Managers anyway, cisco does not recommend it.
Put DHCP on Domain Controllers if you have any in a remote site. or you might even want to look into a dedicated DHCP server solution. Or you could just have remote router give IP's always, and achieve high availability of DHCP by having two remote routers. Most companies normally will have two remote routers anyway, for backup connection back to the HQ. Regards, On Fri, Nov 5, 2010 at 2:24 PM, Pavan K <[email protected]> wrote: > Lets say we are required to configure Branch1 to be an SRST site. > Also during normal operation, Branch1 phones get DHCP from CCM in HQ. > > Now when BR1 is in SRST, > > If any of the phones reset, they will not be able to get DHCP and will be > unable to register to SRST. > Does this question imply an additional DHCP configuration in BR1 site ? > If so, is there any way to make the HQ DHCP primary and BR1 DHCP as > fallback when the HQ DHCP pool is in-accessible. > > > How do people deal with this in real world (other than having local DHCP on > BR1) ? > > -- > - Pavan > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
