delays on incoming calls on queues

  1. 8 years ago

    On a system with Asterisk 13.9.1, FreePBX 12 and FOP2 2.30.02, we have a problem whith incoming calls to queues. When a call enters a queue, the small icons of the agents of the queue start moving indicating the extensions are ringing, but the extension buttons do not turn orange for 10 seconds or more (seems some sort of delay).
    All the agents of the queues are dynamic. We have 12 queues with 8-12 dynamic agents in each queue, and 44 extensions in the panel.
    We have tried FOP2 2.31.00 and 2.31.01, with the same results (but had to revert to 2.30.02 because some bug made some calls appear empty in the queues boxes and would not disappear).

    Can it be caused by too many AMI events? Is there something we can do?

  2. I forgot to mention Eventfilters in manager.conf didn't seem to make any difference

  3. After looking at the problem a bit more, we've seen that the delay happens when there's more of 2 "free" agents in a queue. And it seems exponential: more free agents, more time it will take to show the ringing status of the extensions (even if we hang up the call, the call will appear and then disappear).

    Don't know if it's relevant, but looking at the fop2 log, when the call enters the queue, we can see the RINGING (output with a few greps to only show relevant data):

    127.0.0.1 <- Device: Queue:127
    127.0.0.1 <- State: RINGING
    --
    127.0.0.1 <- Privilege: call,all
    127.0.0.1 <- Device: SIP/350
    127.0.0.1 <- State: RINGING
    --
    127.0.0.1 <- Privilege: call,all
    127.0.0.1 <- Device: SIP/351
    127.0.0.1 <- State: RINGING
    --
    127.0.0.1 <- Privilege: call,all
    127.0.0.1 <- Device: SIP/352
    127.0.0.1 <- State: RINGING
    ....

    But until we see the ChannelStateDesc: Ringing, the buttons do not appear as ringing. Don't really know if it could be a clue.

  4. admin

    21 Jun 2016 Administrator

    FOP2 looks for Event: Newstate and check if its ringing or not based on its headers. If Asterisk delays in sending that event, then it is Asterisk, and not FOP2, who is at fault. But it does not stop there, the Channel in RINGING state might be a local channel, if so the state interface must be defined correctly and match a button definition in FOP2.

    Best regards,

or Sign Up to reply!