Need help to complete VoIP account and OBi200 setup

[teensee]

Hello friends,

Please be aware that I am a newbie with VoIP. This is my first post in this forum.
I've tried to describe my issues to my best, hoping you can help me out
to get my VoIP working properly.

First I have the FPL Desktop installed on my laptop and got it working fine:
I can place a call and can receive a call from a landline.
Both destinations are receiving rings, get the calling number display,
they can answer and hear properly.
At this step, I think that the settings of both my computer and
my ADSL2 modem-router are fine.

Next, I bought the VoIP unlock key.
Via OBiTalk Dashboard, my OBi200 firmware has been upgraded successfully
from version 3.0.1 (Build 4581) to version 3.1.1 (Build: 5463EX).

Then I followed the Obi200 setup guide provided in the Fongo forum
at http://forum.fongo.com/viewtopic.php?f=15&t=18805

Obihai OBi202/200 ATA Setup Guide For Freephoneline (FPL) without Server Failover
version 1.30

and completed the local settings on my OBi200.

My account has been configured on my OBi200 and has successfully registered
to the FPL server voip.freephoneline.ca:5060.

During the first 2 days, I can make calls from the phone connected to my OBi200
to a landline, and I can also receiving calls from a landline.
Both ways of communication are working, but the only issue is the landline phone
got Unknown Name and Unknown Number instead of
Unknown Name (as Name was not provided) and the callerID number.
Because the phone connected to the OBi200 has no screen display so I can't tell
if the landline callerId is displayed or not.
The Fongo Desktop application was also working fine.

Then suddenly my FPL# has stopped working completly.
And the Desktop application can't call out nor receiving any calls.
When I call from the landline to my FPL # 438-xxx-xxxx
the Desktop application doesn't ring, I hear no background sound
until the voice mail of the FPL number announced asking
to leave a message!

My FPL account became unrecognized by the proxy server:
Register Failed: No Response From Server (server=208.65.240.44:5060; retry in 120s)

It looks like my FPL # has been blocked or reconfigured!

After 2 days waiting Fongo Tech Support to complete to investigate on my account,
I received an email suggesting me:
a) try updating the firmware to the latest stable release for your device,
then reconfigure the device
b) to change the ProxyServer to voip4.freephoneline.ca:6060

Since I have already applied the firmware update to version 3.1.1 (Build: 5463EX),
the OBi200's System Status shows that my firmware CONFIGURATION CURRENT with a yellow check mark,
I prefer not apply any unofficial firmware version, especially when I am not sure if that
will work or not.

This is my lastest ATA settings, phone and status:

OBi200 has firmware version 3.1.1 (Build: 5463EX)
The ProxyServer is set to voip4.freephoneline.ca as suggested.
Status: Registered (server=162.213.111.21:6060; expire in 3381s)
PrimaryProxyServer 162.213.111.21:6060
netis VDSL2 Modem Router w/ Firmware Version RTK V2.2.1
FPL Desktop 3.2.7 on Windows 7 Pro

I am not sure how my FPL # was modified and reset.
I am clueless why the FPL Desktop Application was working fine before,
but no longer working now: it cannot make and cannot receive any calls.

Am I right thinking that if my FPL account is setup correctly on the FPL/Fongo servers,
the Fongo Desktop configured with my FPL account should always work normally?
Because qhen I am way from the ATA, I can use the FPL Desktop to access my FPL Voicemail,
make and receive phone calls.

The ATA is independently operated using the Internet, VoIP and my home network.
Even when the ATA is badly configured or failed, the ATA should not affect to
the Fongo Desktop operations?

I have tried to restore my computer to the day that FPL Desktop was working well
but still get no responses upon making or receiving calls. Does this mean the setup
of my FPL account on the servers is needed once more to be reviewed and corrected?
Can you please hep? For background info, Re: Ticket #234522.


