Strange Label issue - FOP2 Forum

13 years ago

loki365
15 Mar 2011

Hi ,
I've been experiencing a weird issue with FOP2 on one of my asterisk PBX's. Upon initial install and configuration of buttons in FOP2, the labels of all buttons are displayed as configured. However, once a connection is established with Asterisk, the labels of the first 4 buttons are discarded and the extension number is displayed in the button. I have tested it with versions 2.11 and 2.20(Final). I have also installed FOP2 on various servers and experienced the same issue. I therefore gather that the issue relates to Asterisk but I'm not sure what to look for within Asterisk.
Any ideas or suggestions would be greatly appreciated.
Thanks
admin
15 Mar 2011 Administrator

Hi,
FOP2 renames labels to queuemember names if you have Local type queue members. Do a "queue show" in the asterisk cli and see if you have Local type queue members that have the same extension / context as your buttons that are being renamed..
loki365
17 Mar 2011

Thanks that sorted out the problem
siax
14 Aug 2011

I had this issue and could solve it (temporarily) by removing the Local/XXX queue member entries (with wrong name) from my queues.
We have Device & User mode and the users are named "First_Name(Space)Last_name"
When re-adding the agent via FOP2.21 beta to his queues, the last letter is removed from his name, when I hit "queue show" in CLI the again. As a result on the next FOP2 login, the labels are again wrong.
why does FOP2 put the name into the queue member list anyway?
when users log into queues via feature code or when I add them via cli they are added without name and all FOP2 labels remain fine.
edit: slightly different issue
admin
15 Aug 2011 Administrator

Fop2 sets the member name for consistency with FreePBX feature codes, otherwise you will end up with different name not only in the realtime views, but also on the queue_log file. FOP2 should use the name as set in FreePBX itself, and spaces in names should be there, it seems that those are breaking up somehow your queue member if I understood correctly? If you add via fop2admin 1.2.6, you see "John" instead of "John Doe" in a "queue show" in the asterisk cli? What is the output from /usr/local/fop2/autoconfig-buttons-freepbx.sh ? Does it use "John" or "John Doe" in the queuechannel directive for your buttons?
siax
16 Aug 2011

ok I try to explain again...
Asterisk 1.6 and FreePBX 2.8.1.4 on Centos (AsteriskNOW)
FOP2.21 beta (language set to German), fop2admin 1.2.6
Test user: 1234 <John Doe>
Test queue: 4567 Test
if 1234 <John Doe> logs into one of our queues via FreePBX feature code 4567*
CLI> queue show
4567 has 1 calls...
Members:
Local/1234@from-queue/n (dynamic) (In use) has taken no calls yet
if 1234 <John Doe> is being added to a queue via cli "queue add member Local/1234@from-queue/n to 4567"
CLI> queue show
4567 has 1 calls...
Members:
Local/1234@from-queue/n (dynamic) (In use) has taken no calls yet
if I go to FOP2 (not fop2admin!!!) and click on the user button status icon and select "add to Test" to put 1234 <John Doe> into the "Test" queue
--> at this point John Doe's FOP2 Button changes to "John Do" immediately, also he is being added as "John Do" to the Test queue
CLI> queue show
4567 has 1 calls...
Members:
John Do (Local/1234@from-queue/n) (dynamic) (In use) has taken no calls yet
edit: issue was a little different
admin
16 Aug 2011 Administrator

Hi,
As far as I know, since FreePBX 2.8 the macros for adding members include the member name option to Local/xxxx channels, for some reason your version is not doing that. Is that a stock freepbx? An update over older versions? Are you sure you did not modify those macros to remove the membername option being passed to addqueuemember?
siax
16 Aug 2011

FreePBX has been updated from 2.7 to 2.8 via the Upgrade Tool, no manual changes...
I'm using User & Device mode, if that is of any help...
thanks for your help!
admin
16 Aug 2011 Administrator
The user&device mode is the issue here, I do not know if this is an overlook in FreePBX or if its by design, but the macro-agent-add macro includes the member name parameter in normal mode, and does not pass the value when in user and device mode:
```
exten => s,n,ExecIf($[${LEN(${THISDEVICE})}!=0]?AddQueueMember(${ARG1},Local/${CALLBACKNUM}@from-queue/n,${DB(QPENALTY/${ARG1}/agents/${CALLBACKNUM})},,${DB
(AMPUSER/${CALLBACKNUM}/cidname)},${THISDEVICE}))

exten => s,n,ExecIf($[${LEN(${THISDEVICE})}=0]?AddQueueMember(${ARG1},Local/${CALLBACKNUM}@from-queue/n,${DB(QPENALTY/${ARG1}/agents/${CALLBACKNUM})}))
```
The last parameter is the state interface parameter, I understand that you cannot pass that parameter to the command if you do not know the device to monitor, but the member name is still present in astdb in whatever mode you are. You can change the 2nd line to include the member name (and exclude the device state) by changing it to this:
```
exten => s,n,ExecIf($[${LEN(${THISDEVICE})}=0]?AddQueueMember(${ARG1},Local/${CALLBACKNUM}@from-queue/n,${DB(QPENALTY/${ARG1}/agents/${CALLBACKNUM})},,${DB
(AMPUSER/${CALLBACKNUM}/cidname)}))
```
However, I do not know if the member name was omitted by design or by mistake.
siax
18 Aug 2011

Sorry, I did a mistake... the issue is slightly different and it has nothing to do with the spaces...
I actually did not really created a test user John Doe, but used an existing test user, who's last name was only one letter.
please check my edited post above. Not the whole last name is being removed. It's the last LETTER only. Tested with different users, different name lengths