Freephoneline, Obihai 200 and Rogers

Have a question or problem with your Fongo application? This forum is the place to get help from both staff and fellow community members.
Fongo recommends Fongo Home Phone for a fully supported Home Phone system for only $4.95/mo
ag2000
Just Passing Thru
Posts: 7
Joined: 12/17/2010

Freephoneline, Obihai 200 and Rogers

Post by ag2000 »

Trying to help my friend to set up his freephone line, Obihai 200 worked fine from my home (Bell internet) but when I installed at his house (Rogers) it says "this account number is not valid" when I am trying to dial out. I used configuration recommended for Rogers and Obihai 100 from this forum. Incomining calls do not work as well.

I tried desktop application and it works fine, WHen I check status it says "Registered (server=98.143.96.114:6060; expire in 2064s)(UAP:5080) ", so it looks like it is registering properly.

Also, echo test works well.

What can cause the problem?

Thanks for your help!
User avatar
Fongo Support
Site Moderator
Posts: 1689
Joined: 01/01/2013

Re: Freephoneline, Obihai 200 and Rogers

Post by Fongo Support »

ag2000 wrote:Trying to help my friend to set up his freephone line, Obihai 200 worked fine from my home (Bell internet) but when I installed at his house (Rogers) it says "this account number is not valid" when I am trying to dial out. I used configuration recommended for Rogers and Obihai 100 from this forum. Incomining calls do not work as well.

I tried desktop application and it works fine, WHen I check status it says "Registered (server=98.143.96.114:6060; expire in 2064s)(UAP:5080) ", so it looks like it is registering properly.

Also, echo test works well.

What can cause the problem?

Thanks for your help!
Hi there,

Please see Mango's reply here:

http://forum.fongo.com/viewtopic.php?f= ... ble#p68060

If you configure OBI by pdf file, you needs to disable provisioning and any update from Obitalk website.

Regards,
Mango
Tried and True
Posts: 411
Joined: 08/14/2014
SIP Device Name: OBi110
Firmware Version: 1.3.0 (Build: 2824)
ISP Name: Telus
Computer OS: Windows 7
Router: Toastman Tomato

Re: Freephoneline, Obihai 200 and Rogers

Post by Mango »

ag2000 wrote:WHen I check status it says "Registered (server=98.143.96.114:6060; expire in 2064s)(UAP:5080) "
This means nothing. FPL always allows registration even when credentials are wrong.

