[VoiceOps] Instant Porting
Mary Lou Carey
marylou at backuptelecom.com
Wed Feb 10 16:40:12 EST 2016
That's funny!
> On February 10, 2016 at 2:17 PM Paul Timmins <paul at timmins.net> wrote:
>
> How about a Vatican II for LNP processes, eh?
>
> On Wed, 02/10/2016 12:20 PM, Mary Lou Carey <marylou at backuptelecom.com>
> wrote:
>
> > > I couldn't pull up the WPR, but obviously their WPR is nothing
> > > like an LSR, which is all written in code and requires a bunch of
> > > fields that verify way more than just the TN/PIN/Address/ZIP accuracy.
> >
> > My guess is that it doesn't require a lot of training to teach someone
> > how to fill out a WPRs because they're in English and to the point. Unlike
> > LSRs that you need an LSOG guide to understand what it's asking for, hours
> > of training to know which fields to populate, and the patience of a saint to
> > fight your way through the process! Sounds like WPRs is the form that all
> > carriers should use to simplify the process, but then iconectiv would be out
> > of business and it would make it way easier for carriers to port numbers
> > away from the ILECs so I don't see that happening without a fight. I guess I
> > should be thankful because it gives people like me a job, but the whole
> > ASR/LSR process just seems stupid to me - like reading the bible in Latin to
> > a group of people who only speak English!
> >
> > Mary Lou Carey
> > BackUP Telecom Consulting
> > 615-791-9969
> >
> >
> > > > > On February 10, 2016 at 12:00 PM Paul Timmins <paul at timmins.net>
> > > > > wrote:
> > >
> > > My understanding is that the winning carrier submits the
> > > subscription, issues an electronic WPR
> > > (https://www.syniverse.com/files/Single_Line_WPR
> > > <https://www.syniverse.com/files/Single_Line_WPR.pdf> .pdf
> > > <https://www.syniverse.com/files/Single_Line_WPR.pdf> ) - similar to an
> > > LSR. The losing carrier verifies the WPR's accuracy (TN/PIN/Address/Zip)
> > > and issues a confirmation and concurrence, and then the winning carrier
> > > electronically activates in SOA.
> > >
> > > > >
> > > > >
> > > Given this is 100% electronic (and all the majors use Syniverse for
> > > their SOA) it's immediate. Wireless carriers don't really have to worry
> > > about things like "do they have complex services like DSL, FTTH with
> > > bundle packaging, etc". They just drop the customer's subscriber
> > > information out of the switch and send a final bill.
> > >
> > > -Paul
> > >
> > > On 02/10/2016 11:50 AM, Mary Lou Carey wrote:
> > >
> > > > > > > I really wonder if the big wireless carriers
> > > > > > > follow the same process that wireline carriers do because
> > > > > > > the typical wireline process takes more than 5 minutes to
> > > > > > > complete. The whole process is:
> > > >
> > > > 1. Issue an LSR order to the losing carrier requesting the
> > > > port.
> > > > 2. When you get confirmation, submit the port request in NPAC
> > > > (or a SOA system connected to NPAC)
> > > > 3. Losing carrier confirms the port
> > > > 4. Winning carrier accepts the port
> > > >
> > > > The greatest portion of time is spent on getting the losing
> > > > carrier to accept the LSR and give confirmation, so I'm thinking these
> > > > wireless carriers must have agreements set up between them that allows
> > > > them to bypass the LSR process and just complete the NPAC work!
> > > >
> > > > Mary Lou Carey
> > > > BackUP Telecom Consulting
> > > > 615-791-9969
> > > >
> > > >
> > > > > > > > > On February 10, 2016 at 9:57 AM Nick Olsen
> > > > > > > > > <nick at flhsi.com> <mailto:nick at flhsi.com> wrote:
> > > > >
> > > > > Exactly this.
> > > > >
> > > > > I actually ported my personal cell number to Verizon from
> > > > > ATT yesterday.
> > > > >
> > > > > Gave the rep my ATT account number, He 30 seconds later
> > > > > asked me for the PIN I set on my ATT account. I provided and my number
> > > > > was working before I hit the door on the way out. Total port time was
> > > > > <5 Min.
> > > > >
> > > > > I questioned the Rep if this was always the case and he said
> > > > > only if porting from Sprint/ATT/T-Mobile. And that basically any other
> > > > > carrier (Not including MVNO's of the above) took 3-5 Business days.
> > > > > Which is about in-line with my current wireline porting.
> > > > >
> > > > > I figure they all exchange so many numbers a day it was in
> > > > > all of their best interest to work together.
> > > > >
> > > > > Not to mention, By automating the process. They don't have
> > > > > to keep an entire call center worth of LNP personnel to handle their
> > > > > volume.
> > > > >
> > > > > Nick Olsen
> > > > > Network Operations
> > > > > (855) FLSPEED x106
> > > > >
> > > > >
> > > > >
> > > > > ---------------------------------------------
> > > > > From: "Alexander Lopez" <alex.lopez at opsys.com>
> > > > > <mailto:alex.lopez at opsys.com>
> > > > > Sent: Tuesday, February 09, 2016 6:00 PM
> > > > > To: "Alex Balashov" <abalashov at evaristesys.com>
> > > > > <mailto:abalashov at evaristesys.com> , "voiceops at voiceops.org"
> > > > > <mailto:voiceops at voiceops.org> <voiceops at voiceops.org>
> > > > > <mailto:voiceops at voiceops.org>
> > > > > Subject: Re: [VoiceOps] Instant Porting
> > > > >
> > > > > I think the incentive is to cooperate because it is a
> > > > > relatively small group of wireless carriers compared to wireline.
> > > > >
> > > > > The main reason being that they don't want their ports held
> > > > > up, so they work well with others.
> > > > >
> > > > > Also since there is a small group they could automate the
> > > > > back office processes between them and submit the request and
> > > > > aknowledgment quickly and without human interaction.
> > > > >
> > > > >
> > > > > -------- Original message --------
> > > > > From: Alex Balashov <abalashov at evaristesys.com>
> > > > > <mailto:abalashov at evaristesys.com>
> > > > > Date: 2/9/2016 4:32 PM (GMT-05:00)
> > > > > To: voiceops at voiceops.org <mailto:voiceops at voiceops.org>
> > > > > Subject: Re: [VoiceOps] Instant Porting
> > > > >
> > > > > This does raise, in light of the OP, the question of what
> > > > > economic or
> > > > > political incentive wireless carriers have to cooperate in
> > > > > relatively
> > > > > seamless porting to/from each other.
> > > > >
> > > > > --
> > > > > Alex Balashov | Principal | Evariste Systems LLC
> > > > > 303 Perimeter Center North, Suite 300
> > > > > Atlanta, GA 30346
> > > > > United States
> > > > >
> > > > > Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
> > > > > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
> > > > > <http://www.csrpswitch.com/>
> > > > > _______________________________________________
> > > > > VoiceOps mailing list
> > > > > VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
> > > > > https://puck.nether.net/mailman/listinfo/voiceops
> > > > > _______________________________________________
> > > > > VoiceOps mailing list
> > > > > VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
> > > > > https://puck.nether.net/mailman/listinfo/voiceops
> > > > >
> > > > > > > > >
> > > >
> > > > Mary Lou Carey
> > > > BackUP Telecom Consulting
> > > > Marylou at backuptelecom.com <mailto:Marylou at backuptelecom.com>
> > > > Office: 615-791-9969
> > > > Cell: 615-796-1111
> > > >
> > > >
> > > > _______________________________________________
> > > > VoiceOps mailing list
> > > > VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
> > > > https://puck.nether.net/mailman/listinfo/voiceops
> > > >
> > > > > > >
> > > > >
> >
> >
> > > > > _______________________________________________
> > > VoiceOps mailing list
> > > VoiceOps at voiceops.org
> > > https://puck.nether.net/mailman/listinfo/voiceops
> > >
> > > > >
> >
> > Mary Lou Carey
> > BackUP Telecom Consulting
> > Marylou at backuptelecom.com
> > Office: 615-791-9969
> > Cell: 615-796-1111
> >
> > >
Mary Lou Carey
BackUP Telecom Consulting
Marylou at backuptelecom.com
Office: 615-791-9969
Cell: 615-796-1111
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20160210/6f482895/attachment-0001.html>
More information about the VoiceOps
mailing list