Hi Daniel,
Just for clarification. This case is about data from non-kamailio xcap server to be handled in a self-written Kamailio module (Railway specific functionality) during call setup, where
we would appreciate the module-API services of the xcap_client module.
Currently discussing it internally, eventually we might implement get_elem method of xcap_client module (just sending GET request and forwarding the body of the response via the API
to the Railway specific module).
KR
Von: Daniel-Constantin Mierla <miconda@gmail.com>
Gesendet: Samstag, 3. Oktober 2020 19:45
An: Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>; Valentin Christoph <Christoph.Valentin@kontron.com>
Cc: Onic Roman <Roman.Onic@kontron.com>; Friedrich Peter <Peter.Friedrich@kontron.com>
Betreff: Re: [SR-Users] xcap_client: storage of document in local DB
Hello,
afaik, xcap_client only fetches the xcap documents from a remote xcap server via http/https, it doesn't do anything else. The fetched xcap document is used by presence modules for watchers management and persentity rules.
On the other hand, xcap_server does the management of xcap documents pushed by the clients, storing/deleting/updating them in database. You do not need xcap_client module if you use the integrated xcap server implemented in the xcap_server module, the presence
modules bind directly to xcap_server internally.
Cheers,
Daniel
On 03.10.20 14:36, Valentin Christoph wrote: