log_next_state_dlg bogus events

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

log_next_state_dlg bogus events

Jan D.
I see some CRITICAL logs in my opensips.log with log_next_state_dlg bogus events. The system is running on debian testing with opensips & opensips-mysql-module from apt with version 1.7.2-1-87691 (newest).

This is the output of this morning till now:

Mar  8 09:22:14 sip2 /usr/sbin/opensips[6883]: CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg 0x7ff4fb2c1ee0 [1210:909918452] with clid 'M2IxNzQ5MTEwM2YzNjM5ZmYzZmI0ODk4MGJiZWNlYzU.' and tags '998c14f2' '15B5F1C4-C96'
Mar  8 09:23:21 sip2 /usr/sbin/opensips[6886]: CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg 0x7ff4fb296938 [2552:1087710093] with clid 'MzkwZmIxYWM2OTVhZDNmOWEzNzcyNDRmZjMxN2NhMmM.' and tags 'f58b3f2d' '15B65E8C-2401'
Mar  8 09:31:02 sip2 /usr/sbin/opensips[6893]: CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg 0x7ff4fb2c5bd8 [3074:1511536125] with clid 'NDczNDBjOTA1YmYyOThjMjFmNDY3M2UzYjhiYjA4NzY.' and tags '507f42e7' '15BD7044-218C'
Mar  8 09:32:11 sip2 /usr/sbin/opensips[6885]: CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg 0x7ff4fb2c1ee0 [3336:319284968] with clid 'ZjQ3ZjIxNDk0ZTZiZTQ4ZTMxMzI5M2FmNmYzN2E3Y2U.' and tags '2e0890ab' '15BE7F74-23EB'
Mar  8 09:32:33 sip2 /usr/sbin/opensips[6893]: CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg 0x7ff4fb29a620 [634:481537164] with clid 'NmFhMGM4MjEzNTcyNGMyMjIxZWFiZjgzYzBiYTNjMTA.' and tags '40a3b947' '15BF0D48-1F1F'
Mar  8 09:39:20 sip2 /usr/sbin/opensips[6887]: CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg 0x7ff4fb2e7770 [1270:281564955] with clid 'MTI1YjI3YTM4NzU4ZWQ2ODM2NTdkN2IwODgwNmJiMjg.' and tags 'df5495ef' '15C49C0C-2149'
Mar  8 09:50:15 sip2 /usr/sbin/opensips[6894]: CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg 0x7ff4fb2d2e10 [2311:533537517] with clid 'ODVlYjBlZGViYmI3YzI5ZTNlZjlkYTViOTI1MWQyMDY.' and tags '59eec92c' '15CF906C-2269'
Mar  8 10:12:19 sip2 /usr/sbin/opensips[6896]: CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg 0x7ff4fb2cf9c8 [3647:1739481573] with clid 'Y2U3NjdmZDNjMWI2Mjc4YTM5ODUxMjZlYWNiZmU3ZmU.' and tags '1f1a1a25' '15E313A0-FF1'
Mar  8 10:19:58 sip2 /usr/sbin/opensips[6893]: CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg 0x7ff4fb2e7770 [3335:844420084] with clid 'NTY2NjhiMjFlODY1MWU4YjkzNzdlODExZGU3ZjhkOGI.' and tags 'dd33eb79' '15EA4930-12CD'
Mar  8 10:24:20 sip2 /usr/sbin/opensips[6898]: CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg 0x7ff4fb29d658 [3981:1714382667] with clid 'NzlhNTBiOWIwMzZhMjM0NjE4YjUyMWVjZjJhZjcyNTg.' and tags 'bf1672ad' '15ED80EC-2113'

Is this a problem / should i be worried?

If more information is needed (i can imagine) let me know what to add to this post.

Gr.

Jan
Reply | Threaded
Open this post in threaded view
|

Re: log_next_state_dlg bogus events

Vlad Paiu
Hello,

