7 10, 2021

JSI Webinar: Prepping for 2022’s Hot Numbering & Porting Requirements

2021-11-02T12:50:12-04:00October 7, 2021|Webinar Recordings|

Not only will carriers likely feel the heat of increased competition in their service areas in 2022, but they’ll also be reporting to a new robocall database and taking steps to help with the launch of 988 as the National Suicide Prevention Hotline. Join us on Thursday, October 7th at 2 p.m. EDT for a 90-minute webinar where we’ll dive into all the hot issues we see on the horizon. Bridget Alexander White will be discussing:

  • Competition: More interconnected VoIP providers (iVoIPs) have direct access to numbering and new CLECs are entering ILEC territories. Are you ready for this influx of porting competitors?
  • Reassigned Numbers Database (RND): The FCC’s commitment to combatting unwanted and illegal calls has led to the creation of a new industry database. Do you understand your new reporting obligations?
  • Nationwide 988 deployment is driving 10DD in over 80 NPAs! The FCC requires all service providers to prepare their networks to route calls to 988 without delay or error. Is your company prepared for 988?

These industry requirements will impact ALL voice service providers. For more information about anything numbering, porting or robocall related, please contact Bridget Alexander White in JSI’s Maryland office at 301-459-7590.

Purchase Recording

Sorry, you missed this webinar! But, a recording of this webinar is available for $249. If you would like to purchase the recording, please contact Brenda Cordwell or Leah Yoakum in the Maryland office at 301-459-7590.

3 08, 2021

Don’t Forget to Update Your Number Portability Procedures

2021-11-02T13:07:57-04:00August 3, 2021|e-Lerts|

Number portability has lost its headliner status recently to robocall prevention, but it cannot be forgotten entirely. New FCC-authorized iVoIPs and competitors are entering rural LEC territories and your company will likely have to port with them. It is important to maintain Number Portability Procedures (NPPs) to ensure that the necessary information is being exchanged by providers to successfully complete port requests. These NPPs also remind porting partners of the FCC port rules, as well as define your business’s port procedures.

The standard information exchanged includes, but is not limited to, your company’s dedicated number portability email address for order submission, your hours of operation, LSR validation fields, and port contacts. However, more information often is needed for successful porting. It is important to review your port procedures regularly to make sure the document accommodates the following:

  • Contact changes due to recent retirements, departures, or promotions;
  • Staff changes/new personnel;
  • New port request processes;
  • Permanently disconnected telephone number requirements;
  • Robocall mitigation procedures;
  • New interconnection agreements with CLECs/WSPs; and
  • New iVoIPs in your service area.

If any of the above changes are applicable to your company, it’s time to revise your Number Portability Procedures. JSI has created NPPs in compliance with FCC port rules and NANC standards beneficial to rural LECs. In addition, your company should confirm that your port partners have your updated number portability procedures business rules and that you have the current NPPs for your port partners.

For assistance updating or creating a set of procedures for your company or with exchanging NPPs with your port partners, contact Lisa Cover in JSI’s Maryland office at 301-459-7590.

3 08, 2021

AT&T to Add Number Transfer PIN to Wireless Port Requests

2021-11-02T13:08:04-04:00August 3, 2021|e-Lerts|

Clients that port wireless telephone numbers from AT&T will soon have another step to complete in the pre-port and port submission process. AT&T is implementing a new port protection policy on postpaid accounts due to a rise in unauthorized port activity in the wireless industry. Beginning in September, companies must acquire a six-digit number transfer PIN from the customer prior to submission of the port request to AT&T and the PIN must be posted on the port request.

AT&T sent this notice to port partners recently:

Effective September 21, 2021, AT&T Mobility will implement a new policy whereby Consumer Postpaid customers must obtain a Number Transfer PIN to use when porting from AT&T to another service provider. This change is being implemented to further protect post-paid customers against unauthorized or fraudulent port outs.

Customers will generate the 6-digit number transfer PIN via the myAT&T app, by dialing *PORT from the AT&T device, or from their myAT&T account online.