Currently, only calls to the landline from the phone connected to the OBi200
is ringing and the landline displays both the correct Name and Calling number.
The new issue is a call placed from a landline doesn't ring the phone connected to the OBi200
before this call is forwarded directly to the FPL VoiceMail.
In the Follow Me Setttings: Status: Disable, Ring Mode: grey out, FollowMe Mode: grey out.

The phone connected to the OBi200 can reach the VoiceMail by dialing *98.


By any chance, if you have successfully used Freephoneline with an OBi200,
can you tell me which OBi200 firmware version you're using and provide me
details about your OBi200 configuration settings.
Or just send me your OBi200 config file (of course without your username and password).

Or even better if you also use the netis DL4422 ADSL2 modem-router,
please share with me your netis configuration settings.

Most importantly, please indicate what firmware version is latest stable release for OBi200
and FPL service provider?

I am sure that the OBi200 is working well with Freephoneline VoIP
as I can see many other members in the forum has already succeeded to use this ATA.

After reviewing my router settings and my OBi200 settings based on
the OBi200 setup guide, since I can't find what I have missed
I've submitted a support request to Fongo about the callerID issue.

Fongo Tech support has provided a link to the same forum that I have used
for my OBi200 settings and asking me to ensure that:

a) I have the latest stable release installed for my OBi200
b) reconfigure my OBi200 again

Dear gurus and VoIP testers, Can you guide, advice, and share your expertise?

[Liptonbrisk]

Next, I bought the VoIP unlock key.
Via OBiTalk Dashboard, my OBi200 firmware has been upgraded successfully
from version 3.0.1 (Build 4581) to version 3.1.1 (Build: 5463EX).

That's not the latest version.
Firmware 3.1.1 (Build: 5577) is the latest official firmware version for both the OBi200 and OBi202: http://fw.obihai.com/OBi202-3-1-1-5577.fw

Then I followed the Obi200 setup guide provided in the Fongo forum

Use version 1.32: http://forum.fongo.com/viewtopic.php?f= ... 439#p74439

Note that X_ProxyServerRedundancy should be disabled (Service Providers-->ITSP Profile (FPL)-->SIP-->X_ProxyServerRedundancy). The screenshots in the guide have always been correct.

Unknown Name (as Name was not provided) and the callerID number.
Because the phone connected to the OBi200 has no screen display

If you don't have a phone with call display, it's impossible to check caller ID when someone calls without you logging into the ATA.
You need a phone that has a "screen display"

1. Dial ***1

2. Enter that IP address into a web browser

3. Navigate to status--> Call History

If you have a phone with caller ID display, and the info shown in the Obihai ATA's call history does not display on your phone, there may be a compatibility issue between your phone and the ATA.
But the bottom line is that you need a "screen display" first.

The incoming call must also reach the ATA (and not be sent directly to FPL's voicemail) in order for CID to appear on the phone.

You can also check your FPL call logs here after logging in at https://www.freephoneline.ca/doGetCallLogs (incoming calls are only listed if they have been answered here).


Why am I not receiving Caller ID Name information on all incoming calls?


CNAM lookups are dependent upon your VoIP service provider--and not the Obihai ATA.

Freephoneline doesn't do CNAM (Caller ID Name) lookups (I.E., Freephoneline doesn't lookup the name of the caller, using the incoming phone number, in an external database). Unless CNAM is being sent by the call provider, which often is not the case with cellular calls, only the phone numbers are going to appear. CNAM lookups cost money, and for a moderately priced one time fee, FPL isn't going to do CNAM lookups.

http://forum.fongo.com/viewtopic.php?f= ... 68&p=25678 (a lot of replies in that thread are incorrect; CNAM will show up if it's sent by the provider)
"Just a reminder, as has been provided in other threads, when the call display feature is enabled, it will only show the information that is being sent by the provider. If that provider only sends a number, we can only display a number. This is especially common for cell phone providers and a number of digital service providers."--Fongo_mike"

