Indeed Jitsi isn't an online service, but XCAP server (which Jitsi can
use to store contact lists and other presence information) is a
network service that can be accessed by any number of Jitsi instances
and serve as a common synchronisation tool. (BTW: this is one of the
main reasons XCAP was developed in the first place).
I am thinking if storing contacts locally when XCAP is enabled is
required / needed at all?
Maybe if XCAP is enabled Jitsi shouldn't use contactlist.xml for SIP
contact storage at all? And use exclusively XCAP service instead? Of
course this would mean no access to contact in case XCAP server is
unavailable. But on the other hand in most cases if XCAP is down, SIP
proxy/registrar will be down too and user will not be able to make
Just a thought... Any comments on this? Is there any reason why
contactlist.xml might be required when XCAP is used?
On 18 August 2011 11:53, Richard Lavoie <firstname.lastname@example.org> wrote:
This might not be a coreect behavior but Jitsi isn't an online service as all the other services it deals with. Thus there is no global communication between different running instances, no matter on which computer they are running.
For this reason, you cannot really synchronize your differents installations other than sharing the folder that contains the configuration of jitsi. Even with that folder shared, there will be problems to update 2 jitsi's instances that are running at the same time.
Maybe you can achieve something with privisionning (not sure if you can manage contacts with it). But if you can use provisionning, you'll have to update the configuration by another mean to get the changes reflected in the provisionning. And the other will probably see the changes on restart.