[OpenSIPS-Users] sip code 487 and log_next_state_dlg: bogus event 4 in state 5

Bogdan-Andrei Iancu bogdan at opensips.org
Tue Feb 24 17:18:55 CET 2015


Hi Mike,

Do you get that on a machine where the dialog states are replicated to ? 
Aside the bin replication, is that server also receiving real SIP traffic ?

I see you have DBG logs - could you grep them for all the logs related 
to that dialog : grep on "0x7fb6de3922b0" .

Regards,

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

On 20.02.2015 01:36, Mike Tesliuk wrote:
>
> Hello Guys,
>
>
> im getting this critical message on my opensips, but i see that this 
> message just appear with the binary replication activated, is this 
> expected ?
>
> Feb 19 07:34:12 sipproxy01 /usr/sbin/opensips[13762]: 
> CRITICAL:dialog:log_next_state_dlg: bogus event 4 in state 5 for dlg 
> 0x7fb6de3922b0 [1887:354100080] with clid 
> '37e9a2df45cc258436f4cb351e60832b at 172.30.1.15:5060' and tags 
> 'as33b7ba8a' 'as40351bae'
> Feb 19 07:34:12 sipproxy01 /usr/sbin/opensips[13762]: 
> DBG:dialog:next_state_dlg: dialog 0x7fb6de3922b0 changed from state 5 
> to state 5, due event 4
> Feb 19 07:34:12 sipproxy01 /usr/sbin/opensips[13762]: 
> DBG:tm:cleanup_uac_timers: RETR/FR timers reset
>
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>




More information about the Users mailing list