Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

FOP2 Community Forum

J

jgould

@jgould
Unfollow Follow
About
Posts
18
Topics
8
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Restore templates/permissions/groups/etc
    J jgould
    Support

    Hi. I moved from freepbx 13 to 15 using the freepbx backup & restore module. I tried to follow an article on using pre/post hooks which did appear to back up the necessary files/folders for FOP2. However on restore FreePBX didn't do anything with them unfortunately. So I tried to copy the files out of the backups to the necessary folders but then realized that was going to be difficult as I wasn't 100% sure of permissions and how to create the executable.

    So instead I tried downloading and installing FOP2 and register it. That went fine. Now I'm trying to get my old FOP2 Manager settings over to the new install. I tried to copy the folder/files over and just overwrite but that didn't work and led to all types of issues with the extension box going invisible (but still there) on the user portal side and users/buttons/etc disappearing from the admin side even though they existed (fyi, I had made sure that FOP2 was fully updated on my old system before migration as well).
    The most important tedious configuration for me is the templates and permissions. If I could at least get those back then I can handle the rest if needed.

    I still have access to the original system (VM) and the backed up files from /usr/local/fop2 & /var/www/html/fop2.


  • Control Volume level in FOP2
    J jgould
    Support

    I have agents that use a SIP softphone with a headset and monitor FOP2 on their laptop. They have the volume set to what I would consider a reasonable level to hear calls and and other sounds from the laptop. For some reason when on calls the callers can hear the "chimes" and "announcements" made from FOP2. The "Queue sounds" saying "caller in queue". And the Queue Alarm plugin that chimes when a call sits in the queue for to long.

    From my testing it doesn't appear the sounds are being fed into the microphone directly from the computer somehow. From what I can tell it seems that the sound is "leaking" from the ear cups of the headset and being picked up by the microphone.

    I've tried to find a way to adjust the FOP2 volumes for chimes and announcements but not having any success.


  • Shows all queues, but only alert on queues agent is member
    J jgould
    Support

    Sometimes agents in 1 queue get calls that need to be sent to a different queue. With extension & ring groups transferring that call is easy in FOP2. They just highlight and transfer. With queues that doesn't seem so simple because you have to decide if you show the queue or not.

    Lets say we have an agent who is a member of QUEUE1. They answer a call and find out that caller should have went to QUEUE2. This agent isn't a member of QUEUE2. Their FOP2 login doesn't show them QUEUE2. Why not? Well, mostly because the notifications for queue activity (chimes, flashing, text-to-speech, etc) trigger for ALL queues the agent has visible in FOP2, even if they aren't currently a member of that queue. Creating restrictions in FOP2 manager handles any permissions issue that we might have so we can restrict if the user can pickup the call, pause agents, etc. But getting constant aural and visual notifications for queues you aren't a member of can become very distracting and annoying.

    Is there any way to do this that I'm missing? What I think would be really nice would be something similar to ring groups but for queues. A second window that you can create that just provides the list of queue numbers. No agent list, callers in queue, etc. This way you could publish this to ALL users.


  • Answer Button
    J jgould
    Plugins

    Google gave me the following translation for the post above;

    I have checked that the plugin that allows to answer calls by sending a SIP notify is only prepared for chan_sip. If Pjsip is used, the action is Pjsipnotify. Is it possible to adapt it? The parameters are the same (in the case of Yealink), only the Action changes.

    Action: PJSIPNotify
    ActionID: <value>
    [Endpoint:] <value>
    [URI:] <value>
    Variable: <value>

    I wanted to say that I noticed the same. PJSIP extensions can't use the answer button and I'd like to see this fixed.

    Also, I'm personally having issues with yealink T46 phones with the latest firmware (and older firmware). Even using chan_sip the answer button hasn't worked for me. However T22P (now discontinued) work fine when using chan_sip. I must be missing something because I'd expect the T46 to handle this.


  • button_custom.cfg not handled correctly
    J jgould
    Support

    Well, still having 1 problem. Call Pickup from a queue on the remote PBX doesn't work. It does however work if I drag the call to my extension. Not sure why that isn't working.


  • button_custom.cfg not handled correctly
    J jgould
    Support

    Really strange. This happens in exactly the same way on both of my FOP2 installs.

    The first time I populated buttons_custom.cfg and reload FOP2 none of the queues showed up and I couldn't pause/unpause agents at the extension level (helpful to pause/unpause in ALL queues).

    I fixed the queue behavior as I mentioned above. However with what I just figured out it might have been a side effect of causing the button to be "removed" and "re-added".

    I moved the buttons_custom.cfg file out of /usr/local/fop2 into my home folder. I then reloaded FOP2 and went into the FOP2 Manager -> Buttons to make sure they were gone (they were). I then moved the file BACK to /usr/local/fop2 and reloaded FOP2. Went into FOP2 Manager -> Buttons and the buttons showed up again. I went to Groups and added them back to the group I created for them. At this point I was back to where I was before, the buttons showing up in FOP2. HOWEVER NOW THE PAUSE/UNPAUSE WORKS!!!

    The queuechannel field in FOP2 Manager STILL does not show up correctly! So there could possibly still be an issue I'm not aware of.

    I suspect that simply removing and re-adding the buttons_custom.cfg file might have solved both problems with the queues showing up and the pause/unpause at the extension level. Because what I had done by changing the queue from [SIP/2097] to [SIP/2097^xxx.xxx.xxx] was to remove the button, and then when I changed it back I was re-adding it.

    I still think something is wrong here. While it appears "fixed" for me, something stopped this from working correctly on initial creation. I'm not sure if the problem might resurface again if I try to add a new button for an extension on the remote system (who is a member of a queue) to buttons_custom.cfg.


  • button_custom.cfg not handled correctly
    J jgould
    Support

    I have two FreePBX servers and am adding the remote server extensions to the primary. On the remote server I ran;

    autoconfig-buttons.sh
    

    Which generates all the button details.

    I then put that into the primary servers buttons_custom.cfg

    For the most part it worked. However,queuechannel doesn't seem to be handled correctly.

    [SIP/2001]
    type=extension
    extension=2001
    label=John Smith
    mailbox=2001@default
    context=from-internal
    email=jsmith@domain.com
    queuechannel=Local/2001@from-queue/n|Penalty=0|MemberName=John Smith|StateInterface=SIP/2001&Local/2001@from-queue/n|Penalty=0|MemberName=John Smith|StateInterface=SIP/2001|Queue=2096&Local/2001@from-queue/n|Penalty=0|MemberName=John Smith|StateInterface=SIP/2001|Queue=2097
    customastdb=CF/2001
    extenvoicemail=*2001@from-internal
    queuecontext=from-queue
    autoanswerheader=__SIPADDHEADER51=Call-Info: answer-after=0.001
    server=XXX.XXX.XXX.XXX
    

    As you can see in FOP2Manager it cuts off after the word Penalty. What I'm experiencing is that these extensions aren't 100% working. For instance when I try to use the pause/unpause at the extension it doesn't work.

    I also have had an issue with the queues defined in buttons_custom.cfg. Initially they would not show up. After reading on this forum a bit I tried editing [SIP/2097] to [SIP/2097^xxx.xxx.xxx] which didn't work. I then went back in and changed it back and magically the queues showed up.

    FYI, yes the buttons were added to a group and should have been visible. Something isn't right here.


  • FOP2 Manager login fails, not enough privledges
    J jgould
    Support

    Read through THIS THREAD.

    Correct permissions are set on

    /var/lib/php/session
    

    Performed the mysql queries as well, and it looks correct.
    My admin account exists (the one I'm logging in with) and the SHA1 hash matches.

    [root@pbx]# mysql -p asterisk -e "select * from ampusers"
    Enter password:
    +----------+---------------+---------------+----------------+----------+---------+
    | username | password_sha1 | extension_low | extension_high | deptname | sections|
    +----------+---------------+---------------+----------------+----------+---------+
    | jgould   | xxxxxxxxxxxxx |               |                |          | *       |
    +----------+---------------+---------------+----------------+----------+---------+
    
    [root@pbx]# mysql -u root -p asterisk -e "select sha1('xxxxxxxx')"
    Enter password:
    +------------------------+
    | sha1('mypass')         |
    +------------------------+
    | xxxxxxxx               |
    +------------------------+
    

    At least on the system that uses the FreePBX internal database. The system that pulls accounts into user manager from AD does not show the AD user account I use for FreePBX GUI Admin access. I suspect those are stored differently.

    Again, all I did between it working and when it stopped was download the latest fop2.tgz to /usr/src, extract, run make file, restart service. This moved me from 2.31.04 to 2.31.11.


  • FOP2 Manager login fails, not enough privledges
    J jgould
    Support

    Did some digging. During the install/upgrade I went from 2.31.04 to 2.31.11.

    At the end I got this;

    New configuration file /usr/local/fop2/fop2.cfg.new installed. Original fop2.cfg preserved.
    New configuration file /var/www/html/fop2/config.new.php installed. Original config.php preserved.
    New configuration file /var/www/html/fop2/admin/config.new.php installed. Original config.php preserved.
    

    Looking at those 3 files I noted that they had some changes, specifically around authentication. So I moved the original files out of the way and renamed the .new files in their place. I also took note of the permissions on the original files and made sure the new ones going in their place matched.

    I have 2 FreePBX/FOP2 systems. One uses is using the FreePBX database backed for users (set in User Manager), while the other one that I mentioned in my original post uses an AD backend.

    Results
    Neither system seemlessly logs into FOP2 after authenticating to FreePBX with my Admin account. HOWEVER, the system using the FreePBX internal backed for users DOES accept the credentials when I provide them at the FOP2 Manager login screen AND the plugins section is shown. The system using the AD backend does NOT accept the credentials for the AD account that I use to login to FreePBX.

    My Guess
    This did work previously with FOP2/FreePBX. I suspect when FreePBX is set to use AD credentials it only worked before because FreePBX and FOP2 were "passing" the FreePBX login session along. That actually trying to type the login credentials into FOP2 Manager would have failed. And currently this passing of the session is broken due to a change on FreePBX or FOP2.


  • FOP2 Manager login fails, not enough privledges
    J jgould
    Support

    13258:@mvogel@cqsimple.com escribió:

    When you login to the admin are you seeing the plugins section?

    Nope. Not unless I log in using last method, bypassing FreePBX authentication mechanism.

    define('USE_BACKEND_AUTH',false);
    

  • FOP2 Manager login fails, not enough privledges
    J jgould
    Support

    Just updated to 2.31.11 and my FreePBX credentials are no longer allowing me to login to the FOP2 Manager section. Before the upgrade I was able to login without issue. After the upgrade of FOP2, and no other changes, I wasn't able to. Logging into FreePBX Admin first and then trying to login to FOP2, which used to automatically log me in, no longer works.

    What I've figured out so far in working on this;

    FreePBX has two sections where you can define user permissions. The old area is under Admin -> Administrators (with a big warning about how this is going away, mind you my FreePBX install isn't 100% updated right now). The other area is under Admin -> User Management. That is where everything is moving, or has been moved.

    I created a user in Admin -> Administrators and granted all the permissions. That login WORKS with FOP2.
    I created a user in Admin -> User Management and granted all the permission. That login DOESN'T WORK with FOP2.

    Now, keep in mind that before upgrade FOP2 just now it DID work with the user created in Admin -> User Management.

    I will note that my FreePBX is setup in Admin -> User Management -> Authentication Setting to use Authentication Engine Microsoft Active Directory. But AGAIN, this worked before the FOP2 upgrade.

    Also, adding to /var/www/html/fop2/admin/config.php

    define('USE_BACKEND_AUTH',false);
    

    allows me to login with the defined admin user/password. But that isn't what I want to do.

    What should I do? Everything else is working fine.


  • Queue Agents not ALWAYS shown
    J jgould
    Support

    Ok, I upgraded the FOP2 Server to Version: 2.31.04. CLI is now working again and was able to check the version.


  • Queue Agents not ALWAYS shown
    J jgould
    Support

    12335:@admin escribió:

    Did you upgrade the FOP2 server?? Not the FOP2 Manager, but the whole server?

    /usr/local/fop2/fop2_server -v

    What is the output?

    Yes. The admin page says;
    FOP2 Server Status: OK - Version: 2.30.03

    I'm trying to run /usr/local/fop2/fop2_server -v (as root user) and it won't complete the command, it just hangs...and top shows fop2_server using 99% CPU.

    Another server running this same setup does not have these issues. Very confused.


  • Queue Agents not ALWAYS shown
    J jgould
    Support

    Hi again. I'm finally getting some time to come back to this. I've cleared the cache on multiple computers. No difference. Here is an example of how strange this is.
    Login1: everyone but login user shows in queue
    Login2: only 1 user shows in queue
    Login3: different 1 user shows in queue
    Login4: all users show in queue except the user that was shown in login3
    and so on
    And then eventually sometimes the queue shows up correctly.

    After performing an upgrade through the admin section I clicked the "reload FOP2" button which I thought restarted the FOP2 service.


  • Queue Agents not ALWAYS shown
    J jgould
    Support

    So, sometimes when an agent logs into FOP2 the queues won't show all agents. For instance I have a queue with 4 static agents. They are all available but the queue only shows 2 of them. I reload the panel and then SOMETIMES all 4 agents show up, no other changes made. And I THINK (but haven't verified) that they will eventually just show up on their own after a certain amount of time, sometimes quite a while.

    FreePBX: 10.13.66-13
    Asterisk: 13.9.1
    FOP2: 2.30.03

    I don't manually define any buttons, queues, or anything like that. I installed and ran through the instructions on integration of FOP2 with FreePBX. I have however upgraded FOP2 and FreePBX over multiple versions over time.

    Any idea why this might happen and what I could look at to help determine the cause.


  • FreePBX panel integration?
    J jgould
    Support

    So I tried the steps in the FAQ.

    How to replace the FOP link in FreePBX to FOP2?
    You can do it by means of modifying your apache configuration file. In Centos the file is located in /etc/httpd/conf/httpd.conf. In Debian it is located in /etc/apache2/sites-available/default. For other distros you can check apache wiki. In this file add the following line:

    alias /panel/ "/var/www/html/fop2/"
    You will then need to copy the index.html file to index_amp.php in order to make FreePBX happy:

    cp /var/www/html/fop2/index.html /var/www/html/fop2/index_amp.php
    After the changes, reload Apache. From then one, all requests to /panel will be redirected to your FOP2 install.

    It doesn't seem to be working for me. I assume this was written for moving from FOP to FOP2. And since FreePBX now provide that other panel by default, I assume the steps aren't the same. I also tried making requests to http://server/panel but that didn't redirect to fop2 either.

    What I was hoping to do was direct the "Operator Panel" links in FreePBX to FOP2. This is a current release of FreePBX. Is this possible?


  • Extension buttons stuck?
    J jgould
    Support

    I guess things always work this way for me. Once I post something I fix it.
    I thought reloading FOP2 from the manager would be the same as starting and stopping the service from the CLI. However that didn't solve my problem. As soon as I ran;

    service fop2 stop
    service fop2 start
    

    The buttons cleared state and seem to be working fine again.


  • Extension buttons stuck?
    J jgould
    Support

    Hello,

    I installed FOP2 months ago in preparation for a bigger deployment and actually purchasing it. At the time everything seemed to work fine. I've since updated the server and updated FOP2. And before I purchased I was going to just make sure everything was still working.

    Well for whatever reason buttons for user extensions seem to be "stuck". For instance I types a feature code *73 and now my line 1 shows that I still have an active outbound call to that number. Another one has *79 stuck. Another has an outbound call to 11 digit North American phone #. I've tried reloading FOP2, reloading Asterisk, and a few other things but nothing worked.

    Any help on why this would be happening and how to fix it?

  • Login

  • Don't have an account? Register

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups