Daniel-Constantin Mierla writes:
> I pushed a patch to master, can you try to see if works? If all ok, you
> can backport to 4.4 branch as well.
Thanks, the error message is now gone. Backport done.
-- Juha
___
sr-dev mailing list
sr-dev@lists.sip-ro
Hello,
I pushed a patch to master, can you try to see if works? If all ok, you
can backport to 4.4 branch as well.
It was indeed a regression added by a commit trying to fix a race for
dialog related events.
Cheers,
Daniel
On 16/09/16 21:51, Juha Heinanen wrote:
> Juha Heinanen writes:
>
>> St
Juha Heinanen writes:
> Still have not figured out why xml document parsing.
"failed to parse xml document" error comes from this call in handle_publish:
/* querry the database and update or insert */
if(update_presentity(msg, presentity, &body, etag_gen, &sent_reply,
sphere) <0
Juha Heinanen writes:
> Sep 16 21:43:09 lohi /usr/bin/pres-serv[29250]: INFO: presence
> [publish.c:305]: handle_publish(): * event name/content_type/type
> 'message-summary'/'application/simple-message-summary'/2
>
> Otherwise OK, but type does not match event name:
Type 2 means PUBL_TYPE
I added syslog message to handle_publish():
/* search event in the list */
event= search_event((event_t*)msg->event->parsed);
if(event== NULL)
{
goto unsupported_event;
}
LM_INFO("* event name/content_type/type '%.*s'/'%.*s'/%d\n"
Enclosed is pcapng of the publish request that presence server calls
handle_publish() on and produces "failed to parse xml document" error
message.
-- Juha
publish.pcapng
Description: publish
___
sr-dev mailing list
sr-dev@lists.sip-router.org
http://
Juha Heinanen writes:
> I don't remember making any changes to the pua_publish request since
> 4.5, where it works.
Typo: 4.5 -> 4.4.
-- Juha
___
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-d
Using latest master, I'm getting error
Sep 16 20:16:36 lohi /usr/bin/pres-serv[1744]: ERROR: presence
[presentity.c:319]: parse_dialog_state_from_body(): failed to parse xml
document 'Messages-Waiting: no#015#012Message-Account:
sip:j...@vm.test.tutpro.com#015#012Voice-Message: 0/0 (0/0)#015#01