The 6-digit Number Transfer PIN will be entered in the PIN/password field on the Wireless Port Requests. The AT&T Mobility Account PIN will no longer be used to validate port outs for Consumer Postpaid TNs. All other validations and assessments remain the same.

If the Number Transfer PIN provided is incorrect, the port request will receive a resolution required response with the error code of “6B-AT&T Number Transfer OIN needed or incorrect” and the remarks will include “AT&T Number Transfer PIN Needed or Incorrect: www.att.com/portout”.

Additional details will be communicated prior to launch, including an overview, specific steps for each customer option and FAQs. All information will be available at www.att.com/porting.

Companies should make note of this change and add it to their internal porting procedures before it begins next month. If you have questions regarding the new AT&T Number Transfer PIN policy, contact Lisa Cover at 301-459-7590.

20 08, 2019

Fraudulent Number Ports are on the Rise

2019-08-20T17:08:39-04:00August 20, 2019|e-Lerts|

What used to be a rare occurrence has turned into a daily concern for carriers. Carriers are reporting that the levels of fraudulent telephone number ports reported by customers have skyrocketed. The industry defines a fraudulent port as one which occurred as the result of an intentional act of fraud, theft, and/or misrepresentation. Examples include the use of numbers for such acts as credit card or vanity number fraud.

Thanks to the limited detail required to port telephone numbers, it’s easy for bad actors to fraudulently port out numbers unbeknownst to the end user and the current service provider. Once the issue is reported, subscribers expect immediate return of their telephone numbers, but the process can be difficult and time consuming.

The Local Number Portability Administration Transition Oversight Working Group (LNPA-TOSC) is conducting informal meetings to brainstorm fraudulent port preventive measures. Although a port “double-check” process that would allow the original service provider to confirm with the customer before porting out the number seems like an obvious solution to the problem, this option won’t likely be resurrected. JSI is part of this industry group and we will notify clients of any new solutions to prevent fraudulent ports.

In the interim, the industry’s best practice approach remains in effect:

  1. Trouble Report: The end user reports the phone service issue to its original service provider.
  2. Internal Investigation: That service provider checks for the number in its billing system, its telephone number port-out list, on its port request and response forms, and in the Number Portability Administration Center (NPAC). If no internal record of the port out exists, but the number was ported in the NPAC, the original service provider notifies the end user and the new provider of the identified problem.
  3. Notification: The preferred service provider notifies the end user of the internal investigation result – the number was ported without the end user’s knowledge – and the plan to regain the telephone number. The “new” provider of the telephone number is informed of the fraudulent port and is requested to work with the preferred carrier to return the number to the end user. NOTE: some carriers require a police report before investigating the claim of a fraudulent port.
  4. Resolution: The preferred carrier and the new service provider complete the port request and response process to port the telephone number back to the preferred service provider and the end user.

For now, JSI recommends clients do the following to alleviate cases of fraudulent ports:

  • Urge your customers to immediately report any suspicious activity associated with their telephone service/account to your company for investigation.
  • Educate your customers on the account protection options offered by your company (for example: requesting a local service provider freeze or adding a passcode/PIN to their account).
  • Educate your staff on how to investigate reported cases of fraudulent ports.
  • Update your Number Portability Procedures to include the process for carriers to report fraudulent ports to your company for investigation.
  • Provide a fraudulent port reporting contact (name, telephone number and email address) in your company’s number portability procedures document.

For more info on fraudulent ports or for assistance creating or updating your company’s number portability procedures, contact Bridget Alexander White in JSI’s Maryland office at 301-459-7590.

19 07, 2018

FCC Nudges Nationwide Number Portability Forward by Amending LNP Query Rules

2018-07-19T12:21:50-04:00July 19, 2018|e-Lerts|

