Number Porting - Complete Handbook

Number porting is a change in the CP (Communications Provider) or Current Network Operator (CNO) of the inbound routing of a telephone number.

UK number porting is made technically possible by onward routing, where the number(s) to be ported are prefixed by the rangeholder or host network operator for the rangeholder with a number porting prefix for the gaining network operator. When a call is placed to the ported number after the porting prefix has been applied the call is then routed directly to the gaining network operator via the designated points of interconnect agreed under the service establishment between the new network operator and the host network or rangeholder.

As such number porting does not change the Ofcom-allocated RH (Range Holder) of a number, as the calls will usually always route through the RH systems or the RH's host network operator.

VoiceHost use BTIPEX (BT IP Exchange) for the vast majority of porting requests for the VoiceHost platform. IPEX has arguably the widest SE (Service Establishment) with range holders and host networks, enabling VoiceHost to facilitate the porting of most UK landline and non-geographic telephone numbers, particularly from the larger tier 1 network operators.

IPEX cannot import a number from a RH or host network that they do not have service establishment (SE) with. In any case, where IPEX do not have SE with a range holder or host network, they will attempt to complete SE with them and sign a porting agreement for the portability of those numbers. The SE process can take a minimum of 55 working days for geographic numbers, however, any errors or obstructions found on the systems they are attempting to service establish will lengthen this timeframe accordingly, in addition, a porting agreement must be signed before porting orders may be exchanged.

For a port request to be accepted by the CNO (Current Network Operator) / Losing CP (LCP) or RH, all of the information on the documents forwarded to the LCP/RH must match what is on file for the telephone number(s) to be ported. It is usually best to contact the current provider and ask them what is on file for the postcode and additional information against the numbers to be ported when filling out the porting document, at this point you may also inform them of your intention to port the number away from them, so that the port request is not obstructed.

VoiceHost can attempt to facilitate direct porting agreements and service establishments with network operators that fall out of scope with the BT standard interconnect agreement. Our porting team will be able to advise you should this situation arise.

When a number ports from a fixed telephone line, the original line is usually ceased. This means that any and all additional services directly provided on the telephone line will also be ceased, e.g broadband or voicemail. Number port prefixing on analogue and digital line (ISDN) import activation's from BT as the range holder usually happens at the exchange level.

When a number is ported to our service, the original RH changes the prefix on the number, so that it routes out to IPEX. It is imported onto the IPEX platform and programmed in their core routing engine, which then routes all calls into that number onwards to the VoiceHost platform.

In order for VoiceHost to port your number onto the VoiceHost VoIP platform, we need, for all numbers:

1. Proof of ownership of the number (ideally in the form of a copy of the latest bill from the current CP)
2. Authorisation from the subscriber to port the number (in the form of a GNP Customer Letter of Authority signed by the subscriber)
3. Relevant telephone number details (in the form of completed porting documents)
4. Range holder CUPID (find on www.telecom-tarrifs.co.uk AND check against Ofcom S1 allocation form)
5. LCP CUPID (may also be Range holder, otherwise is the company billing you for the number)

We are unable to progress any ports without this information.

There are a number of factors that can delay port orders.

1. Redcare / security tag exists on the line. You must cancel Redcare or transfer the service to another circuit number before that number can be ported.
2. The Installation address or postcode is incorrect or does not match the current network operator's data against the number. We need to know the current postcode of the number(s) for a port order to validate correctly. See Pre-Order Validation PoV
3. LCP/RH failure to provide a response. You should always inform the current provider of an intention to port away so that a port order is not held up.
4. No SE (Service Establishment) with LCP/RH. Unfortunately, you as the subscriber can do nothing to affect this.
5. Incorrectly labelled (single line as multiline etc). You should always confirm the line type with the LCP/RH.
6. Incorrect telephone details (main billing number, DDI range etc). You should always confirm with the LCP/RH all attached phone numbers, main billing number etc).

