Hello,
the source code needs to be checked, iirc, at some point there was
an option to use last publish, so the etag was not really
considered.
You said 'intermitent', but I assume is not the case that etag is
used for follow up publish, just the effect on blf.
Cheers,
Daniel
On 17/10/15 13:24, Asgaroth wrote:
Hi
All,
I've come accross an intermittent issue where an initial publish
is sent to our presence server, proxy recieves the subsequent 200
with etag, but the following publish sent does not contain the
sip-if-match header of the recieved 200, which ends up causing
trouble with BLF on our test devices, it also has the added side
affect of not being cleared out of the presentity table, these
entries need to be manually removed.
This does not occur all the time, I can use the same phone and
make several calls before this issue occurs. It is not limited to
a device type, we've tried with panasonic, polycom, cisco, zoiper,
yealink and linksys devices, all exhibit the same sporadic
behaviour.
I've attached an example sip trace of the publish messages where
this happens, you can see the second publish doesnt have the
sip-if-match header whose content should be that of the sip-etag
in the previous 200 to the initial publish.
I'm not sure if there is something I am misunderstanding here, a
configuration issue, or if this is indeed a bug.
Both the proxy and the presence server are running kamailio
v4.3.3.
Any pointers/suggestions/guidance would be appreciated.
If you need any additional info, please dont hesitate to ask.
Thanks
_______________________________________________
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
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com