Followme number cannot be removed ???

[mohnashaat]

Long time ago i saved my cell number as a followme number, now i want to remove it, whwn i opened the followme tab, my cell number wasn't there even that it is still fwding to my cell. and even when i disabled the followme option, it stills fwd to my cell ??!

[TheHardy]

Interesting! I wonder if that one "follow" module upgrade done a few months ago might have messed up somewhere. If your settings page has it empty and disabled and it is still doing it, I have one quick suggestion to try --- set the follow me to another number (any real functioning number) ... one you can use that goes to an automated recording so as NOT to bother anyone is the "Environment Canada Automated Weather Report for Vancouver Region" --- 604-664-9010. It will always either answer with an automated recording (or ring busy, even though it is a multi-line number).

After setting that a forward number, call your FPL #, have it forward, and listen to the weather, hang up. Then go back, remove THIS number, try your FPL # again and see if your cell phone rings...

If your cell # was "stuck", this might "unstick" it.

If this does not resolve the problem, then perhaps PM to FPL-MIKE as he is fairly active here ... he'll most likely want to know your FPL # and potentially what your cell # is that it is fwding to, but he should be able to get someone to look into your account and see why your # is "stuck" ...

Hope solution #1 fixes it for you though! Let us know!

[FONGO_steve]

I'd suggest contacting support for this type of issue as it will need someone with access to our systems to fix (aka our staff). You could also PM me your details too.

[TheHardy]

I'd suggest contacting support for this type of issue as it will need someone with access to our systems to fix (aka our staff). You could also PM me your details too.

WB Steve! I didn't mean to relegate you to 2nd Banana status, you were vay-kay-ing. I had a previous situation where the online management system did not want to let me "unforward" as well, and my simple trick worked; it may NOT be the same issue, as you pointed out though.

Contacting CS is always a good idea (and other forum users are again reminded to NOT disclose your account info to anyone on the forums EXCEPT known FPL employees) --- currently Steve, Kris and Mike... (and a side note, all 3 of which are very good at getting broken things fixed!)

[mohnashaat]

Thanx Hardey for ur solution, i'll try it, but i already send my info to steve

[TheHardy]

Thanx Hardey for ur solution, i'll try it, but i already send my info to steve

Steve'll track down what is wrong ... if it takes a bit for him to get dealt with for you, feel free to try my "non-official" attempt and see if that makes 'er work for ya!

[FONGO_steve]

All clear now

[TheHardy]

All clear now

Super-Steve strikes again! BTW do you get a new FonGo cape to replace your well-worn FPL one?

Unless it is a trade-secret, mind if I inquire as to the nature of the problem, or just a glitch in the software someplace?

[FONGO_steve]

All clear now

Super-Steve strikes again! BTW do you get a new FonGo cape to replace your well-worn FPL one?

Unless it is a trade-secret, mind if I inquire as to the nature of the problem, or just a glitch in the software someplace?

Part of me is almost wondering if it's maybe a browser or java issue - I was able to remove the number fine from the account in my web browser. I also confirmed that my change updated all the appropriate systems as it should.

[mohnashaat]

Thank you Steve

[TheHardy]

Part of me is almost wondering if it's maybe a browser or java issue - I was able to remove the number fine from the account in my web browser. I also confirmed that my change updated all the appropriate systems as it should.

Good to know for future troubleshooting suggestions (in FPL off-hours) ... that is why I was somewhat curious. That explanation may also explain why I had trouble PREVIOUSLY removing a #, but it worked when I PUT one in first, and then deleted the other, then the NEWEST ...

Maybe a COOKIE issue, Steve? Seeing as from a "virgin" box, you gotter going first time out ... Might want to get the web-coders to set the TTL shorter on any COOKIES that the account management interface uses ... ???