I have a FPL account that is several years old. I ported my childhood number to it. For the last 3 months I haven't been using the phone. In fact I was out of the country. I came back and my account is in good standing, I have some long distance credit on it. My link sys apt connected, fine for it and another line I have with FPL. However if someone tries to call from outside the network it says "This number is not in service". I'm freaking out because I don't want to lose the number I have had for 48 years. I also know the config is right because it works fine with my other acct from FPL. I can make calls, but if you try and dial in it says not in service. I put in a ticket but haven't heard back.
Thanks for any help or explanation you can give.
John
Number not in service
-
- Just Passing Thru
- Posts: 17
- Joined: 02/12/2013
- SIP Device Name: HT701 and HT286
- ISP Name: Acanac
- Router: Cisco
-
- Technical Support
- Posts: 2837
- Joined: 10/18/2009
Re: Number not in service
PM the ticket number to Fongo Support here on the forum. (http://forum.fongo.com/ucp.php?i=pm&mode=compose&u=7852)
There isn't really much we can do as a forum due to the fact it is account related. If you can log into your account online, it sounds like it might just be a routing or login problem.
Fongo Support will be your best course of action from here.
There isn't really much we can do as a forum due to the fact it is account related. If you can log into your account online, it sounds like it might just be a routing or login problem.
Fongo Support will be your best course of action from here.
-
- Just Passing Thru
- Posts: 17
- Joined: 02/12/2013
- SIP Device Name: HT701 and HT286
- ISP Name: Acanac
- Router: Cisco
Re: Number not in service
Thanks I sent a PM. Was kind of freaking out because I didn't want to lose the number.
John
John
-
- Site Moderator
- Posts: 1689
- Joined: 01/01/2013
Re: Number not in service
Hi,boatguy wrote:Thanks I sent a PM. Was kind of freaking out because I didn't want to lose the number.
John
I hope you get it resolved very soon.
Was it working properly and just started to do this today, Jan 18 2016?
It doesn't look like the error is coming from our servers as I don't recognize it.
Perhaps you have fwded all your calls to a different number?
Can you check this?
Thanks,