Hi Laurent,

Thanks for you reply.

I did enable CUSTOM_ACCOUNT in DefineWengoOptions.cmake file.

However still can't figure out which "webservice" should push contacts
to QuteCom.

Likely candidates are:

WENGO_SSO_PATH_KEY = "wengo.sso.path"; // I use that one already for
SIP account details

WENGO_INFO_PATH_KEY = "wengo.info.path";
WENGO_SUBSCRIBE_PATH_KEY = "wengo.subscribe.path";
WENGO_CIRPACK_PATH_KEY = "wengo.cirpack.path";
WENGO_DIRECTORY_PATH_KEY = "wengo.directory.path";

Could you please let me know which of the above is responsible for Contact list?

Thanks and best regards,
Chris


2009/8/6 Laurent Tarrisse <laur...@mbdsys.com>:
> Yes, it is possible to fetch contacts from server
>
> You need to enable CUSTOM_ACCOUNT in DefineWengoOptions.cmake
>
> Laurent
>
> Chris Maciejewski a écrit :
>> Hi,
>>
>> Is it currently possible to fetch contacts from the server (in XML format)?
>>
>> I managed to implement
>>
>> <wengo.info.path><string>/oss/info</string></wengo.info.path>
>>
>> to update balance, line number etc.
>>
>> I can see the following in the config.xml:
>>
>> <wengo.directory.path><string>/oss/directory</string></wengo.directory.path>
>>
>> but there is nowhere in the code the above is used???
>>
>> The only "webservices" I can see in src/model/webservices are
>> callforward, info, sms and softupdate.
>>
>> If it is not implemented at the moment, could please someone let me
>> know, where is a best place to start to add this feature?
>>
>> Best regards,
>> Chris
>> _______________________________________________
_______________________________________________
QuteCom-dev mailing list
QuteCom-dev@lists.qutecom.org
http://lists.qutecom.org/mailman/listinfo/qutecom-dev

Reply via email to