Hide offline extensions

Hello!

I use more (>200) extensions. Many of them are periodically offline. How may i hide offline extensions in Main Panel View?
Thanks.

Comments

  • You can alter operator.css, look for the notregistered class and add "display:none;" to it.
  • In my multi server environment the operator.css is on the main server. I have edited that file to say
    .notregistered {
    display:none;
    background:#ddd;
    opacity:.50;
    filter:alpha(opacity=50);
    -khtml-opacity: 0.5;
    -moz-opacity:0.5;

    The offline extensions on the main server are not shown but the offline extension on the other servers are still shown. How can I have all offline extensions, no mater what server be hidden?
  • Hi,

    It works fine, but you must be receiving data from the 2nd manager and you must have qualify set on the sip peers on that 2nd box too.
  • Sorry fof my English.
    Set display:none yet nothing has changed, inactive EXT. displayed on the panel, and even painted green.
    How to check whether the status of the user (or exten) receives from the asterisk FOP2?
  • That works if you flush your browser cache, but it will hide the unregistered extensions.. unregistered is not the same as inactive. If you want to hide inactive (not talking extensions), you can set display:none to the "free" class in operator.css.
  • operator.css
    .notregistered {                                                                                     
    display:none;                                                                                        
    }    
    
    still shows no active users.
    cleaning the cache and check the other PC does not show the result.
    Что я делаю не так ? / What am I doing wrong?
  • I already replied. Perhaps the idiom is playing tricks.

    unregistered <> not active
  • asterisk -r sip show peers registered is exten.
    How to remove Wesley from the operator panel.
  • Sorry, I still do not understand. To monitor unregistered sip peers you must set qualify=yes in the sip peer entry, if using realtime you must set rtcachefriends=yes.
  • hi,
    modify operator.css works fine, but when i filter by queue and go back again, the unregistered are visible again. I have to log on again to make it invisible.
  • That's actually an expected behaviour... version 2.30 has an option to hide unregistered via settings, that will work when filtering views. You might want to give 2.30 beta a try then.
  • How do I hide unregistered via settings, which settings?
  • edited November 2015
    Found it in manager.
    Do I still have to alter operator.css?
    Cause changing the setting in manager only won't have an effect.

    And to add to that, non of the changes I make under settings in FOP2 seem to have an effect. What could be wrong?
    I tried warn close, warn hangup, hide unregistered, etc.
  • Maybe you are referring to presence.js? In that case, version 2.30 presence.js does not mention any configuration variable as before. Your presence.js should not include any of those config settings, or they will override what you set via Manager.

    Check if the changes you made via FOP2 Manager 'stick'. Do they remain in the value you set after refreshing the page? Perhaps you have a permission issue with the file /usr/local/fop2/fop2_settings.db, that should be writable by the web server user.
  • The changes stick with FOP2 manager, they are still there after refreshing the page, but they don't have any effect.
    Is there a way to check for errors whenever writing into /usr/local/fop2/fop2_settings.db fails?
    On my HA system I have a c- option in sysconfig to copy changes to /etc/asterisk/fop2.
  • If changes 'stick', then you do not have issues with permissions. Check that you do not have any preferences set in /var/www/html/fop2/js/presence.js. If you do have them, then they will override whatever you set via web gui. The latest version presence.js does not include any settings, just the options for presence changes, queue penalties and commented section for pauses/reasons, but not other var XXX=YYY setting.
  • This is how my /var/www/html/fop2/js/presence.js looks like. I guess there are no preference settings in there.
    Hm.. what else could be the problem?

    var language = 'en';
    var applicationTitle = 'Flash Operator Panel 2';

    var presence = new Object();
    presence = '';
    presence = '#FF8A8A';
    presence = '#57BCD9';
    presence = '#6094DB';
    presence = '#CDD11B';

    /* Uncomment the following to enable pause menu with reasons
    //
    var pauseReasons = new Object();
    pauseReasons = 1;
    pauseReasons = 2;
    */

    /* Uncomment the following to enable queue penalty set
    //
    var queuePenalties = new Object();
    queuePenalties = 2;
    queuePenalties = 1;
    queuePenalties = 0;
    */

    var availLang = new Object();
    availLang = 'Català';
    availLang = 'Hrvatski';
    availLang = 'Dansk';
    availLang = 'Deutsch';
    availLang = 'עברית';
    availLang = 'Ελληνικά';
    availLang = 'English';
    availLang = 'Español';
    availLang = 'Francais';
    availLang = 'Magyar';
    availLang = 'Italiano';
    availLang = 'Dutch'
    availLang = 'Polski';
    availLang = 'Português';
    availLang = 'Русский';
    availLang = 'Svenska';
    availLang = 'Türkçe';
    availLang = '简体中文';
    var lang = new Object();
  • edited December 2015
    And by the way my settings file is called fop2settings.db, and not fop2_settings.db. Not sure if this is relevant.

    I found that my fop2_settings.db file in /usr/local/fop2 was differnet from
    DB Connection fail: SQLSTATE[HY000]: General error: 8 attempt to write a readonly database
  • Filename is fop2settings.db in /usr/local/fop2 (it was a typo on my part before).

    If you see that error, then any change you make in the GUI should not persist. And fixing that requires to set proper permissions and ownership to the fop2settings.db file, try

    chown asterisk.asterisk /usr/local/fop2/fop2settings.db
    chmod g+w /usr/local/fop2/fop2settings.db

  • Sorry I accidently pressed enter before without finishing my post.
    When I do a:
    diff -r /usr/local/fop2 /etc/asterisk/fop2/, I get:
    Binary files /usr/local/fop2/fop2settings.db and /etc/asterisk/fop2/fop2settings.db differ

    Maybe manager is writing the changes into one file and reading from the other?

    The general error:8 I got when I copied fop2settings from /etc/asterisk/fop2 into /usr/local/fop2
  • I answered in another post, fop2settings.db that counts in your setup is the one in /etc/asterisk/fop2, be sure it is owned by asterisk, that asterisk user can write to it, and also modify the pagebs.fop2settings.php page to point to that directory instead of /usr/local/fop2
Sign In or Register to comment.