Earlier this month, the FCC adopted a Report and Order as a step toward nationwide number portability (NNP) to allow consumers to switch their telephone numbers to any carrier, anywhere in the country. The amended rules relax requirements on which service provider is responsible for querying ported telephone numbers in the Number Portability Administration Center (NPAC) database. Until now, the carrier immediately preceding the terminating carrier (the N-1 carrier) was required to ensure that ported telephone numbers were queried in the NPAC. The FCC relaxed the N-1 requirements to allow the originating service provider or any other carrier in the call path to take responsibility for the query in anticipation of changes to the number porting rules to lift rate center boundary limitations and allow NNP.

The original N-1 rule was put in place to ensure the query costs were split between originating and interexchange carriers and so that calls would not be left unqueried. Today, few consumers have an interexchange carrier that is different from their local provider, which makes N-1 unnecessary in some cases; however, it is still necessary when the providers differ and wireless and iVoiP calls are in the mix. Those calls may be destined to terminate outside the originating carrier’s network and may not fall under the originating service provider’s responsibility in the current N-1 structure.

The change was made because the FCC agreed with commenters that stated requiring the N-1 carrier to perform the query in the NNP environment could result in frequent inefficient and unnecessary queries and routing. For example, a call could route from the originating carrier to an interexchange carrier for the query and back to the originating carrier for termination. Such instances would be avoided if the originating carrier performed the query. However, to continue to ease the potential burden of the originating carrier bearing all query costs, the rule will continue to require the industry to follow the N-1 process if the originating carrier declines to query the number. Whether or not the originating service provider decides to query the call will depend on the query costs and the provider’s ability to route and terminate calls under the “to be determined” NNP protocol selected for the industry.

The N-1 amendment in this Report and Order will be effective 30 days after the Order is posted in the Federal Register.

NNP Next Steps

In addition to the N-1 change, the FCC’s Wireline Competition Bureau earlier this month directed the North American Numbering Council (NANC) to investigate the costs, benefits, and technical requirements of two potential NNP methods: Non-Geographic LRN (NGLRN) and Nationwide LRN (NLRN). The NANC was also charged with recommending the next steps the Commission and industry should take to achieve full NNP. An interim report is due to the Bureau at the December NANC meeting and the final report is due at the NANC’s first meeting of 2019, which is normally held in March.

The Order and the NANC directive are significant for ALL service providers as the ability for consumers to port their telephone number anywhere in the country is arriving sooner that we thought.

If you have questions or would like additional details about NNP, contact Bridget Alexander White in JSI’s Maryland office at 301-459-7590.

3 04, 2018

NPAC Transition Begins This Weekend with SE Region

2018-04-10T13:53:41-04:00April 3, 2018|e-Lerts|

Is Your Company Ready?

The long-awaited event is finally here. The Number Portability Administration Center (NPAC) administrator transition from Neustar to iconectiv begins this weekend on Sunday, April 8th with the NPAC’s Southeast region. The remaining regions convert in May as follows:

May 6: Northeast, Mid-Atlantic and Midwest regions
May 20: Southwest, West Coast and Western regions
May 25: iconectiv’s final acceptance date for all NPAC regions
May 26: The end of Neustar’s regional NPAC service

Attention Southeast Region Clients
You’re up to bat first this Sunday, April 8. Nine states and two U.S. territories – Alabama, Florida, Georgia, Kentucky, Louisiana, Mississippi, North Carolina, South Carolina, Tennessee, Puerto Rico and the U.S. Virgin Islands – comprise the largest of the seven regional NPACs, and, according to Neustar’s NPAC statistics, the Southeast region cutover will impact more than 145 million U.S. telephone lines. So far, iconectiv seems confident that if it can hit a homerun by converting the largest region without issue, the rest will be a walk in the park.

In preparation, JSI encourages all NPAC users, especially those in the Southeast, to make absolutely certain they:

  1. Know your company’s region
  2. Watch for and review any transition notices from iconectiv, especially between April 6th and 9th
  3. Have the contact numbers and email addresses for NPAC assistance on hand, just in case
  4. Know the plan of action should a porting database conversion failure occur

