About to start testing 4.6 for deployment later this year. It will live behind a pfSense firewall which currently manages DHCP and local DNS for all internal hosts. My inclination would be to delegate sipx.domain.com to the new box and allow it to run DHCP for all voice-related devices, but continue to manage the other hosts via DHCP and DNS on pfSense.
Any reason to make the sipx machine(s) authoritative for the entire domain, and manage the non-voice parts there as well? thanks~ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
