<br>just glad of being useful<br><br>Thanks for your feedback!<br><br>One last question: subscriptions are stored on the SER DB?<br>I have <modparam("rls", "db_mode", 1)> on the config file<br><br>
Miguel<br><br><br><div><span class="gmail_quote">On 5/10/06, <b class="gmail_sendername">Vaclav Kubart</b> <<a href="mailto:vaclav.kubart@iptel.org">vaclav.kubart@iptel.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
><br>><br>> I was missing line<br>> lookup_user("To");<br><br>It was missing in the presence handbook too - it will be corrected in<br>next version.<br><br>><br>> Shouldn't the resource list of subscriptions be stored on the SER DB?
<br>> Because I'm getting that Waning all the time and I can't find any entry<br>> related with subscriptions (table rls_subscription, ...)<br><br>No DB is not problem there. I will correct it in CVS - this warning will
<br>not be displayed if parameter will be "0".</blockquote><div><br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> I have captured SIP and HTTP packets with Ethereal, sending file..
<br>> (It doesn't include packets changed between SER and apache because they are<br>> on the same machine and I don't have access to it right now)<br>> SER and apache on <a href="http://193.136.93.140">193.136.93.140
</a><br>> SIP domain = <a href="http://itav140.av.it.pt">itav140.av.it.pt</a><br>> eyeBeam <<a href="mailto:sip:4004@193.136.93.252">sip:4004@193.136.93.252</a>> and <<a href="mailto:sip:4002@193.136.92.68">
sip:4002@193.136.92.68</a> ><br>> After register, client <<a href="mailto:sip:4002@193.136.92.68">sip:4002@193.136.92.68</a> <<a href="mailto:sip:4002@193.136.92.68">sip:4002@193.136.92.68</a>>><br>> changes his status to Away (packet 53)
<br>> <sip:4004> receives the new presence status of <sip:4002> (packet 55 and 75)<br>> But when <sip:4002> renew his PUBLISH (packet 79) he doesn't include a<br>> message body with his presence state.
<br>> So, the subsequent NOTIFY received by <sip:4004> (packet 85) doesn't include<br>> the presence status Away any more, even thou <sip:4002> hasn't changed his<br>> status.<br>> After that, the client <sip:4004> shows <sip:4002> as Available, when he is
<br>> Away.<br><br>Bingo! You have found a bug in SER - thanks! I have read it in RFC now,<br>and in the case of empty body needs the state be refreshed, not cleared<br>as was done. I will correct it soon.<br><br> Vaclav
<br><br></blockquote></div><br>