17 Aug
2018
17 Aug
'18
12:45 p.m.
Hi!
I keep receiving the below logs on Kamailio:
CRITICAL: dialog [dlg_hash.c:955]: log_next_state_dlg(): bogus event 8 in
state 1 for dlg 0x7f59862cd440 [3685:10496]
I understand that state 1 indicates an unconfirmed dialog, can anyone tell
me what bogus event 8 is?
The following is the call flow:
User A ===> Kamailio ==> Provider
From the PCAP trace an INVITE is sent to the provider,
the provider
answers with 100 Trying, 180 Ringing and immediately an OPTIONS
message
with the same call id
Kamailio Provider
INVITE
=================>
100 Trying
<=================
180 Ringing
<================
OPTIONS
<================
Im assuming bogus event 8 is the OPTIONS message? Is an OPTIONS message
normal in this case?
Thanking you very much in advance for your help!
Regards
Phillip
17 Aug
17 Aug
12:57 p.m.
Am Freitag, 17. August 2018, 12:45:15 CEST schrieb Phillman25 Kyriacou:
CRITICAL: dialog [dlg_hash.c:955]:
log_next_state_dlg(): bogus event 8 in
state 1 for dlg 0x7f59862cd440 [3685:10496]
I understand that state 1 indicates an unconfirmed dialog, can anyone tell
me what bogus event 8 is?
The following is the call flow:
User A ===> Kamailio ==> Provider
From the PCAP trace an INVITE is sent to the provider, the provider
answers with 100 Trying, 180 Ringing and immediately an OPTIONS message
with the same call id
Kamailio Provider
INVITE
=================>
100 Trying
<=================
180 Ringing
<================
OPTIONS
<================
Im assuming bogus event 8 is the OPTIONS message? Is an OPTIONS message
normal in this case?
Hello Phillip,
an in-dialog OPTIONS is not normal, it should be not required for the normal
call-flow. I think the OPTIONS is indeed the event 8 here.
You find the event definitions in dlg_hash.h in the dialog module:
/* events for dialog processing */
#define DLG_EVENT_TDEL 1 /*!< transaction was destroyed */
#define DLG_EVENT_RPL1xx 2 /*!< 1xx request */
#define DLG_EVENT_RPL2xx 3 /*!< 2xx request */
#define DLG_EVENT_RPL3xx 4 /*!< 3xx request */
#define DLG_EVENT_REQPRACK 5 /*!< PRACK request */
#define DLG_EVENT_REQACK 6 /*!< ACK request */
#define DLG_EVENT_REQBYE 7 /*!< BYE request */
#define DLG_EVENT_REQ 8 /*!< other requests */
You should ask the provider why they send you this OPTIONS here. But if your
calls are not affected (which I assume) you could also ignore it.
Best regards,
Henning
--
Henning Westerholt
https://skalatan.de/blog/
1:10 p.m.
Thank you so much for your prompt reply and explanation Henning!
Yes the calls are not affected so ill just ignore these messages.
Thanks again!
Phillip
On Fri, Aug 17, 2018 at 1:57 PM, Henning Westerholt <hw(a)kamailio.org> wrote:
Am Freitag, 17. August 2018, 12:45:15 CEST schrieb
Phillman25 Kyriacou:
CRITICAL: dialog [dlg_hash.c:955]:
log_next_state_dlg(): bogus event 8 in
state 1 for dlg 0x7f59862cd440 [3685:10496]
I understand that state 1 indicates an unconfirmed dialog, can anyone
tell
me what bogus event 8 is?
The following is the call flow:
User A ===> Kamailio ==> Provider
From the PCAP trace an INVITE is sent to the provider, the provider
answers with 100 Trying, 180 Ringing and immediately an OPTIONS message
with the same call id
Kamailio Provider
INVITE
=================>
100 Trying
<=================
180 Ringing
<================
OPTIONS
<================
Im assuming bogus event 8 is the OPTIONS message? Is an OPTIONS message
normal in this case?
Hello Phillip,
an in-dialog OPTIONS is not normal, it should be not required for the
normal
call-flow. I think the OPTIONS is indeed the event 8 here.
You find the event definitions in dlg_hash.h in the dialog module:
/* events for dialog processing */
#define DLG_EVENT_TDEL 1 /*!< transaction was destroyed */
#define DLG_EVENT_RPL1xx 2 /*!< 1xx request */
#define DLG_EVENT_RPL2xx 3 /*!< 2xx request */
#define DLG_EVENT_RPL3xx 4 /*!< 3xx request */
#define DLG_EVENT_REQPRACK 5 /*!< PRACK request */
#define DLG_EVENT_REQACK 6 /*!< ACK request */
#define DLG_EVENT_REQBYE 7 /*!< BYE request */
#define DLG_EVENT_REQ 8 /*!< other requests */
You should ask the provider why they send you this OPTIONS here. But if
your
calls are not affected (which I assume) you could also ignore it.
Best regards,
Henning
--
Henning Westerholt
https://skalatan.de/blog/
1:20 p.m.
an in-dialog OPTIONS is not normal, it should be not required for the
normal
call-flow.
i'v seen many in-dialog OPTIONS for checking is dialog alive, but only
after INVITE-OK-ACK handshake.
On 17 August 2018 at 14:10, Phillman25 Kyriacou <phillman25(a)gmail.com>
wrote:
Thank you so much for your prompt reply and
explanation Henning!
Yes the calls are not affected so ill just ignore these messages.
Thanks again!
Phillip
On Fri, Aug 17, 2018 at 1:57 PM, Henning Westerholt <hw(a)kamailio.org>
wrote:
--
Savolainen Dmitri
Am Freitag, 17. August 2018, 12:45:15 CEST
schrieb Phillman25 Kyriacou:
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
CRITICAL: dialog [dlg_hash.c:955]:
log_next_state_dlg(): bogus event 8
in
state 1 for dlg 0x7f59862cd440 [3685:10496]
I understand that state 1 indicates an unconfirmed dialog, can anyone
tell
me what bogus event 8 is?
The following is the call flow:
User A ===> Kamailio ==> Provider
From the PCAP trace an INVITE is sent to the provider, the provider
answers with 100 Trying, 180 Ringing and immediately an OPTIONS message
with the same call id
Kamailio Provider
INVITE
=================>
100 Trying
<=================
180 Ringing
<================
OPTIONS
<================
Im assuming bogus event 8 is the OPTIONS message? Is an OPTIONS message
normal in this case?
Hello Phillip,
an in-dialog OPTIONS is not normal, it should be not required for the
normal
call-flow. I think the OPTIONS is indeed the event 8 here.
You find the event definitions in dlg_hash.h in the dialog module:
/* events for dialog processing */
#define DLG_EVENT_TDEL 1 /*!< transaction was destroyed */
#define DLG_EVENT_RPL1xx 2 /*!< 1xx request */
#define DLG_EVENT_RPL2xx 3 /*!< 2xx request */
#define DLG_EVENT_RPL3xx 4 /*!< 3xx request */
#define DLG_EVENT_REQPRACK 5 /*!< PRACK request */
#define DLG_EVENT_REQACK 6 /*!< ACK request */
#define DLG_EVENT_REQBYE 7 /*!< BYE request */
#define DLG_EVENT_REQ 8 /*!< other requests */
You should ask the provider why they send you this OPTIONS here. But if
your
calls are not affected (which I assume) you could also ignore it.
Best regards,
Henning
--
Henning Westerholt
https://skalatan.de/blog/
2:27 p.m.
Am Freitag, 17. August 2018, 13:20:39 CEST schrieb Dmitri Savolainen:
Hi Dimitri,
you are of course right, this is what I meant as well.
Best regards,
Henning
--
Henning Westerholt
https://skalatan.de/blog/
an in-dialog
OPTIONS is not normal, it should be not required for the
normal
call-flow.
i'v seen many in-dialog OPTIONS for checking is dialog alive, but only
after INVITE-OK-ACK handshake.
2296
days inactive
2296
days old
4 comments
3 participants
participants (3)
-
Dmitri Savolainen -
Henning Westerholt -
Phillman25 Kyriacou