Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

FOP2 Community Forum

  1. Home
  2. Support
  3. Improper rectangle/extension update

Improper rectangle/extension update

Scheduled Pinned Locked Moved Support
4 Posts 2 Posters 62 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G
    G
    ghostbit
    wrote on last edited by
    #1

    Hi Nicolas,

    Just downloaded and installed FOP2 on a FreePBX/CentOS box. Everything is ok except one thing:
    sometimes the extensions/rectangles remain orange for a random amount of time (15-20-25s) before turning green. The extensions are available but showing orange for a while.

    I'm using the default configurations for:
    /etc/asterisk/manager.conf
    /var/www/html/fop2

    I've also enabled "Call Events --> Yes" in FreePBX.

    FreePBX 2.9.0.7
    Asterisk 1.8.6.0
    CentOS release 5.5 (Final) x64
    fop2-2.26-centos5-x86_64
    Twinkle 1.4.2 as voip client
    tried browsers from IE6.0 to latest Chrome/Chromium/Firefox on both Windows and Linux (Ubuntu 12.04)... no luck

    I've seen a similar post but i'm not using queues... only simple ring groups.

    http://dl.dropbox.com/u/1013681/Screenshot from 2012-07-16 15%3A32%3A59.png
    As you can see both lines are available but the user is still orange/red...

    1 Reply Last reply
    0
    • N
      N
      nicolas
      wrote on last edited by
      #2

      Hi,

      Did the user transferred the original call out? Asterisk has a feature/bug where local channels that transfer a call out will remain busy/inuse for as long as the transferred call lives on the system.

      I think that your issue is related to that, it is not a fop2 problem, is the way asterisk works with local channels. Local channels are most probably used when using ring groups, but maybe not on direct calls, so you might see that behavior in ring group delivered (or queue delivered) calls, but not direct calls.

      The above is a guess and what could be happening, as I do not know for sure your users are transferring the calls or not, if that is the case, then there is no real workaround to this, but perhaps a smarter dialplan that uses less local type channels (or bare minimum local channels). But as this is controlled by freepbx it is kind of hard to work your own dialplan with it.

      Best regards,

      1 Reply Last reply
      0
      • G
        G
        ghostbit
        wrote on last edited by
        #3

        Hi Nicolas,

        No transfers... only simple, normal, calls.

        I've been able to reproduce the issue:
        Let's suppose that both lines are idle/inactive. Then the user receives a call and he/she takes it...
        IF during the call the other line rings and the user finishes his original call while that line is still ringing, the rectangle will stay orange, and it will stay that way until both lines become inactive again. BUT, if i press F5 the screen refreshes/relogins and the rectangle turns green immediately as it supposed to be.
        On the other hand, IF the other line is inactive, the rectangle will turn green immediately after the user finishes the call.

        1 Reply Last reply
        0
        • N
          N
          nicolas
          wrote on last edited by
          #4

          Do you have "all" both in read/write in /etc/asterisk/manager.conf ?

          It seems like there are missing manager events in your setup. Also, be sure to set in sip.conf

          callevents=yes

          If you can reproduce the issue with those two settings, then I will have to look at a detailed capture of manager events on your server to trace the issue. I am almost sure it is not a fop2 bug but some problem with manager events. handling multiple calls is something every user does and they do not experience the issue you describe. So be sure to set callevents=yes in sip.conf and that your manager.conf is not filtering events at all.

          In any case, you can try to catch me on the live help. Best regards,

          1 Reply Last reply
          0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          Powered by NodeBB Contributors
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups