In older version of sipXecs there were external xml / cfg files that would be merged in with the system settings. Maybe we need to look at going back to something like that?
An easy way to turn them off for debugging might be nice too. Mike On Sat, Jul 31, 2010 at 8:23 PM, Douglas Hubler <[email protected]> wrote: > On Sat, Jul 31, 2010 at 12:13 PM, Ali Nebi <[email protected]> wrote: > > Yep, i will go this way. I thought that there is a fast way editing some > > property files. > > I think we need to research a more flexible way to enable features in > openfire. Playing catchup with each feature one by one seems like a > silly way to approach this. Same goes for freeswitch modules. We > need to think about a kit where people can assemble support for > missing features on their own or at least have a way to preserve > settings that need to be changed from the console. > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- There are 10 kinds of people in this world, those who understand binary and those who don't. [email protected] blog: http://www.sipxecs.info call: sip:[email protected] <sip%[email protected]>
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
