Routing configuration between source and target systems in Dual Version

During the Dual Version setup, you need to configure call routing between the source and target systems.

This handbook covers:

• Preparation
• Configuration on the source system
  • Steps before the Dual Version provisioning stage
  • Steps after the Dual Version provisioning stage
• Configuration on the target system after the Dual Version provisioning stage

This handbook also provides instructions for cleaning up internal routing entities created on the target system after the migration is complete.

Obtain the SIP cluster IP addresses of the target and source systems (for example, 192.168.0.153 and 192.168.0.107). Contact PortaOne Support if needed.

In PortaBilling, call routing is always performed via a vendor. Therefore, even though no real vendor is involved, you must create a set of internal vendor entities (vendor, vendor tariff, and vendor connections) in the source and target systems. These entities are used exclusively for internal call routing. These entities are used exclusively for internal call routing.

The configuration process consists of two steps, depending on the Dual Version provisioning stage.

1. Step 1 – before the Dual Version provisioning stage startsCreate the required internal vendor entities:
   1. Create a vendor tariff
   2. Create a vendor
   3. Create vendor connections
2. Step 2 – after the Dual Version provisioning stage endsComplete rate configuration:
   1. Check rate codes
   2. Add rates to the vendor tariff
   3. Add rates to the customer and reseller tariff

• Open Service catalog > Tariffs
• Click + Tariff and fill in the details:
  • Name – define the tariff name, e.g., DualVersion_vendor_tariff
  • Currency – select a currency, e.g., USD. You can select any currency, just use it consistently throughout the configuration
  • Service – select Voice calls
  • Applied to – select Vendor
  • Enable the Routing toggle

    

• Click Save

• Open Infrastructure > Vendor
• Click + Add and fill in the details:
  • Name – define the internal vendor name, e.g., DualVersion_vendor
  • Currency – choose the same currency as you selected in the tariff, e.g., USD
  • Opening balance – leave 0
  • Billing period – leave Monthly

    

• Click Save

At this point, you will need to create two vendor connections – To vendor and From vendor types. As a remote IP address, use the IP address of the SIP cluster on the target system, e.g., 192.168.0.153.

To create a To vendor connection, perform the following steps:

• Open the vendor created at step 1.2, e.g., DualVersion_vendor
• Go to Connections, click + Add, and fill in the details:
  • Description – give a descriptive name, e.g., to-192.168.0.153
  • Service type – leave Voice calls
  • Type of connections – leave SIP
  • Direction – leave To vendor
  • Tariff – select the vendor tariff created at step 1.1, e.g., DualVersion_vendor_tariff
  • Leave the Active toggle enabled
  • Identify gateway by – leave IP
  • Remote IP – specify the IP address of the SIP cluster of the target system, e.g., 192.168.0.153
  • Capacity – enter any reasonable number that reflects the expected number of concurrent calls. This value is used only for scaling the load graphs and doesn’t actually limit call capacity

    

• Click Save

When creating a From vendor connection, you will need to assign a vendor tariff that contains a single zero-rate entry with the wildcard (|) ("pipe" symbol) rate code. You can use an existing internal vendor tariff used for on-net calls.

To find this tariff’s name, go to Toolbox > Find connection, filter the connections by Internal status in the Active field, and open the connection used for on-net calls to view the tariff name.

To create a From vendor connection, perform the following steps:

• Open the vendor created at step 1.2, e.g., DualVersion_vendor
• Go to Connections, click + Add, and fill in the details:
  • Description – give a descriptive name, e.g., from-192.168.0.153
  • Service type – leave Voice calls
  • Type of connections – leave SIP
  • Direction – change to From vendor
  • Tariff – select the internal vendor tariff, e.g., Internal tariff
  • Leave the Active toggle enabled
  • Node – select the node with the IP address of the SIP cluster of the source system, e.g., 192.168.0.107
  • Capacity – enter any reasonable number that reflects the expected number of concurrent calls. This value is used only for scaling the load graphs and doesn’t actually limit call capacity
  • Remote IP – specify the IP address of the SIP cluster of the target system, e.g., 192.168.0.153

    

• Click Save

Once you’ve done all the actions at step 1, notify the PortaOne support team.

After the Dual Version provisioning stage is completed, the PortaOne support team will notify you when to proceed with step 2.

During the Dual Version provisioning stage, special rate codes are automatically created for each environment in the source system, e.g., ENV-1319fa2c.

You need to make sure that the environment rate codes are present in the source system. For this, open the specific environment and:

• Go to Service catalog > Rates codes
• Filter the rate codes by custom format
• The Rate codes list should include the rate codes associated with the environment, starting with ENV

  

At this step, you need to add zero rates based on the special environment rate codes to the vendor tariff. To prevent failover and configure LCR routing calculation, each of these rates should have the highest preference (9) and huntstop enabled.

Repeat this step for each environment's rate code. For this, go to:

• Service catalog > Tariffs
• Open the tariff created at step 1.1, DualVersion_vendor_tariff
• Go to Rates and click + Rate, and specify the details:
  • Rate code – select the rate code created during the Dual Version provisioning stage, e.g., ENV-1319fa2c
  • Preference – set 9 (the highest)
  • Huntstop – select the checkbox
  • First interval – leave 1
  • First price – set 0
  • Next interval – leave 1
  • Next price – set 0

    

To enable call routing, rates for the same environment-based rate codes should be added to the tariffs of the customers and resellers that are going to be migrated. For this:

