Phone doesn't ring

Have a question or problem with your Fongo Mobile App? This forum is the place to get help from both staff and fellow community members.
Visit The Fongo Mobile Support Knowledge-base for more.

Phone doesn't ring

Postby Király » 02/08/2019

If I haven't opened the Fongo app for a while (seems to be about 6 hours), my iPhone will no longer ring when I receive a Fongo voice call or SMS. I just get the Apple notification immediately afterwards that a voice call was missed. With SMS it's even worse, I get no notification of the incoming SMS at all until I open up the Fongo app, and then it immediately pops up.

At first I thought that this might be because background app refresh was off, but it's definitely on. What am I doing wrong? Or is this just how Fongo works? I don't want to have to remember to manually open Fongo every few hours.

IMG_0796.PNG
IMG_0796.PNG (108.65 KiB) Viewed 530 times

IMG_0804.PNG
IMG_0804.PNG (118.06 KiB) Viewed 530 times

IMG_0803.PNG
IMG_0803.PNG (126.55 KiB) Viewed 530 times

IMG_0802.PNG
IMG_0802.PNG (126.97 KiB) Viewed 530 times

IMG_0801.PNG
IMG_0801.PNG (100.29 KiB) Viewed 530 times
Király
Just Passing Thru
 
Posts: 4
Joined: 02/08/2019

Re: Phone doesn't ring

Postby Liptonbrisk » 02/08/2019

Look over the "Push Notifications Not Enabled (iOS)" section from
https://support.fongo.com/hc/en-us/arti ... ming-Calls
Please do not send me emails; I do not work for nor represent Freephoneline or Fongo. Post questions on the forums so that others may learn from responses or assist you. Thank you. If you have an issue with your account or have a billing issue, submit a ticket here: https://support.fongo.com/hc/en-us/requests/new. Visit http://status.fongo.com/ to check FPL/Fongo service status. Freephoneline setup guides can be found at viewforum.php?f=15.
User avatar
Liptonbrisk
Technical Support
 
Posts: 890
Joined: 04/26/2010
SIP Device Name: OBi202
Firmware Version: 3.2.2 (Build:5921EX)
ISP Name: Cable
Computer OS: Windows 10 x64 Pro
Router: Asuswrt-Merlin

Re: Phone doesn't ring

Postby Király » 02/08/2019

Liptonbrisk wrote:Look over the "Push Notifications Not Enabled (iOS)" section from
https://support.fongo.com/hc/en-us/arti ... ming-Calls


I've been through that article already and my settings are already what is recommended, push notifications are enabled and I'm getting them. Here are more screen shots of my settings.

IMG_0800.PNG
IMG_0800.PNG (92.18 KiB) Viewed 526 times

IMG_0799.PNG
IMG_0799.PNG (86.89 KiB) Viewed 526 times

IMG_0798.PNG
IMG_0798.PNG (82.05 KiB) Viewed 526 times

IMG_0797.PNG
IMG_0797.PNG (34.96 KiB) Viewed 526 times

IMG_0795.PNG
IMG_0795.PNG (35.19 KiB) Viewed 526 times
Király
Just Passing Thru
 
Posts: 4
Joined: 02/08/2019

Re: Phone doesn't ring

Postby Liptonbrisk » 02/08/2019

To receive notifications for incoming calls when the app is closed, Push needs to be enabled. I’ve had the app closed for a week and incoming call notifications work. If incoming call notifications always work when the app is open but don’t when it’s closed while you’re on Wi-Fi, it may be a NAT firewall or UDP timeout issue. Unfortunately because the app is closed source, I have no clue what the NAT Keep Alive or failed registration timer intervals are. Otherwise, I could offer some other suggestions (other than trying to reinstall the app).

In order for incoming calls to work, your account needs to be registered. If registration is lost, cellular signal strength is weak (internet service is unreliable), or if there’s simply inadequate available bandwidth due to other devices on LAN being in use, incoming calls will go straight to voicemail. But if the problem goes away as soon as you open the app while on Wi-Fi, I would suspect a NAT related issue.

Fongo support staff is not obligated to respond on these forums. If you would like their help, submit a ticket: https://support.fongo.com/hc/en-us/requests/new.
Maybe someone else here has come across this problem too.
Please do not send me emails; I do not work for nor represent Freephoneline or Fongo. Post questions on the forums so that others may learn from responses or assist you. Thank you. If you have an issue with your account or have a billing issue, submit a ticket here: https://support.fongo.com/hc/en-us/requests/new. Visit http://status.fongo.com/ to check FPL/Fongo service status. Freephoneline setup guides can be found at viewforum.php?f=15.
User avatar
Liptonbrisk
Technical Support
 