So, with an incoming call to your FPL #, an incoming phone number will appear on your callerid, but a name only shows if that info is also sent by the provider. Other VoIP services typically charge a fee per call to do a lookup in a CNAM database (phone number is queried for a name in a database). FPL doesn't offer that option. If CNAM info is passed on by the provider, FPL will display CNAM.

Freephoneline supports outbound and inbound CNAM.
But Freephoneline will not do CNAM lookups (which cost money).

Then suddenly my FPL# has stopped working completly.

You need to be checking registration status in the ATA (not the Obitalk web portal) the next time that happens, and provide the full registration status.


A. Dial ***1

B. Enter that IP address into a web browser

C. Navigate to Status-->System Status-->SP(FPL) Service Status--Status

And the Desktop application can't call out nor receiving any calls.

Keep in mind that FPL only allows one device registration per account at any time. The most recently registered device will ring. Others will not.
If you make more than 5 registration attempts within a 5 minute period, you'll end up with a temporary IP ban from the specific FPL SIP server used.

You can not use the FPL desktop app and the OBi200 simultaneously using the same FPL account. And if both the desktop app and OBi200 have collectively made over 5 registration attempts within a 5 minute period, you'll end up being temporarily IP banned.

So, if the ATA is rebooting more than 5 times within a 5 minute period, that will get you temporarily IP banned as well.

My FPL account became unrecognized by the proxy server:
Register Failed: No Response From Server (server=208.65.240.44:5060; retry in 120s)

That's likely due to an automatic, temporary IP ban from voip.freephoneline.ca.

208.65.240.44 = voip.freephoneline.ca

You can't use both the desktop app and your OBi200 simultaneously with the same FPL account. Only one registration per account is allowed at any given time.

And if both the desktop app and OBi200 have collectively made over 5 registration attempts within a 5 minute period, you'll end up being temporarily IP banned.

The lack of a response suggests a temporary IP ban, lack of internet access (if you do have internet access, reboot the ATA), or a NAT issue.
I strongly suspect a temporary IP ban.

Since I have already applied the firmware update to version 3.1.1 (Build: 5463EX),
the OBi200's System Status shows that my firmware CONFIGURATION CURRENT with a yellow check mark,
I prefer not apply any unofficial firmware version, especially when I am not sure if that
will work or not.

It's not unofficial. You're not using the latest official firmware.

Furthermore, I don't recommend using Obitalk.com at all unless you need to configure Google Voice.

How do I stop Obihai from updating firmware without my permission and stop using Obitalk.com?


If you don't disable Obitalk Service (in addition to other settings), Obihai can remotely upgrade firmware on your device without your permission, in the middle of a storm with power flickering, while you're out somewhere. If the power goes out in the middle of a firmware upgrade, you run the risk of wrecking your ATA. Do you want a bricked device? I don't. A UPS might be a good idea, by the way (http://www.newegg.ca/UPS/SubCategory/ID-72. Doesn't have to be from Newegg. Tons of places sell them).

If firmware can be upgraded remotely, Obihai has access to your ATA and can make changes. That's fine if you need technical support. It's not fine if you're into privacy.

After 1 year is up, in order to continue using Obitalk.com to upgrade firmware, you'll need to pay a $10 USD annual fee. However, you don't need to pay if you upgrade firmware manually. Best to learn now how to do it manually, unless, of course, you like paying annual fees.

There's two ways to update firmware for free even if the ATA is out of warranty:

A. Dialing ***6 (and then pressing "1" if an update is available)

http://www.obihai.com/docs/OBiProvisioningGuide.pdf (page 15)

This is a faster method than using the Obitalk web portal since you don't have to log into anything.
If no update is found for you, you'll have to do step B.

B. Manually updating firmware via the device:
http://www.obihai.com/docs/OBiDeviceAdminGuide.pdf (page 43)

Also found after visiting http://www.obihai.com/docs-downloads and clicking on "OBi Device Firmware"

1. Download the above linked file to your computer.

