Porting

nCloud South Africa Number Porting Process and Requirements

The topics below are discussed in this guide.

nCloud voip

Document Options

VOiP Systems

We provide tailer-made VOIP soltions for ISP's

We can provide intergragtion in Splynx system

For more information on Splynx hosting

Click here to send us an email!
voip porting

Overview of Porting in South Africa

Number porting is the process of transferring an existing number to a new carrier. This gives businesses the ability to retain their numbers, which can then be used as an outgoing CLI. nCloud's local licensing and direct subscription to the Number Portability Company (NPC) makes porting in South Africa uncomplicated and easy. In addition, all porting is carried out in line with the Electronic Coomunication ACT, NO 36 of 2005 for Number protability, Gazette 30089, dated 13 July 2007.

Portable Numbers in South Africa

Geographic (local): +271xx, +272xx, +273xx, +274xx, +275xx

Non Portable Numbers in South Africa

Non-geografical National: +2787, +2786
Non-geografical Toll Free: +27800, +27808

Number Porting Requirements

Once your request is received, nCloud will submit the port to the NPC on your behalf using the below legal form and supporting documents that state you are giving the gaining provider (nCloud) the authority to act on your behalf with regards to your numbers.

 

Please submit your port request to porting@ncloud.africa and include the below-required documentation:

 
  • nCloud GNP From.docx Click here to send us an email for a copy of the document
  • Authorization letter (must be on a clients letterhead)
  • Latest telephone invoice or statement (account number and holder verification)
  • In the case of an ISDN, an authorization letter stating whether to cancel or create a new range for the numbers that are not being ported.

Porting Timelines

If all the information you've provided is complete and correct and depending on the complexity of the port we can complete your port request within the following timeframes:

Fixed Line operators

  • Analog Lines: 2 - 5 working days from date of submission (INDIVIDUAL PORT)
  • ISDN/PRI: 7- 14 working days from date of submission (MANAGED RANGE)

Other Providers

  • 7- 10 working days from date of submission

For large orders, numbers need to be ported in batches and can cause longer lead times. Please contact the Porting team when needing to port more than 100 numbers in a batch

What rejections can cause porting delays

  • The MSISDN or DN/DN Range is not valid on the donor operator network.
  • The MSISDN or DN/DN Range is excluded from number portability.
  • For a postpaid subscriber, the MSISDN, account number, and account holder id number do not match.
  • The classification of the account does not match.
  • Subscriber in the suspension of outgoing or incoming calls due to failure to pay a bill.
  • MSISDN or DN/DN Range not valid on SP.
  • Port Request is for an inter-SP port; for this NO, inter-SP ports are handled outside the CRDB.
  • Other reasons:
    • Porting Back
    • Malicious
    • Fraudulent
    • Posted in Error
  • A participant has a routing problem.
  • A participant has an authorization problem.
  • The participant has a transmission problem.
  • Accept and Move to Managed GNP
  • The installation address is outside the geographic area associated with the DNs/DN Ranges specified in the request.
  • DN Range is not exclusively used by the operator requesting the port.
  • DN(s) or DN Range are excluded from porting under Regulation 3.
  • Account Number is not the account number used by the donor operator for the DN(s) or DN Range for which porting is requested.

Common reasons why the losing carrier would reject your port request

  1. The number or number block is not a valid number or number black on the donor operators network, or the number block is not used exclusively by the entity requesting the porting
  2. The number or number block is excluded from number portability under regulation 3
  3. The account number in the request is not the account number used by the donor operator for the number of numbers or number block for which porting is requested
  4. The subscriber is already subject to suspension of outgoing or incoming calls because of failure to pay a bill
  5. The number or number block is already subject to a porting process
  6. The number or number block has already been ported in the last 2 months
  7. The donor operator shall not reject a request to port a number or number block because the subscriber still owes money, nor may the delay the porting until the debt is collected, unless the subscriber is already subject to suspension of outgoing or incoming calls because of failure to pay a bill
  8. The donor operation shall not reject a port for a number or number block due to a remainder term on an existing agreement.

Can a ported number be reversed?

If a client ported in error or forgot to ask for the ADSL service to be retained, the porting request can be withdrawn within 60 days of its submission. However, any associated fees may not be refundable