+1 for the idea. But I'd like to offer to think a bit different way: will it be helpful to use different/independent sofia profile, listening on different port, say 15160, and different/independent context in the FS dialplan for openACD integration? Just an idea...
Rgds, Nikolay. > -----Original Message----- > From: sipx-users-boun...@list.sipfoundry.org > [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of > George Niculae > Sent: Wednesday, November 10, 2010 6:17 PM > To: Discussion list for users of sipXecs software > Subject: [sipx-users] when to reload Freeswitch dial plans > > Hi All, > > I am working on OpenACD integration (it use Freeswitch dial > plans) and one requirement is to replicate Freeswitch dial > plan on admin action only - say admin configures several > extensions and wants this to take effect only when they all > are configured. In order to do this I am going to mark > Freeswitch service with a reload needed flag and send > reloadxml command only on a specific action (same way as > restarting marked services today from services page). > The issue here is that at this moment conferences are using > Freeswitch dial plans as well and any change on conferences > automatically reloads dial plans - this will make also > OpenACDs extensions to be taken into account. I discussed > this with Douglas and agreed for changing conference to use > same mechanism / workflow: conference changes will need a > reload action on service page in order to be taken into account. > > Please let me know what do you think about introducing this > new step for configuring conferences. > > Thanks, > George > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