VoiceHost is able to request the line information (associated address) held by a CP/NO that is UK registered on the Ofcom scheme. This mitigates the trial/error of porting numbers with unknown details.

The Ofcom register is available here: App_J3-Consolidated_Contacts_Register-PoV_Process-v8.4.pdf

The number porting process is always GCP (Gaining Communications Provider) led and exists exclusively for the end-user/subscriber. This means that to export numbers, the subscriber follows the import process with another provider. The LCP simply validates the data submitted accordingly. A Customer Letter of Authority (CLoA) is still required with the new provider, and this is checked prior to exports being progressed. Porting guidelines are industry-wide so the process will usually be similar to another CP.

It is always expeditious to provide VoiceHost with a copy of the CLoA if your porting timescale is short as delays in receiving this from the GCP will cause the port to time-out as it cannot be validated.

Any number that has been ported into to BTIPEX can usually be ported out again, i.e where we are not the range holder. Numbers imported to VoiceHost can usually be exported as they were initially imported, or split accordingly, however, if numbers to be ported were a range of numbers was imported then that entire range must be exported in order to keep the desired number(s).

Geographic numbers where VoiceHost is the range holder may be exported away from VoiceHost but there are some caveats to the IPEX platform to be aware of, both of which should hopefully be negated in the future:

1. Once number ranges allocated by Ofcom to range holders that built on IPEX have been exported away from IPEX, they cannot yet return to IPEX, importantly this includes any other IPEX Communications Provider (e.g. if a number exported to the BT PSTN wants to port somewhere else this cannot be fulfilled at present).
2. Number ranges allocated by Ofcom to VoiceHost which are built on IPEX can presently only be prefixed away from IPEX once. This means that the porting prefix cannot be updated or changed for subsequent ports to other network operators, thereby making the initial export of the VoiceHost number permanent until advised accordingly by IPEX as above
3. Non-Geographic number ranges (beginning 03, 05, 08 or 09) allocated by Ofcom to VoiceHost and built on IPEX cannot currently be exported and export requests of this nature are currently out of technical scope.

Numbers that are not in service cannot be exported. The number(s) to be ported must be live and be working in order to be ported. Any number ports requested for numbers that fail when calling will be rejected.

Reseller / Wholesale bulk porting of subscribers' numbers into or out of VoiceHost is not supported as number portability exists for subscribers (i.e. end-users) wishing to change provider only. Any reseller ports requested will be rejected. The above process is mandatory in all circumstances. See here for more information:http://stakeholders.ofcom.org.uk/binaries/telecoms/numbering/letter101212.pdf

The Export Process:

1. Submit your GNP request to the GNP.
2. VoiceHost will be notified by BT Openreach of the export request.
3. VoiceHost will validate the request and notify the subscriber/reseller for legitimacy.
4. Legitimate requests are then cleared for export subject to lead times.

• Single Line Geographic - A single telephone number beginning 01 or 02, that is not part of a DDI range, is not the main billing number for a DDI range, and is not part of a multi-line.
• Multi Line Geographic - Multiple lines on one or more telephone numbers, including WLR analogue Multi-Line and single-number ISDN.
• Simple DDI - Multiple digital lines (ISDN/T1/E1/SS7) on one or more telephone numbers, consisting of a main billing number. It can contain a whole block of DDI's (minimum 10, multiple of 10) and/or have SNDDIs on the circuit.
• Complex DDI - Multiple digital lines (ISDN/T1/E1/SS7), consisting of part of a block of DDI's, and a main billing number. Note: All DDI's attached to the circuit must be included on porting document, and intention given as to which numbers to port. Any numbers not ported will be handed back to the RH.
• Single Line Non Geographic - A single telephone number that is non geographic, is not part of a DDI range, is not the main billing number for a DDI range, and is not part of a multi-line or Feature Line.
• Multi Line Non Geographic - Multiple non geographic telephone numbers, consisting of an original and whole block of DDI's (minimum 10), and a main billing number.
• International - Telephone numbers from countries outside the UK (+44).