• Service catalog > Tariffs
• Select a customer and reseller tariff
• Go to Rates and click + Rate, and specify the details:
  • Rate code – select the rate code created during the Dual Version provisioning stage, e.g., ENV-1319fa2c
  • Preference – set 9 (the highest)
  • Huntstop – select the checkbox
  • First interval – leave 1
  • First price – set 0
  • Next interval – leave 1
  • Next price – set 0

Configuration on the target system can be performed at any time after the Dual Version provisioning stage, regardless of the source system configuration.

During the Dual Version provisioning stage, the special rate codes are automatically created for each environment in the source system, e.g., ENV-1319fa2c.

You need to make sure that the environment rate codes are present in the target system. For this, open the specific environment, go to:

• Service catalog > Rates codes
• Filter the rate codes by custom format and environment prefix
• The Rate codes list should include the rate codes associated with the environment, starting withENV

• Open Service catalog > Tariffs
• Click + Tariff and fill in the details:
  • Name – define the tariff name, e.g., DualVersion_vendor_tariff
  • Currency – select USD. You can select any currency, just use it consistently throughout the configuration
  • Service – select Voice calls
  • Applied to – select Vendor
  • Enable the Routing toggle

    

• Click Save

For this, go to:

• Service catalog > Tariffs
• Open the tariff created at step 1.1, DualVersion_vendor_tariff
• Go to Rates and click + Rate, and specify the details:
  • Rate code – select the rate code created during the Dual Version provisioning stage, ENV-1319fa2c
  • Preference – set 9 (the highest)
  • Huntstop – select the checkbox
  • First interval – leave 1
  • First price – set 0
  • Next interval – leave 1
  • Next price – set 0

    

• Open Infrastructure > Vendor
• Click + Add and fill in the details:
  • Name – define the vendor name, e.g., DualVersion_vendor
  • Currency – leave USD
  • Opening balance – leave 0
  • Billing period – leave Monthly

    

• Click Save

At this step, you again need to create two vendor connections – To and From types. As a remote IP address, use the IP address of the SIP cluster on the source system, e.g., 192.168.0.107.

To create To vendor connection, perform the following:

• Open the vendor created at step 1.2, e.g., DualVersion_vendor
• Go to Connections, click + Add, and fill in the details:
  • Description – give a descriptive name, e.g., to-192.168.0.107
  • Service type – Voice calls
  • Type of connections – SIP
  • Direction – To vendor
  • Tariff – select the vendor tariff created at step 1.1, e.g., DualVersion_vendor_tariff
  • Leave the Active toggle enabled
  • Identify gateway by – IP
  • Define the IP address in the Remote IP field, e.g., 192.168.0.107
  • Capacity – enter any reasonable number that reflects the expected number of concurrent calls. This value is used only for scaling the load graphs and doesn’t actually limit call capacity

    

• Click Save

When creating a From vendor connection, you will need to assign a vendor tariff that contains a single zero-rate entry with the wildcard (|) ("pipe" symbol) rate code. You can use an existing internal vendor tariff used for on-net calls.

To find this tariff’s name, go to Toolbox > Find connection, filter the connections by Internal status in the Active field, and open the connection used for on-net calls to view the tariff name.

To create From vendor connection, perform the following:

• Open the vendor created at step 1.2, e.g., DualVersion_vendor
• Go to Connections, click + Add, and fill in the details:
  • Description – give a descriptive name, e.g., from-192.168.0.107
  • Service type – leave Voice calls
  • Type of connections – leave SIP
  • Direction – change to From vendor
  • Tariff – select the internal vendor tariff, e.g., Internal tariff
  • Leave the Active toggle enabled
  • Node – select the node with the IP address of the target system, e.g, 192.168.0.153
  • Capacity – enter any reasonable number that reflects the expected number of concurrent calls. This value is used only for scaling the load graphs and doesn’t actually limit call capacity
  • Remote IP – the IP address of the SIP cluster of the source system in the Remote IP field, e.g., 192.168.0.107
• Click Save

  

Here, you need to create the special zero rates based on the special environment rate codes. Rates should be created for each environment and added to the tariffs for customers and resellers that are going to be migrated. For this, go to:

• Service catalog > Tariffs
• Select a customer and reseller tariff
• Go to Rates and click + Rate, and specify the details:
  • Rate code – select the rate code created during the Dual Version provisioning stage, e.g., ENV-1319fa2c
  • Preference – set 9 (the highest)
  • Huntstop – select the checkbox
  • First interval – leave 1
  • First price – set 0
  • Next interval – leave 1
  • Next price – set 0

    

After the Dual Version migration is completed, you can remove the previously created entities at steps 3.2-3.6 on the target system, as these entities are no longer necessary. However, you can keep them for future Dual Version migrations if planned.

If you decide to do a clean-up on the target system and have no plans to perform another Dual Version migration, then:

1. Remove vendor connections
2. Discontinue rate in customer, reseller, and vendor tariffs
3. Delete rate codes

At this step, you need to remove vendor connections created in steps 3.2-3.6 of the Configure the target system section.

1. Infrastructure > Vendors > and open the needed vendor
2. Go to Connections, hover over a specific connection, and click Delete

   

1. Go to Service catalog > Tariffs and open the needed tariff
2. Go to Rates and select a specific rate
3. Click Edit and mark the rate as Discontinued

   

To delete a specific rate code, you will need to wait till the discontinued rate with this rate code is deleted from the system. The period is set in the Rates.Cleanup_interval option on the Configuration server.

After this period of time, perform the following:

1. Open Service catalog > Rate codes
2. Select the rate codes and click Delete