2. Access the web page of the OBi device (OBi via Internet/WAN Port):

From a phone attached to the PHONE port of the OBi dial * * * 1
The IP address of the OBi will be read to you
Open a new browser window on your PC and enter the IP address of the OBi.
E.g. 192.168.1.110
When prompted, enter "admin" for username and "admin" for password.
If you have previously changed the password, use that instead of "admin."
OBi202/OBi302 Note: To access the OBi via the LAN port, by default the LAN port IP (Gateway) address is: 192.168.10.1
OBi202/OBi302 Note: To access the integral web page via the WAN port, you may need to enable WAN access. To do this, from the connected phone dial ***0. Next, enter 30# - Press 1 to enter a new value - Press 1# to enable - Press 1 to save.

(Instructions copied from ShermanOBi).

3. Now that you have accessed the OBi web page, go to the "System Management" - "Device Update" page. From there, "Browse" to the firmware file you just downloaded above and click Update.

4. Wait for the OBi to restart (approx. 30-60 seconds) and you will be good to go.


New firmware releases offer new options that sometimes aren't quickly added to the web portal. Consequently, in my opinion, it's best to stop relying on the web portal --unless, of course, you need to provision Google Voice or want to use OBiExtras ($4.99/month USD service). I don't.


To ensure Obihai and a ITSP provider can't, without your permission, update your device's firmware remotely, you must do the following (all three steps):

1. Dial ***1, and enter the IP address you're told into your web browser

2. Navigate to System Management-->Auto Provisioning

a) For Auto Firmware Update ---> ensure method is disabled

b) For ITSP Provisioning ---> change method to disabled (uncheck default box)

c) For OBiTalk Provisioning--->change method to disabled (uncheck default box)
Keep in mind changes made in Obitalk.com web portal will no longer transfer to your device
after this change is made.

(submit)

3. Navigate to Voice Services-->OBiTALK Service-->Obitalk service Settings
a) uncheck enable and uncheck the default box
You will not be able to call other Obihai devices using their respective Obitalk numbers after making this change. Also the OBi Echo test will no longer work if you disable OBiTALK Service.

(submit/reboot)

This is my lastest ATA settings, phone and status:

PrimaryProxyServer 162.213.111.21:6060

Note that X_ProxyServerRedundancy should be disabled (Service Providers-->ITSP Profile (FPL)-->SIP-->X_ProxyServerRedundancy) for the non-failover version of the guide (the screenshots are correct).

If you use the Obitalk web portal (http://www.obitalk.com) to configure your ATA, keep in mind that you must continue using it to configure your ATA unless you disable Obitalk Provisioning first. Otherwise whatever settings you change will eventually be overwritten (they will be transferred from your Obitalk.com account to your ATA) by what you previously entered at obitalk.com anyway. If you wish to disable this behaviour, dial ***1. Enter that IP address into a web browser. Navigate to System Management-->OBiTalk Provisioning-->select Disabled for the method. Save. Reboot ATA. Afterwards, obitalk.com won't overwrite whatever changes you make via the device's interface (via IP address).

Pick one method (obitalk.com) or the other (IP address of device) for changing device settings. But do not use both methods. Keep in mind that activating Google Voice requires using the Obitalk.com web portal if your Obihai ATA is using post-OAuth 2.0 firmware.

netis VDSL2 Modem Router w/ Firmware Version RTK V2.2.1

I'm not familiar with that device at all. If you don't have your own router that hasn't been provided to you by your ISP, I would probably continue using voip4.freephoneline.ca:6060 in your OBi200 to circumvent potential SIP ALG issues. It's possible there are no SIP ALG issues in that modem/router combo. But if you can't find the SIP ALG feature or are unsure, yourself, then use voip4.freephoneline.ca:6060. voip4.freephoneline.ca:6060 is meant to help with (a lack of proper two-way audio due to) faulty SIP ALG functions in routers.

As for the remainder of your post, I feel most of the issues you're having are due to using your FPL account on multiple devices simultaneously (FPL desktop app and OBi200).
I'm not sure how long it takes for the temporary IP ban to clear (or be reset).

It's impossible to switch FPL servers in the desktop app. I can't remember, but I think it uses voip.freephoneline.ca. And then your OBi200 was, previously, also using voip.freephoneline.ca. It should now be easy to understand, given that only 5 registration attempts are allowed within a 5 minute period, how you were IP banned by voip.freephoneline.ca.

"As May 2013, our servers will rate limit REGISTER requests to a maximum of 10 requests per 5 minutes. Each authentication round usually consumes 2 requests (digest auth), so it is a fair number given our guidelines. Also, it does not affect INVITES (which are also authenticated)...

This rate limit is applied per IP address as our service is tailored to residential Canadian users (ADSL/Cable)."

https://community.freepbx.org/t/trunk-s ... ca/22479/8

But in the Obihai ATA, you can choose between voip.freephoneline.ca, voip2.freephoneline.ca, and voip4.freephoneline.ca:6060. So, if you're banned on one server, you can try another (with the understanding that only voip4.freephoneline.ca:6060 circumvents buggy SIP ALG features in routers; the other two FPL SIP servers don't).
If you're banned on one server, try another.

