FOP2 ADDMEMBER/REMOVEMEMBER issue

10 years ago
macros
2 Jul 2014
HI,
Every time I add member to a queue in a FOP2 I get following messages in queue_log file:
```
1404293734|MANAGER|5101|Local/2101@from-queue/n|ADDMEMBER|
1404293738|MANAGER|5101|Local/2101@from-queue/n|REMOVEMEMBER|
```
But when i add member through feature code *455101 i get following messages:
```
1404293806|1404293803.0|5101|Local/2101@from-queue/n|ADDMEMBER|
1404293806|MANAGER|5101|Andrey Dudnikov|ADDMEMBER|
1404293819|1404293817.1|5101|Local/2101@from-queue/n|REMOVEMEMBER|
1404293819|MANAGER|5101|Andrey Dudnikov|REMOVEMEMBER|
```
As you can see when I use feature code Asterisk use MemberName in ADDMEMBER/REMOVEMEMBER messages, and I can find this in a Asternic CC Stats Pro by the agent name. But when I use FOP2 GUI I should find it by Agent/[number] in Asternic CC Stats Pro.
Is there a way to change queue_log messages to use MemberName when I add agent through FOP2 GUI?
admin
2 Jul 2014 Administrator

What fop2 version are you using? FOP2 has the membername feature added since a long time ago, I asume you either have manual and incomplete configurations, or a really old version?
/usr/local/fop2/fop2_server -v
To set the member names, among other settings for add/remove members, you have to add the queuechannel directive to your button configuration (if you do that by hand, autoconfiguration scripts for freepbx will do that automatically):
queuechannel=Local/101@from-queue/n|Penalty=0|MemberName=Reception|StateInterface=SIP/101
macros
3 Jul 2014

# /usr/local/fop2/fop2_server -v
fop2_server version 2.27
I'm using it with Asterisk 11 and FreePBX 2.11. Buttons were configured with autoconfiguration, and in table fop2buttons there is MemberName filled up with name, but any way in messages there is just Local/2101@from-queue/n not the name.
admin
4 Jul 2014 Administrator

Asteirsk does not log member names for add/remove and pause events in its default configuration. It is not a fop2 problem. Look at the log_membername_as_agent parameter for queues.conf, or use tailqueuelogFreePBX28 that finds the events with Local/xxx and replace that with their names in the mysql database.
This is for the asterisk wiki:
Added new option log_member_name_as_agent, which will cause the membername to be logged in the agent field for ADDMEMBER and REMOVEMEMBER queue events if a state_interface has been set.

macros

9 Jul 2014

I can assure you that there are no any log_member_name_as_agent or log_membername_as_agent parameter at my configuration. I'm using Asterisk 11.7.0 and FreePBX 2.11.0.38.

[root@CCPBX parselog]# 
[root@CCPBX parselog]# grep -r member_name /etc/asterisk/
[root@CCPBX parselog]# grep -r membername /etc/asterisk/
[root@CCPBX parselog]#

I've tried out tailqueuelogFreePBX28 and now Asterisk queue log messages doubles:

1404895589|1404895587.0|5101|Local/2101@from-queue/n|ADDMEMBER|
Check agent Andrey Dudnikov
Exists in cache Andrey Dudnikov = 2
1404895589|MANAGER|5101|Andrey Dudnikov|ADDMEMBER|
Check agent Andrey Dudnikov
Exists in cache Andrey Dudnikov = 2

1404895762|1404895759.1|5101|Local/2101@from-queue/n|REMOVEMEMBER|
Check agent Andrey Dudnikov
Exists in cache Andrey Dudnikov = 2
1404895762|MANAGER|5101|Andrey Dudnikov|REMOVEMEMBER|
Check agent Andrey Dudnikov
Exists in cache Andrey Dudnikov = 2

admin
10 Jul 2014 Administrator

tailqueuelog does not alter your queue_log file at all. If you have double entries in queue_log, they are produced by asterisk or some other application, but NOT tailqueuelog, that passively monitors that file.
macros
11 Jul 2014

I just need some help in FOP2 and Asternic CC Stats Pro that I bought.
admin
11 Jul 2014 Administrator

A better line of support would be the live help at www.fop2.com, so you can describe your issue and we can narrow down quicker with questions. Broad or general questions/problems are almost impossible to answer, the chat let us quickly get to the point, unlike email or forums that are slower.