FOP2 Community Forum

I am not sure if I understand your question. The point is that in general, call centers have Agents, and those agents have names, and those names are not fixed to a particular device. If you have queue members, and those are fixed, then use that member name when you add queue members (FreePBX does this by default for example). It is not that hard to do, or is it ? What I do not see is the point of having an extension 100, then adding a queue member Local/100 with a name different than the one assigned to the extension itself. In any case, you have a good point, perhaps button renaming should have a toggle switch to turn it off.

In the original announcement I mentioned clearly the difference and that fop2 actually had less features (at that time) than fop1, this was on june 2009: View Post 2 There is a strong reason not to use regular expressions, just run fop1 and fop2 servers side by side and compare cpu usage. The benefits of regexp buttons are limited and do not justify at all their existance. You can substitute the AUTO/SIP with a proper autoconfig script. Here is a rather crude example, there are other in the online doc: #!/bin/bash for A in asterisk -rx "sip show peers" | awk '{print $1}' | cut -d/ -f1 | sed -e '1d' do echo "[SIP/$A]" echo "type=extension" echo "extension=$A" echo "context=from-internal" echo "label=Extension $A" echo "mailbox=$A@default" echo "extenvoicemail=*$A@from-internal" done (Not tested, just typed it here as is), then you execute this in your button configuration file via an #exec command, and you will have automatic sip buttons for your panel.

opent chrome javascript console and look for the error there, I think there is a bad named div (custom_toolbar) or similar, that has a typo. It is easy to fix, but I do not remember the name, it will popup in the javascript console. Just fix that name in the index.html file and it should work.