Agents in queue become always visible after update to 2.31.07

  1. 7 years ago
    Edited 7 years ago by bazoozoo

    After update to 2.31.07, i have a strange problem: fop2 thinks thats users alvays online and available, but it is not tru!
    -image-

    pbx*CLI> queue show
    9999 has 0 calls (max unlimited) in 'rrmemory' strategy (23s holdtime, 136s talktime), W:0, C:954, A:166, SL:67.7% within 60s
       Members:
          Си... (Local/903@from-queue/n from hint:903@ext-local) (ringinuse enabled) (Unavailable) has taken no calls yet
          Балтабаева Марина Марленовна (Local/902@from-queue/n from hint:902@ext-local) (ringinuse enabled) (Unavailable) has taken no calls yet
          Ва... (Local/901@from-queue/n from hint:901@ext-local) (ringinuse enabled) (Unavailable) has taken no calls yet
          Васильева Людмила Семеновна (Local/908@from-queue/n from hint:908@ext-local) (ringinuse enabled) (Unavailable) has taken no calls yet
          Му... (Local/907@from-queue/n from hint:907@ext-local) (ringinuse enabled) (Unavailable) has taken no calls yet
          Юр... (Local/906@from-queue/n from hint:906@ext-local) (ringinuse enabled) (Unavailable) has taken no calls yet
          Га... (Local/905@from-queue/n from hint:905@ext-local) (ringinuse enabled) (Unavailable) has taken no calls yet
       No Callers
    
    default has 0 calls (max unlimited) in 'ringall' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 0s
       No Members
       No Callers

    incall is more important than other states imho, you want to know if a queue member is in a call or not, then that incall state works and it is not dependent on custom hints or other possible states .

    Best regards,

  2. strange, but it looks like happen anly when apllying freepbx settings, so forget about it, it's not a problem.

  3. admin

    19 Jan 2017 Administrator

    Well, the problem is this:

    Asterisk 13, has an "incall" status. Besides the "state". FOP2 gives more weight to the "incall" status than the "state", as it was modeled to have only ONE possible state for queue members.

    So most probably AMI events are displaing something like:

    Status: 4
    Incall: 0

    4 is unavailable, but it is not in a call (and fop2 sets it to free/available).

    So my guess is that the solution would be to make incall status not to take precedence over unavailable or invalid agent states.

  4. what if just ignore incall state?

  5. admin

    28 Jan 2017 Administrator Answer

    incall is more important than other states imho, you want to know if a queue member is in a call or not, then that incall state works and it is not dependent on custom hints or other possible states .

    Best regards,

or Sign Up to reply!