![]() ![]() ![]() |
|
Only one - did the number port kill the Spark broadband?
Interesting that Spark were confused about the number still being with them.
huckster:
Only one - did the number port kill the Spark broadband? Interesting that Spark were confused about the number still being with them.
Short answer: No I think not.
Long overthought answer: 😀
Hmm. Well at the same time that I ported the number I also moved over to the second port on the ONT and started using @quic service. So I can't say for sure the broadband plan ended on port one then and there. I don't think it did.
Even after I had confirmation that the landline port had occurred from Hero, checking the home line that morning, I could still hear dial tone on the phone ports in the house (the old Spark VoIP service) but if I called the landline my phone was not ringing my Hero app was so that port of the number had definately occured as I had been advised by Hero.
The fact that Spark seemed unaware of the landline port over the following 24 hours seemed a bit weird from my customer perspective. Talking to Hero they were reassuring the things they needed to do and advise Spark of had been done. It was suggested to me by the Hero CSO I spoke with that Spark's records may just take longer to update?
I do think having a second port on the ONT and using that for the new ISP is the safer/smarter way to go when migrating. Just in case ;)
Quic "Sprinter" UFB - Ref (free setup): R338237EFDIUJ
Agency BBS | fsxNet | Agency News | Total FM
Bit the bullet and have attempted to follow the "safe" route for my circumstances.
Phone line split from Broadband and turned into a CustomerLink line. Broadband is now naked and has a new, funky 16blah "line" number.
Port request scheduled for Friday.
|
![]() ![]() ![]() |