Please double check that your AuthUserName is your (friend's) FPL number, exactly 11 digits, beginning with 1.
ag2000
Just Passing Thru
Posts: 7
Joined: 12/17/2010

Re: Freephoneline, Obihai 200 and Rogers

Post by ag2000 »

Fongo Support wrote:
ag2000 wrote:Trying to help my friend to set up his freephone line, Obihai 200 worked fine from my home (Bell internet) but when I installed at his house (Rogers) it says "this account number is not valid" when I am trying to dial out. I used configuration recommended for Rogers and Obihai 100 from this forum. Incomining calls do not work as well.

I tried desktop application and it works fine, WHen I check status it says "Registered (server=98.143.96.114:6060; expire in 2064s)(UAP:5080) ", so it looks like it is registering properly.

Also, echo test works well.

What can cause the problem?

Thanks for your help!
Hi there,

Please see Mango's reply here:

http://forum.fongo.com/viewtopic.php?f= ... ble#p68060

If you configure OBI by pdf file, you needs to disable provisioning and any update from Obitalk website.

Regards,
Thanks for the quick reply,
I will try that. However, it is still strange why it worked from my home without disabling the provisioning. Also, as I understand, if I use provisioning - as long as I use proper information (server, port, credentials etc.), it should work, too - correct?

Is this possible that using VoIP from 2 different IP addresses the same day could cause a problem? I also tried rogers phone hotspot, to eliminate router issue, maybe FPL system did not like it?
Mango wrote:
ag2000 wrote:WHen I check status it says "Registered (server=98.143.96.114:6060; expire in 2064s)(UAP:5080) "
This means nothing. FPL always allows registration even when credentials are wrong.

Please double check that your AuthUserName is your (friend's) FPL number, exactly 11 digits, beginning with 1.
Thanks, I verified username and password many times, and reapplied them as I thought it could cause the problem, but it definitely did not help.

Is UAP still OK to use default port 5080 for rogers modems? I tried 6060, but it also did not seem to make a difference.

Is there any test I can do to ensure correct authentication?
Mango
Tried and True
Posts: 411
Joined: 08/14/2014
SIP Device Name: OBi110
Firmware Version: 1.3.0 (Build: 2824)
ISP Name: Telus
Computer OS: Windows 7
Router: Toastman Tomato

Re: Freephoneline, Obihai 200 and Rogers

Post by Mango »

Yes, either of those numbers should be fine for X_UserAgentPort.

It should theoretically be fine to use the equipment from different IP addresses.

With FPL, you are already doing the best authentication test which is making a phone call.

Just to check, did you use voip4.freephoneline.ca on port 6060 when you tested on your Bell internet connection? It's fine to use the Rogers proxy with a Bell internet connection (but not the other way around).
ag2000
Just Passing Thru
Posts: 7
Joined: 12/17/2010

Re: Freephoneline, Obihai 200 and Rogers

Post by ag2000 »

Mango wrote:
Just to check, did you use voip4.freephoneline.ca on port 6060 when you tested on your Bell internet connection? It's fine to use the Rogers proxy with a Bell internet connection (but not the other way around).
With Bell I changed back to voip.freephoneline.ca and port 5060.

However, I am able to pinpoint exact cause of the problem now.

I just purchased key for myself as I decided to port one of my own landlines to freephone line as well.
So, I took the device I configured for my friend to my house and tested again (assuming it will work with Bell) - but now it was giving me the same error message (this account is not valid).

I replaced his credentials with mine, and everything started to work (with my phone number of course).!!!

Now I was asking myself - why his account worked when I configured it first day at my house (with Bell)? The only difference I see that at that time he had original FPL number, and next day he received ported number from Bell on the same account.

SO, it looks like it has nothing to do with Rogers or Bell, but somehow after porting his number, his credentials/key stopped working.

In any case - what is the proper way for my friend to contact FPL and ask to reassign his key (ID and password), or perhaps reset his account? BTW, his account works well from desktop application.

BTW - my own number will be ported tomorrow, so I will see if I will experience the same problem (as I also purchased key and number porting at the same time.).

******************************************************************************************

EDIT : As I realized that problem happened after porting I started to read through this forum and found very important message from Jake
Things I will mention -
1. When you port your number in, you will loose the FPL number you have currently.
2. When your number is ported into FPL you will have to go into your ATA and change your username setting from your current FPL number to your newly ported number INCLUDING the initial 1.
I kept using the number that was assigned prior to porting as I thought it remains as username!!!

I will report the results!!!
Mango
Tried and True
Posts: 411
Joined: 08/14/2014
SIP Device Name: OBi110
Firmware Version: 1.3.0 (Build: 2824)
ISP Name: Telus
Computer OS: Windows 7
Router: Toastman Tomato

Re: Freephoneline, Obihai 200 and Rogers

Post by Mango »

I'm glad it's working now!
ag2000
Just Passing Thru
Posts: 7
Joined: 12/17/2010

Re: Freephoneline, Obihai 200 and Rogers

Post by ag2000 »

OK, quick report - everything works now at my friend's place.
The only side note - I had to put Obihai in DMZ (with a strong password). For some reason, when I used recommended rogers configuration for Obihai (and disabled provisioning) - whenever I tried to call someone - call was received properly however I could not hear them and they could not hear me. Putting Obihai in DMZ solved the problem. SO, I guess, I will need to look into port forwarding and find out which ports have to be forwarded to make it work. This is not urgent but still needs to be done - to be safer, I guess.

I have no problem with Bell, the same configuration works even without DMZ...
Mango
Tried and True
Posts: 411
Joined: 08/14/2014
SIP Device Name: OBi110
Firmware Version: 1.3.0 (Build: 2824)
ISP Name: Telus
Computer OS: Windows 7
Router: Toastman Tomato

Re: Freephoneline, Obihai 200 and Rogers

Post by Mango »

Try the following:

1) Verify that ITSP Profile A >> SIP >> X_DiscoverPublicAddress is checked.
2) Use the router to forward the UDP port range 16600-16798 to the ATA. (This is the default UDP range from ITSP Profile A >> RTP.)
3) If neither 1) or 2) work, open a ticket at http://support.fongo.com/anonymous_requests/new, explain the symptoms, and ask for your account to be verified.

If possible, I would like to see things working without DMZ.
ag2000
Just Passing Thru
Posts: 7
Joined: 12/17/2010

Re: Freephoneline, Obihai 200 and Rogers

Post by ag2000 »

Mango wrote:Try the following:

1) Verify that ITSP Profile A >> SIP >> X_DiscoverPublicAddress is checked.
2) Use the router to forward the UDP port range 16600-16798 to the ATA. (This is the default UDP range from ITSP Profile A >> RTP.)
3) If neither 1) or 2) work, open a ticket at http://support.fongo.com/anonymous_requests/new, explain the symptoms, and ask for your account to be verified.

If possible, I would like to see things working without DMZ.
Thanks, will try it later tonight!
ag2000
Just Passing Thru
Posts: 7
Joined: 12/17/2010

Re: Freephoneline, Obihai 200 and Rogers

Post by ag2000 »

Just realized I never posted my results. Big thanks to Mango as everything is working well for my friend with Rogers.

However, I found that today I started to experience similar problems with my Bell router, the other party could hear me but I could not hear them, and reboot of Obihai unit did not help. In the past everything was working well.

So, I did port forwarding on my Bell router as well, as was recommended by Mango in the previous post and everything started to work!