[Liptonbrisk]

Also . . .

Are Freephoneline’s SIP servers down? My ATA isn’t registered.


A. Visit http://status.fongo.com/ to check server status.


B. Double check your Registration timers (refer to page 19). For RegistrationPeriod use 3600, and
RegistrationRetryInterval should be 120. If your ATA makes more than 5 registration attempts in 5 minutes, you will end up being temporarily IP banned by the specific FPL server the ATA was sending registration requests to.

C. If the service status website doesn’t note any issues, then chances are the problem is on your end. In your Obihai ATA or at Obitalk.com, Navigate to Voice Services-->SP(FPL) Service-->X_UserAgentPort. X_UserAgentPort should be a random port number between 30000 and 65535. Just pick a port number in that range. Change to a new port number in that range. Click the “submit” button, and reboot the ATA. (If you use Obitalk.com to change settings, you will need
need to use Obitalk.com).

If changing X_UserAgentPort works, you were dealing with a corrupted NAT connection in your router.

Possibly a NAT router connection was never disconnected or never timed out properly. And, then, the ATA keeps the corrupted connection in a persistent state over and over again. (Credit goes to Mango for this information). Possibly, this problem is due to the router's UDP timeout being in excess of the ATA's Failure Retry timer (RegisterRetryInterval with Obihai ATAs). With FPL, that's 120 seconds.


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, 10, 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.

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 Tools-->Other settings. In part, for this reason, I tend to use Asus routers. 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.


D. You can also try rebooting your modem–>router (wait for it to be fully up and transmitting data)–>ATA (in that order). This is the proper device reboot order.

[Liptonbrisk]

Nettis 4422 modem from Carry Telecom
http://www.carrytel.ca/support.aspx. (click the "Internet" tab)

Q : DSL - My VoIP phone does not work with Netis 4422 modem.

A: Please download the newest Netis firmware file at http://www.carrytel.ca/download/netis1228.zip, and update the firmware file netis1228.img for your modem. The new firmware has been tested and working with most of Voip phone providers



Contact your ISP for more information.

[Liptonbrisk]

Firmware 3.1.1 (Build: 5589) is now the latest firmware version for both the OBi200 and OBi202: http://fw.obihai.com/OBi202-3-1-1-5589.fw
Firmware 3.1.1 (Build: 5589) also works with version 1.32 of the guide.

Changelog is located at https://www.ukvoipforums.com/viewtopic.php?f=25&t=987

[teensee]

Hello Liptonbrisk,

First, thank you very much for giving full answer and clear explanation
about the issues that I've met and providing the steps that I should follow.