It seems one of your endpoints is sending BYEs while the dialog is still
in early state.
OpenSIPS currently ignores such requests and does not end the dialog,
and instead outputs those CRITICAL messages to the logging facility.

Regards,

Vlad Paiu
OpenSIPS Developer
http://www.opensips-solutions.com


On 03/08/2012 11:31 AM, Jan D. wrote:

> I see some CRITICAL logs in my opensips.log with log_next_state_dlg bogus
> events. The system is running on debian testing with opensips&
> opensips-mysql-module from apt with version 1.7.2-1-87691 (newest).
>
> This is the output of this morning till now:
>
> Mar  8 09:22:14 sip2 /usr/sbin/opensips[6883]:
> CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg
> 0x7ff4fb2c1ee0 [1210:909918452] with clid
> 'M2IxNzQ5MTEwM2YzNjM5ZmYzZmI0ODk4MGJiZWNlYzU.' and tags '998c14f2'
> '15B5F1C4-C96'
> Mar  8 09:23:21 sip2 /usr/sbin/opensips[6886]:
> CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg
> 0x7ff4fb296938 [2552:1087710093] with clid
> 'MzkwZmIxYWM2OTVhZDNmOWEzNzcyNDRmZjMxN2NhMmM.' and tags 'f58b3f2d'
> '15B65E8C-2401'
> Mar  8 09:31:02 sip2 /usr/sbin/opensips[6893]:
> CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg
> 0x7ff4fb2c5bd8 [3074:1511536125] with clid
> 'NDczNDBjOTA1YmYyOThjMjFmNDY3M2UzYjhiYjA4NzY.' and tags '507f42e7'
> '15BD7044-218C'
> Mar  8 09:32:11 sip2 /usr/sbin/opensips[6885]:
> CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg
> 0x7ff4fb2c1ee0 [3336:319284968] with clid
> 'ZjQ3ZjIxNDk0ZTZiZTQ4ZTMxMzI5M2FmNmYzN2E3Y2U.' and tags '2e0890ab'
> '15BE7F74-23EB'
> Mar  8 09:32:33 sip2 /usr/sbin/opensips[6893]:
> CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg
> 0x7ff4fb29a620 [634:481537164] with clid
> 'NmFhMGM4MjEzNTcyNGMyMjIxZWFiZjgzYzBiYTNjMTA.' and tags '40a3b947'
> '15BF0D48-1F1F'
> Mar  8 09:39:20 sip2 /usr/sbin/opensips[6887]:
> CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg
> 0x7ff4fb2e7770 [1270:281564955] with clid
> 'MTI1YjI3YTM4NzU4ZWQ2ODM2NTdkN2IwODgwNmJiMjg.' and tags 'df5495ef'
> '15C49C0C-2149'
> Mar  8 09:50:15 sip2 /usr/sbin/opensips[6894]:
> CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg
> 0x7ff4fb2d2e10 [2311:533537517] with clid
> 'ODVlYjBlZGViYmI3YzI5ZTNlZjlkYTViOTI1MWQyMDY.' and tags '59eec92c'
> '15CF906C-2269'
> Mar  8 10:12:19 sip2 /usr/sbin/opensips[6896]:
> CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg
> 0x7ff4fb2cf9c8 [3647:1739481573] with clid
> 'Y2U3NjdmZDNjMWI2Mjc4YTM5ODUxMjZlYWNiZmU3ZmU.' and tags '1f1a1a25'
> '15E313A0-FF1'
> Mar  8 10:19:58 sip2 /usr/sbin/opensips[6893]:
> CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg
> 0x7ff4fb2e7770 [3335:844420084] with clid
> 'NTY2NjhiMjFlODY1MWU4YjkzNzdlODExZGU3ZjhkOGI.' and tags 'dd33eb79'
> '15EA4930-12CD'
> Mar  8 10:24:20 sip2 /usr/sbin/opensips[6898]:
> CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg
> 0x7ff4fb29d658 [3981:1714382667] with clid
> 'NzlhNTBiOWIwMzZhMjM0NjE4YjUyMWVjZjJhZjcyNTg.' and tags 'bf1672ad'
> '15ED80EC-2113'
>
> Is this a problem / should i be worried?
>
> If more information is needed (i can imagine) let me know what to add to
> this post.
>
> Gr.
>
> Jan
>
> --
> View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/log-next-state-dlg-bogus-events-tp7354379p7354379.html
> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: log_next_state_dlg bogus events