Posts: 890
Joined: 04/26/2010
SIP Device Name: OBi202
Firmware Version: 3.2.2 (Build:5921EX)
ISP Name: Cable
Computer OS: Windows 10 x64 Pro
Router: Asuswrt-Merlin

Re: Phone doesn't ring

Postby Király » 02/10/2019

Thanks for the detailed reply. I get this problem both when I'm at home using wifi, and when I'm out using cellular data. Does this mean it could still be a NAT firewall problem?
Király
Just Passing Thru
 
Posts: 4
Joined: 02/08/2019

Re: Phone doesn't ring

Postby Liptonbrisk » 02/10/2019

Király wrote:Thanks for the detailed reply. I get this problem both when I'm at home using wifi, and when I'm out using cellular data. Does this mean it could still be a NAT firewall problem?


No, or at least it wouldn't be an issue involving a router on your end, since you're not using a router when you're using cellular data. The reason for failed calls while on cellular data can be different. If you're walking into a poor cellular signal area or are getting high pings and jitter to Fongo Mobile's servers, then you can expect problems. While on Wi-Fi, a NAT hole could close or NAT corruption could occur, which is why I was mentioning UDP timeouts.


Fongo Mobile's servers are located in Southern Ontario.


http://forums.redflagdeals.com/merged-f ... #p29184315
"People located in southern portions of Ontario using Fongo Mobile, Fongo Home, and Freephoneline are generally going to have better experiences than those who aren't, with those specific services. People on Rogers, Bell, Telus or their affiliated mobility providers in strong LTE areas in Southern Ontario will generally have better experiences as well (as opposed to people, for example, in some locations, on Freedom Mobile)."

Why?

"Ping is a measurement of data packet transmission, and ping does affect delay or lag. All gamers know, almost inherently, that lag affects them negatively. A PC gamer will pound his or her keyboard in hope that a character will respond on his or her monitor, quickly, but when there's a delay or lag, reality doesn't meet expectation. A gamer can see this problem visually. Over VoIP, anything over 200-210 ms, you will typically start to encounter crosstalk due to increased delay, even if the untrained ear doesn't notice. All VoIP services are subject to the same scientific principles including the fact that speed of transmission affects delay. When pings (and especially) jitter are high, VoIP can be a pretty horrible experience . . . Anyone using any communication service (or even when playing online games or using other online services) should understand that the longer the path to the server being used, the greater the potential exists for a problem to occur somewhere along that path."

If you ever play an MMO or select an online game server, gamers almost always choose servers that are closest to them for the most responsive online gaming experience, for a very good reason.


Fongo Mobile is in Ontario and uses SIP protocol.
For jitter, ping, and traceroutes, test to 162.213.111.27

Anything over 200ms is unacceptable. You'll begin to encounter crosstalk, even if an untrained ear doesn't notice. So, if you're getting really high pings and jitter, I would avoid the service you're testing.

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.

Bad jitter can produce broken up audio or choppiness during phone calls. Severe jitter/ping spikes can cause calls to drop and for incoming calls to not be received. Ping affects delay from the time someone speaks until the time it's heard.


Whether you have a strong cellular data signal matters if you're using cellular data to place VoIP calls."


1.Use winmtr http://winmtr.net/download-winmtr/. Ping about 100 times.
When using WINMTR, look at the very last line or hop when checking your pings.

If you're on a Macintosh, maybe this helps: https://www.reddit.com/r/TagPro/comments/2j6qx7/how_to_run_an_mtr_on_mac/

When using WinMTR, look at your average ping and then maximum ping. Although WINMTR doesn't provide a jitter value, you can get an idea of what yours is by subtracting maximum ping from your average.
Jitter is the difference between each successive ping.
The bigger the difference, the bigger the problem.

Same with ping, which represents lag or delay. The lower your ping and jitter, the better.


There are iOS apps, such as Net Analyzer, that allow users to run ping tests to IPs, which would probably be a better idea since the problem is on a smartphone.
Please do not send me emails; I do not work for nor represent Freephoneline or Fongo. Post questions on the forums so that others may learn from responses or assist you. Thank you. If you have an issue with your account or have a billing issue, submit a ticket here: https://support.fongo.com/hc/en-us/requests/new. Visit http://status.fongo.com/ to check FPL/Fongo service status. Freephoneline setup guides can be found at viewforum.php?f=15.
User avatar
Liptonbrisk
Technical Support
 
