Bell and Telus incoming calls are fast busy

[harleys]

Hi all,

I hope someone can explain this... About a week or 2 ago my wife's Telus cell phone stopped being able to call our FPL Home line, running a Cisco SPA112 (latest firmware), 613-288-8xxx. I have a Rogers cell phone and I can call our home no problem. I went to work to try to call from our Bell Business line and it too can not call my home. I then called all the people I convinced to move to FPL:
my dad, 514-684-3xxx, running GrandStream HT502, he configured himself
my bestman, 514-683-7xxx, running GrandStream HT502, he configured himself
my mom-in-law, 514-558-9xxx, running GrandStream HT286, FPL configured it years and years ago, FPL sold me the unit preconfigured!!
my dad-in-law, 514-748-2xxx, running GrandStream HT701, I configured
And the same thing, none of them can receive my call from a Bell line, all fast busy...

Any ideas?

[Mango]

For interest's sake, please try to use your Bell Business line or your wife's Telus cell phone to call 1.289.850.1573. This number is with Fibernetics, but not Free Phone Line. If you hear "that number has not yet been assigned", the call was routed correctly.

Either way, I think you will need to submit a ticket at http://support.fongo.com/anonymous_requests/new . Since it affects multiple carriers (Telus and Bell) and multiple FPL accounts, I do not think this is something you will be able to resolve by yourself.

[harleys]

Thanks Mango for your quick reply, I just tried to call 1-289-850-1573 and I get the same fast busy... So does the mean that this is a Telus routing issue? Again this only started happening a couple weeks ago. We've been a FPL customer for over 5 years...

Can someone with a Bell line do a test to that number? I can try to go to a neighbour's house and try it too, but I have tried from both my workplaces, as I am an IT consultant, currently on 2 contracts...

[Mango]

This confirms the problem affects more of Fibernetics than just FPL. I'm sorry I don't have a Bell line to help test with, but I think you've tested sufficiently to warrant a ticket.

I'm mildly surprised there aren't more posts about this.

[ckkatan]

I just tested my FPL line using both Rogers and Bell cell (registered to voip.FPL.com). I received a fast busy signal with Rogers and 1 ring then fast busy signal with Bell.

I reset it to voip2.FPL.com, then problem resolved.

Similar busy signal happened to our line a few days ago as well. I resolved it by switching from one server to another.

@Fongo Support, should I submit a ticket to request for investigation?

[Mango]

Your symptoms are different from harleys'.

Be sure that NAT Keep Alive is enabled on your ATA, and that Register Expires is set to 3600.

Next time the problem happens, try to change your ATA's SIP Port to a random number between 20000 and 65535, while the problem is happening. If that solves the problem, it indicates the problem is with your configuration. From there we can troubleshoot further.

[ckkatan]

Hi Mango,

I double checked. The ATA setting is exactly as per the FPL setting procedure. The NAT Keep Alive is enabled, and Register expires is set to 3600. The SIP port is also set to a random number outside of the default ranges.

It seems to be working properly 99% of the times. Except when registration renewal time is at 300 seconds or less (both times when I noticed this problem). Any other idea how to resolve this issue?

Many thanks.

[tango]

Thanks Mango for your quick reply, I just tried to call 1-289-850-1573 and I get the same fast busy... So does the mean that this is a Telus routing issue? Again this only started happening a couple weeks ago. We've been a FPL customer for over 5 years...

Can someone with a Bell line do a test to that number? I can try to go to a neighbour's house and try it too, but I have tried from both my workplaces, as I am an IT consultant, currently on 2 contracts...

I still have a Bell landline and called, received a voice msg "that number has not yet been assigned, please contact technical...".
I also used my FPL phone to call, also heard the exact same voice msg "that number has not yet been assigned..."

Hope this helps!