Loss of input to FPL softphone

[TheHardy]

Here's one that I have had before, but I have not been able to find a solution.

I use the FPL softphone (3.0.3.0). I initiate a call, and while talking, flip to another window. Usually it has been Firefox, sometimes with a java script app, sometimes not. Today I was working in a wordprocessor doc while online with the FPL softphone.

What happens is that when I switch back to the FPL softphone, I am no longer able to INPUT anything to it ... well, not 100% accurate -- I can use the buttons (Keypad, Contacts, Menu) but any of the keypad input (or keyboard input) that I make has any result on the "called" end. I can hear touchtones on my end, but they do not register on the called end. Furthermore, the "DISCONNECT" button on the softphone has no effect. The call timer keeps going, and the only way to stop it is to end the softphone altogether, exit and reload.

Java error? Any insight? Thanks in advance!

[lauren]

It could very well be a java error. The best way to figure this out is to uninstall the softphone and your current version of java. Try reinstalling both programs again and see if that works. It does tend to work after installing java again. If that does not work, I would suggest giving our support team a call at 1.866.515.5550. Thanks

[TheHardy]

Unless java is crashing (or being caused to crash by softphone...??). I have the latest version of java up and running, and no other programs that utilize java are having any problems whatsoever, only the FPL softphone.

I am not sure how to contact the 'code-writers' of the FPL-branded softphone other than via FPL, so if you could please forward this as an official BUG REPORT to them, it would be much appreciated. It happens intermittently, but almost ALWAYS while I am trying to navigate some IVR system which requires keypad input.

If you have "DIRECT" contact info for them and wish to forward that for me via PM, I can send all the relevant info to them myself.

Thanks in advance ...

[DaBones]

my FPL softphone does the same thing, on 2 different computers.. I've pretty much given up on it..
sometimes it works ok, and other times it's crap.. I know that a year or so ago I had an older softphone version and it worked great, but this one doesn't act right at all..

I am having a really hard time talking myself into buying the config file. because I don't know if the service will be as unstable on other softphones and/or my android smart phone running sipdroid or csipsimple over wifi.... curently I can run sipgate (US SIP provider) using QuteCom Softphone and also on my Cell just fine, so I know my connection should be ok.. ....but using Google Voice callback is annoying, not to mention only having a US number is hard to get ppl to call me on.

how do I know it's not a waste of $50 bucks?

[ddd]

In case it may help you: here under is my 3.0.3.0 solution, in private with Steve.

Subject: Eureka
Sent: Mon Aug 08, 2011 12:08 am

I uninstalled FPL; then deleted every FreePhoneLine* folders (just found in Documents and Settings); reinstall = Perfect now! [...]

It may be a win7 side effect: to be able to delete those folders, I had to give myself, permission. It is very tricky... At that time, I found something in Internet that taught me how to.

[TheHardy]

I am not sure what the updates in 3.0.3 were over 3.0.1 were, but with all the bugs and inconsistencies that I have found in .3 I am wondering if I should try to find an older version to install and use instead!! The main kicker for me is the non-functional incoming caller-id support. Having to constantly reboot before making important phone calls which may require consistent keypad input is also rather annoying not to mention time consuming.

Too bad that there is not a "change-log" or other easily available information/documentation for the FPL softphone app. If there were not too many major fixes over .1 and it was a stable piece of software, then it may well be worth rolling-back and installing it if I could find it somewhere.

Anyone have an opinion on this?

It may be a faster solution than waiting on an update for the "well known" issues that 3.0.3.0 seems to have ... unless there is an official word from the development department!?