> > I think I'll avoid doing that and let the phones reregister > over time. > Shouldn't be more than about 10 or so minutes for them to > reregister I would think.
For remote users, worst case is 5 minutes. For non-remote users, it's 60 minutes. > On 4/30/2010 8:33 AM, Scott Lawrence wrote: > > On Thu, 2010-04-29 at 18:02 -0500, Josh Patten wrote: > > > >> Now that I reread your post Scott, it make much more > sense, and this > >> is what we ultimately decided to do. One question that may > or may not > >> be worth asking, is there an easy way to "copy" > registrations over so > >> that the mock upgrade system will immediately have all > registrations > >> so actually "downtime" will be minimal? > >> > > Yes. If, _before_ you bring up any services, you copy > > /var/sipxdata/sipdb/{registration,subscription}.xml from the old > > systems to the new ones, then the dynamic data will be correct. > > Copying back after the swap might not work. > > > > > > > > > _______________________________________________ > sipx-users mailing list sipx-users@list.sipfoundry.org List > Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > sipXecs IP PBX -- http://www.sipfoundry.org/ > _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/