Douglas Hubler <[email protected]> wrote on 25-05-2012 11:01:14: > On Fri, May 25, 2012 at 2:59 AM, <[email protected]> wrote: > >> then we should make sure webmin works. Did you typically install > >> webmin on sipxecs systems before or just thinking ahead? > > > > I think it is important that there is at least also a UC interface where > > the important things for the UC system can be set. Like certain DHCP > > options. > > yes, agree. > > >> The DNS doesn't have to be the same that your entire company uses. I > >> cannot find a good reason not to run the DNS. > > > > IP address management is a reason why the "company DNS" should at least > > reflect > > the A records of IP addresses that are used. > > yes, a common setup is to copy records (A or SRV) records from the > sipxecs system for SIP and IM to your company DNS server. sipxecs > maintains it's own DNS because "everything is a DNS issue" and sipxecs > breaks horribly all the time when we rely on company DNS server to be > correct. In addition the number of records we require now for a HA > system has exploded because a lot more services are HA now. If before > copying the "RR" records was problematic, now it's 10x worse. The > silly thing is that these records were only used internally by sipxecs > so why make admins go thru the torture. Funny thing is this hasn't > changed much from 4.4, but it wasn't clear before that this is > actually what happened.
So we have 2 usertypes: - the UC client devices, these are mainly hardphones and softphones on any OS. These need access to the SIP SRV records etc. Since the world is moving more and more to software I think in bigger installations these should run from the "company DNS". - the UC servers, these need a separate set of DNS records, only used between them. These can be provided by the "UC DNS". There are then 3 options: 1) Use UC DNS for servers and UC clients, this would mean that the UC clients only need the standard UC records or there is a forwarding to the company DNS. There also has to be a (DHCP) way to point the UC clients to the UC DNS instead of the company DNS if it's not the same. 2) Use UC DNS for the servers and the company DNS for the clients, this means putting the necessary records in the company DNS. All records are available on the UC servers as well. This is the safest I think because the client records are available everywhere. No changes on DHCP. 3) Use company DNS for all, meaning entering all records in the company DNS. This requires special skills and time, but would work OK. Do you want all 3 options? 1) Is a good option if the UC DNS&DHCP is the main DNS/DHCP, webmin would be nice then as well. If there is another company DNS&DHCP then 2) can be used (if wanted in combination with 1)) I am now using option 3), this would be more for the bigger organisations were everything has to be controlled centrally. In the future I might swap to 2) to make sure the server part is OK. 1) is not an option because we have a high available fully managed IP address management solution in place for all clients (UC or not UC). > _______________________________________________ > 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/
