Hello all.
I've been testing presence module for a while and I do notice that presentity table grows endlessly over time. Each time a call is made a new record is added in presentity with a different etag. In documentation, namely developers guide we can read this:
int etag_not_new; /* * 0 - the standard mechanism (allocating new etag for each Publish) * 1 - allocating an etag only for an initial Publish */
How can I tell the presence module in kamailio config to work using the second form of the above?
Looking forward to hear from you.
BR,
--
*Nuno Miguel Reis* | *Unified Communication** Systems* M. +351 913907481 | nreis@wavecom.pt WAVECOM-Soluções Rádio, S.A. Cacia Park | Rua do Progresso, Lote 15 3800-639 AVEIRO | Portugal T. +351 309 700 225 | F. +351 234 919 191 *GPS http://maps.google.com/maps/ms?msa=0&msid=202333747613191340808.0004b4b227a6144f0df88 | www.wavecom.pt http://www.wavecom.pt/** http://www.wavecom.pt/*
[image: Description: Description: WavecomSignature] http://www.wavecom.pt/pt/wavecom/premios.php
[image: Publicity] http://www.wavecom.pt/pt/mail_eventos.php
Nuno Reis writes:
I've been testing presence module for a while and I do notice that presentity table grows endlessly over time. Each time a call is made a new record is added in presentity with a different etag.
presence module does not do anything with calls. it handles publish and subscriber requests and generates notifies.
when publish is handled, it is the job of the publisher to place correct etag in subsequent refresh publish requests.
-- juha
Hi Juha. Thanks for answering me back. In my particular case my publisher is Kamailio itself. You can see a code snippet for my presence configs (attached) in my kamailio config file. I'm using pua to generate SIP PUBLISH messages on 127.0.0.1 and probably that isn't the best approach, but I don't have other. Any suggestions?
Cheers,
--
*Nuno Miguel Reis* | *Unified Communication** Systems* M. +351 913907481 | nreis@wavecom.pt WAVECOM-Soluções Rádio, S.A. Cacia Park | Rua do Progresso, Lote 15 3800-639 AVEIRO | Portugal T. +351 309 700 225 | F. +351 234 919 191 *GPS http://maps.google.com/maps/ms?msa=0&msid=202333747613191340808.0004b4b227a6144f0df88 | www.wavecom.pt http://www.wavecom.pt/** http://www.wavecom.pt/*
[image: Description: Description: WavecomSignature] http://www.wavecom.pt/pt/wavecom/premios.php
[image: Publicity] http://www.wavecom.pt/pt/mail_eventos.php
On Tue, Jan 20, 2015 at 7:37 PM, Juha Heinanen jh@tutpro.com wrote:
Nuno Reis writes:
I've been testing presence module for a while and I do notice that presentity table grows endlessly over time. Each time a call is made a new record is added in presentity with a different etag.
presence module does not do anything with calls. it handles publish and subscriber requests and generates notifies.
when publish is handled, it is the job of the publisher to place correct etag in subsequent refresh publish requests.
-- juha
-
Juha Heinanen -
Nuno Reis