FOP2 Community Forum

They are safe for filtering for the FOP2 manager user. Do not set them for the admin user or any user that might be used by other applications. Also, check the fop2 documentation for the latest version of recommendations/setup at www.fop2.com/docs. I have seen in some systems that rtcp events should be filtered out via wildcard, like RTCP* , for example. Best regards,

Sorry to wake such an old post but I'm having this problem and haven't been able to solve it. I have Elastix 2.5 and FOP 2.28. When using Users and Devices, when I login, most of the time (but not all) the extension that was on the device continues to show it's in a call to *11 and continues to look as thought connected, and when I logoff, the state of the user appears as though still logged in and the *12 call still active (forever). The event I see in debug mode looks correct: 127.0.0.1 <- Event: UserEvent 127.0.0.1 <- Privilege: user,all 127.0.0.1 <- UserEvent: UserDeviceRemoved 127.0.0.1 <- Uniqueid: 1580380014.8496411 127.0.0.1 <- Data: 51133,44444 Which event is it looking at? I noticed the hangup event is usually right before it notifies the browser and the AccountCode is missing and the CallerIdNum is the new user on the device: 127.0.0.1 <- Event: Hangup 127.0.0.1 <- Privilege: call,all 127.0.0.1 <- Channel: SIP/44444-00237eb8 127.0.0.1 <- Uniqueid: 1580379756.8495839 127.0.0.1 <- CallerIDNum: 44444 127.0.0.1 <- CallerIDName: device 127.0.0.1 <- ConnectedLineNum: <unknown> 127.0.0.1 <- ConnectedLineName: <unknown> 127.0.0.1 <- AccountCode: 127.0.0.1 <- Cause: 16 127.0.0.1 <- Cause-txt: Normal Clearing Any ideas?

If event_mask is commented, it defaults to "all", if you limit the event mask you will miss some events... I do not know why are you having problems, just live event_mask commented, it should work fine. Are you connecting to AMI locally? or via wan / slow link? You can always start fop2_server in debug mode, but that will make it slower, but will help you see if events are getting corrupted, or the ami connection reset. If you are running FOP1, disable it, it will make AMI perform better without an unneeded extra connection.