Page 1 of 1

Desktop app test connection issue

Posted: 08/14/2018
by DevonK
Hi,

I'm trying out the FPL PC desktop app to see if the call quality and reliability is sufficient for me to dump Bell and go with FPL or Fongo. When I run the built-in connection test from the app, the call service reports as OK, but the data transfer fails with the message "unable to send/receive sound data! Port 13000 should be available." Despite getting this error, I can both send and receive calls with the desktop app and the call quality is good, no dropouts or choppiness in the few tests of it run so far. I have tested my internet connection with a few VoIP test tools and it passes with flying colours.

I tried opening the 13000 UDP port manually in my Windows XP firewall, it made no difference. I do have the SIP ALG running on my Dlink DIR 655 router, but it does not interfere with calls so far. Can I safely ignore this test failure and feel confident Fongo or FPL is going to work for me?

Re: Desktop app test connection issue

Posted: 08/16/2018
by mh1983
Yes, ignore. I believe there are other posts in this forum that say the test is meaningless.

Re: Desktop app test connection issue

Posted: 08/16/2018
by DevonK
mh1983 wrote:Yes, ignore. I believe there are other posts in this forum that say the test is meaningless.
Thanks for letting me know.

Re: Desktop app test connection issue

Posted: 08/17/2018
by Liptonbrisk
DevonK wrote: I tried opening the 13000 UDP port manually in my Windows XP firewall, it made no difference.
Port forwarding is a security risk.
Port forwarding should only be done when all else fails. Your calls weren't failing.

Yes, that test is useless.

Re: Desktop app test connection issue

Posted: 08/17/2018
by DevonK
Liptonbrisk wrote:
DevonK wrote: I tried opening the 13000 UDP port manually in my Windows XP firewall, it made no difference.
Port forwarding is a security risk.
Port forwarding should only be done when all else fails. Your calls weren't failing.

Yes, that test is useless.
Thanks. Yes I closed the port in the firewall as soon as I saw it didn't help with the test.