No subject
Thu Feb 3 19:02:41 CET 2011
...
DLG_STATE_CONFIRMED 4 /*!< confirmed dialog */
...
DLG_EVENT_REQPRACK 5 /*!< PRACK request */
...
I understand it means we are receiving a PRACK in a confirmed dialog (ACK
received), doesn't it? I guess it can be due either to an error of the SIP
stack of the caller side or this PRACK is a rtx due to networking issues
(not probable, I think).
Thanks a lot,
regards
Ant=F3n
2011/3/4 Daniel-Constantin Mierla <miconda at gmail.com>
> Hello,
>
>
> On 3/3/11 10:19 AM, Anton Roman wrote:
>
> Hello,
>
> thanks for your quick reply, my answer is inline.
>
> 2011/3/2 Daniel-Constantin Mierla <miconda at gmail.com>
>
>> Hello,
>>
>> looks like related to the callbacks for dialog module. Are you loading
>> other modules that require dialog module?
>>
>
> we are using some features of dialog module such as ending dialogs after =
a
> timeout period, and we are using engage_mediaproxy() function, as well. I=
t's
> an old configuration we had to put in production with no time enough to
> test. Do you recommend not to use dialog module if not strictly required?
>
>
> usage of dialog module was always safe and working great for me. But I us=
e
> it mostly alone, never with mediaproxy module, just with pua_dialoginfo
> module in some cases. From the logs, the crash was related to the callbac=
k
> system exported by dialog module for the other modules willing to hook in=
to
> dialog, it is why I asked about the other modules to be sure there is at
> list one binding to dialog.
>
> So, like with other modules, if there is a problem discovered there, it i=
s
> important that we fix it - this is a module used a lot by many. Therefore
> usage is encouraged when needed :-)
>
> Cheers,
> Daniel
>
>
> --
> Daniel-Constantin Mierlahttp://www.asipto.com
>
>
--00248c7118c9ce77d9049dbc5184
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Ok,<br><br>=A0I updated the code in the server. I'm testing the changes=
on Tuesday and I'll send feedback to the list. <br><br>We found dialog=
module very useful because of the information and functionality it provide=
s. For example, we are using its exported function dlg_end_dlg to cleanly e=
nd all the active calls when stopping Kamailio is required for maintenance =
reasons. We are also using the dlg_bridge function to implement click-to-di=
al applications and it works fine.=A0 =A0 =A0 <br>
<br><div>On the other hand, in the logs of the server we detected the unref=
erence problem, we got the logs showed below quite often. I don 't know=
if it can be related to the unreference problem. Since it has=20
a CRITICAL log level I'm not sure if this is so because it can mean a r=
eal problem or Kamailio can safety deal with it: =A0 <br></div>
<div><br></div><div><font face=3D"'courier new', monospace">Mar=A0 =
2 17:21:30 kamailio2 /usr/local/sbin/kamailio[32153]: CRITICAL: dialog [dlg=
_hash.c:615]: bogus event 5 in state 4 for dlg <b>0x7f2d0a3d30e0</b> [306:1=
818049706] with clid '<a href=3D"mailto:92515995-3508071667-342415 at usmi=
ap1etx02.mydomain.com">92515995-3508071667-342415 at usmiap1etx02.mydomain.com=
</a>' and tags '3508071667-342428' '7A242CC-0'<br>
Mar=A0 2 17:21:30 kamailio2 /usr/local/sbin/kamailio[32153]: DEBUG: dialog =
[dlg_hash.c:770]: dialog <b>0x7f2d0a3d30e0</b> changed from state 4 to stat=
e 4, due event 5<br>Mar=A0 2 17:21:30 kamailio2 /usr/local/sbin/kamailio[32=
153]: DEBUG: tm [t_lookup.c:1379]: DEBUG: t_newtran: msg id=3D4077 , global=
msg id=3D4076 , T on entrance=3D(nil)<br>
Mar=A0 2 17:21:30 kamailio2 /usr/local/sbin/kamailio[32153]: DEBUG: tm [t_l=
ookup.c:528]: t_lookup_request: start searching: hash=3D356, isACK=3D0<br>M=
ar=A0 2 17:21:30 kamailio2 /usr/local/sbin/kamailio[32153]: DEBUG: tm [t_lo=
okup.c:470]: DEBUG: RFC3261 transaction matched, tid=3D3178c7ec929daf0e4ade=
2b303de82a20<br>
Mar=A0 2 17:21:30 kamailio2 /usr/local/sbin/kamailio[32153]: DEBUG: tm [t_l=
ookup.c:728]: DEBUG: t_lookup_request: transaction found (T=3D0x7f2d0a82bca=
0)<br>Mar=A0 2 17:21:30 kamailio2 /usr/local/sbin/kamailio[32153]: DEBUG: t=
m [t_reply.c:1430]: DEBUG: reply retransmitted. buf=3D0x7f2d2eff4160: SIP/2=
.0 5..., shmem=3D0x7f2d0a72cb90: SIP/2.0 5<br>
Mar=A0 2 17:21:30 kamailio2 /usr/local/sbin/kamailio[32153]: DEBUG: dialog =
[dlg_hash.c:599]: unref dlg <b>0x7f2d0a3d30e0</b> with 1 -> 3<br>Mar=A0 =
2 17:21:30 kamailio2 /usr/local/sbin/kamailio[32153]: DEBUG: <core> [=
usr_avp.c:646]: DEBUG:destroy_avp_list: destroying list (nil)<br>
Mar=A0 2 17:21:30 kamailio2 /usr/local/sbin/kamailio[32153]: DEBUG: <cor=
e> [usr_avp.c:646]: <br></font><br><div><font face=3D"'courier new&#=
39;, monospace"><br><span style=3D"font-family: arial,helvetica,sans-serif;=
">From dlg_hash.h</span><br>
<span style=3D"font-family: courier new,monospace;">...</span><br style=3D"=
font-family: courier new,monospace;"><span style=3D"font-family: courier ne=
w,monospace;"></span></font><span style=3D"font-family: courier new,monospa=
ce;">DLG_STATE_CONFIRMED=A0=A0=A0 4 /*!< confirmed dialog */</span><font=
face=3D"'courier new', monospace"><span style=3D"font-family: cour=
ier new,monospace;"></span><br style=3D"font-family: courier new,monospace;=
">
<span style=3D"font-family: courier new,monospace;">...</span><br style=3D"=
font-family: courier new,monospace;"></font></div>
</div><span style=3D"font-family: courier new,monospace;"></span><font face=
=3D"'courier new', monospace"><span style=3D"font-family: courier n=
ew,monospace;">DLG_EVENT_REQPRACK=A0=A0=A0=A0 5 /*!< PRACK request */</s=
pan></font><br style=3D"font-family: courier new,monospace;">
<span style=3D"font-family: courier new,monospace;">...</span><br><br><div>=
I understand it means we are receiving a PRACK
in a confirmed dialog (ACK received), doesn't it? I guess it can be du=
e either to an error of the SIP stack of the caller side or this PRACK is a=
rtx due to networking issues (not probable, I think). <br>
</div><br>Thanks a lot,<br>regards<br><br>Ant=F3n<br>=A0 =A0 <br><br><div c=
lass=3D"gmail_quote">2011/3/4 Daniel-Constantin Mierla <span dir=3D"ltr">&l=
t;<a href=3D"mailto:miconda at gmail.com" target=3D"_blank">miconda at gmail.com<=
/a>></span><br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
=20
=20
=20
<div bgcolor=3D"#ffffff" text=3D"#000000">
Hello,<div><br>
<br>
On 3/3/11 10:19 AM, Anton Roman wrote:
<blockquote type=3D"cite">Hello,
<div><br>
</div>
<div>thanks for your quick reply, my answer is inline.<br>
<br>
<div class=3D"gmail_quote">2011/3/2 Daniel-Constantin Mierla <span =
dir=3D"ltr"><<a href=3D"mailto:miconda at gmail.com" target=3D"_blank">mico=
nda at gmail.com</a>></span><br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.=
8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div bgcolor=3D"#ffffff" text=3D"#000000"> Hello,<br>
<br>
looks like related to the callbacks for dialog module. Are
you loading other modules that require dialog module?<br>
</div>
</blockquote>
<div>=A0</div>
<div>we are using some features of dialog module such as
ending dialogs after a timeout period, and we are using
engage_mediaproxy() function, as well. It's an old
configuration we had to put in production with no =A0time
enough to test. Do you recommend not to use dialog module if
not strictly required?</div>
</div>
</div>
</blockquote>
<br></div>
usage of dialog module was always safe and working great for me. But
I use it mostly alone, never with mediaproxy module, just with
pua_dialoginfo module in some cases. From the logs, the crash was
related to the callback system exported by dialog module for the
other modules willing to hook into dialog, it is why I asked about
the other modules to be sure there is at list one binding to dialog.<br=
>
<br>
So, like with other modules, if there is a problem discovered there,
it is important that we fix it - this is a module used a lot by
many. Therefore usage is encouraged when needed :-)<br>
<br>
Cheers,<br><font color=3D"#888888">
Daniel</font><div><br>
<br>
<pre cols=3D"72">--=20
Daniel-Constantin Mierla
<a href=3D"http://www.asipto.com" target=3D"_blank">http://www.asipto.com</=
a></pre>
</div></div>
</blockquote></div><br>
--00248c7118c9ce77d9049dbc5184--
More information about the sr-users
mailing list