No did on buttons after some minutes

  1. 10 years ago

    Hi,

    I recently updated a fop to v2.28.
    When someone login into the panel the group buttons shows the did numbers when they are attending a call.
    Few minutes later the new incoming calls starts not showing the did number. It just show "Line 1 inactive", but the time counter is fine and background color of the button is fine.

    After 10 minutes, all buttons have this problem. If I refresh, the problem is solved (including in wrong buttons before refresh) until few minutes again.

    I try just restarting the service but it isn't enough.
    I'd attached a screenshot.

    If you need more information, let me know please.
    Thanks

  2. admin

    7 Nov 2014 Administrator

    Did you modify fop2.cfg in any way, specifically the poll_interval value? If so, undo whatever you did and restart the service.

  3. [general]
    ; AMI definitions
    manager_host=*********
    manager_port=5038
    manager_user=***********
    manager_secret=**************
    
    web_dir            = /var/www/html/fop2
    
    ; Global Config
    poll_interval      = 86400
    poll_voicemail     = 1
    monitor_ipaddress  = 0
    
    ; Force blind transfer on asterisk 1.6
    blind_transfer     = 1
    
    spy_options="bq"
    
    whisper_options = "w"
    
    monitor_filename=/var/spool/asterisk/monitor/${ORIG_EXTENSION}_${DEST_EXTENSION}_%h%i%s_${UNIQUEID}
    monitor_format=wav
    monitor_mix=true
    
    user=****:****:all
    
    buttonfile=buttons.cfg
  4. I have another fop 2.28 in another pbx with the same problem

    FOP2 shows Line 1 inactive and the timer running when someone is talking.

  5. admin

    12 Nov 2014 Administrator

    You will have to enable debug in fop2 and stop it at the exact moment you notice a button becoming inactive with timer. The log will show us what events are firing up that behaviour.

    service fop2 stop
    cd /usr/local/fop2
    script capture.log
    ./fop2_server -X 511

    (log into fop2, wait until you notice the problem)

    ctrl-C
    exit
    service fop2 start

    Then look at the capture.log file, at the end of it you will see events related to the trouble extension, those events are firing that state change/problem. If you do not stop capturing at the same time it happens, it will be really hard to look for the events as the log will be huge.

  6. Hi,

    The moment when starts failing showing Line 1 Inactive over Active Buttons I get:

    127.0.0.1 <- Event: Newstate^M
    127.0.0.1 <- Privilege: call,all^M
    127.0.0.1 <- Channel: SIP/*******304-0000007c^M
    127.0.0.1 <- ChannelState: 6^M
    127.0.0.1 <- ChannelStateDesc: Up^M
    127.0.0.1 <- CallerIDNum: 304^M
    127.0.0.1 <- CallerIDName: Se*******o 4^M
    127.0.0.1 <- ConnectedLineNum: 988****69^M
    127.0.0.1 <- ConnectedLineName: 988****69^M
    127.0.0.1 <- Uniqueid: 1415871156.124^M

    The ConnectedLineNum is correct.

  7. admin

    13 Nov 2014 Administrator

    can you send me whatever comes next in full debug after that event ? Do you see something like:

    uso connected line **** y ******

    ?

or Sign Up to reply!