>Regarding MS DNS users there is simply nothing that can be done about that. You can choose one or the other at this point. Until >MS joins the rest of the world on DNS then the sipXecs cluster will either have to be run on a separate subdomain or the user will >have to give up location based registrations and SIP routing.
I don't see anything wrong with that. However if you wish to reduce the number of users that have DNS related problems, MS users have to be addressed as well. I think a great number of the users out there have an MS domain that SipX is a part of. If the software did some "hand holding" in how to setup the MS DNS records (and detect their presence for that matter) you will reduce these. It does this right now, but should do a better job if possible. Users need to be more educated during product setup. They need to know the how's and whys for a subdomain etc. One huge problem is the DNS and DHCP setup are part of the install process. I think that is incorrect. All the initial install should do prior to the web gui is configure the network enough to "get to" the gui. After that it is much easy to convey information on DNS and DHCP to a user. This also makes changes much easier down the road... I feel the first time the gui is run it should have a wizard to walk the user though setting up their voice domain. During that phase you can provide graphics, web-links, etc to help the user to make the correct choices. The wizard could be reused afterwards to reconfigure things if needed... I think that would go a long way to reducing problems. PS while you're at it, IP address reconfiguring is a big headache right now as well. I know a lot of people test using one address and need to change to another to move it to production. The wizard should handle this as well so the proper DNS records can be "conveyed" to MS DNS users so they can make the changes. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
