republican-creole
site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Share Topic
Posting?
Post a:
Post a:
Links: ·Bell Direct Forum ·Bell FAQ ·Alcatel FAQ ·Inside Wiring FAQ ·Stalls and Freezes Help ·Bell Reviews
AuthorAll Replies

freejazz_RdJ

join:2009-03-10
kudos:1

reply to dc2323

Re: [Homephone] Bell won't accept 30 day notice of porting numbe

The LSR issued by your new service provider should constitute notice. If it doesn't for Bell, then someone should raise this issue on the regulatory side. To my knowledge, the LSR does constitute notice because the whole point of the LNP process is that the customer doesn't have to contact their old service provider.

As for the pending order issue, it isn't really a policy decision. All of the legacy billing/ordering systems for telcos have limitations surrounding pending orders. For most, you can't have 2 orders queued up; only 1 order at a time can be pending or in progress. Even if there isn't that IT limitation, a pending order is a conflict for porting because the order action could contradict the port request. What if there is already a port, a move or a disconnection in the system; should whatever port request comes in simply cancel whatever the pending order is?

HeadSpinning
MNSi Internet

join:2005-05-29
Windsor, ON
kudos:5

You can have multiple orders pending against a line except for an out order. Once there is an out order pending, nothing else can be issued unless it is cancelled.

The only exception is a subsequently authorized port out request, which will cancel the out order associated with the pending (older) port out request, and trigger a a new PL Version of the LSC to the first provider stating that the original port out was cancelled due to more recent authorization.

The whole port out process gets messy when for example Bell is re-selling service to another provider (Teksavvy, Primus, Allstream, etc.), and doesn't inform them of the port out. The customer is left having to argue it, and the reseller is left not knowing what's going on.
--
MNSi Internet - »www.mnsi.net


freejazz_RdJ

join:2009-03-10
kudos:1

I see the Canadian way of working is different. For some carriers, multiple port attempts for a single TN will lock all the ports requests and puts them in conflict or rejected status. And everyone has to start fresh. But each carrier is different: the logic on handling request (conflict management, slamming detection, etc) can be fully customized in the LNP software I worked with (LSMS-SOA by SAIC).


Saturday, 25-May 02:19:26 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 13.5 years online © 1999-2013 dslreports.com.
Most commented news this week
Hot Topics