No Incoming Calls "Number not in Service"

[nezzie]

I had a FPL number since March, running fine through my PAP2T. Had the ports fwd'ing all fine on my router, and two weeks ago I had FPL port my number over to them. Since then I cannot receive incoming calls. When calling my number, you get an operator that says "The number you've reached is not in service". I figured it must be the old phone company, so I called them, and they checked out everything, and said nope, you number was ported over 12 days ago, there is nothing "lingerin" in their system, that would bring up such a message, as far as they are concerned I am not their customer anymore.

I double/triple/quadrupole checked my PAP2T config. I updated my SIP user ID, from the old FPL number, to me new Ported phone number, also reconfirmed all my SIP settings from FPL.ca. Rebooted the PAP2T, and my router a half dozen times, and still same problem.

I called FPL support, they said they cannot provide tech support too me, for the PAP2T, so I am SOL. They suggested I "reopen" my fwd'ing ports on my Router, UDP 5060 - 5061. I closed them, reopened them, saved rebooted, still no go. I called old phone Co. back to ensure that the "next person" would tell me the same story that all was fine, and again they said it was. I called back FPL support, talked with them and still got nowhere. I am stumped, is this the phone co. of is this an FPL problem? I can make outgoing calls fine, just no incoming ones. I am using the PAP2T from the Device COnfiguation section, within the FPL forums, as well y setup is a TP-LINK TL-WR841N router, and a PAP2T Firmware Version: 3.1.15(LS).

Anyone have any ideas?

[TheHardy]

I had a FPL number since March, running fine through my PAP2T. Had the ports fwd'ing all fine on my router, and two weeks ago I had FPL port my number over to them. Since then I cannot receive incoming calls. When calling my number, you get an operator that says "The number you've reached is not in service". I figured it must be the old phone company, so I called them, and they checked out everything, and said nope, you number was ported over 12 days ago, there is nothing "lingerin" in their system, that would bring up such a message, as far as they are concerned I am not their customer anymore.

I double/triple/quadrupole checked my PAP2T config. I updated my SIP user ID, from the old FPL number, to me new Ported phone number, also reconfirmed all my SIP settings from FPL.ca. Rebooted the PAP2T, and my router a half dozen times, and still same problem.

I called FPL support, they said they cannot provide tech support too me, for the PAP2T, so I am SOL. They suggested I "reopen" my fwd'ing ports on my Router, UDP 5060 - 5061. I closed them, reopened them, saved rebooted, still no go. I called old phone Co. back to ensure that the "next person" would tell me the same story that all was fine, and again they said it was. I called back FPL support, talked with them and still got nowhere. I am stumped, is this the phone co. of is this an FPL problem? I can make outgoing calls fine, just no incoming ones. I am using the PAP2T from the Device COnfiguation section, within the FPL forums, as well y setup is a TP-LINK TL-WR841N router, and a PAP2T Firmware Version: 3.1.15(LS).

Anyone have any ideas?

Which # is coming up NIS? The old FPL # or the ported-IN #? If you make an outgoing call, what shows up on the receiving Caller ID? There was a similar post in another thread I replied to, not sure if it was you double-posting or not ...

Once a port is done, if it is ported INTO FPL on an existing FPL account, the old account (phone number) is OVERWRITTEN with the ported-IN # ... the FPL# will then be OUT OF SERVICE ...

If it is your ported-IN # that is coming up NIS when someone calls it, then it is an FPL problem -- once the port is initiated, your OLD telco washes their hands of you and it is the new company all the way ... it could be a messed up port, in which case it will be up to FPL to sort it out, even if your OLD telco buggered it up, as FPL (as soon as the VERY first paperwork for the port starts getting done!) is NOW responsible for that #! You will need to make sure you pursue this as high up as you need to in order to get it resolved.