Jan D.
Vlad,

Your right, it is a X-lite client behind a buggy nat router (speedtouch).

Can I do some scripting to get rid of the critical logging and give a nice response?

Maybe with the dlg_flag, or something like ie.:

if(is_method("BYE") && ...)
{
        xlog("L_INFO", " INFO : 501 BYE in dialog state x\n");
        sl_send_reply("501", "Method Not Supported Here");
        exit;
}

Gr.

Jan
Reply | Threaded
Open this post in threaded view
|

Re: log_next_state_dlg bogus events

Vlad Paiu
Hello,

Please check the $DLG_status pvar at [1] . Basically, do
     if (is_method("BYE") && $DLG_status < 3) {
         sl_send_reply("501", "Method Not Supported Here");
     }

[1] http://www.opensips.org/html/docs/modules/1.7.x/dialog.html#id295284

Regards,

Vlad Paiu
OpenSIPS Developer
http://www.opensips-solutions.com


On 03/08/2012 04:07 PM, Jan D. wrote:

> Vlad,
>
> Your right, it is a X-lite client behind a buggy nat router (speedtouch).
>
> Can I do some scripting to get rid of the critical logging and give a nice
> response?
>
> Maybe with the dlg_flag, or something like ie.:
>
> if(is_method("BYE")&&  ...)
> {
> xlog("L_INFO", " INFO : 501 BYE in dialog state x\n");
> sl_send_reply("501", "Method Not Supported Here");
> exit;
> }
>
> Gr.
>
> Jan
>
> --
> View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/log-next-state-dlg-bogus-events-tp7354379p7354979.html
> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: log_next_state_dlg bogus events

Jan D.
Vlad,

Still a little question: The dialog docs tell me i can check the dialog status after doing a loose route:

1.9.2. $DLG_status : Returns the status of the dialog corresponding to the processed sequential request. This PV will be available only for sequential requests, after doing loose_route().

In my script i moved the check into my loose route like this:

if(loose_route())
{
                xlog("L_INFO", " INFO : route 0 LOOSE_ROUTE\n");

                if (is_method("BYE") && $DLG_status < 3)
                {
                                xlog("L_ERROR", " INFO : 501 BYE with $DLG_status not supported here\n");
                                sl_send_reply("501", "Method Not Supported Here");
                                exit;
                }
                else
                {
                                xlog("L_ERROR", " INFO : BYE with $DLG_status OK\n");
                }
}

Now i still get an error in my log files:
Mar 14 10:55:52 /usr/sbin/opensips[14227]: ********** ROUTE 00 ********** BYE 89.146.10.180
Mar 14 10:55:52 /usr/sbin/opensips[14227]: CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg 0x7f800574c688 [1887:925512554] with clid 'MGJjY2RmNmMzNmRmYTdhZmYxMTFkMTdjM2ZiMGU1Y2I.' and tags '6b07d36d' '34F196CC-2329'
Mar 14 10:55:52 /usr/sbin/opensips[14227]:  INFO : route 0 LOOSE_ROUTE
Mar 14 10:55:52 /usr/sbin/opensips[14227]:  INFO : 501 BYE with 2 not supported here

What can i do to get rid of the critical error?

FYI: When calling out with X-lite (4.1 63214) and canceling the request after some time, X-Lite generates a BYE and after this a CANCEL, quite strange...