• Single Line Geographic - Porting Form, Letter of Authority, Copy of Latest Bill
• Multi Line Geographic - Porting Form, Letter of Authority, Copy of Latest Bill
• Simple & Complex DDI - Porting Form, Letter of Authority, Copy of Latest Bill
• Non Geographic - Porting of Non-Geographic Numbers Notice, Copy of Latest Bill
• Multi Line Non Geographic - Porting of Non-Geographic Numbers Notice, Copy of Latest Bill
• International - Requirements vary and are country specific

NOTE: THESE ARE THE MINIMUM LEAD TIMES:

• Single Line Geographic Import - 4 to 13 working days
• Multi Line Geographic Import - 7 to 25 working days
• Simple DDI - 10 to 23 working days
• Complex DDI - 22 to 25 working days
• Non-Geographic Import  - 15+ working days
• International (non-uk)  - Varies between countries

1. Customer submits to VoiceHost: Porting form (Customer Letter of Authority / CLoA), copy of the latest bill.
2. VoiceHost submits to IPEX using online portal with CRD (Customer Required Date).
3. IPEX complete an automated look up on their systems, verifying line type and range holder.
4. If details match records with LCP/RH, the order is confirmed.
5. IPEX receive response from LCP/RH confirming acceptance on DD/MM/YYYY@HH:MM
6. VoiceHost notifies the customer that number has been accepted to port.
7. At least 24 hours prior to port, VoiceHost will add the porting number to the customer's account ready to receive traffic from BT IP Exchange.
8. On date and time of port, IP Exchange automatically loads number onto ENUM and direct calls from that number to VoiceHost so they are ready to catch traffic from RH.
9. RH automatically applies porting prefix so calls are routed to IP Exchange
10. Confirmation that number has ported is sent by IP Exchange to us.
11. VoiceHost test-call after receiving completed port notification to make sure calls are routing correctly. If not routing correctly, escalate to BT immediately.

1. Customer submits to VoiceHost: Porting form, Letter of Authority, copy of the latest bill.
2. VoiceHost submits a request to IPEX using online portal.
3. IPEX then apply this information on a NPOR form manually.
4. NPOR gets sent to BT Openreach, who send it off to the LCP/RH.
5. LCP/RH then check the details on the NPOR and respond back to Openreach accordingly, if rejected providing the reason why.
6. Openreach then sends the response to IPEX.
7. If accepted, a confirmation response is sent to VoiceHost confirming date and time the porting process will begin
8. At least 24 hours prior to the port, VoiceHost add numbers into customer's account ready to receive traffic.
9. On the date of port, VoiceHost manually configures the number port on IP Exchange portal after the Port Configuration Window Start(s). This loads it into ENUM.
10. On date and time of port, VoiceHost call IP Exchange, give reference number(s) and/or MBN, and ask them to progress the port and perform a test-call to make sure ENUM load is correct.
11. Openreach then progresses the port, where the RH applies the porting prefix, and inbound traffic on PSTN should then route through to VoiceHost.
12. If there is downtime of 15 minutes or more VoiceHost ring IP Exchange requesting they escalate due to the downtime.

