Hi Nicolas,

The only buttons we have configured in the manualy buttons.cfg file is the external numbers. Everything else is done via the fop2admin module. So if I comment out the auto-gen script users can't log in (because their logins aren't generated by the autoconfig-users-freepbx.sh script).

I did briefly stop this warning once fop2 starts in debug mode (it's the first output I receive after about 1 second pause):

./fop2_server -X 15 | tee /tmp/fop2.log

Use of uninitialized value in quoted execution (``, qx) at /tmp/par-root/cache-5b978559a4be4f63ec5bdb8fa23daafc97123f45/inc/lib/FOP2/License.pm line 591.

So at the moment it's all working again, seemingly after a reboot of the server, but there is no real explanation as to why it is working. I have noticed the following difference:

At the moment (with the attended transfer working) I can see:
i) The fop2 panel is showing a "Line 1 inactive" message for all the buttons (both extensions and buttons we use to forward and transfer calls to external numbers) and changes state as calls are made accordingly. Before this was missing.

ii) Before when it was occasionally working, when you click on one of the external numbers, the Transfer to voicemail button would be greyed out as it is obviously not an extension with voicemail. At the moment, it doesn't do that, but attended transfers are working.

iii) Probably the best way to describe the erroneous behaviour is when I have, say, extension 201 dealing with a call and I log in to fop2 with extension 202 and then try to transfer a call (which obviously fail because you're not logged in as 201). However, although I have been testing with different users I am pretty sure I was testing previously with the correct user to the SIP account I was using. Someone else mentioned some potential issues with using devices & users mode on fpbx (which is what we're using). Could it be that or should I just lay off the sugar?

Thanks,
Carel

In case it helps someone else, in the fop2 admin module we had one of more groups selected for each user, which for some reason didn't match up with the groups in the buttons.cfg file. So, changing the users to have NO group membership disabled the group checking which meant the buttons were then displayed.

C

Hi Nicolas,

Here's one of the buttons which is in buttons.cnf:

[SIP/02031234567]
type=extension
extension=02031234567
context=transfer
label=Test Button
group=GROUPA

Kind Regards,
Carel

Hi,

Asterisk: 1.8.20.0
FreePBX: 2.10.0
FOP: 2.2.27 64bit
OS: Centos 6.4 (64bit)

Issue: From a fresh restart (amportal restart and then fop2 restart), you can normally get one attended transfer to work. After that subsequent attended transfers doesn't work and it looks like the buttons are completely unresponsive. We have a number of external numbers we have buttons configured for to transfer out to, and usually once you click on one of these buttons the Transfer to Voicemail button is greyed out, but when the buttons become unresponsive, this does not get greyed out as normal.

Any ideas on what may be causing this? The logs when running fop2 in debug does not show any command being sent to asterisk other than the regular ping.

Thanks,
Carel

Hi,

Is there a way to set up quick dial buttons on fop2? We want users to be able to transfer calls to an external number in the same way they would do to an internal extension on using the fop2 panel.

Any ideas?

Thanks,
Carel

Hi,

We are trying to mimic a customer's hosted fop2 setup with their own on-site config. fop2 is up and running fine, but they have buttons they use to forward calls to external numbers. Specifically it would look like this:

• They have different groups for each of their external numbers (which looks like we can get to work with group= parameter)
• They also have extension buttons that are linked to the external numbers so their agents would click on the button, then press either the attended / unattended xfer button.

Any ideas on how to make this work? From their old config we have this type of button config, but fop2 seems to ignore it. There's no such sip device, so I'm not sure whether we need to be adding it in, but I've not really had any luck doing that yet. When I've tried to replace the device name to an existing SIP device (e.g. SIP/201) fop2 forwarded the call to 202@from-internal instead :-/. The config will be changing on a regular basis so we'd like to avoid hacking sip devices if possible.

[SIP/02081234567]
type=extension
extension=02081234567
context=transfer
label= Company X
group=Group Y

Any ideas?

Thanks,
Carel

next guy reminded, thanks! Hanging my head in shame for not having thought about this when I first had the problem 3 days ago....

C