Cannot disconnect call

[floatingshed]

The title says it all!

More often than not I have to force the software to close in order to disconnect.
I went to the website looking for a software update, but couldn't see any.

My current version is 3030, on windows xp

All help appreciated. Thanks.

[TheHardy]

Known problem -- java issue. Happens with both FPL and DV clients. Currently no fix, and no word whatsoever from Fongo about any update coming to fix this (and other) problems ...

[floatingshed]

Thanks for the info.

[FONGO_mike]

More information on this topic can be found in this thread

[TheHardy]

Errr, Mike, wrong issue -- it is not the dialpad/java issue, the "hanging" state on FPL 3.0.3.0 is _NOT_ fixed by downgrading java. It is a hard-coded programming error where the application becomes NON-RESPONSIVE to _ALL_ input (including close button) and the only option to terminate it is a CTRL-ALT-DEL task-manager HARD KILL.

I have had this problem for well over a year that I have been running FPL 3.0.3.0 and it is unresolved. It usually happens after at least a 6+ min call (out or in) or after 20+ mins of inactivity on the application (partial -- can stll accept a call, but as soon as you do, app becomes non-responsive).

Your referenced thread was SPECIFICALLY for the dialpad issues on DV ....

[FONGO_mike]

Sorry, i missunderstood. I was thinking it was that the call could not be terminated as the dial pad was not responsive.

[TheHardy]

Sorry, i missunderstood. I was thinking it was that the call could not be terminated as the dial pad was not responsive.

Well, 50% of the way there -- the dialpad IS unresponsive, but it is part of the FPL3.0.3.0 issue where the WHOLE program becomes non-responsive and is NOT java-version dependant (like the DV issue).

They are similar but not the same; like I say, the FPL softphone just seems to "go braindead" after a while and completely stop responding. I have documented this in other posts, but if you require more detailed information and some non-clinical testing results, I am more than happy to provide them.

Here's the other thing ... even though the FPL app shows the call as still ticking away in the call duration, the actual logs will show correct termination at the time, and the other end of the line is released correctly--so long as the other person hangs up (not flashhooks); if the other party has flashhooked, your FPL app maintains the connection, as the far-side has not been released --- this has lead to the other party coming back on the line after 30 mins when I was not able to do a HARD KILL on the program due to other processes running .... made for a very interesting conversation and the other person was NOT at all happy about the 30 mins of airtime they managed to waste (but that was not my problem....)