Porting Guide

Ofcom number assignment

Ofcom allocates geographic numbers to Service Providers or Range Holders (RH). Service Providers and RH then allocate their numbers to businesses and residential customers. When a number is allocated to a RH, the RH will never change.

Porting agreements

Before Packnet can submit a porting request on your behalf, we must first establish the number is in service and residing on a network where a porting agreement is in place.

If a number is not in service then we cannot port it into our network.

Our porting agreements are ever-expanding, but if we cannot port an area code then contact our support desk at voip@pack-net.co.uk.

Number types

Single or Multi-Line

Geographic numbers have two main categories: Single-Line or Multi-Line ports.

Industry definition of a Single-Line

A single-line order is for a single line which terminates on a socket that has a single number allocated to a line.

Industry definition of a Multi-Line

Multi-line orders cater for ranges of numbers or PBX groups that terminate on equipment (e.g. ISDN) configured for use by an End User or Customer. This includes the following:

• Multi-Line (30 Lines or less)
• Multi-Line (31 lines or greater)
• Complex DDI
• Feature net and Feature lines

Number types included in a porting request

Main Billing Number (MBN)

The number which all other telephone numbers on an allocated range are billed against. There can be multiple MBNs on a single invoice. Please check with your current provider if you are not sure, or share a recent invoice with our porting desk.

DDI Range

DDIs (Direct Dialling In) also referred to as DIDs are a range of numbers used for callers to dial directly a specific extension or user. DDI numbers are associated with the MBN. There can be multiple DDI ranges associated with one MBN. DDI ranges should be listed on your invoice.

Associated Number

Numbers that are dependent on the MBN for service and are linked to the MBN. They will be ported along with the MBN and any DDI ranges.

Other Number

Numbers registered to the same postcode but not associated with the MBN. Other Numbers should be included in the porting request with a note to say if they are to be ported, ceased or retained.

Porting request types

There are 3 main categories of porting requests: Provide, Subsequent and Return to Range Holder

Provide

The number's RH and Current Provider (CP) are the same and the number has not been ported before. Example:

1. The number's RH and CP are BT
2. The number is ported from BT to Packnet (provide port)

Subsequent

The number's RH and CP are different and the number has been ported before. Example:

1. The number's RH and CP are BT
2. The number is ported from BT to Packnet (provide port)
3. The number is ported again from Packnet to Virgin Media (subsequent port)

Return to Range Holder

The number's RH and CP are different, and the number is being ported back to the RH network. Example:

1. The number's RH and CP are BT
2. The number is ported from BT to Packnet (provide port)
3. The number is ported from Packnet to BT (return to range holder)

Lead times

Different porting requests have different minimum lead times. Note the lead times are guidelines only and not guaranteed.

The following lead times apply for UK Geographic Numbers:

Non-geographic ports have a lead time of 7 working days.

For subsequent geographic ports, the minimum lead times apply plus 3 working days. For subsequent non-geographic ports, it is 10 working days.

Submitting a porting request

Porting requests are submitted using an industry-agreed Customer Letter of Authority (CLOA). Packnet hosts an interactive CLOA here: https://mymetis.co.uk/porting

When asking us to port a number you must provide all the required information on your CLOA.

A complete guide to the CLOA can be found here: https://help.pack-net.co.uk/article/69-customer-letter-of-authority-cloa-explained

Porting procedure

1. Packnet receives your CLOA form
2. Packnet will review and verify the submitted information where possible
3. Packnet will contact you to confirm the porting request and ask for additional or missing information when applicable
4. Once all the information is available, Packnet will submit the porting request to the supplier with the earliest available porting date based on Lead Times, unless otherwise advised
5. The supplier will advise the Losing Provider of the porting request, who will then verify the submitted data and either
   1. Reject the porting request due to missing or invalid information
   2. Confirm the porting request and issue a confirmed porting date
6. If the porting request is rejected, Packnet will contact you to try and resolve the issue
   1. Once the rejection is resolved and any missing or invalid information is verified, Packnet will submit a new porting request
7. If the porting request is accepted, Packnet will contact you with the confirmed porting date
8. Packnet will import the numbers 24 hours before the confirmed porting date, allowing you to create your dial plan or send us the instructions
9. The porting request is completed on the confirmed porting date. Packnet advises you the port has been completed and whether calls are completing as expected