fop2 on Elastix 2.2

moose

So i installed fop2 on Elastix 2.2 64bit but didnt use the "addons" section to install it, i used the tarball for centos (licensed version).

I've got some issues with:-
- Transfer to voicemail (the button is there and not grayed out but it doesn't forward to voicemail, clicking it does nothing and turning on logging in fop2 shows nothing when you hit the button)

My question is, can i just go and reinstall it from the Elastix addons to see if that resolve the issue? Do i need to do any manual uninstalling first?

nicolas

It is just a minor configuration issue, also it is sometime a misunderstanding.

FOP2 cannot and will not alter your dialplan in any way. That means that if you do not have configured in your dialplan a special extension to go directly to voicemail, then you cannot configure FOP2 to do such thing.

To setup the voicemail extension for a button, in the button config itself you have to set something like this:

extenvoicemail=*100@from-internal

That means that for that particular button, to reach comedian mail directly you must dial *100 on the from-internal context.

So, to troubleshot, first run this command on your server to find out what voicemail extension is being configured:

/usr/local/fop2/autoconfig-buttons.sh

Inspect the output, look for the extenvoicemail for some of your extensions. What do you see there? Then try, from *your phone*, to dial that extension you see. Does it go to voicemail?

Maybe it is a bug in the FOP2 manager that is not setting the correct voicemail extension (something you can change in the buttons page itself), or perhaps it is just not configured in your system..

moose

So I can dial *120 and I do hit comedian mail so that does work.

If i run /usr/local/fop2/autoconfig-buttons.sh the relevent line for 120 is shown as

extenvoicemail=*120@from-internal

fop2 manager has "*120@from-internal" in "Extension to Voicemail" section

So that all appears correct, what would be the next step to get troubleshoot this?

---

Edit: all good, got it sorted

nicolas

There are two places to look for debug information, on the client side (browser), by opening the javascript console (chrome, firefox, safari and I think even latest IE all include a debug/javascript console by default). Open it up and attempt a transfer to voicemail and look at the browser console to see if an action is being delivered to the server.

The other part is the server side, you can start fop2_server with debug enabled to have a log file, to do so, edit /etc/sysconfig/fop2 and add "-X 511 -l /var/log" to your current OPTIONS line (that means that you must leave whatever you have already defined and add the aforementioned parameters). So, the OPTIONS line should end up looking something similar to this:

[fixed]
OPTIONS="-d -X 511 -l /var/log"
[/fixed]
Then restart FOP2 with the command

[fixed]
service fop2 restart
[/fixed]

Then, when you attempt a transfer to voicemail, inspect the /var/log/fop2_debug.log and search for the string 'tovoicemail' and look all of the events/messages that happens after that.

Best regards,