> -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Krzeminski, Damian (BL60:9D30) > Sent: Monday, September 21, 2009 8:10 AM > To: [email protected] > Subject: Re: [sipX-dev] Initialization issues in sipXecs with > Openfireplug-in > > Martin Pepin wrote: > > Hi, > > > > I have updated the source tree to the latest revision. I > keep seeing > > exception back traces in the Openfire errors.log file. It > used to work > > better in the middle of last week. I have listed the issues I have > > found. I am blocked on the last issue #3. > > > > bash-3.2$ svn info > > Path: . > > URL: _http://sipxecs.sipfoundry.org/rep/sipXecs/main_ > > Repository Root: _http://sipxecs.sipfoundry.org/rep/sipXecs_ > > Repository UUID: ab1d8caa-1f67-47f1-9e81-24633a41865c > > Revision: 16543 > > Node Kind: directory > > Schedule: normal > > Last Changed Author: dworley > > Last Changed Rev: 16543 > > Last Changed Date: 2009-09-18 20:43:45 -0400 (Fri, 18 Sep 2009) > > > > Issue #1: sipxrest.xml layout differs from sipxrest.xml.example and > > file path mismatch ======= Running the latest ede_build_devuser.sh > > script this weekend to refresh my development environment, > I noticed > > that file sipxrest.xml is now automatically generated under > > .../INSTALL/etc/*sipxpbx/sipxrest*/sipxrest.xml. Based on Ranga's > > instructions, last week I used to manually copy file > > .../main/sipXrest/sipxrest.xml.example to > > .../INSTALL/etc/*sipxpbx/*sipxrest.xml, then edited file > sipxrest.xml > > to match my sipXecs server settings. So this is a path > mismatch *and* > > the layout and field names of the sipxrest.xml file > somewhat differs > > from that of file sipxrest.xml.example. > > I cannot really help with any of the specific problems with > Openfire but I have seen on #sipx that Huijun and Ranga > agreed to change the name of sipXrest configuration file to > sipxrest-config.xml. This is what sipXconfig generates at the > moment and this is what sipXrest process descriptor accepts. > > http://sipxecs.sipfoundry.org/rep/sipXecs/main/sipXrest/sipxre > st-process.xml.in > > Openfire plug-in should never read sipxrest-config.xml > (because there is no guarantee that Instant Messaging bundle > is activated on the same server as sipXrest service) If > openfire needs any information about sipxrest such data > should be placed directly in one of the openfire config file > or in domain-config. > > [...]
You are right. I just committed a temporary fix to allign the filenames but I will look into following your recommendation. _______________________________________________ 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/
