Is FOP2 Compatible with VoipNow ?

jrechojrecho
in Support
We have several VoipNow servers is FOP2 compatible with 1.6.5 or 2.0.2.

You can find out more about VoipNow.com

Please advise.

I tried doing it the manual way because voipnow 1.6.5 is running asterisk 1.2 but when I go to the folder of fop2 I get:

Forbidden
You don't have permission to access /fop2/ on this server.

However the service is started and when I run the the test I get that the test is ok

I followed the instructions in both
http://www.fop2.com/documentation-installation-3.php and http://www.fop2.com/documentation-configuration-1.php

make install could not copy the html directory to the var/www/fop2 because in voipnow it does not exsist. So I manually copied it to the voipnow directory using: mv html /usr/local/voipnow/admin/htdocs/fop2

I see that everything seems to be in the correct place but could not get it to work.

Be advised that on voipnow the extension are after the customers account number example extension 100 for account ID 0002 is 0002*100 so the full extension number includes a (*) in it I am not sure if this will interfer with FOP2

I have aslo added the extension to the buttons.cfg but not sure if it would work here is what I put in:
[SIP/0003*600]
type=extension
extension=600
context=from-internal
label=M. Test name
mailbox=0003*600default
extenvoicemail=*0003*600@from-internal

Tell me what you think please

Kindest Regards

John

Comments

  • nicolasnicolas
    Hello,

    FOP2 is not fully compatible with Asterisk 1.2. It works, but not fully (for example, queue buttons do not work well). Anyways, it *does* show status, etc. You will have to do the manual install as you did and it should work. I remember the * for the device name when dealing with FOP1 development. I believe (but I did not test it) that FOP2 will work ok with those channel names.

    What was the problem after you copied the html directory? Were you presented with the login box? Were you able to login? Did you see the buttons as configured in the buttonfile ?

    Anyways, my advice would be to upgrade to Asterisk 1.4 as I will not support 1.2. I rather devote time to make features works on asterisk 1.6 and not in 1.2... The manager protocol in 1.2 required a lot of fake events and tweaks.

    Best regards,
  • jrechojrecho
    Sorry VoipNow 2.0 is running asterisk 1.6

    sorry all I get is when I go to the website name/fop2

    Forbidden

    You don't have permission to access /fop2/ on this server.
  • nicolasnicolas
    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,
  • jrechojrecho
    Nice !!! I was missing index.html

    I got it to work but noticed that if I use an extension like 0003*122 to login then I loose all of the menu options even if I have the extension login set to all. But when I use just 122 it works fine. This is not good because I will not be able to use this in multi tenant environment. Since the same extension number could be on multiple accounts.

    We are making great progress let me know what you think. I also noticed that your client does not work in IE8 I had to use Firefox to make it work in EI8 it sits on connecting to server attempt: 1 and never does anything.
  • nicolasnicolas
    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,
  • jrechojrecho
    I am running in multi tennant mode. You did not answer the question. Why are all the action buttons not showing up on the top.
  • nicolasnicolas
    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,
  • jrechojrecho
    Nicolás

    I installed it on the newest VoipNow 2.0.3 running asterisk 1.6.1.4
    And it comes up but I am having the following problems
    I can not dial,listen,whisper, transfer the only button that works is record everything elst deos nothing when I click on it.
    I am also not able to get the trunks to show up.

    I am using Linksys SPA962 phones to originate the calls on trixbox they work fine and I have all of your features but on this asterisk no luck :cry:

    Can you help ?

    Thanks
  • nicolasnicolas
    Hi,

    In asterisk 1.6 you have to grant the "originate" permission to the asterisk manager user.
  • jrechojrecho
    Can you please tell me how to do that. I am not that good with Linux
  • jrechojrecho
    Hi Nicolas first thank you for all your help Ias I told you I opened a ticket with VoipNow and here it their response


    Hello,

    The peers are kept in the mysql database and are handled by kamailio not asterisk, so it will not work.


    Best regards,
    Razvan Lixandru – Unix/Linux Support Engineer
    (IT/TS) Technical Support
    Rack-Soft SRL
  • ezytelezytel
    Hi guys,

    I'm running VoipNow in an HA array and already have FOP2 working on the system, except for the MySQL requirements like the dialpad etc.

    In order to activate these features, I contacted 4PSA, and their response floored me! They said ...

    "If you perform any of these changes to the VoipNow server, we will no longer be able to support it, sorry."

    What an arrogant and astonishing response! These are MY servers, and I've paid them nearly $2000USD in recent months to buy unlimited licenses etc, and to then be told that installing FOP2 would see them refuse me support in future is outrageous.

    So, the point of all this is to ask if it's possible to install FOP2 on a cPanel server running CentOS 5, and have it monitor my VoipNow servers as extra servers?

    Here's hoping this is possible.

    Kerry
  • nicolasnicolas
    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,
  • jrechojrecho
    Thanks or the answer but I am sorry I am more confused. We got it installed and I can see what each extension is doing but Nicolas and I could not get any action to work.

    We have plenty of servers available can you please tell me hoe you got actions to work ???.

    Thanks again
  • nicolasnicolas
    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,
  • ezytelezytel
    Hi Nicolás,

    I'll take the time to ask the guys at 4PSA about the Asterisk/AMI issue, and will post their response. It would certainly be good if we could get this happening. And your willingness to consider acommodating us is greatly appreciated.

    And you're right about the make-up of VoipNow. It is indeed a hybrid of Kamailio and Asterisk, and somehow, the guys at 4PSA have a very powerful system that works very, very well. But for all its power, it has some serious restrictions, and sadly, this is one of them.

    Oh well, swings and roundabouts, as they say ...

    Kerry
  • jrechojrecho
    I got the answer now all we need is for Nicolas to tell us how to make this work

    The AMI requests to VoipNow have to be done trough voipnowcallapid on port 1234, not directly to asterisk.

    An originate action should look like this for a local call:

    Channel: SIP/0003*002
    Context: from-internal
    Exten: 0024*001
    Priority: 1
    Callerid: whetever<1234567>
    Timeout: 25000
    Async: 1
    ActionID: 8d40accfbdc287025398

    The caller is 0003*002 and the callee is 0024*001.

    For an external call it should look like this:

    Channel: SIP/0003*002
    Context: from-internal
    Exten: 08040
    Priority: 1
    Callerid: whetever<1234567>
    Timeout: 25000
    Async: 1
    ActionID: 8d40accfbdc287025398
  • jrechojrecho
    I did do what they said
    The user name is admin and the password is whatever you set the admin password to in it is setup in the interface in Unified Communications -> System Preferences -> CallAPI.

    [root@as3 fop2]# /usr/local/fop2/fop2_server --test
    Flash Operator Panel 2 - No valid license found. Demo Mode
    Connection to manager OK!

    but now I see nothing no events to actions
  • jrechojrecho
    Actions only works once and after they are ignored until I restart the service fop2. Can you please help.

    Thank you for everything. And congrats on the Award you deserve it.
  • jrechojrecho
    Did anyone figure how to make it work ??
  • nicolasnicolas
    it is not compatible.
Sign In or Register to comment.

© Asternic Corp 2024