<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
a quick look in the code seems to use all xml nodes. Mybe you can
add some debug messages in presence_dialoginfo/notify_body.c in
agregate_xmls() functions and see what is not executing.<br>
<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 29/04/14 20:39, Klaus Feichtinger
wrote:<br>
</div>
<blockquote cite="mid:535FF1EA.9040607@inode.at" type="cite">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Hi,<o:p></o:p>
<div class="moz-forward-container">
<div class="WordSection1">
<p class="MsoNormal">I have a question regarding the presence
+ presence_dialoginfo modules of Kamailio (tested with
version 3.2.x and 3.3.x).<o:p></o:p></p>
<p class="MsoNormal">My SIP user agents are generating SIP
PUBLISH requests for the event “dialog” and some of these
PUBLISH requests contain multiple dialog elements in the
message body. Kamailio is accepting content of these
messages and storing that information in the “presentity”
table of the corresponding DB. Taking a look into the
presentity table is confirming that both dialog elements of
the PUBLISH request are stored (as body content).</p>
<p class="MsoNormal">However, why does the SIP NOTIFY request,
which is sent to the "active_watchers" of this event,
contain only one of these dialog entries – even that the
modparam “force_single_dialog” is set to “0” or (for
comparison) unset (using default value "0")? Are multiple
dialog entries not / no longer supported by the Kamailio
“presence_dialoginfo” module? The README of this module
(through all versions incl. 4.1.x) is explaining the
opposite:<br>
<o:p>[...]<br>
This module by default does body aggregation. [...] e.g.
if the entity has multiple dialogs the pua_dialoginfo will
send multiple PUBLISH), the module will parse all the
received (and still valid, depending on the Expires header
in the PUBLISH request) XML documents and generate a
single XML document with multiple "dialog" elements.<br>
[...]<br>
<br>
</o:p></p>
<p class="MsoNormal">Exemplary content of a PUBLISH request
looks like this:<o:p></o:p><br>
</p>
<p class="MsoNormal">PUBLISH <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:sip:117104@172.31.60.87">sip:117104@172.31.60.87</a>
SIP/2.0<br>
Via: SIP/2.0/UDP
172.31.60.54:5060;rport;branch=z9hG4bK1118069411<br>
From: <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:sip:117104@172.31.60.87"><sip:117104@172.31.60.87></a>;tag=4024173055-29882384-1398422652889<br>
To: <a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:sip:117104@172.31.60.87"><sip:117104@172.31.60.87></a><br>
Call-ID: <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:4044398119-29882384-1398422652889@172.31.60.54">4044398119-29882384-1398422652889@172.31.60.54</a><br>
CSeq: 21 PUBLISH<br>
Max-Forwards: 70<br>
Content-Disposition: render;handling=required<br>
Expires: 600<br>
Event: dialog<br>
Content-Type: application/dialog-info+xml<br>
Content-Length: 1053<br>
<br>
<?xml version="1.0"?><br>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
version="00000000004" state="full" entity=<a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:sip:117104@172.31.60.87">"sip:117104@172.31.60.87"</a>><br>
<dialog id=<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:4044468572-29882384-1398422652855@172.31.60.54">"4044468572-29882384-1398422652855@172.31.60.54"</a>
call-id=<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:4044468572-29882384-1398422652855@172.31.60.54">"4044468572-29882384-1398422652855@172.31.60.54"</a>
direction="initiator"><br>
<state>terminated</state><br>
<remote><br>
<identity><a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:sip:1101015004@172.31.60.13">sip:1101015004@172.31.60.13</a></identity><br>
<target uri=<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:sip:1101015004@172.31.60.13">"sip:1101015004@172.31.60.13"</a>/><br>
</remote><br>
<local><br>
<identity><a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:sip:117104@172.31.60.87">sip:117104@172.31.60.87</a></identity><br>
<target uri=<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:sip:117104@172.31.60.87">"sip:117104@172.31.60.87"</a>/><br>
</local><br>
</dialog><br>
<dialog id=<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:2310720239-29882384-1398422648572@172.31.60.54">"2310720239-29882384-1398422648572@172.31.60.54"</a>
call-id=<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:2310720239-29882384-1398422648572@172.31.60.54">"2310720239-29882384-1398422648572@172.31.60.54"</a>
direction="initiator"><br>
<state>confirmed</state><br>
<remote><br>
<identity><a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:sip:117103@172.31.60.87">sip:117103@172.31.60.87</a></identity><br>
<target uri=<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:sip:117103@172.31.60.87">"sip:117103@172.31.60.87"</a>/><br>
</remote><br>
<local><br>
<identity><a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:sip:117104@172.31.60.87">sip:117104@172.31.60.87</a></identity><br>
<target uri=<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:sip:117104@172.31.60.87">"sip:117104@172.31.60.87"</a>/><br>
</local><br>
</dialog><br>
</dialog-info><br>
<br>
</p>
Exemplary content of the NOTIFY request looks like this:<o:p></o:p><br>
<br>
NOTIFY <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:sip:117101@172.31.60.54:5060">sip:117101@172.31.60.54:5060</a>
SIP/2.0<br>
Via: SIP/2.0/UDP
172.31.60.87;branch=z9hG4bKaeb3.066c77d0000000000000000000000000.0<br>
To: <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:sip:117101@172.31.60.87;tag=827287863-29882384-1398420840764">sip:117101@172.31.60.87;tag=827287863-29882384-1398420840764</a><br>
From: <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:sip:117104@172.31.60.87;tag=1f98950b7b1f526eff73c08f9ffc96bd-947a">sip:117104@172.31.60.87;tag=1f98950b7b1f526eff73c08f9ffc96bd-947a</a><br>
CSeq: 152 NOTIFY<br>
Call-ID: <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:1176683682-29882384-1398420840764@172.31.60.54">1176683682-29882384-1398420840764@172.31.60.54</a><br>
Content-Length: 600<br>
User-Agent: kamailio (3.2.4 (i386/linux))<br>
Max-Forwards: 70<br>
Event: dialog<br>
Contact: <a class="moz-txt-link-rfc2396E" href="sip:172.31.60.87:5060"><sip:172.31.60.87:5060></a><br>
Subscription-State: active;expires=1370<br>
Content-Type: application/dialog-info+xml<br>
<br>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
version="00000000004" state="full" entity=<a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:sip:117104@172.31.60.87">"sip:117104@172.31.60.87"</a>><br>
<dialog id=<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:4044468572-29882384-1398422652855@172.31.60.54">"4044468572-29882384-1398422652855@172.31.60.54"</a>
call-id=<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:4044468572-29882384-1398422652855@172.31.60.54">"4044468572-29882384-1398422652855@172.31.60.54"</a>
direction="initiator"><br>
<state>terminated</state><br>
<remote><br>
<identity><a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:sip:1101015004@172.31.60.13">sip:1101015004@172.31.60.13</a></identity><br>
<target uri=<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:sip:1101015004@172.31.60.13">"sip:1101015004@172.31.60.13"</a>/><br>
</remote><br>
<local><br>
<identity><a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:sip:117104@172.31.60.87">sip:117104@172.31.60.87</a></identity><br>
<target uri=<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:sip:117104@172.31.60.87">"sip:117104@172.31.60.87"</a>/><br>
</local><br>
</dialog><br>
</dialog-info><br>
<br>
In other words: it is not inserting all (stored) dialog
elements into the notification request. Please give me a hint,
what there could be wrong.<o:p></o:p> Maybe it is just a
misunderstanding of the description.....
<p class="MsoNormal">Br<br>
Klaus<o:p></o:p></p>
</div>
<br>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla - <a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a>
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a></pre>
</body>
</html>