> Hi,> > There are a few parameters editable via sipXconfig (or that > sipXconfig will hardcode for start). > Most probably sipXconfig will store these params as user > settings; the question is where does sipXopenfire need to > retrieve those settings from? > (Is it sipxopenfire.xml, or from another location)? I think we need to take a giant step back on that one. The tracker states a requirement and proposes a solution based on message audits. I'm not at all convinced at this point that this feature should be done via message audits. I'm hoping that there are better ways to get at the logged messages than to do some post processing on the entirety of XMPP messages that have been exchanged between clients. The first step towards the resolution of this problem is to appoint someone to evaluate the possible approaches to solving this issue. Once this is done, the sipXconfig requirements will become clear. [Forwarding this to the list, as I've sent to wrong list address in the first place] |
_______________________________________________ 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/