I've used the official and new firmware version file, OBi202-3-1-1-5577.fw, to update my OBi200.
and l used that Setup Guide version 1.32 for the settings of my OBi200.

You are 100% right. I need to use a phone with display screen.
I have an old UNIDEN digital answering phone DECT 6.0 with display screen connected to the ATA OBi200.
With the firmware 3.1.1 (Build: 5463EX), I can hear the dial tone but the phone doesn't ring nor
displaying when an incoming call was placed.
There may be a compatibility issue between the 2 devices, or incorrect settings, or a bug in the firmware 5463EX? That why I've used the non-display phone for now.
After each test, I verified call status either in the OBi200 call history or in the call logs of the FPL web site.

Thanks you Liptonbrisk for many new things that I've learned from you.
I've seen that you've added a new reply about the latest firmware 5589 in March 2017 for OBi200.

My VoIP is partially working for a few hours and now stopped working.
After locally update OBi200 to the lastest firmware 3.1.1 (Build: 5577), I have 2 new issues:
1) An incoming call has its call ID displayed, but it has one way audio issue: the caller/landline
can't hear the voice from the FPL VoIP phone.

2) The VoIP phone has dial tone but can't make outgoing call.

I have no idea what I have missed.
What I have tried: Re-power cycle and reboot all devices in proper order:
Ensure that my Internet connection, my local network, and my ATA are working. FPL status is registered.
Ensure that the Fongo VoIP Services Status are ok. Ping to all FPL VoIP proxy servers and receive no loss.
Review ATA settings using the Guide 1.32 and re-apply if necessary. I can't find anything wrong.

Since I know now that I can't use the ATA and the FPL Desktop app at the same time, I have also tried to remove
my FPL account in the FPL Desktop app.
What can I do now?
Do I have to request Tech Sup to apply a "Force request" on my account, to resolve the one way audio issue?

Two days later until today, my FPL account always get Register Failed for any VoIP proxy servers:
voip, voip2, and voip4.freephoneline.ca.

Status Register Failed: No Response From Server (server=162.213.111.21:6060; retry in 44s)

So I am getting stuck now, until someone from Fongo Tech Support help
and reset my FPL account status so my account can be registered.

I've submitted 2 requests to tech Support asking to 'force account registration'.
But nobody has really look at its contents.
I got automatic reply with useless suggestions for my deadlock situation!

Fongo Request Received - Ticket #236623 - Voip unlock key become unregistered (see attachment}
Fongo Request Received - Ticket #236610 - Account became unregistered

Can you help to have a human read the ticket instead?
I feel unfair after paying for the VoIP but get into a deadlock situation for many days
because proxy servers keep swapping my account from "registered" to "banned" repeatedly.

Why Fongo and FPL not publishing clearly these rules and restrictions
in the websites about what you can use and what you cannot do or use?
Such as you cannot use the FPL desktop and the VoIP account at the same time
for the same FPL account.

Luckily, we have you to help and to explain on what went wrong.
Many many thanks again, Liptonbrisk.

[Liptonbrisk]

I have an old UNIDEN digital answering phone DECT 6.0 with display screen connected to the ATA OBi200.
With the firmware 3.1.1 (Build: 5463EX), I can hear the dial tone but the phone doesn't ring nor
displaying when an incoming call was placed.

Well, you need to get incoming audio working properly first before you can determine whether there's a compatibility issue with your handset (other possibilities include ring voltage, but it's not worth
pursuing other possibilities if incoming calls aren't working: http://forums.redflagdeals.com/setup-vo ... #p24833419). Incoming audio needs to work first.

I've seen that you've added a new reply about the latest firmware 5589 in March 2017 for OBi200.

Yes, I'm using 3.1.1 (Build: 5589) without any issues, but I'm extremely skeptical the issue you're having is OBi200 firmware related.

My VoIP is partially working for a few hours and now stopped working.
After locally update OBi200 to the lastest firmware 3.1.1 (Build: 5577), I have 2 new issues:
1) An incoming call has its call ID displayed, but it has one way audio issue: the caller/landline
can't hear the voice from the FPL VoIP phone.

