itdept2015

Member

Last active 6 years ago

  1. 8 years ago
    Thu May 12 21:07:39 2016

    Oops... I realized what I should do after that ;) Here's the message after I entered the right interface.

    [root@localhost ~]# /usr/local/fop2/fop2_server -X 15 -i em1
    Flash Operator Panel 2 - Invalid license for this machine.
    Flash Operator Panel 2 - Invalid license for this install (i).
    Flash Operator Panel 2 - Invalid license for this install (hostname mismatch)
    Flash Operator Panel 2 - Invalid license for this version.
    You must reactivate your license using the --reactivate option.

    And if I run the --reactivate:

    [root@localhost ~]# /usr/local/fop2/fop2_server -i em1 --reactivate
    Reactivation failed! (ERROR)
    
    You must purchase the annual maintenance fee in order to upgrade your
    version ( https://www.fop2.com/buy.php ).
    
    Or you can keep running the version you have installed now.

    I don't want to steal the license from my production server right now, but if that server did fail and I switched to this secondary server, what commands would I want to run to switch it over? Do I HAVE to unload the license from the primary? (what if it is totally dead?)

  2. Thu May 12 21:02:44 2016

    eth0: error fetching interface information: Device not found

    FOP2 was unable to find an eth0 interface to bind the license to.
    Please specify a valid NIC name with the -i command line parameter, for example:

    /usr/local/fop2/fop2_server -X 15 -i eth1

  3. Tue May 10 19:36:55 2016

    I have a second FreePBX server that we will either put in High Availability, or just have on hand to switch out. I know I will need a second license for this server, but I'm fine with having limited buttons for now. What I'm trying to nail down is the exact steps required to get FOP2 up and running after a restore.

    I'll tell you what I did so far:

    I did a full backup of the original server and used that to restore to the second PBX. This included:
    /usr/local/fop2/fop2.cfg
    /etc/sysconfig/fop2
    /etc/rc.d/init.d/fop2
    /usr/local/fop2/fop2settings.db
    (And all the other default directories and MySQL tables)

    After restore, I am able to get into the https://second_PBX_ip_address/fop2/admin, but it says the "fop2 server is not responding".

    On SSH, I ran "service fop2 status" and got "fop2_server dead but subsys locked". If I stop and start the service, I get the same thing.

    I reinstalled fop2 by wget'ing the latest tgz, unpacking and the "make install", but still get the same error. I rebooted and got the same error.

    I saw your post about running "netstat -lnp | grep 444" to see if any other service is taking the 4443 port, and got no listing.

    What else could be the issue?

  4. 9 years ago
    Wed Nov 11 00:43:04 2015
    itdept2015 posted in FOP2 dial box trouble.

    UPDATE: Ends up it wasn't a bug at all. Restrictions wasn't the problem either. This was a PEBKAC (problem exists between keyboard and chair). First off, the reception phone I was trying to log in with was not yet provisioned (set up in FreePBX, but phone was not plugged in). Thus the dial option would not show.

    Then, once I noticed that and provisioned the phone, I was clicking dial from my desk and the reception phone was getting the ring, 300 feet away (I was expecting my phone the ring, stupidly), so I wasn't noticing it was actually working. It just looked like it wasn't responding, but it was waiting for the phone to be picked up.

    Perhaps a little indication to pick up the phone, or phone not provisioned would be nice (if that data is accessible to fop2). If not, then at least people will see this forum and slap their foreheads like I did. Cheers!

  5. Thu Nov 5 17:07:11 2015

    Thank you! Now I couldn't find any documentation on the format of these "Channels". I saw that someone posted a quote from you that:

    So, suppose you have: SIP/100 and SIP/200 and you want to monitor state for both channels in just one button, then edit SIP/100 extension button and add SIP/200 to the channel field. And then disable SIP/200 if it appears in the button page as a separate one.

    First datum that is good to know: format for sip extensions is "SIP/200".
    Next datum that is good to know: you have to disable the secondary extension.

    Now what I don't know: how do you list multiple channels? I tried SIP/100|SIP/200 and SIP/100,SIP/200 but neither worked. (I have a phone with three extensions).

    Next Q: Can I have the phone originate from an available extension, or does it have to be only one?

  6. Tue Nov 3 18:23:06 2015

    Feature Request:
    I have several users who need two line extensions, such as Support which has a second extension on a ring group for incoming support calls (they are not interested in queues yet). This causes multiple buttons to show up in FOP2, and sometimes they are not listed next to each other, since FOP2 sorts by extension number (maybe this could just be handled by providing a sorting option--sort group by name or extension). But you could also tie these multiple extensions to one button. It could be a global option, though I could see the odd-man-out requiring more granular control (one extension in a Support group and another extension in an Internal Calls group).

    And if they were tied to one button, ideally there would be control over which extension is their primary preferred extension for incoming calls (ability to sort the order that they appear in the button).

    Food for thought. Would also be a nice feature for receptionists, so they can find users faster and not have multiple entries for each.

  7. Sun Nov 1 00:43:34 2015
    itdept2015 posted in FOP2 dial box trouble.

    @admin Did you create custom permissions? What is the output from

    /usr/local/fop2/autoconfig-users.sh | grep perm

    ?

    No recordings is to keep people from recording, but using "all". I ended up dropping this and giving detailed permissions to the appropriate templates. So I'm not using that anymore.

  8. Sun Nov 1 00:41:37 2015
    itdept2015 posted in FOP2 dial box trouble.

    @admin Did you create custom permissions? What is the output from

    /usr/local/fop2/autoconfig-users.sh | grep perm

    ?

    I got this:
    perm=norecordings:record:

  9. Fri Oct 23 17:50:23 2015
    itdept2015 posted in FOP2 dial box trouble.

    Yes, the other buttons show. All show and hide as I edit their permissions. Just not "dial".

  10. Thu Oct 22 23:53:48 2015
    itdept2015 posted in FOP2 dial box trouble.

    I have several users that even if I give them "all" permission, they still don't have a dial button in FOP2. The phone is provisioned and everything is working except the dial button will not show (this is a licensed FOP2). I run the autoconfig-users-freepbx.sh and currently get this for that user (I switched it back off of "all" to the permissions I want that user to have):

    user=400:1324:dial,hangupself,pickup,transfer,transferexternal:All Extensions:configonreload

    What else can I check to debug this?

View more