Submitting a Port

How-To Video

How-To Guide

Pre-requisite:

• Sonar can process a port order with only one losing carrier per submission. If multiple Losing Carriers are included in submission, Sonar will generate an error and specify the losing carriers involved without identifying the current Losing Carrier per number. To resolve this issue, Sonar offers a Qualify LNP tool for identifying the Losing Carrier on a per single number basis. Instructions on how-to use this tool can be found here.
  

Step 1: Log in to Sonar

• Access Sonar by clicking on the relevant link below which is provided in your provisioning starter pack.

Step 2: List Porting orders

• Navigate to the top left actor menu, select Porting, then select List Porting Orders.

Step 3: Create Cat C Porting Order

• Under the LNP Orders tab, scroll down to the bottom of the page and select Create Cat C Porting Order.
  

Step 4: Add numbers to be ported

• Select Add Number Range under the section labeled Numbers To Be Ported.
  
• Then populate the Initial Number, Group Size and Quantity Fields.
  

• ‍Initial Number: Represents the first number from which the number block begins. The E.164 format must be adhered to, for instance: 61299990000.
  ‍
  ‍Group Size: Keep this field set to 1
  ‍
  ‍Quantity: Generates a sequential output of numbers from the initial number specified.
  ‍
  Example:
  If you intend to port a consecutive block of 500 numbers starting from 61299990000, you would input 61299990000 as the initial number, followed by 1 as the group size, and set the quantity to 500. This action will load 500 sequential numbers into the port.
  

Step 5: Complete destination information

• Complete the fields in the Destination section. Once completed select Create.
  

• Account: Symbio account to be billed.
  
  Account Number: End-customer's account number with the losing carrier.
  
  Preferred Cutover Date: Please specify your preferred date for the port cutover. While we strive to accommodate your preference, we cannot guarantee the exact requested date. Ensure that the date you specify is at least two weeks in the future. The confirmed cutover date will be provided in the Logged Ticket.
  
  Customer/Company:  End-customer's name as its printed on the losing carriers invoice.
  
  PAF Signed Date: Date the end-customer signed the porting authority form (PAF). This date/time cannot be in the future.
  
  Address: Provide the complete address of the end customer as it appears on the invoice from the losing carrier, or use the address of the service to be ported. Avoid the use of PO Boxes.
  
  Map To: Specifies where to map the ported numbers to. In nearly all cases, this should be set to 'Remote route'.
  
  Remote Route: Field appears when "Map To" is set to Remote route. This field sets the specific trunk/route for the DIDs once ported.
  
  Subscription: Field appears when "Map To is set to Remote Route. This field should be set to Geographic type subscription.
  
  Site: Field appears when "Map To" is set to Remote Route. Leave this field set to Default.
  
  Listing Code: This pertains to if you want the numbers listed in the White Pages.
  
  Type of Service: The default setting for the field is Fixed type. It is recommended not to modify this setting unless you have received guidance from Symbio advising otherwise.
  
  IPND Information: If you are transferring numbers for a single site, you can use this function. However, if you are porting numbers for multiple sites, it is advisable to keep this field empty and make use of the bulk upload process.
  ‍
  External Reference: You may enter your own ticket reference or other relevant information here, if needed.
  
  Billing Reference: You may enter your own billing reference identifier here, if needed.
  
  Logged Reference: Links an existing Logged ticket to the Sonar Port Order. If left empty, a new Logged ticket will be automatically generated and linked to the Sonar Port Order. The Logged ticket serves as the port communications channel between Symbio and the customer.