[SR-Users] Bogus event 8 in state 1 for dlg

[Henning Westerholt]

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/