To prepare the industry for the first regional transition, the North American Numbering Council’s (NANC’s) Local Number Portability Administration – Transition Oversight Committee (LNPA-TOSC) will receive a regional cutover review on Wednesday, April 4 from the Transition Oversight Manager (TOM) and iconectiv. Later that same day, the TOM will facilitate a special webcast dedicated to Southeast regional cutover preparation.

JSI plans to attend both sessions and those clients who subscribe to our LNP Essentials Bundle will receive a special synopsis of the transition status, tools for monitoring the conversion in real time, updated vendor contact information, and any last minute changes, brick walls, or possible agreed upon vendor rollback plan in case of cutover failure.

For more information or questions regarding the NPAC Transition, contact Bridget Alexander White at 301-459-7590.

14 08, 2017

New NPAC Registration Dates Quickly Approaching

2017-08-14T14:32:38-04:00August 14, 2017|e-Lerts|

All carriers must register in order to continue porting

The FCC issued a Public Notice reminding all service providers currently porting telephone numbers using the Number Portability Administration Center (NPAC) that they must complete the registration process by August 31, 2017, if they plan to test their NPAC interface. The registration and testing are part of the process to transition NPAC operation from Neustar to iconectiv. Those companies that do not need to test their NPAC connectivity have until October 31, 2017, to complete the registration process.

If your company uses JSI’s Service Order Administration (SOA) to port numbers in the NPAC, individual company testing is not necessary but registration needs to be completed by October 31st. JSI’s testing will automatically meet the requirement for all JSI SOA clients. If your NPAC access is not via JSI, then individual company testing may be necessary. It depends on how your company connects to the NPAC.

Regardless of the method by which service providers interface with the NPAC, registration with iconectiv is required. iconectiv’s goal is to complete registration prior to the onset of the actual regional conversions.

The iconectiv NPAC registration process consists of three stages: The Non-Disclosure Agreement (NDA), Transition User Application (TUA), and the Regional User Agreement (RUA). As a helpful guide to completing the registration process with iconectiv, you’ll need to submit the following support documentation along with the TUA:

  • Certificate of Insurance Coverage
  • Proof of Operating Authority/State Certification

In addition, the following network information and contacts are needed to complete the TUA and RUA:

  • General contact information
  • Law enforcement contact
  • Security contact
  • Billing contact
  • 499 ID
  • OCN
  • SS7 vendor
  • NPAC access and usage

For assistance with beginning or completing the iconectiv registration process, testing questions, or to verify your NPAC interface method, please contact Bridget Alexander in JSI’s Maryland office at 301-459-7590. You can also purchase a recording of the “Surviving the NPAC Transition” webinar Bridget presented last fall which covers this process.

For information on JSI’s porting services and flexible SOA packages, contact Karen Hoffman at 301-459-7590.

13 03, 2017

JSI’s Online Port Ordering System Hits 200K Milestone

2017-05-19T10:09:35-04:00March 13, 2017|News|

200,000 Port Requests Submitted and Processed Since Its Launch

JSI’s online number porting request system today processed its 200,000th online order, reaching that milestone in 11 years since the site’s launch and doubling the number of orders in four and a half years. As local number portability took hold in the 1990s, JSI was the first consulting firm to offer Service Order Administration (SOA) management services to its clients. The online system, which officially launched in late February 2006, makes it simple for clients to submit their orders to activate, release or disconnect ported numbers in the NPAC, keep track of what’s been submitted, and be assured that orders were received and processed in a timely manner.

Alma Telephone of Georgia submitted the first official online order, requesting a number disconnect on February 28, 2006. Today’s activate request from Guadalupe Valley Communications, a Texas CLEC, was the 200,000th order received and processed by our Network Services staff.

Clients have enthusiastically embraced the online system, and today submit an average of 217 port requests each business day through the MyJSI website. Each of these is completed by our staff, and archived for the client to see on the site.

If you have any questions about the Network Services/SOA system or would like to discuss how it could help your company, please contact Karen Hoffman, staff director – Network Services, at 301-459-7590.

Go to Top