Gr.

Jan
Reply | Threaded
Open this post in threaded view
|

Re: log_next_state_dlg bogus events

Bogdan-Andrei Iancu-2
Hi Jan,

Actually this is a hen and the egg problem : in order to get access to
DLG_status, the request must be matched against the dialog (and matching
is done inside this loose_route() ) ; on the other hand, the error you
see is generated during the matching itself :)

I see no way to get rid of the error without chancing the actual code.

Regards,
Bogdan

On 03/14/2012 12:07 PM, Jan D. wrote:

> Vlad,
>
> Still a little question: The dialog docs tell me i can check the dialog
> status after doing a loose route:
>
> 1.9.2. $DLG_status : Returns the status of the dialog corresponding to the
> processed sequential request. This PV will be available only for sequential
> requests, after doing loose_route().
>
> In my script i moved the check into my loose route like this:
>
> if(loose_route())
> {
> xlog("L_INFO", " INFO : route 0 LOOSE_ROUTE\n");
>
> if (is_method("BYE")&&  $DLG_status<  3)
> {
> xlog("L_ERROR", " INFO : 501 BYE with $DLG_status not supported
> here\n");
> sl_send_reply("501", "Method Not Supported Here");
> exit;
> }
> else
> {
> xlog("L_ERROR", " INFO : BYE with $DLG_status OK\n");
> }
> }
>
> Now i still get an error in my log files:
> Mar 14 10:55:52 /usr/sbin/opensips[14227]: ********** ROUTE 00 **********
> BYE 89.146.10.180
> Mar 14 10:55:52 /usr/sbin/opensips[14227]:
> CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg
> 0x7f800574c688 [1887:925512554] with clid
> 'MGJjY2RmNmMzNmRmYTdhZmYxMTFkMTdjM2ZiMGU1Y2I.' and tags '6b07d36d'
> '34F196CC-2329'
> Mar 14 10:55:52 /usr/sbin/opensips[14227]:  INFO : route 0 LOOSE_ROUTE
> Mar 14 10:55:52 /usr/sbin/opensips[14227]:  INFO : 501 BYE with 2 not
> supported here
>
> What can i do to get rid of the critical error?
>
> FYI: When calling out with X-lite (4.1 63214) and canceling the request
> after some time, X-Lite generates a BYE and after this a CANCEL, quite
> strange...
>
>
> Gr.
>
> Jan
>
>
> --
> View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/log-next-state-dlg-bogus-events-tp7354379p7371331.html
> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: log_next_state_dlg bogus events

Max Mühlbronner
I was worried about the same thing, until i noticed the critical error
just means a client sends a bye (event 7) for a dialog in
progress.(state 2) when he should send a CANCEL instead.
So there is nothing to worry about, right!?


Best Regards


Max M.

On 03/14/2012 01:20 PM, Bogdan-Andrei Iancu wrote:

> Hi Jan,
>
> Actually this is a hen and the egg problem : in order to get access to
> DLG_status, the request must be matched against the dialog (and
> matching is done inside this loose_route() ) ; on the other hand, the
> error you see is generated during the matching itself :)
>
> I see no way to get rid of the error without chancing the actual code.
>
> Regards,
> Bogdan
>
> On 03/14/2012 12:07 PM, Jan D. wrote:
>> Vlad,
>>
>> Still a little question: The dialog docs tell me i can check the dialog
>> status after doing a loose route:
>>
>> 1.9.2. $DLG_status : Returns the status of the dialog corresponding
>> to the
>> processed sequential request. This PV will be available only for
>> sequential
>> requests, after doing loose_route().
>>
>> In my script i moved the check into my loose route like this:
>>
>> if(loose_route())
>> {
>>         xlog("L_INFO", " INFO : route 0 LOOSE_ROUTE\n");
>>
>>         if (is_method("BYE")&&  $DLG_status<  3)
>>         {
>>                 xlog("L_ERROR", " INFO : 501 BYE with $DLG_status not
>> supported
>> here\n");
>>                 sl_send_reply("501", "Method Not Supported Here");
>>                 exit;
>>         }
>>         else
>>         {
>>                 xlog("L_ERROR", " INFO : BYE with $DLG_status OK\n");
>>         }
>> }
>>
>> Now i still get an error in my log files:
>> Mar 14 10:55:52 /usr/sbin/opensips[14227]: ********** ROUTE 00
>> **********
>> BYE 89.146.10.180
>> Mar 14 10:55:52 /usr/sbin/opensips[14227]:
>> CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg
>> 0x7f800574c688 [1887:925512554] with clid
>> 'MGJjY2RmNmMzNmRmYTdhZmYxMTFkMTdjM2ZiMGU1Y2I.' and tags '6b07d36d'
>> '34F196CC-2329'
>> Mar 14 10:55:52 /usr/sbin/opensips[14227]:  INFO : route 0 LOOSE_ROUTE
>> Mar 14 10:55:52 /usr/sbin/opensips[14227]:  INFO : 501 BYE with 2 not
>> supported here
>>
>> What can i do to get rid of the critical error?
>>
>> FYI: When calling out with X-lite (4.1 63214) and canceling the request
>> after some time, X-Lite generates a BYE and after this a CANCEL, quite
>> strange...
>>
>>
>> Gr.
>>
>> Jan
>>
>>
>> --
>> View this message in context:
>> http://opensips-open-sip-server.1449251.n2.nabble.com/log-next-state-dlg-bogus-events-tp7354379p7371331.html
>> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>>
>> _______________________________________________
>> Users mailing list
>> [hidden email]
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
>


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: log_next_state_dlg bogus events

Jan D.
In reply to this post by Bogdan-Andrei Iancu-2
Bogdan,

Thanks for the quick reply. I understand my programming at least is OK. The critical log entries are just inconvenient when reading the log files. Returning a 501 works for x-lite, it then comes back with a Cancel. If not returning a 501 strange things happen (INVITE to failover etc).

I only see the problem only with x-lite clients. Do you know that sending a BYE before a Cancel is 'wrong'? If so I can open a bug report with X-lite.

Gr.

Jan
Reply | Threaded
Open this post in threaded view
|

Re: log_next_state_dlg bogus events

Bogdan-Andrei Iancu-2
In reply to this post by Max Mühlbronner
Hi Max,

Noting to worry about - actually, the RFC says that you may send a BYE
instead of CANCEL (one of the SIP's bullshits), but from a proxy
perspective, nothing changes - the proxy has to route the BYE any other
BYE and if it gets to the callee, it is up to callee to cancel the call
(if supporting BYE as CANCEL);

Probably what we should do is to simply make OpenSIPS silent about this
case - anyhow it has nothing to do (from dialog state transition point
of view).

Regards,
Bogdan

On 03/14/2012 03:20 PM, Max Mühlbronner wrote:

> I was worried about the same thing, until i noticed the critical error
> just means a client sends a bye (event 7) for a dialog in
> progress.(state 2) when he should send a CANCEL instead.
> So there is nothing to worry about, right!?
>
>
> Best Regards
>
>
> Max M.
>
> On 03/14/2012 01:20 PM, Bogdan-Andrei Iancu wrote:
>> Hi Jan,
>>
>> Actually this is a hen and the egg problem : in order to get access
>> to DLG_status, the request must be matched against the dialog (and
>> matching is done inside this loose_route() ) ; on the other hand, the
>> error you see is generated during the matching itself :)
>>
>> I see no way to get rid of the error without chancing the actual code.
>>
>> Regards,
>> Bogdan
>>
>> On 03/14/2012 12:07 PM, Jan D. wrote:
>>> Vlad,
>>>
>>> Still a little question: The dialog docs tell me i can check the dialog
>>> status after doing a loose route:
>>>
>>> 1.9.2. $DLG_status : Returns the status of the dialog corresponding
>>> to the
>>> processed sequential request. This PV will be available only for
>>> sequential
>>> requests, after doing loose_route().
>>>
>>> In my script i moved the check into my loose route like this:
>>>
>>> if(loose_route())
>>> {
>>>         xlog("L_INFO", " INFO : route 0 LOOSE_ROUTE\n");
>>>
>>>         if (is_method("BYE")&&  $DLG_status<  3)
>>>         {
>>>                 xlog("L_ERROR", " INFO : 501 BYE with $DLG_status
>>> not supported
>>> here\n");
>>>                 sl_send_reply("501", "Method Not Supported Here");
>>>                 exit;
>>>         }
>>>         else
>>>         {
>>>                 xlog("L_ERROR", " INFO : BYE with $DLG_status OK\n");
>>>         }
>>> }
>>>
>>> Now i still get an error in my log files:
>>> Mar 14 10:55:52 /usr/sbin/opensips[14227]: ********** ROUTE 00
>>> **********
>>> BYE 89.146.10.180
>>> Mar 14 10:55:52 /usr/sbin/opensips[14227]:
>>> CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg
>>> 0x7f800574c688 [1887:925512554] with clid
>>> 'MGJjY2RmNmMzNmRmYTdhZmYxMTFkMTdjM2ZiMGU1Y2I.' and tags '6b07d36d'
>>> '34F196CC-2329'
>>> Mar 14 10:55:52 /usr/sbin/opensips[14227]:  INFO : route 0 LOOSE_ROUTE
>>> Mar 14 10:55:52 /usr/sbin/opensips[14227]:  INFO : 501 BYE with 2 not
>>> supported here
>>>
>>> What can i do to get rid of the critical error?
>>>
>>> FYI: When calling out with X-lite (4.1 63214) and canceling the request
>>> after some time, X-Lite generates a BYE and after this a CANCEL, quite
>>> strange...
>>>
>>>
>>> Gr.
>>>
>>> Jan
>>>
>>>
>>> --
>>> View this message in context:
>>> http://opensips-open-sip-server.1449251.n2.nabble.com/log-next-state-dlg-bogus-events-tp7354379p7371331.html
>>> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>>>
>>> _______________________________________________
>>> Users mailing list
>>> [hidden email]
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>
>>
>
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: log_next_state_dlg bogus events

Bogdan-Andrei Iancu-2
In reply to this post by Jan D.
Hi Jan,

I was just saying to Max (see the other email) that BYE instead CANCEL
seems to be according to RFC; and as the dialog module has nothing to do
on a BYE in early state, we could simply remove the error log and let
the callee to decide if the BYE should be accepted or not.

Regards,
Bogdan

On 03/14/2012 03:24 PM, Jan D. wrote:

> Bogdan,
>
> Thanks for the quick reply. I understand my programming at least is OK. The
> critical log entries are just inconvenient when reading the log files.
> Returning a 501 works for x-lite, it then comes back with a Cancel. If not
> returning a 501 strange things happen (INVITE to failover etc).
>
> I only see the problem only with x-lite clients. Do you know that sending a
> BYE before a Cancel is 'wrong'? If so I can open a bug report with X-lite.
>
> Gr.
>
> Jan
>
>
> --
> View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/log-next-state-dlg-bogus-events-tp7354379p7371762.html
> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: log_next_state_dlg bogus events

Flavio Goncalves
Hi Jan, 

I had the same issue recently, I have captured some packets at the same exact time of the messages. In some cases, if your system becomes unresponsive for a few seconds, CANCELs were not relayed by the proxy (actually I saw several requests without any reply for some time). Then, the other side sent a BYE (some sort of timeout I believe) in early state because it didn't receive the CANCEL request. This was happening because of a MYSQL stored procedure (billing) closing records in a large database with millions of acc records, mysqld was going to 100% and blocking the system. I stopped the stored procedure and the system stopped presenting these messages. So, maybe this is something to worry about. I hope you don't have the same issue, but I believe it is worth to check. 

Flavio E. Goncalves
 



On Wed, Mar 14, 2012 at 3:08 PM, Bogdan-Andrei Iancu <[hidden email]> wrote:
Hi Jan,

I was just saying to Max (see the other email) that BYE instead CANCEL seems to be according to RFC; and as the dialog module has nothing to do on a BYE in early state, we could simply remove the error log and let the callee to decide if the BYE should be accepted or not.

Regards,
Bogdan


On 03/14/2012 03:24 PM, Jan D. wrote:
Bogdan,

Thanks for the quick reply. I understand my programming at least is OK. The
critical log entries are just inconvenient when reading the log files.
Returning a 501 works for x-lite, it then comes back with a Cancel. If not
returning a 501 strange things happen (INVITE to failover etc).

I only see the problem only with x-lite clients. Do you know that sending a
BYE before a Cancel is 'wrong'? If so I can open a bug report with X-lite.

Gr.

Jan


--
View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/log-next-state-dlg-bogus-events-tp7354379p7371762.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: log_next_state_dlg bogus events

Vlad Paiu
Hi Flavio,

According to the RFC, the callee side must not send a BYE for a dialog in early state.
I have just edited the dialog state machine to no longer log BYEs from the caller's side for dialogs in early state as bogus.

Regards,
Vlad Paiu
OpenSIPS Developer
http://www.opensips-solutions.com 

On 03/20/2012 11:46 PM, Flavio Goncalves wrote:
Hi Jan, 

I had the same issue recently, I have captured some packets at the same exact time of the messages. In some cases, if your system becomes unresponsive for a few seconds, CANCELs were not relayed by the proxy (actually I saw several requests without any reply for some time). Then, the other side sent a BYE (some sort of timeout I believe) in early state because it didn't receive the CANCEL request. This was happening because of a MYSQL stored procedure (billing) closing records in a large database with millions of acc records, mysqld was going to 100% and blocking the system. I stopped the stored procedure and the system stopped presenting these messages. So, maybe this is something to worry about. I hope you don't have the same issue, but I believe it is worth to check. 

Flavio E. Goncalves
 



On Wed, Mar 14, 2012 at 3:08 PM, Bogdan-Andrei Iancu <[hidden email]> wrote:
Hi Jan,

I was just saying to Max (see the other email) that BYE instead CANCEL seems to be according to RFC; and as the dialog module has nothing to do on a BYE in early state, we could simply remove the error log and let the callee to decide if the BYE should be accepted or not.

Regards,
Bogdan


On 03/14/2012 03:24 PM, Jan D. wrote:
Bogdan,

Thanks for the quick reply. I understand my programming at least is OK. The
critical log entries are just inconvenient when reading the log files.
Returning a 501 works for x-lite, it then comes back with a Cancel. If not
returning a 501 strange things happen (INVITE to failover etc).

I only see the problem only with x-lite clients. Do you know that sending a
BYE before a Cancel is 'wrong'? If so I can open a bug report with X-lite.

Gr.

Jan


--
View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/log-next-state-dlg-bogus-events-tp7354379p7371762.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________ Users mailing list [hidden email] http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: log_next_state_dlg bogus events

Jan D.
Dear Vlad,

I still see al lot of 'CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2' errors in the log files.

The machine is running debian 1.7.2-1-89461.

Apr 19 15:54:47 /usr/sbin/opensips[20986]: CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg 0x7f787c39ce08 [2555:974702198] with clid 'N2RmZWZlZGM4ZjU3NDBiMmMzZGJmNDM0MDMxMWYxYmU.' and tags 'e4c7250e' 'EF300F18-910'

I understood the dialog state machine wase edited and should not log this events anymore?

Gr.

Jan