Queue members not showing in queue button

[Jeremy]

I tried another system running Asterisk 13.8 and have the same issue when trying both FOP2 2.30.06 and 2.31.00.
Is this a bug or am I doing something wrong?
I can try and get an Asterisk 12 installation together as a test just to see if it is isolated to Asterisk 13 or not.

[nicolas]

Hi Jeremy,

The only thing that I think is funny is the member name for your queue members. You usually have just a name, like John, not a full callerid string like it seems you have:

"Clerk 14" <>

With quotes for the name and empty number between <>

How are you adding your queue members?

Best regards,

[Jeremy]

I made the sip.conf by hand and did leave off the extension after the name. I just changed it to get rid of the quotes, space and add the extension as follows:

[1002](softphone)
username=1002
callerid=Clerk02 <1002>
context=default

One thing I noticed after restarting Asterisk is that the new CallerID's weren't taking effect! It seems that was due to me having PersistentMembers=yes in queues.conf, which I just changed to no and restarted again. Now the caller ID's are correct in queue show:

CLI> queue show
IN-Lanes has 0 calls (max unlimited) in 'rrmemory' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 600s
   Members:
      "Clerk02" <1002> (sip/1002 from sip/1002) (ringinuse disabled) (dynamic) (Not in use) has taken no calls yet
   No Callers

But they unfortunately still don't show up in the queue buttons in FOP - they still say Agents: 0 and don't list the actual members.

I feel like we are getting closer, though. I'll keep tinkering...

[nicolas]

Still, a queue member name is something different than a callerid in sip.conf

A queue member name could be Clerk02, instead of "Clerk02" <1002>

How are you adding queue members? Queue member names are NOT in direct relation with callerid settings in sip.conf

[Jeremy]

Oh. That's interesting. The callerid in sip.conf is the only place I used the name "Clerk" ever. The members are adding and removing themselves from their softphone client. The only identifying information they provide in the softphone is server IP, SIP username/ password and AMI manager username/password. The softphone list the queues and they tick the boxes next to the queues they want.

To help remove the softphone from the equation, I just tried adding a queue member from the Asterisk console using

*CLI> queue add member sip/1002 to IN-Lanes

When I do that, the member does look a little different in the console, but still no change on the button itself:

CLI> queue show
IN-Lanes has 0 calls (max unlimited) in 'rrmemory' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 600s
   Members:
      sip/1002 (ringinuse disabled) (dynamic) (Not in use) has taken no calls yet
   No Callers

If I do the above while running FOP2 in debug mode, I get the following output:

127.0.0.1            <- Event: DeviceStateChange
127.0.0.1            <- Privilege: call,all
127.0.0.1            <- Device: Queue:IN-Lanes_pause_sip/1002
127.0.0.1            <- State: INUSE

127.0.0.1            <- Event: QueueMemberAdded
127.0.0.1            <- Privilege: agent,all
127.0.0.1            <- Ringinuse: 0
127.0.0.1            <- Penalty: 0
127.0.0.1            <- StateInterface: sip/1002
127.0.0.1            <- PausedReason:
127.0.0.1            <- Queue: IN-Lanes
127.0.0.1            <- MemberName: "Clerk02" <1002>
127.0.0.1            <- Interface: sip/1002
127.0.0.1            <- Membership: dynamic
127.0.0.1            <- CallsTaken: 0
127.0.0.1            <- InCall: 0
127.0.0.1            <- LastCall: 0
127.0.0.1            <- Status: 1
127.0.0.1            <- Paused: 1

Use of uninitialized value in hash element at script/fop2_server.pl line 10115.

Does that last line perhaps help narrow down this issue at all?

[nicolas]

Ok that is new then... it seems the queue add member will use the callerid from the sip device if not specified on the command. Try this:

queue add member SIP/1002 to In-Lanes as 'Clerk 02'

[nicolas]

Also, in order to log into queues from a phone, some kind of application is being used. That is not something that is built in anywhere... what applications are you using ?

[nicolas]

Another thing, having sip/1002 (in lower case) might also be an issue, you should try to use SIP/1002 instead, but I do not know if you have access to that phone application somehow to modify the command.

[nicolas]

Ok, the issue is with the quotes on the membername. I will fix this for the next minor release. If you catch me on the live help I can send you a patched version so you can try it out.

Best regards,

[Jeremy]

Ah, you've got it!
If I do "queue add member SIP/1002 to In-Lanes"

In-Lanes has 0 calls (max unlimited) in 'rrmemory' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 600s
   Members:
      SIP/1001 (ringinuse disabled) (dynamic) (Unavailable) has taken no calls yet
   No Callers

No quotes - and it DOES show up in the Queue button as "Clerk02" (the callerid).
Oddly, the "as" at the end of the queue add member line is not working at all - it rejects the command. No matter though.

So I either need to figure out how to ditch the quotes or get that patched version from you. I'm not sure what is adding them, though, since I took them out of the callerid string entirely, and the phone app doesn't specify it anywhere in its config (but maybe it is reading it from Asterisk's callerid and adding the quotes before sending the AMI command).

On a side note, I do have an older system elsewhere running Asterisk 1.8.7 with FOP2 2.26 where the queue buttons work fine even though it also has quotes in the member names.

Thanks for all your help thus far!!! I'll try and find you in live chat.

[nicolas]

New version uses JSON more extensively, and the JSON declaration breaks if quotes are not properly escaped. If you catch me on the live help I will be able to send you a version for you to try (actually, it is already done and works because I tried it)., or you can wait until 2.31.01 that I will release next week(ish).

Best regards,

[specomm]

I have the same problem also..

When i have upgrade the latest version all queue members not shown like before ..
please help me..

[nicolas]

First of all, clear your browser cache.

Second, did you configure buttons manually via buttons.cfg or similar? If so, you must be sure the queue buttons have a context and extension headers defined, otherwise they won't display its members.