You did battle with a war file. Then you automated your battleplan. Seems like this should be addressed architecturally but wrapping all the parameters inside the war file makes any real customization (ports, etc.) Somewhat problematic.
It also seems this might be an additional reason cpu usage stays high "longer" at bootup compared to versions prior to 4.2? ============================ Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ ----- Original Message ----- From: [email protected] <[email protected]> To: Discussion list for users of sipXecs software <[email protected]> Cc: sipXecs developers <[email protected]> Sent: Tue Sep 14 15:15:08 2010 Subject: Re: [sipx-users] Session timer help needed. For those interested, here's a quick hack script to set your session timer to -1 (NO-TIMEOUT). It works nicely. #/bin/bash mkdir ~/tmp mkdir ~/sipxbackups cp /usr/share/java/sipXecs/sipXconfig/sipxconfig.war ~/sipxbackups cd ~/tmp jar xvf /usr/share/java/sipXecs/sipXconfig/sipxconfig.war perl -e 's/timeout>15/timeout>-1/g' -p -i ~/tmp/WEB-INF/web.xml jar cvf sipxconfig.war * cp -u sipxconfig.war /usr/share/java/sipXecs/sipXconfig/ Be sure to restart sipxecs when you are finished. -Jim _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
