Failed Registration starting at around 10:30PM EST
Failed Registration starting at around 10:30PM EST
Anyone else having problems? Was working fine around 10pm EST but now is down. I rebooted the router and the adapator.
Also, cannot get into the login page for FPL. It just times out.
Was able to login to FPL. SIP settings show Connected, but still failing registration. odd.
Also, cannot get into the login page for FPL. It just times out.
Was able to login to FPL. SIP settings show Connected, but still failing registration. odd.
Re: Failed Registration starting at around 10:30PM EST
I have trunks registered to both the voip and voip2 servers. The trunk that is registered to voip2.freephoneline.ca is fine, the other one is not connecting - so there must be a problem with that server again.
Try to switch over to the voip2 server and see if you connect again.
Try to switch over to the voip2 server and see if you connect again.
Re: Failed Registration starting at around 10:30PM EST
I just changed the registration to the voip2 server and my failed trunk came back online straight away, so there is certainly something wrong on the voip.freephoneline.ca server it would seem.
Re: Failed Registration starting at around 10:30PM EST
Thanks for the reply Jake. VOIP2 seems to be working. I didn't try making a call, but it registers and I do get a dialtone.
-
- Lightly Seasoned
- Posts: 194
- Joined: 06/09/2010
- SIP Device Name: SPA3102
- Firmware Version: 5.2.13(GW002)
- ISP Name: Cogeco Cable
- Router: DPC3848VM (Modem/Router)
- Location: Burlington, Ontario
Re: Failed Registration starting at around 10:30PM EST
For your information -
Location Burlington, Ontario:
I just noticed at 2335hrs my registration was down. (could have been longer). Just now at 2358hrs came back online without changing anything.
Back down again at 0000hrs.
Hopefully it will get sorted out.
Location Burlington, Ontario:
I just noticed at 2335hrs my registration was down. (could have been longer). Just now at 2358hrs came back online without changing anything.
Back down again at 0000hrs.
Hopefully it will get sorted out.
Re: Failed Registration starting at around 10:30PM EST
I was also having connections issues all night here in Barrie, Ontario.
I just switched my server from voip.freephoneline.ca to voip2.freephoneline.ca and now I am connected again.
I hope it stays connected now.
Thanks Jake
I just switched my server from voip.freephoneline.ca to voip2.freephoneline.ca and now I am connected again.
I hope it stays connected now.
Thanks Jake
Re: Failed Registration starting at around 10:30PM EST
Well the funny thing was I switched that failed trunk back to voip.freephoneline.ca a little while later and it still stayed connected, so maybe the server was just having a funny 5 minutes.
There was definitely a problem on that server that didn't seem to be on the voip2 server. From what I have seen the voip2 server seems to be stable compared to the voip server, but that could be because less people are connected to it.
Let's see if Fongo will advise us of anything in the morning, if they even noticed
There was definitely a problem on that server that didn't seem to be on the voip2 server. From what I have seen the voip2 server seems to be stable compared to the voip server, but that could be because less people are connected to it.
Let's see if Fongo will advise us of anything in the morning, if they even noticed
-
- Active Poster
- Posts: 65
- Joined: 03/18/2012
- SIP Device Name: Obi202
- Firmware Version: 3.2.2 5857EX
- ISP Name: Teksavvy Cable+DSL
- Computer OS: Windows 10 pro 64bit
- Router: Sonicwall TZ500+R7000+EX7000
- Smartphone Model: iPhone 6s ios 11.4
- Android Version: Galaxy S3 Tab Oreo
- iOS Version: ipad pro 9.3.3 JB
Re: Failed Registration starting at around 10:30PM EST
failed registration now 1:09am in toronto.
EDIT:changed to voip2, got back.
EDIT:changed to voip2, got back.
-
- Just Passing Thru
- Posts: 18
- Joined: 06/01/2010
- SIP Device Name: Linksys PAP2T-NA
- ISP Name: Teksavvy
- Computer OS: Windows 7
Re: Failed Registration starting at around 10:30PM EST
Same here. I checked the Asterisk log and lot's of registration time outs with FPL over the night. I just changed from voip to voip2 to see what happens in the next hours - it's online now.
What do you guys have for the registration time? I have defaultexpiry = 120 (seconds) which is the default in Asterisk and I was thinking to increase that value and reduce the number of registrations.
What do you guys have for the registration time? I have defaultexpiry = 120 (seconds) which is the default in Asterisk and I was thinking to increase that value and reduce the number of registrations.
Re: Failed Registration starting at around 10:30PM EST
The registration time Fongo wants you to use is 3600. I changed mine to that several weeks back and it has been fine.
While you are in there messing around, I changed mine registry retry time to 120 as requested by Fongo.
http://support.freephoneline.ca/entries ... redentials
While you are in there messing around, I changed mine registry retry time to 120 as requested by Fongo.
Code: Select all
registertimeout=120
-
- Just Passing Thru
- Posts: 18
- Joined: 06/01/2010
- SIP Device Name: Linksys PAP2T-NA
- ISP Name: Teksavvy
- Computer OS: Windows 7
Re: Failed Registration starting at around 10:30PM EST
Thanks Jake for your comments. I updated my registration times accordingly.
-
- Quiet One
- Posts: 26
- Joined: 11/20/2012
- SIP Device Name: SPA112
- Firmware Version: 1.3.2_014
- ISP Name: Start Communications
- Computer OS: Windows 7 x64
- Router: DIR-827
Re: Failed Registration starting at around 10:30PM EST
I really wish they would update the SIP settings/register expires value on the desktop app settings page of the website.
It's pretty evident that with all the changes setting register expires to 180 is far too low now. I've even tried 300, 900 but I still frequently end up with registration failed messages - until I change the value to 3600
Please update your website to correct this misleading information if 180 is no longer valid - it will cause ongoing grief for both customer and provider!
It's pretty evident that with all the changes setting register expires to 180 is far too low now. I've even tried 300, 900 but I still frequently end up with registration failed messages - until I change the value to 3600
Please update your website to correct this misleading information if 180 is no longer valid - it will cause ongoing grief for both customer and provider!