Hi,

That error is from apache. I cannot tell you exactly how to fix it... verify your apache access and error log files. Maybe you are specifying an incorrect path, or there is some directive restricting access to that directory. Maybe you do not have a proper index file (as configured in apache)... if the later, you can try to browse: http://your.url/fop2/index.html and see if that works.

Best regards,

For multi tennat setup you have to use panel contexts and login with the extension number only.

http://www.fop2.com/documentation-confi ... OP2Context

And the client DOES work with IE8. Not sure why you are having troubles...

Best regards,

Yes I answered the question, but maybe I was not clear.

You have to use multi tenant setup on FOP2 as described in the documentation I pointed. In fop2.cfg something like:

[0003]
user=600:1111:all
buttonfile=tenant-0003.cfg

[0004]
user=600:2222:all
buttonfile=tenant-0004.cfg

And then the button file tenant-0003.cfg

[SIP/0003*600]
type=extension
extension=600
context=CHANGE_TO_APPROPIATE_CONTEXT
label=M. Test name
mailbox=0003*600default
extenvoicemail=*0003*600@from-internal

And the button file tenant-0004.cfg

[SIP/0004*600]
type=extension
extension=600
context=CHANGE_TO_APPROPIATE_CONTEXT
label=John Doe
mailbox=0004*600default
extenvoicemail=*0004*600@from-internal

Finally, you load the fop2 page specifying the context/tenant you want to see:

http://your.url/fop2?context=0003

When you do that, you will login with the extension number for your tenant, for example 600, and the password for the 600 user in that particular context (1111). If you set in the url context=0004 then the password for user 600 will be 2222.

That is the correct way. As 003*600 is not an extension but part of a device name. You are not dialing 003*600 from your phone right?

You have to configure buttons with extensions numbers that can be dialed, and their proper context for your tenant. (PLEASE CHECK THAT in your asterisk dialplan as you copied a config with "from-internal" context, but I do not think that you will use that same context for different tenants). The device name for the button seems correct. (Again, you must probably use a distinct context per tenant)

If you are not logging in with an extension number that has also a button defined with that same extension number, then you are not going to see the action buttons, because YOU WONT BE ABLE to perform actions at all as there won't be a known originating device for the actions to be performed.

The extension you use to login is matched with an extension on the button list, and from there it takes the device to use... so if you originate a call, fop2 know WHAT device to use to originate that call.

Best regards,

Hi,

In asterisk 1.6 you have to grant the "originate" permission to the asterisk manager user.

I do not know if every voipnow version uses kamailio or not. But to make things clear, currently FOP2 works with Asterisk via the AMI. It does not interact with kamailio or any other proxy or voip software than Asterisk itself.

With jrecho we were able to monitor activity, but he was not able to perform actions. And there is no solution to that as in that voipnow setup Asterisk does not know about the devices.. FOP2 says: originate a call from SIP/XXXX*YYYY (that is listed in the asterisk's sip peers list), but Asterisk responds that there is no such peer/device.

I will NOT add kamailio or specific product support like the one required by voipnow. If you are happy with monitoring, then it might work well, but do not expect actions to work at all. FOP2 can be run on a separate server running cpanel or whatever, and monitor external asterisk boxes. But you will have to configure the buttons manually.

If voipnow provides a way to originate calls using the Asterisk Manager, and they document exactly how to do that, then I *might* consider adding support for it, or maybe I do not have to touch anything but just configure the buttons correctly.

I am sorry, but FOP2 is a $40 product advertised to work with Asterisk. It is not a $999 product advertised to work with Kamailio.

On the bright side, I wrote automatic configuration scripts for freepbx, thirdlane, and some others Asterisk GUI's that I do not remember their names. And I will be writing a FreePBX module to configure users and permissions for FOP2. And I am updating FOP2 so it can be integrated and used as an Agent console for Asternic Call Center Stats or any other Asterisk software. It is an experimental API but it works, so developers will be able to integrate it with their products.

Best regards,

I am sorry, I cannot tell you how to make actions work with that. 4psa might be able to tell you, not me.

As per your post, they say is that it is NOT possible. *They* said that, not me. It is not that voipnow is broken, but that they are not using plain Asterisk but a hybrid Kamailio and Asterisk config.

If voipnow tells you how to originate a call or redirect a call using AMI, then copy that reply/documentation here in the forums and I will see how to configure fop2 buttons to work. If they say that it is impossible to do that using AMI, then fop2 will never work for performing actions on that setup. It is not a question on device names, it is a question on what software is driving/controlling the calls. In your setup is kamailio, not Asterisk. As to why Asterisk lists peers globally, display AMI events but cannot originate a call or list individual peers, it is again a matter of 4psa/voipnow and not fop2.

AMI = Asterisk Manager Interface

Best regards,

it is not compatible.