-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Scott Lawrence Sent: Monday, January 11, 2010 1:31 PM To: Xingjun Chu Cc: sipX-dev Subject: Re: [sipX-dev] DNS Records configuration for Windows
On Mon, 2010-01-11 at 11:38 -0500, Xingjun Chu wrote: > Hi, > > I am working on a solution to automatically add the required DNS records > generated by the tool "sipx-dns" to Windows DNS server if applicable. > Basically it uses a open source tool "winexe" and a Windows support tool > DnsCmd.exe to achieve this. > "winexe" allows Linux users to issue a command to remote Windows server. > DnsCmd.exe is a windows support tool to interact with Windows DNS and > can be downloaded from Microsoft website. > > For this, some provision needs to be done > > 1) DNS server IP of course > 2) A Windows user credentials with admin privilege (username / > password) > 3) Also indication this is a windows DNS. > > I am looking into about the UI part for provision and integration point > with sipX. > > I am thinking this occurs in both system setup phase (initial value) and > in sipXconfig (can be changed later). > > In system setup phase, this could be done at the DNS setting phase > (inside sipxecs-setup-system). In the setup phase, we should just do what we do now - there is no need to distinguish any further than between a DNS service provided by the sipXecs system and some other DNS server. > Inside sipXconifg, we should have an entry point dedicated for DNS > setting for both Windows or Linux scenarios (Maybe move DNS advisor > there too) > I should think that somewhere in the settings for the system, if we are >using an external DNS, there should be a set of configuration for: > boolean: DNS server is Windows > and iff that is true, then the name and credentials for that server. There are instances where the IT staff that maintains the Windoze domain is not a part of the team that does the telephone work, and as such, there is not a total trust amongst them. Sometimes there is a total distrust. They could be different companies, different departments, etc. I can see cases where IT is not going to give up access to the windoze server. Does it maybe make more sense to have a standalone application that can be run that has limited access to the configuration within SipXecs that could be ran by these IT entities themselves? Or, have a user operation that can be included for someone to have limited access to the ability to run this utility? _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
