29 Aug
2011
29 Aug
'11
10:58 p.m.
Hello,
On 8/29/11 8:49 PM, Juha Heinanen wrote:
Juha Heinanen writes:
looking at the xmlrpc command content, I see the E-Tag value set, for
the first publish, shouldn't it be empty and the presence server returns
the value to be used later for updates?
At the first sight, the condition in the C piece of code above reads
like: if the etag value is publish command is set, there must be a
presentity structure.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
pua/send_publish() function and it spits out 418
in this piece of code:
presentity= search_htable(&pres, hash_code);
if(publ->etag&& presentity== NULL)
{
lock_release(&HashT->p_records[hash_code].lock);
return 418;
}
any idea, how this hash table gets its contents, because looks like
send_publish() does not find presentity sip:jh@vm.test.f although it
exists in presentity db table?
if pua module gets hash table contents from pua
table, it is in my case
empty.