I think it would probably be replaced in an upgrade or update so it having it as a configurable item in sipconfig is perhaps the more permanent fix.
On 9/14/10, Jim Canfield <[email protected]> wrote: > On Tue, Sep 14, 2010 at 2:59 PM, Tony Graziano <[email protected] >> wrote: > >> You did battle with a war file. Then you automated your battleplan. >> > > Funny. > > >> >> Seems like this should be addressed architecturally but wrapping all the >> parameters inside the war file makes any real customization (ports, etc.) >> Somewhat problematic. >> > > If sipxconfig.properties worked, this wouldn't be an issue. > -- Sent from my mobile device ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
