I agree with the staging and test plan, this is something we do. I want to implement a procedure on the production servers to help insure that we are as bullet proof as possible. On Fri, Feb 5, 2010 at 11:58 AM, Rupa Schomaker <rupa@rupa.com> wrote:
it'll alert you to syntax errors, but pretty much any other mistake you'll find out when calls start failing or misbehaving. Better to have a staging server where you test stuff out (with a test plan!).
On Fri, Feb 5, 2010 at 1:42 PM, Lon Baker <lon@kickasspixels.com> wrote:
I'm looking for the best practice for testing configuration changes on a live Fresswitch server.
Is it best to use reloadxml in the cli? Will that alert us to issues with syntax and other errors without bringing down the server?
Lon
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- -Rupa
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org