[SR-Users] Presence WARNING after publish and no NOTIFY

[Daniel-Constantin Mierla]

Hello,


On 23.10.17 08:46, Yuriy Gorlichenko wrote:
> Hi
> Yes but i suppose the trouble in the
> pidf+xml (websockets based endpoint uses it meanwhile hardphones uses
> dialog-info+ xml
> As i understood it not accepts dialog states. Only presentity.
>
> am i right? 
> If yes i will safe our time) if not, let me know - i will collect logs
> ASAP.

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, ...

Cheers,
Daniel
>
> On Oct 23, 2017 09:37, "Daniel-Constantin Mierla" <miconda at gmail.com
> <mailto:miconda at gmail.com>> wrote:
>
>     Hello,
>
>     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.
>
>     Cheers,
>     Daniel
>
>
>     On 17.10.17 17:49, Yuriy Gorlichenko wrote:
>>     Hi use 5.0.1 with presence
>>     for TCP/UDP endpoints presence works PERFECT
>>     but for WS socket presence i see next (small cleaned log here
>>     with all described  bellow https://pastebin.com/8a77ggj0 ):
>>
>>     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
>>
>>     WS endpoint added to active_watchers table.
>>
>>     But when Subscribed endpoint makes for example some call and
>>     presence server sends PUBLISH i see: 
>>
>>     presence [presentity.c:426]:
>>     delete_presentity_if_dialog_id_exists(): Presentity already
>>     exists - deleting it
>>
>>     At the logs and then presence server doesn't send NOTIFY to WS
>>     endpoint
>>
>>     What is the issue of this? Can not understand why it happens. Can
>>     someone to help me understand this?
>>
>>     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
>>
>>
>>     _______________________________________________
>>     Kamailio (SER) - Users Mailing List
>>     sr-users at lists.kamailio.org <mailto:sr-users at lists.kamailio.org>
>>     https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>     <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>
>
>     -- 
>     Daniel-Constantin Mierla
>     www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>
>     Kamailio Advanced Training, Nov 13-15, 2017, in Berlin - www.asipto.com <http://www.asipto.com>
>     Kamailio World Conference - www.kamailioworld.com <http://www.kamailioworld.com>
>

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training, Nov 13-15, 2017, in Berlin - www.asipto.com
Kamailio World Conference - www.kamailioworld.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20171023/94c203f2/attachment.html>