Liptonbrisk wrote:For the Freephoneline desktop app . . .
Make sure that you're not muting anything (microphone/speakers), and that you tested to ensure your mic is working before fiddling around with the app:
http://win10faq.com/fix-microphone-settings/
And make sure you test incoming calls for 1-way audio issues before paying anything to FPL (you'll need a mic and headphones/speakers to test). Test on a computer that's connected to your router (without DMZ or port forwarding enabled). Should you encounter 1-way audio issues, look for a feature called SIP ALG in your router (you may need to call your ISP if you're using a modem/router combo) and disable that feature.
Steps i,ii, and iv below are for help dealing with 1-way audio issues with Freephoneline desktop application.
from
http://forums.redflagdeals.com/fongo-at ... #p27011164
You can try the Freephoneline desktop app for free:
https://www.freephoneline.ca/downloadDesktopApplication
It requires 32-bit Java to run. If you have problems installing the desktop app, visit
http://forum.fongo.com/viewtopic.php?f= ... 63&p=74810.
A.Use winmtr
https://sourceforge.net/projects/winmtr/
B. For Freephoneline.ca (based in Ontario), test to voip.freephoneline.ca (let winmtr ping about 100 times), voip2.freephoneline.ca, and voip4.freephoneline.ca. You can copy text to clipboard and paste your results (do not post your own IP public address though) and post them for others to examine if you want.
C. Look at the very last hop or line. Take a look at your average ping--and your maximum. You want those values to be relatively close.
You do not want high pings and lots of jitter (you do not want a lot of variation between each ping). If you get horrible results (pings over 200ms), you should probably avoid FPL.
I get between 11 (voip.freephoneline.ca and voip2.freephoneline.ca)-24ms (voip4.freephonline.ca) on average, depending on the server I'm testing to. Preferably, you want pings below 100ms.
Anything over 200ms is unacceptable.
What you don't want to see is 40, 45, 50, 35,
500, 40, 30, 45,
700. That's bad jitter.
You want relatively consistent pings without a lot of variation.
Try the free FPL desktop app first:
https://www.freephoneline.ca/downloadDesktopApplication.
Make sure that you're not muting anything (microphone/speakers), and that you tested to ensure your mic is working before fiddling around with the app:
http://win10faq.com/fix-microphone-settings/
And make sure you test incoming calls for 1-way audio issues. Test on a computer that's connected to your router (without DMZ or port forwarding enabled). Should you encounter 1-way audio issues, look for a feature called SIP ALG in your router (you may need to call your ISP if you're using a modem/router combo) and disable that feature.
i. Typically it's better to have your own router and to stick whatever modem/router combo your ISP gives you into bridge mode.
ii. Disable SIP ALG in your own router. Many modem/router combos that are issued by ISPs have faulty SIP ALG/SPI functions enabled, with no way to disable them. These features can mangle SIP headers. If you don't know how to disable SIP ALG, contact your router's brand or contact your ISP.
To understand why SIP ALG is often a serious headache visit
https://www.voip-info.org/routers-sip-alg/ (scroll down to "SIP ALG Problems")
iii. Properly enable QoS in your router for your computer that's running the Freephoneline desktop app (and ensure no other programs are running on your computer that are hogging bandwidth while using the Freephoneline desktop app). Refer to your router's manual or contact your ISP if you were issued a modem/router combo from them (typically those routers suck and have horrible or absent QoS functions).
I'm not a huge fan of this website, but it suffices for an explanation of QoS:
http://www.voipmechanic.com/qos-for-voip.htm
Avoid anything it says about the G.729
iv. If you still get one-way audio issues with the Freephoneline desktop app, you may need to port forward, which is a security risk (and not advisable).
The FPL desktop app uses ports 5060-5061,6060-6061,13000-13001 if you're going to port forward for the desktop app (you need to port forward to the LAN IP of the computer you're using. For most home networks the IP will begin 192.168.xxx.x). Refer to your router's manual to learn how to port forward (if your router came from your ISP, contact your ISP).
I would start just by port forwarding 13000-13001 only, which is for RTP (audio packets). If that still doesn't work, you can try adding 6060 or 6061. The most dangerous ports to forward are 5060-5061 and really shouldn't be necessary if you're forwarding 6060 or 6061 anyway. I guess if all else fails, forward all of them: 5060, 5061,6060, 6061,13000, and 13001.
These are all UDP ports.
5060, 5061, 6060, and 6061 should be alternate SIP ports.
Only port forward if all else fails (and only do it temporarily, since it's a security risk).