http://track.sipfoundry.org/browse/XCF-3194
Bogdan: I did not apply the patches yet. They look OK but there might be some more changes needed: Dial plan replication in current code is triggered in several places from UI (web) code - where possible it should be moved to neoconf so that replication happens when system is reconfigured through non-UI activity. Replicating dial plan is an invasive activity: sipXconfig should not do it too often. If admins save several dialing rules in a short time-span they are most probably just reconfiguring the dialplan: we should wait for a quiet period and replicate then. Please compare how we handle replicating dataset: we have a 'lazy' and 'eager' implementations. When dataset replication is triggered several times in a short period of time it only results in a single replication request. It would probably make sense to implement DialPlanActivationManager that uses similar mechanism. I do not think that the underlying mechanism insures that behavior at the moment, I might be wrong on that. 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