1. The subscriber has to fill in a separate Non-Geographic Number Porting Notice - this form must be typed, printed on customer-headed paper, signed and dated and sent back to us with a copy of a bill from LCP. There must be an account number the subscriber has with the current provider where available, the address of the Losing Communications Provider and contact email address and telephone number, and the Gaining Communications Provider must be VoiceHost Ltd and our address.
2. If resellers are involved in the transaction the porting lead-time stretches - for non-geographic porting all parties have to be informed of the port request. The minimum lead time for non-geographic number porting is 15 working days.
3. Once all the correct subscriber paperwork is received, VoiceHost sends the paperwork to IPEX, who then process the port request on VoiceHost's behalf via BT Inbound Services. Inbound Services then send a port request to the current communications provider (this could be a reseller), or reject the port request because of incorrect paperwork or inability to port.
4. BT, upon acknowledgement of the porting request to the end-users provider, then approach the RH with a port order.
5. Once the port order has been accepted, a confirmed date for the port to take place will be confirmed to IPEX, and if appropriate a fixed time or time range.
6. At least 24 hours prior to the port taking place, VoiceHost will add the number(s) required into the subscriber's VoiceHost account ready to receive inbound calls,
7. On the date and time of the port, IP Exchange builds the number(s) on ENUM, then contact RH to initiate porting prefix.
8. The number should then have been ported, VoiceHost does test calls to confirm number routes to us correctly. If there is downtime of 15 minutes or more VoiceHost ring IP Exchange requesting they escalate due to the downtime.

POR (Port Override Requests) exist to force through a number porting request when the LCP is deliberately blocking or being obstructive towards the end users right to retain the telephone number.

POR (Port Override Requests) can be placed on any UK originating line type be it Geographic, Non-Geographic, Residential or Business, Single or Multiline

The decision to initiate the POR process must be a joint decision made by the End User’s Retailer (i.e. the Gaining Party-GP) and the Gaining Wholesaler (i.e. the Gaining CP-GCP), on the basis that both parties will have first hand knowledge of the port order in question and the obstacles preventing it’s progress.

POR (Port Override Requests) have a 6 stage process

• Stage 1 – POR alert
• Stage 2 – POR trigger
• Stage 3 – POR Evidence Pack
• Stage 4 - POR Pack submitted for EAP approval
• Stage 5 – POR Executive Authorisation Panel (EAP)
• Stage 6 – POR execution & closure

Most common number Port rejection reasons can be avoided by completing a PoV (See above)

Here are some of the common rejection codes and their reasons and explanations

• Code 2 = CUPID missing or invalid
• Code 6 = Porting telephone number missing or invalid
• Code 15 = Other (must detail reason for rejection separately)
• Code 25 = Single Line Order but porting telephone number is Multi Line
• Code 26 = Multi Line Order but porting telephone number is Single Line
• Code 30 = Telephone Number Already Ported
• Code 31 = Customer has no service with LCP
• Code 32 = Porting request out of current scope for Number Portability
• Code 41 = LCP Installation Postcode invalid
• Code 44 = Telephone number(s) associated with MBN missing or invalid
• Code 52 = Invalid Range Holder (i.e. telephone number does not belong to Range Holder)

In the context of this document, the following acronyms are used:

• IPEX = British Telecom IP Exchange
• IPEX = IP Exchange
• CUPID = Communications Unique Provider ID
• CP = Communications Provider
• LCP = Losing Communications Provider
• CNO = Current Network Operator
• GNP = Geographic Number Porting
• CRD = Customer Required Date
• RH = Range holder
• SE = Service Establishment
• DDI = Direct Dial In
• ISDN = Integrated Services Digital Network (ISDN2e or BRI, ISDN30e or PRI)
• PSTN = Public Switched Telephone Network
• SS7 = Switched Signaling 7 – a set of protocols typically on a fixed E1 circuit defining call routing and signaling
• NGN = Non-Geographic Number
• ENUM = E.164 Number Mapping - IPEX's call routing engine which directs incoming calls on telephone numbers to the allocated carriers/destinations

VoiceHost has successfully imported numbers from the below Range Holders - Errors and omissions excepted

This is not an exhaustive list and the a Range Holder not appearing does not mean that a route to porting numbers is not available with the exceptions of: Guernsey (01481), Jersey (01534), Isle of Man (01624)

• Any BT IP Exchange Annex A Communications Provider  (Annex B CPs {i.e. Gamma} bill the same on IPX as they do on TDM and are not possible to port from without a direct porting agreement between VoiceHost and the CP)

*If the range holder of a number you wish to port from is not in this list, please call our porting team to find out whether a port request for the desired number(s) is likely to proceed or not.