a) Refer to page 17 of the manual. Use voip4.freephoneline.ca:6060

b) Ensure that you're using the proper firmware for your modem/router combo: http://forum.fongo.com/viewtopic.php?f=8&t=18964#p74447
Contact your ISP to see if you're using the latest tested firmware for VoIP.

c) Try a new random port number between 30000 and 65535 for X_UserAgentPort.

The VoIP phone has dial tone but can't make outgoing call.

The ATA needs to be receiving server responses (or otherwise registered) from Freephoneline in order for that to work properly.

(You're geting "no response received" from the server).

Review ATA settings using the Guide 1.32 and re-apply if necessary. I can't find anything wrong.

The extremely important settings are the registration timers. These are also listed on page 17:

d) RegistrationPeriod should be 3600, and RegisterRetryInterval should be 120s.

e) If you ported in a phone number to Freephoneline, your SIP Username has changed.
Double check your SIP Username and SIP Password after logging in at https://www.freephoneline.ca/showSipSettings

Those entries need to be listed under Voice Services-->SP(FPL) Service-->SIP Credentials

AuthUsername is your SIP Username.
AuthPassword is your SIP Password.

f) Ensure that X_UsePublicAddressinVia is enabled under Service Providers-->ITSP Profile (FPL)-->SIP.

Since I know now that I can't use the ATA and the FPL Desktop app at the same time, I have also tried to remove
my FPL account in the FPL Desktop app.
What can I do now?

You can uninstall the FPL desktop app on any computer you have in your household. If the desktop app is running and logged in, then the desktop app is registered with FPL. That's a problem.

Do I have to request Tech Sup to apply a "Force request" on my account, to resolve the one way audio issue?

You can certainly try doing so, although that won't fix the actual registration issue you're describing below.

A registration issue and a one-way audio issue are separate issues. "Forced registration" doesn't actually address a registration issue.

https://support.fongo.com/hc/en-us/requests/new
Select "VoiP Unlock Key"-->"My account inquiry" for the issue type. Request a forced registration, and mention your one-way audio issue.

Two days later until today, my FPL account always get Register Failed for any VoIP proxy servers:
voip, voip2, and voip4.freephoneline.ca.

Status Register Failed: No Response From Server (server=162.213.111.21:6060; retry in 44s)

This is what I would do:



1) I would uninstall the Freephoneline desktop app from all of your computers.

2) Update modem firmware

3) Unless you're using Google Voice or need Obitalk (for OBi to OBi device calling), I would factory reset your ATA: https://www.obitalk.com/info/faq/Troubl ... tory-Reset. And I would remove your device from your Obitalk.com web portal account.

4) Then I would follow the steps I listed earlier under "How do I stop Obihai from updating firmware without my permission and stop using Obitalk.com?" in this thread.

5) I would unplug my router and ATA for at least two hours (especially the ATA) to try to clear the IP ban if there is one. I'm not sure how long the temporary IP ban lasts for. Possibly it's longer than 2 hours. I'm not sure.

6) Finally, I would follow version 1.32 of the guide, step by step, starting on page 11: http://forum.fongo.com/viewtopic.php?f= ... 439#p74439.

7) I would use voip4.freephoneline.ca:6060 when I get to page 17.

8) I would probably request a forced registration.

Can you help to have a human read the ticket instead?

I can't because I don't work for Fongo or Freephoneline. You can send a private message to Fongo Support with your ticket numbers though: http://forum.fongo.com/ucp.php?i=pm&mode=compose&u=7852

Such as you cannot use the FPL desktop and the VoIP account at the same time
for the same FPL account.

It's not just the desktop app. It's anything: ATA, smartphone, computer, etc. You can't register your Freephoneline account more than once at any given time. So if you have multiple ATAs, you can't register the same FPL account on more than one ATA either.