Just imho:

Won't it be better to keep "activate" button in the UI?

Because there is hi possibility that "auto-activation" will lead to numerous
proxy/registrar restarts instead of just one..

I think, that auto activation of dialplan creates conditions for significant
non necessary downtime.

Again: this is just imho from the administrator perspective.

Thanks and regards,

Nikolay.

 

  _____  

From: Laurentiu Ceausescu [mailto:[email protected]] 
Sent: Tuesday, February 03, 2009 2:28 PM
To: Nikolay Kondratyev
Cc: 'Damian Krzeminski'; [email protected]
Subject: Re: [sipX-dev] sipXconfig: automatic dial plan replication

 

Yes, proxy and registrar services are restarted.
You can check real status in system / servers page, services tab -  but  in
real time. Jobs status page doesn't contain this information. 
Laurentiu

Nikolay Kondratyev wrote: 

By the way, does the activation of dial plan still require restart of proxy
and registrar services?
If yes, does the job status page take it into account?
Nikolay.
 
  

-----Original Message-----
From: [email protected] [mailto:sipx-dev-
[email protected]] On Behalf Of Damian Krzeminski
Sent: Tuesday, February 03, 2009 3:52 AM
To: [email protected]
Subject: [sipX-dev] sipXconfig: automatic dial plan replication
 
It's been mentioned here before but since this is quite a big change I
wanted to write a separate e-mail: sipXconfig does not require that you
activate dial plan any more (there is no UI to do that). Dial plan will be
automatically activate after any changes that require it are performed
(enabling/disabling/reordering rules, adding removing gateways/SBCs,
intercom changes etc.).
 
You can verify that dial plan activation happened on Job Status page.
 
Please say something if you think that dial plan has not been activated
when you expected it, or has been activated when you did not.
 
Jsut as before, starting sipXconfig in'first-run' mode (sipxconfig.sh
--first-run) will force an activation.
 
Laurentiu: can you have a look at my changes to your latest patch. I moved
one more call from web to neoconf (when saving the rule). Seems to work
for
me: but if you had reasons to keep it in 'web' module please let me
    

know...
  

D.
 
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
    

 
 
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
  

 

_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to