25 Oct
2006
25 Oct
'06
1:57 a.m.
Hi,
SER always generates new tuple IDs for newly published tuples. This is
because it can collect information from more sources - more clients can
send PUBLISH with the same tuple IDs, but according to RFC 3903 tuples
can rewrite each other only if they were published with the same entity
tag (SIP-ETag header field).
If you don't want to use tuples created from registration status you can
set PA module parameter "use_callbacks" to 0.
Or do you need for clients which published something not to use
tuples generated from registration status and for those which doesn't
publish anything to use such tuples? This is not possible right now, but
it is not too hard to implement it...
Vaclav
On Tue, Oct 24, 2006 at 06:00:03PM +0200, Diego Do?ate wrote:
Hi,
I am using the "presence snapshot" version of the SER server, and I want
to use a presence service. My problem is related to the "id" parameter
within the <tuple> (in the NOTIFY xml). The test is like that:
User A subscribes to the presence of user B : receives a NOTIFY with 1
<tuple> (id="none", <basic> is closed)
User B registers in SER: user A receives a NOTIFY with 1 <tuple>
(id="string", <basic> is open)
User B publishes a new presence state: user A receives a NOTIFY with 2
<tuple> (the 2nd is the same as the previous one, and a new one is attached
first with different "id" string value.
I would like only 1 <tuple>, since the device is the same, is it my
problem (something in the PUBLISH), or is it in the SER? How can I know this
"id"? Whatever I put in the PUBLISH <tuple> "id", the SER puts
another
string in the NOTIFY created...
Thaks in advance
Diego Do?ate