FOP2 Community Forum

Hi,

Yes, they are trying to use FOP2 to select which call to pick up from the queue sometimes. Yes, they can answer the phone directly, but they cannot directly pick up call #2 or #3 from the queue (etc.).

The problem is that the client consists of end users who will not know how to turn on debug mode. I guess I can turn it on for them and do from there.

Mark

Hi,

A client has reported issues with FOP2. There is one queue for operators, and the client reported that only the top call in the queue could be answered. If an operator tried to answer any other call from the queue, the caller was disconnected.

They are asking for an immediate resolution, so any help would be greatly appreciated.

Thanks,

Mark

Yes, thank you very much!

Hi,

I just purchased a license and entered the code, and now I can't access FOP2. It just stalls at connection attempt #1. I could access in lite mode (after help from Nicolas resolving a configuration error).

Test shows:

/usr/local/fop2/fop2_server --test
Flash Operator Panel 2 - Valid License (1)
Connection to manager OK!

I need to have this up ASAP, so any help will be appreciated.

Thanks,

Mark

Hi,

We also might need to transfer a license (as we are moving from one server to another). The problem is that we want to get the new server set up and running first (as a clone of the old server), and make sure everything works before pointing traffic to the new server. So, for a few hours, we might need FOP2 working fully on both servers.

What is the recommended procedure for this kind of transfer?

Also, speaking of licenses, I saw something about yearly renewals (or something similar). Is the license fee one-time or annual?

Thanks,

Mark

Hi,

I have a full version running on an OpenVZ VPS. We need to move that VPS to a different host node, where the VPS will have a different IP address. Will this kill the license? If so, what do we need to do in order to make the license work on the new host node?

Thanks,

Mark

Problem solved via live support chat...again, the best support I've seen anywhere. Even cheerful support when the problem is user error.

Thank you.

Hi,

I am running FOP2 (registered version) on an OpenVZ VM. I had to reboot the VM. After that, I could not log into FOP2. I checked and found out that it is not running. And I cannot start it. It just hangs on:

Starting Flash Operator Panel 2:

...and it never fully starts.

It worked fine before the reboot.

What could be causing this?

Thanks,

Mark

Hi,

It's definitely not DND. That has been checked multiple times, and it happens on multiple extensions too.

Also, if it was DND, calls would go right to voicemail. But the way it is now, calls go to voicemail after the standard ring time period...but there's no ringing.

I will look into a SIP trace.

Thanks,

Mark

However it sound strange to me that you can actually see the routing problems you describe with fop? Maybe I did not understand the issue..

Okay, I'll try to explain better. Normally, when a call is made from one extension to another, the receiving extension shows the "ringing" icon (the flashing phone icon with the ringing indicator). So, when I am logged into FOP2 using extension 105 (for example) and I call 108 (for example)...normally I would see the indication that 108 is ringing. Then, when the party answers, the icon changes to the incoming call icon (not flashing, with the arrow indicating that it's an incoming call).

However, when the problem happens, the behavior is different. I call extension 108, and instead of the ringing icon, I just see the incoming call icon. The phone does not appear to be ringing, which is indeed true. The client reports that the phone never rings in this case. After the normal ring period, voicemail picks up...although the client's phone never rang.

So, FOP2 properly shows this behavior. Since the client is far away and cannot always help us with testing, the operator panel gives us the perfect way to test the behavior. When we dial an extension and do not see the ringing icon, this is an indicator that the routing issue is still there.

I hope this explanation helps.

Thanks,

Mark

Anyways, the test is easy. Just stop fop2, and remove the dummy interface, and let asterisk run for a couple more days and see if you still experience those issues.

One problem is that we need an operator panel to check to see if the issues are gone. The client is far away, so we use the panel to watch the behavior. How would we re-activate FOP1 to do this?

Thanks.

Thank you.

Can you tell me how to remove the dummy interface? I am not familiar with this process in OpenVZ. I only created the interface to facilitate the licensing of FOP2, following the instructions provided.

Also, will removing the interface prevent the license from working, or was it a one-time check?

Thanks,

Mark

To further clarify, we also suffered from the issue reported by someone else in the forum, with extensions going gray often. (This also started right after installing FOP2 full version.) We can stop them from going gray by turning off the qualify feature in FreePBX. However, with qualification off, we get the behavior mentioned above. So, with qualification, extensions seem to work fine...if they qualify. But, most of the time, they don't qualify and remain gray. This is true even if we set qualify time high, like 8000 or even 20000.

Any help will be appreciated.

Hi,

