phone suddenly stopped working

[johnt89]

Freephoneline on OBI200
Was working fine until yesterday.

Nothing has been changed on device, router, or modem.

Have already power cycled the device and checked the SIP settings on OBI device page. All looks to be normal and same as before.

Anyone know what is happening?

Thanks

[Liptonbrisk]

a) Try a different phone

b) What happens if you attempt to place a call?

c) What does the registration status in your ATA indicate for Freephoneline?
Dial ***1. Enter the IP address you hear into a web browser
Navigate to Status-->System Status-->SP(FPL) Service Status-->Status

d) What brand and model modem and router are you using?

e) You can also get some very general ideas from visiting https://www.obitalk.com/info/support/troubleshooting.
However, I would ignore anything that site says about enabling DMZ.

1. Read pages 9 and 10 from the PDF guide: http://forum.fongo.com/viewtopic.php?f= ... 805#p73839

2. Refer to the PDF guide (pages 47 and 48): http://forum.fongo.com/viewtopic.php?f= ... 805#p73839
(Steps A to D; follow each step, step by step, slowly and carefully)

Step B, by the way, is one of several explanations for why an issue can occur without you doing anything.

have already power cycled the device

That's not the proper device boot order. Pay close attention to step D on page 48.
But you should start at step A first on page 47.

As a last resort, I would reset the ATA to factory defaults and configure the ATA properly using the PDF guide.

Also, for general info, I would encourage people to read the preamble (pages 1 to 4) from the PDF guide: http://forum.fongo.com/viewtopic.php?f= ... 805#p73839.

[kehodder]

Mine stopped working for incoming calls this last week as well. Obi200 5804, says registered. If a change the server it works for a couple calls inbound then no more-but still says registered. I tried a few things in the guide now but never had to prior. Also tried 5757EX..same result. Outgoing works fine

[Liptonbrisk]

Mine stopped working for incoming calls this last week as well. Obi200 5804, says registered. If a change the server it works for a couple calls inbound then no more-but still says registered. I tried a few things in the guide now but never had to prior. Also tried 5757EX..same result. Outgoing works fine

I have had no incoming or outgoing call problem (nor do the people I've setup FPL for) for years that I could not attribute to an issue on FPL's end (and that's pretty rare). It's not just a few things you should be doing in the guide. It's the entire guide that you should be using. A factory reset and using the guide would likely resolve most general issues people have with FPL.

Please note that only one registration per FPL account is allowed at any time.
When there are multiple devices/softphones using the same account, only the most recent registration is valid. The previous device will lose registration (despite the ATA's registration status) and incoming calls will not work on it. Registration is required for incoming calls but not for outgoing calls. In other words people sharing their FPL accounts or otherwise trying to register their FPL accounts with smartphone SIP apps/desktop apps while simultaneously using the same FPL account on their ATAs are out of luck for incoming calls.


1. Put whatever modem/router combo Shaw gave you into bridge mode to ensure you're bypassing the SIP ALG feature is in the device they gave you (and also to ensure you're not in a double NAT scenario). Contact Shaw if need be. If you just have a modem from Shaw you can ignore this step, but make sure the device is absolutely not a modem/router combo first.

2. You're using Xwrt-Vortex. In your router, navigate to Advanced Settings–>WAN–>NAT Passthrough–>SIP Passthrough. Change SIP Passthrough to “Enabled + NAT helper.” Click “Apply.”

Latest version of Xwrt-Vortex is found at http://xvtx.ru/xwrt/download.htm.

3. In your ATA (or Obitalk if that's what you use . . . don't use both methods), navigate to Service Providers-->ITSP Profile (FPL)-->RTP
KeepAliveInterval: 20

Refer to page 23.

4. Navigate to Service Providers-->ITSP Profile (FPL)-->SIP
X_UsePublicAddressInVia: enabled

Refer to page 22.


5. Navigate to Voice Services-->SP(FPL)
X_KeepAliveEnable: Checked
X_KeepAliveExpires: 20
X_KeepAliveMsgType: notify

Ensure those are the settings for your ATA.

Refer to page 24

6. 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.

A 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.

Getting access to both UDP Unreplied Timeout and UDP Assured Timeout settings in consumer routers may be
difficult, if not impossible. Asuswrt-Merlin, third party firmware for Asus routers, does offer easy access to these two
settings, which are found under General–>Tools-->Other settings. In part, for this reason, I tend to use Asus routers
that work with Asuswrt-Merlin. However, 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.
The keep alive interval for FPL is 20. The SIP Registration Failure Retry Wait Time is 120. I use 10 for UDP
Unreplied Timeout and 117 for UDP Assured Timeout.


7. Follow the steps, slowly and carefully, step by step down the list on pages 42 to 44. But it would be better just to use the guide from beginning to end.
Actually, page 45 also applies (if a ton of other devices on your LAN are hogging bandwidth, you may encounter problems).
On page 16, there's an explanation of what can happen when there's jitter, packet loss, and huge ping spikes.
If you experience related issues to FPL's SIP servers, you're going to have problems.

Concerning page 45, if you have a router that supports Asus Bandwidth Monitor (you might; I'm not sure) . . .
Click https://www.asus.com/US/support/FAQ/1008717.
Assign your ATA highest priority, and give everything else on your Local Area Network a lower priority than your ATA.

In order for Bandwith Monitor (found under Adaptive QoS in an Asus or Merlin supported router) to work properly, first, you must turn all devices in your household that connect to the internet (smartphones, computers, smart thermostats, hubs, console gaming systems, roku/apple tv, etc.) so that they are listed.

Drag and drop "Highest" onto your ATA. Do not assign "highest" to anything else. Assign a lower priority to everything else (it's your choice for what priority to use for each device--but don't use "highest" on anything other than your VoIP device). Click "apply".

Use QoS - WAN/LAN Bandwidth Monitor (and not the QoS tab) in the router.
Login to the router. Navigate to Adaptive QoS-->Bandwidth Monitor. Assign your computer highest priority, and assign a lower priority to every other device listed (turn on all devices on your Local Area Network first so that they all populate in the device list). You just drag and drop priorities onto the devices. Then you click the "apply" button.

Then reboot the router (wait for it to fully up and running). Then reboot ATA.

8. Proper device boot order is always Modem--->Router (wait for it to be fully up and broadcasting Wi-Fi SSIDs)-->ATA in that order.
If your internet connection is constantly dropping and returning, keep that device boot order in mind and contact your ISP.
Because the registration period is 1hr with FPL, registration may not be attempted again until 60 minutes has passed (FPL's registration status in the ATA may
still indicate that it's registered during that interval despite the fact it's really not).

[kehodder]

Please note that only one registration per FPL account is allowed at any time.

Well, I'm embarrassed , you nailed with that one there. After following every step, I'm pretty sure I had before but went through every one again. Again, worked for the first incoming call then quit working immediately after. I then logged into freephoneline website just to check the SIP settings and it reported a desktop app was the registered device instead of the Obi ATA. For some reason, a mistake of mine no doubt, an old desktop app was running on my HTPC....and because of this it kept stealing the registration from the ATA. How this ancient app got launched I don't know...I'd like to blame it on the cat that likes to walk on the keyboard. I went up and rebooted that PC and all is good. I'll just delete that app as it has never been used for ~8 yrs since I bought the SIP key.
Many thanks Liptonbrisk!

[Liptonbrisk]

I'll just delete that app as it has never been used for ~8 yrs since I bought the SIP key.

Well, you can just make sure it's not running instead, if you prefer.

Many thanks Liptonbrisk!

You're very welcome!