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?
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/

Reply via email to