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 | nr...@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 <j...@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 >
presence.cfg
Description: Binary data
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
