<html><body>
<p>Hi Anca,<br>
<br>
I picked up your commit and I'm testing now. Thanks for the very fast response!<br>
<br>
I'm tracing down another issue (see below if interested) and I'm looking for the code that generates the to tag upon an initial subscription. I cannot find it. Can anyone point me to it?<br>
<br>
I'm getting messages: <br>
Sep 13 11:06:28 sdc01sip01 /var/run/openser/opensips-pres[13733]: ERROR:presence:get_stored_info: record not found in hash_table<br>
Sep 13 11:06:28 sdc01sip01 /var/run/openser/opensips-pres[13733]: ERROR:presence:handle_subscribe: getting stored info<br>
<br>
And also:<br>
Sep 13 11:02:30 sdc01sip01 /var/run/openser/opensips-pres[13748]: ERROR:db_mysql:db_mysql_do_prepared_query: driver error: Duplicate entry 'XXXXXXXXXXXXXXXXX-NzExMWUzODdmZDc1YTFiNTFlNGU3ZWQ' for key 'active_watchers_idx'<br>
<br>
I think the two might be related, and I want to understand how to to-tag is generated since it is a key to both the db and hash look ups.<br>
<br>
Thanks,<br>
Kennard<br>
<br>
<img width="16" height="16" src="cid:1__=07BBFD0EDFF13A328f9e8a93df9@logitech.com" border="0" alt="Inactive hide details for Kennard_White---09/10/2010 09:44:43 AM---Hi, Running opensips HEAD code, it seems that in at least on"><font color="#424282">Kennard_White---09/10/2010 09:44:43 AM---Hi, Running opensips HEAD code, it seems that in at least one case the presence</font><br>
<br>
<font size="2" color="#5F5F5F">From: </font><font size="2">Kennard_White@logitech.com</font><br>
<font size="2" color="#5F5F5F">To: </font><font size="2">OpenSIPS users mailling list <users@lists.opensips.org></font><br>
<font size="2" color="#5F5F5F">Date: </font><font size="2">09/10/2010 09:44 AM</font><br>
<font size="2" color="#5F5F5F">Subject: </font><font size="2">[OpenSIPS-Users] double reply by presence</font><br>
<font size="2" color="#5F5F5F">Sent by: </font><font size="2">users-bounces@lists.opensips.org</font><br>
<hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br>
<br>
<br>
<font size="4">Hi,<br>
<br>
Running opensips HEAD code, it seems that in at least one case the presence PUBLISH handling code attempts to generate two replies. Please see log trace below.<br>
<br>
In this particular case, I think presence_xml needs to return some flag to let the core presence module know that it has already replied. Or perhaps the core presence code could query sig/tm to see if a reply has already been sent.<br>
<br>
I'm happy to make the changes and submit patch if that is helpful, but please let me know which direction I should take so that the patch will be accepted.<br>
<br>
One other minor request: would be helpful if the "bad body format" message could also log the from address (or perhaps the callid -- something to make to traceable).<br>
<br>
Thanks,<br>
Kennard<br>
<br>
<br>
Sep 10 09:14:37 sdc01sip01 /var/run/openser/opensips-pres[15704]: ERROR:presence_xml:xml_publ_handl: bad body format<br>
Sep 10 09:14:37 sdc01sip01 /var/run/openser/opensips-pres[15704]: ERROR:presence:handle_publish: in event specific publish handling<br>
Sep 10 09:14:37 sdc01sip01 /var/run/openser/opensips-pres[15704]: ERROR:tm:_reply_light: failed to generate 500 reply when a final 415 was sent out<br>
Sep 10 09:14:37 sdc01sip01 /var/run/openser/opensips-pres[15704]: ERROR:signaling:sig_send_reply_mod: failed to send reply with tm module<br>
Sep 10 09:14:37 sdc01sip01 /var/run/openser/opensips-pres[15704]: ERROR:presence:send_error_reply: sending 500 Server Internal Error reply<br>
Sep 10 09:14:37 sdc01sip01 /var/run/openser/opensips-pres[15704]: ERROR:presence:handle_publish: failed to send error reply </font><tt>_______________________________________________<br>
Users mailing list<br>
Users@lists.opensips.org<br>
</tt><tt><a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a></tt><tt><br>
</tt><br>
</body></html>