<div dir="ltr">Ok. So then this task should be closed. Thx fr reply)<br>Will do dialog state notification by other methods.<br><br>Is ther any plans to integrate sending pure text (not SIP) via websocket proto to client?</div><div class="gmail_extra"><br><div class="gmail_quote">2017-10-23 10:31 GMT+03:00 Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Hello,<br>
</p><span class="">
<br>
<div class="m_5210715477506056983moz-cite-prefix">On 23.10.17 08:46, Yuriy Gorlichenko
wrote:<br>
</div>
<blockquote type="cite">
<div dir="auto">Hi
<div dir="auto">Yes but i suppose the trouble in the</div>
<div dir="auto">pidf+xml (websockets based endpoint uses it
meanwhile hardphones uses dialog-info+ xml</div>
<div dir="auto">As i understood it not accepts dialog states.
Only presentity.</div>
<div dir="auto"><br>
</div>
<div dir="auto">am i right? </div>
<div dir="auto">If yes i will safe our time) if not, let me know
- i will collect logs ASAP. <br>
</div>
</div>
</blockquote>
<br></span>
Yes, dialog-info+xml is for dialog states and pidf+xml should be for
user presence states, so they are different events and a publish for
one will not trigger a notify for the other. It was more or less
what I wanted to see in headers, if the subscribed events are the
same, if expires values are ok, ...<br>
<br>
Cheers,<br>
Daniel<div><div class="h5"><br>
<blockquote type="cite">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Oct 23, 2017 09:37,
"Daniel-Constantin Mierla" <<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>> wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Hello,</p>
<p>can you grab the logs from kamailio as well as the sip
traffic at the same time? We need to see all the headers
in these sip requests to be able tot rack what
operations have to be done.</p>
<p>Cheers,<br>
Daniel<br>
</p>
<br>
<div class="m_5210715477506056983m_-2666417663345806318moz-cite-prefix">On
17.10.17 17:49, Yuriy Gorlichenko wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi use 5.0.1 with presence<br>
for TCP/UDP endpoints presence works PERFECT<br>
but for WS socket presence i see next (small cleaned
log here with all described bellow <a href="https://pastebin.com/8a77ggj0" target="_blank">https://pastebin.com/8a77ggj0</a>
):<br>
<br>
When WS endpoint subscribes - kamailio After kamailio
sends 202 to SUBSCRIBE message (see it on client) it
sends fast NOTIFY correcly without any trouble, and i
see at the kamailio reply from WS endpoint - 200<br>
<br>
WS endpoint added to active_watchers table.<br>
<br>
But when Subscribed endpoint makes for example some
call and presence server sends PUBLISH i see:
<div><br>
presence [presentity.c:426]:
delete_presentity_if_dialog_id<wbr>_exists():
Presentity already exists - deleting it<br>
<br>
At the logs and then presence server doesn't send
NOTIFY to WS endpoint<br>
<br>
What is the issue of this? Can not understand why it
happens. Can someone to help me understand this?<br>
<br>
And the dump i see that kamailio send first NOTIFY
form UDP port but then translates it to tls for
websocket and i see correct NOTIFY at the WS
endpoint</div>
</div>
<br>
<fieldset class="m_5210715477506056983m_-2666417663345806318mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
Kamailio (SER) - Users Mailing List
<a class="m_5210715477506056983m_-2666417663345806318moz-txt-link-abbreviated" href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a>
<a class="m_5210715477506056983m_-2666417663345806318moz-txt-link-freetext" href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">https://lists.kamailio.org/cgi<wbr>-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
<pre class="m_5210715477506056983m_-2666417663345806318moz-signature" cols="72">--
Daniel-Constantin Mierla
<a class="m_5210715477506056983m_-2666417663345806318moz-txt-link-abbreviated" href="http://www.twitter.com/miconda" target="_blank">www.twitter.com/miconda</a> -- <a class="m_5210715477506056983m_-2666417663345806318moz-txt-link-abbreviated" href="http://www.linkedin.com/in/miconda" target="_blank">www.linkedin.com/in/miconda</a>
Kamailio Advanced Training, Nov 13-15, 2017, in Berlin - <a class="m_5210715477506056983m_-2666417663345806318moz-txt-link-abbreviated" href="http://www.asipto.com" target="_blank">www.asipto.com</a>
Kamailio World Conference - <a class="m_5210715477506056983m_-2666417663345806318moz-txt-link-abbreviated" href="http://www.kamailioworld.com" target="_blank">www.kamailioworld.com</a></pre>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
<pre class="m_5210715477506056983moz-signature" cols="72">--
Daniel-Constantin Mierla
<a class="m_5210715477506056983moz-txt-link-abbreviated" href="http://www.twitter.com/miconda" target="_blank">www.twitter.com/miconda</a> -- <a class="m_5210715477506056983moz-txt-link-abbreviated" href="http://www.linkedin.com/in/miconda" target="_blank">www.linkedin.com/in/miconda</a>
Kamailio Advanced Training, Nov 13-15, 2017, in Berlin - <a class="m_5210715477506056983moz-txt-link-abbreviated" href="http://www.asipto.com" target="_blank">www.asipto.com</a>
Kamailio World Conference - <a class="m_5210715477506056983moz-txt-link-abbreviated" href="http://www.kamailioworld.com" target="_blank">www.kamailioworld.com</a></pre>
</div></div></div>
</blockquote></div><br></div>