Porting Archives | Access4

Unified Porting Redirection Service

Move your customer’s services with no diversion costs during the porting process

The Unified Porting Redirection (UPR) Service is designed to enable the migration of services to Access4’s environment prior to the porting process being completed and removes the complication with legacy porting workarounds. The service provides a single point for redirection of existing Geo Numbers within Australia.

The process effectively strips out the diversion process and delivers the call as if the number was hosted on the Access4 platform. The service doesn’t require any customised settings in SASBOSS nor any temporary numbers or licences.

How it Works

For every call, Access4 receives to the numbers in the Unified Redirection Number matrix, the diversion header which has ‘original called’ number (the number that has redirected the call) is examined against the provisioned numbers in our platform and delivered to the corresponding service.

This process effectively strips out the diversion process and delivers the call as if the number was hosted on the Access4 platform.

Process

1) Initiate port to Access4 as per the standard process.

2) Wait for PNV request to be confirmed and verified, at this point numbers will be added to the DID inventory and be available for allocation.

3) Configure SASBOSS services with correct number allocation.

4) Configure diversion of client numbers as follows:

a) Preference is to arrange Exchange Based Diversion (EBD).

b) Alternatively, if EBD is unavailable, numbers can be diverted from a managed end or PBX as long as the ‘original called’ number is preserved in the redirection signalling.

c) All numbers can be diverted on a ‘many to one’ basis to one of the following region based numbers in the attached matrix.

5. Once the service and diversions are in place, it is the partner’s responsibility to test the redirection is working correctly.

6. In the event calls aren’t terminating to the correct service, please check the SASBOSS service configuration and ensure the ‘original called’ number is present in the signalling prior to lodging a ticket with Access4’s TAC.

7. Once porting is completed and the diversion ceases, no changes need to be made to the SASBOSS services.

Benefits of the UPR service

  • No call costs for diversions during porting
  • Customers can move without waiting for porting to take place
  • Porting happens seamlessly in the background without any partner intervention
  • Prior to implementation, the customers own numbers are assigned to services removing the need to assign/remove dummy numbers during migration
  • Customer will dial out using their advertised numbers
  • The customer can redirect all their numbers to one centralised number allowing for exchange-based diversions. This means that customers can ‘turn off’ the services with the previous carrier.
  • Helpful for customers who have 1 or 1000 numbers.

Managing the Porting Process

In this blog, we’ll describe porting, a key process between carriers when moving one number from one telephony provider to another. It’s a common situation where the customer is with a particular carrier and wants to move services to another provider, in this case, Access4. The process refers to transferring Direct In Dial (DiD) geographical numbers, inbound numbers and international toll-free numbers.

The key to successful porting is following the established process and ensuring accurate information is provided to avoid delays. We advise all our partners to put enough time into reviewing their submission to be sure they can deliver all the required details.

1) Collecting all documents required to support a porting request

Supplying a copy of your client’s latest invoice (not older than 3 months) speeds up the process and allows us and the carrier to work through anomalies without reverting back to you or the client for further information; while we understand that this might be considered as a confidentiality challenge, it allows all parties included to confirm ownership of the number and the complexity of service to avoid any future miscategorization, during the porting process.
Partners are required to have written authority from their customer, authorising them to port on their behalf. By regulation, the losing carrier can challenge the authority, so it’s necessary to have these details stored in the event proof of authority is required.

2) Identifying your numbers category

Before you log a Porting request, you will need to identify which category the number/s belong to. There are three types of porting categories:

 

Category A – A simple PSTN analogue phone on the copper or NBN or SIP number. It can’t have complex services listed for Category C.
Category C – Any PSTN single number that has complex services attached or multiple 10/100/1000 number blocks – if you notice that you are not in the Category A it’s possible that you are Category C. See the table for a full description.
1300/1800 numbers.

What if you are not sure about which category? It’s best to discuss this in advance, so we are happy to help you to define the number category. Once that is done, you can proceed with the next step.

3) Upload a copy of the retail invoice to SASBOSS as part of the porting request.

The timeline after your porting request (step by step guide):

1. Your request received – Access4 receives and submits numbers to gaining carrier on a Porting Authority Form (PAF) with the retail invoice as proof of ownership. Timeline: submitted with 4 business hours.

2. Pending acceptance – The gaining carrier submits porting number validation (PNV) request to the losing carrier and awaits a PNV response. Timeline for Category A: 7 Business Days / Timeline for Category C/1300: 9 business days.

3. Submitted to carrier – Gaining and losing carriers have verified the request through an SNA/CNA and are awaiting port time and date. Numbers are imported into SASBOSS.

4. Verified – Port verified by a losing carrier. At this point, the numbers are automatically inserted into the DiD Inventory and are available for activation and outbound CLID over stamping. Timeline for step 3) and 4): Category A: 7 business days / Category C/1300: 15 business days.

5. Booked – Partner & End Customer have agreed on porting time and date. Timeline for Category A: Between 2-30 business day’s notice required. Timeline for Category C: Between 12-60 business day’s notice required. Porting will be between the 08:00 and 16:00 hours.

6. Completed – The Port has been completed and carrier sends a confirmation to Access4. SASBOSS is updated and the partner is informed via a ticket update. Timeline: Within one hour of commencement.

Note: the client may experience a short outage as the carriers update their routes.

Challenges and most common questions

The biggest challenge faced during porting is the accuracy of the information provided during submission. This includes associated numbers (missing numbers part of a group) and wrongly associated numbers (numbers that need to be disassociated because they don’t belong to the group or customer). If this occurs delays are inevitable and the process effectively starts again.
By selecting the ‘ASAP’ option in the porting machine the process is sped up as we’ll get the opportunity to request the first available date. Both carriers will have to agree that there is a vacant spot in their porting schedule. If the spot is available, the request gets accepted and automatically updated in the system, and visible in the SASBOSS.
Rescheduling charges

Partners can request to move the date but must do so with at least 48 hours notice prior to the scheduled port booking. No charges apply for the first reschedule, but an $80 fee applies for subsequent moves. Some carriers won’t allow more than 2 changes to the porting date, so we request partners manage customer expectations and lock dates in.

Rejection and cancellation charges

Rejection charges apply in the event the port can’t proceed due to misinformation submitted that can’t be resolved with 2 requests from the carrier. Please refer to your price-book for failed/withdrawn porting costs. In the event a partner cancels the port after the batch has been verified, the withdrawn fee applies.

Design + code by Jalapeno Creative.

Scroll to top