Post a Reply
2108 views

FOP2 MONITORING ERROR *11

  1. 8 years ago

    moses

    15 Nov 2016
    Edited 8 years ago by moses

    Dear FOP Team,

    Now our customer using freepbx userdevice mode, but sometime there is issue on fop2 monitoring

    I put on attachment screenshoot

    On the pic we can see user : 2206 error *11 and duration (05:09:11)

    In normal state if login *11 it should be like "2199"

    If i check user 2206 via command line :

    [root@fop2server ~]# asterisk -rx "core show hints" | grep 2206

    [root@fop2server ~]# asterisk -rx "database show" | grep "2206"
    /AMPUSER/2206/answermode : disabled
    /AMPUSER/2206/ccss/cc_agent_policy : generic
    /AMPUSER/2206/ccss/cc_offer_timer : 30
    /AMPUSER/2206/cfringtimer : 0
    /AMPUSER/2206/cidname : 2206
    /AMPUSER/2206/cidnum : 2206
    /AMPUSER/2206/concurrency_limit : 0
    /AMPUSER/2206/language :
    /AMPUSER/2206/noanswer :
    /AMPUSER/2206/outboundcid :
    /AMPUSER/2206/password : 2206
    /AMPUSER/2206/queues/qnostate : usestate
    /AMPUSER/2206/recording :
    /AMPUSER/2206/recording/in/external : dontcare
    /AMPUSER/2206/recording/in/internal : dontcare
    /AMPUSER/2206/recording/ondemand : disabled
    /AMPUSER/2206/recording/out/external : dontcare
    /AMPUSER/2206/recording/out/internal : dontcare
    /AMPUSER/2206/recording/priority : 10
    /AMPUSER/2206/ringtimer : 0
    /AMPUSER/2206/voicemail : novm
    /CALLTRACE/2206 : 2051
    /CW/2206 : ENABLED

    We can't find mapping device (/AMPUSER/2206/device) , user (/DEVICE/XXX/user) and core show hints

    In normal state (User 2199) we can file user, device and core show hints

    [root@fop2server ~]# asterisk -rx "database show" | grep "2199"
    /AMPUSER/2083/ccss/last_number : 2199
    /AMPUSER/2137/ccss/last_number : 2199
    /AMPUSER/2199/answermode : disabled
    /AMPUSER/2199/ccss/cc_agent_policy : generic
    /AMPUSER/2199/ccss/cc_offer_timer : 30
    /AMPUSER/2199/ccss/last_number : 2199
    /AMPUSER/2199/cfringtimer : 0
    /AMPUSER/2199/cidname : 2199
    /AMPUSER/2199/cidnum : 2199
    /AMPUSER/2199/concurrency_limit : 0
    /AMPUSER/2199/device : 185
    /AMPUSER/2199/language :
    /AMPUSER/2199/noanswer :
    /AMPUSER/2199/outboundcid :
    /AMPUSER/2199/password : 2199
    /AMPUSER/2199/queues/qnostate : usestate
    /AMPUSER/2199/recording :
    /AMPUSER/2199/recording/in/external : dontcare
    /AMPUSER/2199/recording/in/internal : dontcare
    /AMPUSER/2199/recording/ondemand : disabled
    /AMPUSER/2199/recording/out/external : dontcare
    /AMPUSER/2199/recording/out/internal : dontcare
    /AMPUSER/2199/recording/priority : 10
    /AMPUSER/2199/ringtimer : 0
    /AMPUSER/2199/voicemail : novm
    /CALLTRACE/2199 : 2199
    /CW/2199 : ENABLED
    /DEVICE/185/user : 2199

    [root@fop2server ~]# asterisk -rx "core show hints" | grep 2199
    2199@ext-local : SIP/185 State:Idle Watchers 0

    My fop2 version : FOP2 Server Status: OK - Version: 2.29.03

    Can you help me to solve this issue?

    Thanks

    Thanks

  2. admin

    15 Nov 2016 Administrator

    Not sure if I follow you completly.

    FOP2 does not set or unset *any* ASTDB entry for FreePBX. That is done completely by FreePBX itself, if you see inconsistencies there, it is not because of FOP2, it is a problem with FreePBX.

    Anyways, I am not sure there are any inconsistencies in ASTDB either.

    The error you see is a "stuck" call when dialing *11 to log in or out (we cannot be sure).

    What FOP2 version are you using?
    What Asterisk version are you using?

    That information is important. You might be seeing an out of order issue, there was some work done on FOP2 to avoid that a few years ago, perhaps you have an old FOP2? Finally, Asterisk 13 introduced many out of order AMI event issues, so a bug might have been reintroduced (regression), that affects FOP2.

    The out of order problem was like this, think that FOP2 only track *devices*

    You login with extension 1111 from device AAAA
    (fop2 maps AAAA to 1111)
    You make a call from AAAA, extension 1111 shows activity in FOP2 correctly
    You dial *11 to log out. FOP2 notices device up AAAA when dialing *11 and sets the device as busy
    FreePBX runs user_login_out.agi and fires UserEvent to unmap AAAA and 1111
    FOP2 sees the UserEvent and unmaps AAAA and 1111 (this is the order problem)
    device AAAA hangs up from *11 (but AAAA is not associated to 1111 any longer, so the button remains stuck).

    The above problem was fixed years ago.. so, what is your FOP2 version and what your ASterisk version? Do you experience an *11 stuck *EVERY* time you log out, or it happened once, randomly?

  3. moses

    17 Nov 2016

    Hi Fop2,

    Thanks your response

    My fop2 version : FOP2 Server Status: OK - Version: 2.29.03

    Asterisk 11.6.0

    It happened once, randomly

    Thanks

  4. admin

    18 Nov 2016 Administrator

    Ok, a random event that cannot be reproduced is not something I can work to fix, unfortunately. You can clear that up by restarting the FOP2 service with:

    service fop2 restart

    If you can make it happen (reproduce the problem), every time you try. Or perhaps with some specific actions, *then* I can capture logs, analyze them and see if it is fixable.

    Best regards,

or Sign Up to reply!