[OpenSIPS-Users] Dialog Module and Bogus Event 8 in state 2

[Sven Schulz]

Directly after the 183 Ringing is a NOTIFY message coming from the
destination (which is a Cisco Sip gateway). The source sends a corresponding
200 OK to this NOTIFY (also a cisco PBX).

So is the "bogus event" something I should be concerned with or is it more
of an informational error message?

0.000000    10.1.2.52 -> 10.1.1.82    SIP/SDP Request: INVITE
sip:phonenumber at xx.edu:5060, with session description
  0.000291    10.1.1.82 -> 10.1.2.52    SIP Status: 100 Giving a try
  0.001830    10.1.1.82 -> 10.1.1.60    SIP/SDP Request: INVITE
sip:18148656116 at 10.1.1.60, with session description
  0.004343    10.1.1.60 -> 10.1.1.82    SIP Status: 100 Trying
  1.474100    10.1.1.60 -> 10.1.1.82    SIP/SDP Status: 183 Session
Progress, with session description
  1.474240    10.1.1.82 -> 10.1.2.52    SIP/SDP Status: 183 Session
Progress, with session description
  1.483850    10.1.1.60 -> 10.1.1.82    SIP Request: NOTIFY
sip:10.1.2.52:5060
  1.483962    10.1.1.82 -> 10.1.2.52    SIP Request: NOTIFY
sip:10.1.2.52:5060
  1.486091    10.1.2.52 -> 10.1.1.82    SIP Status: 200 OK
  1.486133    10.1.1.82 -> 10.1.1.60    SIP Status: 200 OK
  4.252373    10.1.1.60 -> 10.1.1.82    SIP/SDP Status: 200 OK, with session
description
  4.252756    10.1.1.82 -> 10.1.2.52    SIP/SDP Status: 200 OK, with session
description



On 1/12/11 6:19 AM, "Bogdan-Andrei Iancu" <bogdan at voice-system.ro> wrote:

> Hi Sven,
> 
> "Bogus Event 8 in state 2" is translated to receiving an indialog
> request (non ACK, non BYE) while dialog in early state.....maybe it is a
> PRACK to the 183....can you check that ?
> 
> Regards,
> Bogdan
> 
> Sven Schulz wrote:
>> Running opensips 1.6.3, dialog module seems to function correctly
>> however I keep getting these messages:
>> 
>> CRITICAL:dialog:log_next_state_dlg: bogus event 8 in state 2 for dlg
>> 0x2b33956052c0 [2284:61359203] with clid
>> '11a0bd80-d2c160b0-1a-3402010a at 10.1.2.52
>> <%2711a0bd80-d2c160b0-1a-3402010a at 10.1.2.52>' and tags
>> 'd5edda48-9c10-424c-b200-8ec1eb8e532c-42504961' '292F5834-D13'
>> 
>> They only seem to happen when an INVITE is followed by a 183 RINGING
>> message. INVITES without a 183 wont get this error messege. Is this
>> normal or should I be concerned?
>> 
>> 
>> Sven Schulz
>> Penn State University
>> Telecommunications and Network Services
>> 814.865.6116
>> sip:sven at psu.edu
>> 
>> ------------------------------------------------------------------------
>> 
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>   
>