Posts: 890
Joined: 04/26/2010
SIP Device Name: OBi202
Firmware Version: 3.2.2 (Build:5921EX)
ISP Name: Cable
Computer OS: Windows 10 x64 Pro
Router: Asuswrt-Merlin

Re: Phone doesn't ring

Postby Liptonbrisk » 02/10/2019

While you're on Wi-Fi, you're subject to the limitations of your own router (or someone else's). The following information applies to Freephoneline users, but Fongo Mobile is also a SIP service, and the same principles apply. The problem with me discussing #4 with respect to Fongo Mobile is that, because I can't see what settings are used, I have no clue (I could guess, I suppose, but I would prefer not to) what values Fongo Mobile is using for NAT Keep Alive and Failed Registration Retry Interval.

#1 matters for security.

For #2, Alternate Fongo Connection is the same thing as using voip4.freephoneline.ca:6060 (for Freephoneline users), which is intended for use with buggy SIP ALGs.

#3 mentions ATA, but you would instead want to assign highest priority to your smartphone.

While on Wi-FI, you also need to consider the possibility of congestion during prime time (8p.m. to midnight, especially on Sundays, when everyone in your area will be home), which is the best time to run tests. That's an ISP issue (possibly oversold its service in your area).



---


Typically, for VoIP SIP services, especially for freephoneline, you want

1) a router that does not have a full cone NAT,

Visit https://www.think-like-a-computer.com/2 ... es-of-nat/.
Mango from the Obitalk.com forums writes,
“Use a restricted cone NAT router, and do not use port forwarding or DMZ. Restricted cone NAT will only permit
inbound traffic from the service provider you're registered to. If you have a full cone NAT router, it will allow traffic
from any source. This is probably not what you intend.
If you have a Windows computer, you can test your router using the utility here:
http://www.dslreports.com/forum/remark,22292023. To run it, use stun stun.ekiga.net from a command prompt.”
Essentially, you download the stun-test.zip file; extract the stun.exe file from within the zip file to an easily
accessible location; use an elevated command prompt (visit
http://www.thewindowsclub.com/how-to-ru ... inistrator); change directory (cd) to the
directory or location where you extracted stun.exe (visit
http://www.digitalcitizen.life/command- ... c-commands); and type “stun stun.ekiga.net” without
the quotation marks followed by the enter/return button on your keyboard.
Asus routers, at the time of this writing, produce port restricted cone NAT routers, for example and are fine,
provided you’re using one with Asuswrt-Merlin, third party firmware installed.

2) a router that lets you disable SIP ALG if it's buggy,

To understand why SIP ALG often causes horrible problems, please visit
http://www.voip-info.org/wiki/view/Routers+SIP+ALG (scroll down to the section on SIP ALG problems).

If you're dealing with a modem/router combo issued by an ISP or a router with SIP ALG forced on, you may have
to use voip4.freephoneline.ca:6060 for the Proxy Server. The purpose of voip4.freephoneline.ca:6060 is to circumvent
faulty SIP ALG features in routers.

3) a router that allows you to set QoS or assign highest priority to your ATA or IP Phone over all other devices on your LAN (local area network),

For a very general description of what QoS can do for you, visit https://www.voipmechanic.com/qos-for-voip.htm.
The basic idea is if you're torrenting or have a bunch of other computers, smartphones, tablets, etc. downloading and uploading (hogging all your available bandwidth), you don't want
your ATA not to have access to enough bandwidth to make or receive calls properly. So QoS or a Bandwidth Monitor feature (which is just another form of QoS) is a really good idea for VoIP users.

I often get an occasional relative complaining to me, "Hey my calls sound choppy." And then when I go visit, some kids are playing MMOs on a computer, while another person is downloading a huge file,
and another person is backing up files to a cloud service all at the same time someone else is trying to talk on the phone. All those devices, without QoS enabled, are fighting over available bandwidth along with the ATA.

and 4) A router that lets you adjust both Unreplied and Assured UDP timeouts.

Thanks to Mango, many of us now understand that in order for ATAs to remain registered and working properly with a VoIP SIP provider like Freephoneline, in particular after power failures, the following conditions must be met:

UDP Unreplied Timeout (in your router) < NAT Keep-alive Interval (in your ATA; for Obihai ATAs this is X_KeepAliveExpires) < UDP Assured Timeout (in your router) < SIP Registration Failure Retry Wait Time (or RegisterRetryInterval in Obihai ATAs)

“<“ means less than.

