<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<style type="text/css">.mceResizeHandle {position: absolute;border: 1px solid black;background: #FFF;width: 5px;height: 5px;z-index: 10000}.mceResizeHandle:hover {background: #000}img[data-mce-selected] {outline: 1px solid black}img.mceClonedResizable, table.mceClonedResizable {position: absolute;outline: 1px dashed black;opacity: .5;z-index: 10000}
</style></head><body style="font-family: arial,helvetica,sans-serif; font-size: 10pt;"><div>You only need look at what the UNE circuit IDs are to know how the ILECs feel about them.......DS1s and DS3s both have FU in them! LOL!</div>
<div> </div>
<div>iconectiv used to be Telcordia, which was originally BellCore. In the past Telcordia only produced Telecom documentation, sold industry codes, and adminstered the BIRRDS database, which is what they produce the LERG and TPM reports from. Some of Telcordia's documentation like the ASOG, LSOG and NC/NCI list were not that helpful in the last 20 years because many of the fields could be changed by the carrier so every ILEC used them in a different way. When I said the ILEC published these codes on their website. I didn't mean it was easy to find! In my opinion, putting everything on the web but the kitchen sink and having it accompanied with a horrible search engine was their way of making it as hard as possible for the CLEC to operate. I happen to know where they hide most things because I've worked in the industry 19 years and documented their location as much as possible so I could help my clients. However, if you're new to the arena and trying to figure it out on your own it would be near impossible to get anything done. </div>
<div> </div>
<div>That's interesting that Ericsson is going to be taking over porting. I wonder if that means they are taking all the arms that NEUSTAR claims are separate entities. I've always described NEUSTAR's entities as kissing cousins because they are really just divisions who all share the same name in their e-mail communications(neustar.net, neustar,biz, etc). Those divisons include NANPA, the Pooling Administration, NPAC, and NECA. A year or so ago they bought out Targus (who handled CNAM storage) and TNSI who is one of the two largest SS7 providers.</div>
<div> </div>
<div>So I guess my question would be are they taking over ALL of NEUSTAR or just the the NPAC portion?</div>
<div> </div>
<div>Mary Lou Carey</div>
<div>BackUP Telecom Consulting</div>
<div>615-791-9969</div>
<div><br>> On December 7, 2015 at 11:06 AM Peter Beckman <beckman@angryox.com> wrote:<br>> <br>> <br>> I hadn't heard of Iconectiv (one "n") before. I found this:<br>> <br>> http://www.ericsson.com/news/150326-fcc-authorizes-local-number-portability_244069647_c<br>> <br>> Was it Neustar prior to this change?<br>> <br>> I dream of a process for LNP that goes like this:<br>> <br>> 1. Customer goes to current carrier, requests a Porting Authorization<br>> Code for a number (or set of numbers), either online or over the phone.<br>> <br>> 2. Current carrier generates a Porting Authorization Code and provides<br>> it to the Customer.<br>> <br>> 3. Customer goes to new carrier, provides Phone Number, Current<br>> Carrier, and the Porting Authorization Code.<br>> <br>> 4. New carrier submits port request to Current Carrer with the Number<br>> and Porting Authorization Code. No name, billing address, PIN/SSN,<br>> just those three things.<br>> <br>> 5. Current carrier matches the Porting Authorization Code with their<br>> records for that Number and the port goes through.<br>> <br>> Since all of this is centralized, just have Iconectiv manage it -- the<br>> Current Carrier uses an API with Iconectiv to register the number and get a<br>> code back. The New Carrier uses the API with Iconectiv with the number and<br>> the code to verify porting. Codes expire after x days.<br>> <br>> Will Iconectiv bring this level of sanity to porting in the NANP? Or will<br>> it be more of the same, with rejections for an incorrect street abbreviation?<br>> <br>> I know it's more complicated than that to implement, but it really ticks me<br>> off how difficult it is to port numbers these days if you aren't a Tier 1<br>> wireless carrier.<br>> <br>> Beckman<br>> <br>> On Sat, 5 Dec 2015, Erik Flournoy wrote:<br>> <br>> > Aloha Group,<br>> ><br>> > I'm curious to know others thoughts on where they believe the traditional<br>> > PSTN is going vs VOIP and VoLTE. Now that Iconnectiv will be administering<br>> > the LNP in the US I feel as though it's the best time to try and propose<br>> > new or more up to date solutions that allow smaller carriers to operate.<br>> ><br>> > For example there is no charge to have the ability to port numbers in NPAC,<br>> > but there is a monthly charge for the remote access to the NPAC. Then the<br>> > interconnectivity at the LEC level. The archaic ways of telecom have not<br>> > seemed to change much although VOIP is now in my opinion the standard of<br>> > telecom. VOIP will soon be able to get code blocks and route via SIP vs SS7<br>> > and LERG. LERG, ASR/LSR, SS7 all systems owned by one monopolizing company.<br>> <br>> ---------------------------------------------------------------------------<br>> Peter Beckman Internet Guy<br>> beckman@angryox.com http://www.angryox.com/<br>> ---------------------------------------------------------------------------_______________________________________________<br>> VoiceOps mailing list<br>> VoiceOps@voiceops.org<br>> https://puck.nether.net/mailman/listinfo/voiceops<br>> _______________________________________________<br>> VoiceOps mailing list<br>> VoiceOps@voiceops.org<br>> https://puck.nether.net/mailman/listinfo/voiceops</div>
Mary Lou Carey<br>BackUP Telecom Consulting<br>Marylou@backuptelecom.com<br>Office: 615-791-9969<br>Cell: 615-796-1111</body></html>