Thanks for updating the patch. I still have some questions - and I am trying to explain here how configuration files are replicated in general, so I decided to send this to the list.
David Saint (JIRA) wrote: > [ > http://track.sipfoundry.org/browse/XX-5594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44249#action_44249 > ] > > David Saint edited comment on XX-5594 at 10/22/09 2:39 PM: > ----------------------------------------------------------- > > Updated code in rev016924 based on Damian's comments: > > > Please note that with this update the sipxivr task is now required for > servers with the Conference role, since that task is used to capture > conference status messages from freeswitch. If sipXconfig is to enforce it you need to add conferencing bundle to sipxivr definition in services.beans.xml (and test if it does not break something). I don't see such change in the patch. That's quite a change BTW. For many reasons discussed on this list it would be much better if recording service was independent of sipXivr. > > - conferencebridge.xml continues to contain all conferences since we can > record WAV files on all the conference servers, the files get sent back > to the mailbox server. Every file that is replicated needs a service to which it belongs to. You need to decide if conferencebridge.xml is a sipXivr configuration file or a sipXfreeswitch configuration file. Part of the configuration file definition is information if service restart is required when file is generated. By default sipXconfig *will* restart the service. If it's not needed configuration file needs to set its "restartRequired" property to false (I hope this is the case here: otherwise we will be restarting voicemail and autoattendant every time conference is added/removed etc.) The configuration file needs to be declared as a part of the service. See service.beans.xml and check any of the service 'configurations' element. The configuration file will be automatically replicated with all the other files that belong to this service. The implementation that is in the patch will result in hard to catch "Resource Missing" errors since sipXconfig does not know which configuration file it needs to push for which service. ConferenceBridgeProvisioningImpl.deploy already replicates freeswitch and sipXivr - so if the new file belongs to one of them no changes in deploy are needed. I am still not clear why we are replicating all conference names to all services: each instance of sipXivr will only records conferences that run on its own server, right? Why does it need to know about all conferences on all servers? _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
