Queue Button presence not working on multiple server setup
Hi
We are using FOP2 in a multi tenanted way and with multiple asterisk servers. We are having issues with the queue button as follows:
Customer x is on server 1. When customer X logs in, all the queue members (stored in queue_members table using realtime architecture) are populated in the queue button, incoming calls to the queue show on the queue button and the presence indication works for the members of the queue button.
Customer y is on server 2. When customer y logs in the queue button shows no members even though they are assigned to the queue via a realtime table. If queue members are added through the fop2 interface they will show on the queue button but the member icon never shows when the member is in use even though the extension button for the same extenion/member does show all activity.
Incoming calls never show on the queue button either even though they are being routed through the queue.
Extension buttons work completely normally for customer y.
The asterisk configuration for the 2 servers is identical as the servers are deployed and controlled by puppet. The queue configuration for the 2 queues is the same apart from the queuename, timeout and context.
The queue buttons are set up as follows
[QUEUE/<queue-name>]
type=queue
label=<Distinct Label>
extension=<queue-name>
context=<customer-outgoing-context>
I tried adding server=x.x.x.x to the queue button from customer y but this broke the fop2 service.
Has anyone else encountered this problem and know what is going wrong and how to fix it?
Thanks in Advance
Ish
We are using FOP2 in a multi tenanted way and with multiple asterisk servers. We are having issues with the queue button as follows:
Customer x is on server 1. When customer X logs in, all the queue members (stored in queue_members table using realtime architecture) are populated in the queue button, incoming calls to the queue show on the queue button and the presence indication works for the members of the queue button.
Customer y is on server 2. When customer y logs in the queue button shows no members even though they are assigned to the queue via a realtime table. If queue members are added through the fop2 interface they will show on the queue button but the member icon never shows when the member is in use even though the extension button for the same extenion/member does show all activity.
Incoming calls never show on the queue button either even though they are being routed through the queue.
Extension buttons work completely normally for customer y.
The asterisk configuration for the 2 servers is identical as the servers are deployed and controlled by puppet. The queue configuration for the 2 queues is the same apart from the queuename, timeout and context.
The queue buttons are set up as follows
[QUEUE/<queue-name>]
type=queue
label=<Distinct Label>
extension=<queue-name>
context=<customer-outgoing-context>
I tried adding server=x.x.x.x to the queue button from customer y but this broke the fop2 service.
Has anyone else encountered this problem and know what is going wrong and how to fix it?
Thanks in Advance
Ish
Comments
If you need this to work, you *must* use the server directive in the queue buttons. And you must be using the latest fop2 version.
Best regards,
I tried adding the server option again and it worked this time.
I must have done some human error last time and misspelt server or something...
Thanks for your help