Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


rossnixon

37 posts

Geek
+1 received by user: 7


#311618 1-Feb-2024 16:39
Send private message

There seems to be an issue that ISPs can't solve.

We switched ISPs in December. Lets call them ISP-1 & ISP-2.

We had Fibre with a VOIP Homeline with ISP-1.
When we switched to ISP-2 we forgot to advise we wanted to keep our Homeline.

 

ISP-2 said they can't access the number unless ISP-1 reactivates it first.

 


Over several weeks we have tried several times to get ISP-1 to reactive it.
They have been unable to do so.
Now 30+ days have elapsed and they say the number is now in quarantine, and they can do nothing.

Perhaps ISP-2 (who we are the customer of) should be able to sort it out without us spending 4-5 hours talking to low-level techs and sales people?
Should we ask them to escalate this to VOCUS who supplies their services?

 

 

 

Thanks!


Filter this topic showing only the reply marked as answer Create new topic
Wheelbarrow01
1784 posts

Uber Geek
+1 received by user: 2638

Trusted
Chorus

  #3189499 1-Feb-2024 23:47
Send private message

I've never had much to do with the porting of landline numbers (and when I did was a very long time ago), so don't take anything I write as gospel, but my understanding in this situation is that there is nothing at all RSP2 can do at this point to connect your previous phone number. In order to port a number, it must still be connected. And in order to reconnect a number from scratch, they must already have control of it in their own number pool, which in this case they do not.

 

The phone number you were originally assigned for the connection at your address will be part of what is called a code block. The major RSPs such as Spark, Devoli, OneNZ, Vocus etc all have unique code blocks assigned to them - these are specific number ranges from which they are allowed to allocate phone numbers to their customers. Smaller RSPs would likely use code blocks belonging to the larger organisations that they wholesale through.

 

End users can port their existing number over to a different provider, but the new provider only has a right of control over the number while it's active on their network. If it ends up getting disconnected, I believe there are only limited circumstances where the non-native provider can get that number reactivated, and only within a limited timeframe. After that, the number is quarantined to be returned to the RSP who holds the code block for the number range that the individual number was originally pulled from.

 

The question here is whether RSP1 in your case was the original code block holder for your phone number - they may not have been if you had already changed providers at some time in the past. For example, let's say you originally connected with Telecom in the early 2000's, and then in 2015 you ported the phone number to Vodafone on a new fibre service. And now you have asked 2Degrees to transfer the fibre broadband service to them, but forgot to mention the landline number. OneNZ (formerly Vodafone) didn't receive an outport request, so the number ends up getting disconnected. You realise the mistake after the fact but neither OneNZ nor 2Degrees can do anything as the number has been quarantined back to the original code block assignee - in this case Spark (formerly Telecom).

 

There's two obvious points of failure here - one was you the end user forgetting to request the landline number to be ported. Realistically if you had not forgotten to request the number port, you likely would not be in this situation. The second failure is potentially RSP1, who claim they could not get the number reconnected. I am not sure of the ins and outs of that - possibly their system would not allow them to reconnect the number without an actual physical line connection to an address (although the Customerlink service is designed for precisely that - activating a phone number and holding it at the exchange in a virtual state that allows it to be ported, diverted or answered virtually by voicemail. I guess the 3rd failure is reaching 30 days which may mean retrieving the number is now nigh on impossible.

 

You may be able to use https://www.nad.org.nz/number-register/ to try and determine which RSP is the holder of the code block for your phone number. They may be able to get it back for you, but I don't pretend to know what the odds of that might be.

 

Again, don't take anything I have said as gospel - it will not surprise me if some switched on porting guru debunks half of what I have just written....





The views expressed by me are not necessarily those of my employer Chorus NZ Ltd




nztim
4012 posts

Uber Geek
+1 received by user: 2710

ID Verified
Trusted
TEAMnetwork
Subscriber

  #3189542 2-Feb-2024 08:37
Send private message

When you disconnect a number the number gets returned to the "owner" of the numbering block

 

User this site as a term of reference to find the number block owner https://www.nad.org.nz/

 

You then need to get a connection with the "owner" where the number sits, once you have that you can port it to whoever your like.





Any views expressed on these forums are my own and don't necessarily reflect those of my employer. 


rossnixon

37 posts

Geek
+1 received by user: 7


  #3189659 2-Feb-2024 15:11
Send private message

Thanks for the answers.

 

 

 

On checking via the info provided, the phone number block is owned by Spark.
However when phoned a day or so ago, they claimed that was nonsense - nothing to do with them.

Rather than open an account with them (what a hassle), to get the phone number back, and ready for porting, we 'bit the bullet' and got a new phone number from ISP-2 today. Should be active tomorrow.


Filter this topic showing only the reply marked as answer Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.