Depending on your endpoint devices, not all things "may work properly" with this approach, like MWI.
On Tue, Jun 5, 2012 at 11:06 AM, [email protected] <[email protected]>wrote: > On Mon, 25 Jun 2012 10:09:48 -0400, Michael Picher wrote: > > yea good point... maybe i'm a bad interwebber but i always set mine to 5 > > mins :-) > > > > On Mon, Jun 25, 2012 at 10:02 AM, [email protected] <[email protected]> > > wrote: > >> BTW you may want to lower the TTL of the old zone before doing so if > >> you've got access to it. It may take a few to propagate around. > > That's a good point. > I don't see a problem with having a very short TTL on an outgoing domain. > > > > > > > > >> From: [email protected] [sipx-users- > >> [email protected]] On Behalf Of Michael Picher > >> [[email protected]] > >> > >> Sent: Monday, June 25, 2012 9:53 AM > > To: [email protected]; Discussion list for users of sipXecs software > > Subject: Re: [sipx-users] DNS SRV one domain to another for remotes > > > > > > yes, just set a domain alias on the new cluster with the old domain... > > then swing the external dns A records to point to the new outside IP's. > > > > > >> On Mon, Jun 25, 2012 at 9:45 AM, > >> [email protected] <[email protected]> wrote: > >> > >> On Mon, 25 Jun 2012 05:26:46 -0400, Michael Picher wrote: > >> But you haven't given me any information about WHERE this domain name > >> setting is programmed in this simple router such that it would make a > >> difference to the installation... > >> Re-read my question please. > >> > > > > Your question seemed pretty straight forward, not sure what I missed. > > > >>> And, now, what setting is it specifically that is programmed in the > >>> router you are worried about? > >>> > > > > The domain name. That would be in the Registration/Proxy Server setting > of > > the routers voip section. > > Then I said that the users authentication details don't have to change. > > Those details are identical across both sipx servers. > > > > Since I can't get at the routers, I was wondering if I could change the > dns > > record to force users to automatically switch from the old sipx server to > > the new one. > > So basically, I would edit the old sipxA.com record to point to the IP of > > the new server sipxB.com for example. > > > > > >> Mike > >> > >> On Sun, Jun 24, 2012 at 5:45 PM, [email protected] <[email protected]> > >> wrote: > >>> On Sun, 24 Jun 2012 17:28:17 -0400, Michael Picher wrote: > >>> And, now, what setting is it specifically that is programmed in the > >>> router > >>> you are worried about? And how many of them are you talking about > here? > >>> > >> > >>> Only a handful but none in just one area. > >>> > >> The authentication information isn't going to change, only the domain > name > >> is. I am trying to propagate the last of the users from an old system I > >> need to shut down and onto a new system. The replacement system has a > >> different domain name however. > >> > >> > >>>> On Jun 24, 2012 11:04 AM, "[email protected]" <[email protected]> > >>>> wrote: > >>>> > >>>> They are all Linksys RT31P2-NA. Users were supposed to put them just > >>>> behind their providers so we could get at them if we needed to change > >>>> anything but some folks put them behind their own routers so we can't > >>>> get > >>>> at them. Since I can't change the router info, it would be cool if I > >>>> could simply change the dns info, then shut down the old server so > >>>> that > >>>> those users automatically get moved to the new server. > >>>> > >>> > >>>> On Sun, 24 Jun 2012 05:02:31 -0400, Michael Picher wrote: > >>>> What are these routers you speak of? > >>>> > >>>> > >>>> On Sun, Jun 24, 2012 at 1:23 AM, [email protected] <[email protected] > > > >>>> wrote: > >>>>> Their routers are all statically set with the old domain name and > >>>>> user > >>>>> authentication details. > >>>>> > >>>> > >>>> On Sat, 23 Jun 2012 16:36:38 -0400, Tony Graziano wrote: > >>>>> That will work but not the "best" way to do it (MWI may have an > >>>>> issue, > >>>>> etc.). > >>>>> > >>>>> Is the customer auto provisioned (devices) via sipx? > >>>>> > >>>> > >>>>> On Sat, Jun 23, 2012 at 3:00 PM, [email protected] > >>>>> <[email protected]> > >>>>> wrote: > >>>>>> On Sat, 23 Jun 2012 11:52:35 -0700, [email protected] wrote: > >>>>>> > >>>>>>> The domain alias setting comes to mind. Maybe worth a shot? In > >>>>>> sipXsupervisor -> System -> Domain -> and down at the bottom "Add > >>>>>> Alias". > >>>>>> > >>>>> > >>>>>> Sounds like that could work. Only thing is, this is a live system > >>>>>> so I > >>>>>> only have one shot at this. > >>>>> Anyone know for sure if that would work? I would point the old > >>>>> domain > >>>>> dns/srv records to the new sipx server's IP. > >>>>> > >>>>>> > >>>>>> -----Original Message----- > >>>>>> From: [email protected] [mailto:sipx-users- > >>>>>> [email protected]] On Behalf Of > >> [email protected] > >>>>>> Sent: Saturday, June 23, 2012 2:47 PM > >>>>>> To: sipx-users > >>>>>> Subject: [sipx-users] DNS SRV one domain to another for remotes > >>>>>> > >>>>>> Well, wasn't really sure how to word that in the subject but > >>>>>> here's > >>>>>> the > >>>>>> issue. > >>>>>> > >>>>>> I have some remotes that need to be migrated over to a new sipx > >>>>>> server. > >>>>>> I > >>>>>> can't get at their routers to change the old domain name and the > >>>>>> new > >>>>>> sipx > >>>>>> box is on a new domain name. > >>>>>> > >>>>>> I was wondering if I could simply point the old domain dns > >>>>>> information > >>>>>> to > >>>>>> the new sipx box which has a new domain name. This would work fine > >>>>>> using > >>>>>> regular dns but I'm not sure if sipx will allow the users to > >>>>>> authenticate > >>>>>> since sipx won't know anything about the old domain name. > >>>>>> > >>>>>> I could always add another domain name in the new sipx dns record > >>>>>> but > >>>>>> am > >>>>>> still not sure if sipx will allow them to authenticate since they > >>>>>> are > >>>>>> looking for a different domain name. I realize dns srv is simply a > >>>>>> means > >>>>>> to > >>>>>> get to a certain domain but as I say, will sipx, which only knows > >>>>>> about > >>>>>> it's own domain allow the user to authenticate? > >>>>>> > >>>>>> I hope this makes sense. > >>>>>> > >>>>>> Mike > >>>>>> > >>>>>> _______________________________________________ > >>>>>> sipx-users mailing list > >>>>>> [email protected] > >>>>>> List Archive: > >> http://list.sipfoundry.org/archive/sipx-users/ > >>>>>> _______________________________________________ > >>>>>> sipx-users mailing list > >>>>>> [email protected] > >>>>>> List Archive: > >> http://list.sipfoundry.org/archive/sipx-users/ > >>>>> _______________________________________________ > >>>>> sipx-users mailing list > >>>>> [email protected] > >>>>> List Archive: > >> http://list.sipfoundry.org/archive/sipx-users/ > >>>> _______________________________________________ > >>>> sipx-users mailing list > >>>> [email protected] > >>>> List Archive: > >> http://list.sipfoundry.org/archive/sipx-users/ > >>> _______________________________________________ > >>> sipx-users mailing list > >>> [email protected] > >>> List Archive: > >> http://list.sipfoundry.org/archive/sipx-users/ > >> _______________________________________________ > >> sipx-users mailing list > >> [email protected] > >> List Archive: > >> http://list.sipfoundry.org/archive/sipx-users/ > > _______________________________________________ > > sipx-users mailing list > > [email protected] > > List Archive: > >> http://list.sipfoundry.org/archive/sipx-users/ > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! ~~~~~~~~~~~~~~~~~~ Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab 2013! <http://sipxcolab2013.eventbrite.com/?discount=tony2013%22> -- LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
