Any tips for speeding up a re-connection after being "slammed"

Forums › New Zealand Broadband › Any tips for speeding up a re-connection after being "slammed"

1 | 2 | 3

alavaliant

222 posts

Master Geek

Subscriber

#2783470 24-Sep-2021 11:24

trig42:

It's not that easy to find the serial number on an ONT.

Here's one we've just had installed at one of our sites - where is the Serial? You wouldn't wat people taking them off the wall to find it.

That somewhat feels to me like something chorus could improve on. If there was an obvious and clear unique id/serial on the top of the ont it would help ensure transfers were done more accurately.

KiwiSurfer

1450 posts

Uber Geek

ID Verified

Lifetime subscriber

#2783589 24-Sep-2021 13:44

nztim:

There are merits to not requiring the losing service provider when transferring a connection - for example Vodafone brought out numerous RSPs over the years and the ONT could still be in the chorus database as "wave, ihug, telstraclear, etc"

Easily solved by allowing the 'Vodafone' entry in a transfer request to be accepted on a request relating to a connection that has the RSP listed as any of the following: 'Vodafone', 'Wave', 'IHUG', 'TelstraClear', et al. This is not really a hard problem to solve automatically given the mappings between current RSP names and previous RSP names is known. A simple database table could easily hold mappings between current RSPs (e.g. Vodafone) and all the possible RSP name/IDs that they now look after. It's strange that 'oh lets ignore the LSP name' is being considered an actual solution...

Lorenceo

904 posts

Ultimate Geek

Trusted

#2783779 24-Sep-2021 17:15

trig42:

Here's one we've just had installed at one of our sites - where is the Serial? You wouldn't wat people taking them off the wall to find it.

I have the same model. You don't need to remove it from the wall to see the SN. It's on the right side of it, along with a QR code and Wi-Fi information.

After my install, I found a little sheet of stickers on my garage floor. Initially I was going to bin it along with the bits of cable sheathing, etc that had been left on the floor. Upon closer inspection I realised each sticker had the ONT serial number and corresponding barcode on it. I stuck one of them to the front of the ONT and another inside the comms cabinet. I assume Nokia supplies these with all of their ONTs. It would be nice if part of the install procedure included attaching one of them to the front of the ONT.

Gen 2 ONTs all have the serial and a QR code on the front I believe.

As far as I'm aware Gen 1 ONT SNs are only visible after removing the ONT from the mounting bracket, and looking at the sticker on the back of it.

nztim

3816 posts

Uber Geek

ID Verified

Trusted

TEAMnetwork

Subscriber

#2783818 24-Sep-2021 19:09

KiwiSurfer:
nztim:

There are merits to not requiring the losing service provider when transferring a connection - for example Vodafone brought out numerous RSPs over the years and the ONT could still be in the chorus database as "wave, ihug, telstraclear, etc"

Easily solved by allowing the 'Vodafone' entry in a transfer request to be accepted on a request relating to a connection that has the RSP listed as any of the following: 'Vodafone', 'Wave', 'IHUG', 'TelstraClear', et al. This is not really a hard problem to solve automatically given the mappings between current RSP names and previous RSP names is known. A simple database table could easily hold mappings between current RSPs (e.g. Vodafone) and all the possible RSP name/IDs that they now look after. It's strange that 'oh lets ignore the LSP name' is being considered an actual solution...

That would be a mere to maintain for Chorus to maintain and quite frankly not their problem

Vocus is another example they have about 9 different RSPs in the chorus database

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

KiwiSurfer

1450 posts

Uber Geek

ID Verified

Lifetime subscriber

#2783892 24-Sep-2021 19:43

nztim:

That would be a mere to maintain for Chorus to maintain and quite frankly not their problem

Vocus is another example they have about 9 different RSPs in the chorus database

It is their problem because they're the one that keeps this data in their database and carrying out the process for switching RSPs. RSPs don't acquire other RSPs every day so it's not really a big hassle to update a database table when it happens. When ISP A buys ISP B and notifies Chorus of this, Chrous could quite simply add a record to a table to indicate ISP A should be treated the same as ISP B for the purpose of LSP checking. Your Vocus example would simply require 9 rows to be added to a table -- 9 different RSP ID/names, each mapped to Vocus (Slingshot=Vocus, Orcon=Vocus, SKY=Vocus, et al). Over the course of a typical year this may well see a few rows being added (as well as removed as RSPs eventually move their customers off old systems etc) but I hardly see this as a significant amount of work for Chorus. The trickiest thing would be to change the code that does the LSP checking so that in the case a strict check fails (e.g. transfer request has RSP "Vodafone" which does not match actual RSP "IHUG") it falls back to the checking the table for extra IDs/names (so e.g. it'll try checking alternative RSP ID/names and finally match whatever ID/name is in the database for IHUG). They'll also need to test this to ensure it works as expected etc. This could improve the process to the point that it's not necessary to get rid of the LSP check because the process is able to work as customers would expect for Vodafone, Vocus, etc cases.

Jase2985

13461 posts

Uber Geek

ID Verified

Lifetime subscriber

#2783953 24-Sep-2021 23:23

alavaliant:

That somewhat feels to me like something chorus could improve on. If there was an obvious and clear unique id/serial on the top of the ont it would help ensure transfers were done more accurately.

The model 300's come with a small bag with at least 2 stickers with the serial numbers on them. so i dont know why they dont stick them on. I put one on the outwards facing side of mine as chorus were leaving.

raytaylor

4014 posts

Uber Geek

Trusted

#2784569 26-Sep-2021 15:25

chevrolux:

liquidcore: Perhaps @Wheelbarrow01 could chime in :)

Not really a Chorus issue! Just slack RSP issue.

Yes it is a chorus issue.

Chorus dont require the new provider to provide any details about the old provider anymore. They just accept the churn request.

Chorus should be verifying the name of the previous retailer before accepting a churn request - this was an automated system until a few months ago.
The new retailer could only get this information from the customer if they had permission to take over the service.

Ray Taylor

There is no place like localhost

Spreadsheet for Comparing Electricity Plans Here

GoodSync

GoodSync. Easily back up and sync your files with GoodSync. Simple and secure file backup and synchronisation software will ensure that your files are never lost (affiliate link).

raytaylor

4014 posts

Uber Geek

Trusted

#2784579 26-Sep-2021 16:02

Wheelbarrow01:

After consultation with the industry, Chorus recently decided to trial the removal of Losing Service Provider validation in a fibre transfer scenario.

I dont know of any isp that wanted that change. I know a few even contacted their account managers to say dont do it.

I can only see it applying to ParadiseSaturnIhugAPhone or Vocus and as mentioned, its just a database find&replace change. Or a tool can be built to make the necessary changes.

LSP validation needs to be re-enabled.

1) LSP name concerns: Simply ask the customer or get some industry knowledge. RSPs should be able to load the different brands they trade under into the chorus portal and the services each of those brands provide.
Eg. ISPCo1-Fiber = ISPCo3
Eg. ISPCo1-DSL = ISPCo2

2) Address concerns: New RSP just uses the chorus mapping tool to look up the address and get the correct SAM

Ray Taylor

There is no place like localhost

Spreadsheet for Comparing Electricity Plans Here

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#2784589 26-Sep-2021 16:29

Maybe the ultimate solution is that the transfer can occur without validation if a serial number is provided, but losing RSP validation is required if the serial number isn't provided.

1 | 2 | 3