29 Aug
2011
29 Aug
'11
11:30 p.m.
On 8/29/11 10:23 PM, Juha Heinanen wrote:
--
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
Daniel-Constantin Mierla writes:
OK, I see, so in this case the condition in should be relaxed to allow
sending publish with etag even there is no presentity in pua table.
Cheers,
Daniel
The presentity table is built when a PUBLISH is
received, did you sent
another PUBLISH before so that you have a record in this table? Or how
was it added in this table so that you could get the etag value?
there are several
sources that can send publish for user's voicemail
box. for example, user can listen voicemails by calling to his/her
voicemail box and in that case publish is send by sems. another
possibility is that use listens voicemail on web page and in that case
web app sends the publish. in both cases, the app first checks from
presentity table which etag to use, because it has no way to know that
some other app has sent publish for the same presentity in the
meantime. In the xmlrpc command, there was an etag value,
have you tried with '.'
as etag?
i haven't tried with "." etag yet. i'll try that
tomorrow.
-- juha