[QUEUE/1]
type=queue
label=BuZe I 30
extension=1
context=out

The above is correct, the important thing is to have extension and context defined as above. That setup WILL work, be sure to restart fop2 just in case, and reload the web page too.

mysql> select name,context from queue_table;
+------+---------+
| name | context |
+------+---------+
| 1 | |
+------+---------+

The context in the realtime database is empty. Shoud I set one? Or use the context from the dialplan where the calls come in or which one?

The extension is the name of the queue:

[QUEUE/1]
type=queue
label=BuZe I 30
extension=1
context=out

is that ok?

It show queus and agents, but updates only when poll_interval takes place (I believe).
Udo

If so, be sure your queue button has the extension and context keywords...

otherwise the button will not update (this is a requirement for the last fop2 version).

... adding a queue member in realtime will not make it appear in fop2, unless you signal the manager with a reload or you modify your realtime application to fire some manager events.

I'm facing exactly this problem: Queues and members in realtime, but they are not updated in FOP2 (latest version, licensed). What manager events do I need to 'fire' to signal it to FOP2 ?

Udo

There are some instances of realtime that will not work as expected, for example: adding a queue member in realtime will not make it appear in fop2, unless you signal the manager with a reload or you modify your realtime application to fire some manager events.