When a modem leases a new IP address, a problem can arise where prior associations using the old IP address are maintained in the router. When the ATA attempts to communicate using the old IP address, the response is unreplied, and then if the UDP Unreplied timeout is greater than the Keep Alive Interval (and UDP Unreplied timeout is often set to 30 by default in consumer routers) a problem arises where the corrupted connection persists. If UDP Unreplied timeout is, for example, 17, and the NAT Keep Alive Interval is 20, then the corrupted connection will timeout or close. A new connection will be created, and everything will work fine.

Another problem can occur when the Keep-Alive interval is greater than UDP Assured Timeout (often 180 by default in consumer routers): the NAT hole will close due to the ATA not communicating frequently enough with the SIP server. In turn, incoming calls may, intermittently, not reach the ATA. Again, X_Keepalives expires is supposed to be 20 with FPL.

(the above settings are making reference to those in Obihai ATAs)

Getting access to both UDP Unreplied Timeout and UDP Assured Timeout settings in consumer routers may be difficult, if not impossible. Asuswrt-Merlin (I would avoid any model below/less powerful than an RT-AC68U), third party firmware for Asus routers, does offer easy access to these two settings, which are found under General–>Tools-->Other settings. My understanding is that third party Tomato firmware has these two settings as well. So if your router supports Tomato firmware, that may be another option. Note that I will not be held accountable any damage resulting from failed firmware updates. Apparently, Mikrotik routers also allow users to change both Assured and Unreplied UDP timeout settings as well: https://forums.redflagdeals.com/recomme ... 2115672/2/

The keep alive interval for FPL is 20. The SIP Registration Failure Retry Wait Time is 120. I use 17 for UDP Unreplied Timeout and 117 for UDP Assured Timeout.



ISPs do not issue customers routers that can do all four things I just listed. Typically it's far better to have your own router with strong QoS functions and a restricted cone NAT firewall,
disable whatever SIP ALG feature is enabled in the router, and stick whatever modem/router combo your ISP gives you into bridge mode. For Bell Hubs, visit http://forums.redflagdeals.com/please-s ... r-1993629/. For Rogers, visit https://www.rogers.com/customer/support ... ridgemodem.
Please do not send me emails; I do not work for nor represent Freephoneline or Fongo. Post questions on the forums so that others may learn from responses or assist you. Thank you. If you have an issue with your account or have a billing issue, submit a ticket here: https://support.fongo.com/hc/en-us/requests/new. Visit http://status.fongo.com/ to check FPL/Fongo service status. Freephoneline setup guides can be found at viewforum.php?f=15.
User avatar
Liptonbrisk
Technical Support
 
Posts: 890
Joined: 04/26/2010
SIP Device Name: OBi202
Firmware Version: 3.2.2 (Build:5921EX)
ISP Name: Cable
Computer OS: Windows 10 x64 Pro
Router: Asuswrt-Merlin

Re: Phone doesn't ring

Postby Liptonbrisk » 02/10/2019

You can also try running http://vac.visualware.com/index.html at 8p.m. (or between 8 p.m. and 11 p.m.)

Select a test server location that's located close to the SIP server (southern Ontario) you're using.
A MOS score below 4.0 is bad news. It means call quality will not be good. And if the score is below 4 while on cellular data, I would consider the possibility that calls could drop, periodically, or that incoming calls may not work.

Uninstalling and reinstalling the app won't hurt anything, and I doubt it matters, but iOS 12.1.4 is available.

It's also possible that something else is happening in your case that I'm not considering. Fongo support staff is not obligated to respond on these forums. If you would like their help, submit a ticket: https://support.fongo.com/hc/en-us/requests/new. Their business hours are 9AM-4PM EST, Monday to Friday excluding holidays. I would allow 48 business hours for a response after a ticket has been submitted.
Please do not send me emails; I do not work for nor represent Freephoneline or Fongo. Post questions on the forums so that others may learn from responses or assist you. Thank you. If you have an issue with your account or have a billing issue, submit a ticket here: https://support.fongo.com/hc/en-us/requests/new. Visit http://status.fongo.com/ to check FPL/Fongo service status. Freephoneline setup guides can be found at viewforum.php?f=15.
User avatar
Liptonbrisk
Technical Support
 
Posts: 890
Joined: 04/26/2010
SIP Device Name: OBi202
Firmware Version: 3.2.2 (Build:5921EX)
ISP Name: Cable
Computer OS: Windows 10 x64 Pro
Router: Asuswrt-Merlin


Return to Community Support

Who is online

Users browsing this forum: No registered users and 1 guest

cron