Page 1 of 1

The cellular number you have called is not assigned.

PostPosted: 07/31/2018
by bridonca
I ported a number from Rogers to Koodo yesterday. The port likely took within an hour. The port works when I use my other cellular accounts, Google Voice and Magic Jack. However, when I use the various Fongo services I have at my disposal, I get this as a recording "The cellular number you have called is not assigned."

Out of curiosity, how long does it take for Fongo to recognize a port?

Re: The cellular number you have called is not assigned.

PostPosted: 07/31/2018
by Liptonbrisk
Unfortunately, I don't know the exact time. Is it working for you now? The same issue has been reported when people port into Freephoneline/Fongo. Other carriers appear to get updated before Fibernetics (for example, at viewtopic.php?f=8&t=19239 Bell's system has already recognized the port, and it's just a waiting game). Give it until tomorrow morning. If the issue persists, send a ticket in. As you indicate, it's usually just a matter of waiting.

Re: The cellular number you have called is not assigned.

PostPosted: 08/01/2018
by bridonca
I was under the assumption a port has nothing to do with the calling carrier, though this seems not to be the case with Fongo. I am more interested in how Fongo does it, being they seem to be the oddball in this setup. In any case, I was never concerned Fongo would eventually route to the new port eventually. All is good.

Re: The cellular number you have called is not assigned.

PostPosted: 08/01/2018
by Liptonbrisk
To clarify, I mean that when porting takes place, routing updates need to occur. Some carriers take awhile to fully update routes, and random issues, such as what you witnessed, can occur.

Porting notifications go to NPAC and once activated, the porting changes get broadcasted to CLECs, or, at least, that's my understanding. The updates are supposed to happen automatically, but for whatever reason, Fibernetics' interval for updates seems to be a bit slower than with some other companies. I find these types of issues typically resolve within 24hrs. If not, intervention is required (submit a ticket).