It used to be you has to "activate" dial plan changes. NOW a warning is given. Obviously you can opt to do that at a time that suits you, but until siptrunking can be moved onto an "island" approach or rewritten, I do not see how it is as simple as a feature request.
On 8/19/10, Worley, Dale R (Dale) <[email protected]> wrote: > ________________________________________ > From: [email protected] > [[email protected]] On Behalf Of Krisztian Ganyai > [[email protected]] > > We have a system where dial plans are added/modified relatively > frequently. After each change some services have to be restarted(proxy > and registrar), which is accounted as a system downtime. > > Is there a way/chance/possibility to avoid these restarts when a dial > plan is changed? > _______________________________________________ > > Not currently. But with sufficient code changes it could be done. You > could enter an "Improvement" Jira and get people to vote for it. > > Dale > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > -- 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/
