i added some debug to pua_mi/mi_pua_publish() function and
pua/send_publish() function and got to syslog:
Aug 29 20:57:41 sip /usr/sbin/pres-serv[3861]: INFO: pua_mi [mi_func.c:254]:
send publish
Aug 29 20:57:41 sip /usr/sbin/pres-serv[3861]: INFO: pua [send_publish.c:403]:
pres_uri=sip:j...@vm.test.fi
Aug 29 20:57:41 sip /usr/sbin/pres-serv[3861]: INFO: pua_mi [mi_func.c:258]:
publish result <418>
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:j...@vm.test.f although it
exists in presentity db table?
-- juha
_______________________________________________
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