We are having issues with extensions misrouting (e.g., call 105 and get 150, etc.), and with incoming calls not ringing in many cases. In FOP2, the incoming call will show the incoming call icon at the receiving extension, but not the ringing icon. And the person does not hear the phone ring. (Yes, the ringer is turned up.)

This even happens at a location where things worked fine for two months. The only change we've made in our configuration is installing the full version of FOP2. This is on an OpenVZ setup, so we had to set up the virtual network device to activate the license.

I'm not saying that FOP2 is causing our issues, however we've exhausted just about everything else. And this is the only thing we changed in our config. Is there any chance that FOP2 (or the virtual network device) is causing these issues? How would we troubleshoot this? Unfortunately, we need an operator panel to view the behavior, since the client is 3000 miles away.

Any advice would be appreciated.

Thanks!

We recently experienced the same issue. After some diagnostics and log tracking, we realized that the Asterisk qualify feature was turning extensions off because of the qualification criteria. In this particular case, it only happened to users who had a computer attached to their telephone in passthrough mode. So, something about sharing an Ethernet port was delaying the qualify responses.

We simply set the qualify function to "no" for each extension, and they've all been green ever since.

Hi,

I need to change the name on an extension that has been taken over by a different person. I have done this in FreePBX, but FOP2 still shows the old name, even after restarting the panel.

I am not quite sure how the configuration works with buttons. I thought that FOP2 automatically pulled in the latest Asterisk information to populate the buttons. I know that it's stored in a config file, but I thought I should probably ask before editing that.

How can I change the name/label on the button for this extension?

I did try to search the forum first, but it will not allow searching for the word "button" because it is "too common." It is too bad that the forum software will not allow a search including a term that is part of FOP2's operations.

Thanks,

Mark

Update: I was able to get on live support chat, and I received the best support I have ever had on any product. After patient troubleshooting, it was determined that my issue is not with FOP, but was an issue with the OpenVZ VPS not responding to "localhost". The solution was easy...just a quick change to the FOP config file to point it to the localhost by IP instead. Even though the issue was not with his product, his concern was still solving the problem and getting me up and running.

Thanks for a great product and great support!!! You have won a customer.

Hi,

Thank you for the fast response.

Can you clarify what port errors are you referring to?

For example, running a test yields this result:

Couldn't connect to localhost:5038 (Server 0)

Running a test in debug mode yields:

Can't listen to port 4445

I have tried the recommended things such as turning off the original FOP, moving it to a different port, and running the same tests with iptables turned off. Same results.

Despite this issue, it is sometimes possible to log into the panel. Sometimes it is not. And, as mentioned, when I am logged in, the panel is not fully functional. For example, the red and green status indicators are not there...the panel is showing extensions and trunks, but is not reflecting their true activity. Of course, I would expect something like this based on the error messages. Even if I am seeing the interface, I know that something is wrong under the hood.

I think you do not have problems but just need a little training on what you can do and how.

For the most part I think this is correct. On the other hand, I followed the instructions to the letter, so I am not sure which step I missed or did incorrectly. Is there a step missing in the guide, or is there a different guide that might yield better results? I followed the one specifically for PIAF. I notice that there is another guide focused on Elastix, but it's indicated that this guide should also work for PIAF and other distributions.

I do agree that, once the connection issue is resolved, I will understand how to use the panel. I already understand it (as the basic operational concepts are actually quite simple), but I just want to confirm it by doing it.

FOP2 does not pass any audio at all, it displays activity as seen from the PBX and it can originate and redirect calls to endpoints registered to the PBX. But you still need an endpoint (aka phone) to actually talk , spy, etc..

I figured that this was probably the case. Should FOP2 work in conjunction with an operator using a softphone (e.g., X-Lite or something comparable)? In the system I am working on, the desire is to give operators PCs instead of physical phones.

I will be online in about 5 hours from now...

Thank you. I will look for you.

Mark

Hi,

I'm trying to test FOP2 on a PIAF system running on OpenVZ using the template provided by PIAF. After installing I got the port errors that some people have reported, and I still get those intermittently. Therefore, it's not always possible to log in. Sometimes I can't log in at all, and other times I can log in immediately. Other times there are several attempts before one works.

Even when I can log in, the panel is not working properly. I see the buttons, but they don't actually reflect the system's activity. The red or green indicators are not there...just the faded round indicators. And, even when extensions are active, nothing changes in the panel. None of the functions seem to work.

Also, I'm not sure how the panel is supposed to work if I can get it to start working. Since it controls all of the traffic, do the operators get their audio from the panel? Or must they also log in with a SIP client or phone? I can't imagine that, since the panel controls the transferring and other things...therefore it would have a hard time controlling an external client or device. Maybe I will understand this better when I can get the panel to work.

What could I be missing?

Thanks,

Mark