When routing a call, service providers can choose from multiple carriers to route the given call. Finding the cheapest paths to routing calls can save money for service providers. ClearIP’s LCR feature enables the minimization of call termination costs and increases profit margins.
The LCR tables are searched after the Inbound Routes and Outbound Routes tables. If a call matches a route defined in the Inbound Routes or Outbound Routes tables, then an LCR lookup is not performed for the given call.
NOTE: To use any of the routing features, first make sure that routing is enabled in the SBCs page under Organization.
LCR Products
The LCR Products page is used to list the names of the different available product offerings which are used to define custom groupings of LCR Providers to query for LCR. At least one LCR Product must be created in ClearIP to enable the LCR service.
ClearIP supports the option to create multiple LCR products. For example, two different products may be offered, with each product offering routes of distinct price ranges and qualities of service.
Defining which providers apply to a given product is defined in the LCR Provider Policies, and which calls apply to a given product is defined in the LCR Product Policies.
If selling call termination services to other carriers, then for each LCR product, it can be configured to have only profitable routes are returned by setting the Enforce Profit Margin field to Yes. The profit margin can be defined by a percentage or a fixed amount. If a Required Profit Margin Percentage and Required Profit Margin Fixed Amount are both configured for an LCR product, then ClearIP uses the greater amount as the profit margin to enforce. ClearIP returns routes that meet the enforced profit margin.
Before LCR profit margins can be enforced, applicable billing rates must be provided in the Billing Rates page.
LCR Product Policies
The LCR Product Policies table determines which LCR products should be used for certain calls. Specific SBCs, users, groups, service providers, or calling numbers can be matched to any LCR product.
For users with a single LCR Product, a single LCR Product Policy should be created to apply the LCR Product to all outbound calls.
For users with multiple LCR Products, multiple LCR Product Policies must be created to distinguish which LCR Products to apply to different types of calls.
LCR Product | Comment | SBC | Service Provider | Group | User | Calling Country | Calling Number |
---|---|---|---|---|---|---|---|
Gold LCD Product | Default Outbound | Default Outbound | Customer 1 | ||||
Gold LCD Product | 14045233030 | ||||||
Silver LCD Product | Default Outbound |
In the above example, the Silver LCR Product is used as the default LCR Product for all subscribers because all the columns to the right of the Comment column are left blank. The Gold LCR Product is reserved for specific subscribers which can either be provisioned based on their calling number or Service Provider, Group, and User value. If a call does not match one of rules for the provisioned calling numbers or Service Provider, Group, and Users defined for the Gold LCR Product, then the call uses the Silver LCR Product.
If sending both inbound and outbound calls to ClearIP, the rules must be redirected to only apply to outbound calls, so LCR lookups are not performed for inbound calls.
LCR Providers
The LCR Providers table lists the names of all carriers to be used across all LCR Products. LCR Providers are matched to a specific LCR product in the LCR Provider Policies page.
LCR Provider Policies
The LCR Provider Policies page is used to assign providers to specific LCR products. Each product can have unlimited providers, and each provider can be assigned to multiple products.
For users with a single LCR Product, all LCR Providers to the LCR Product should be assigned by adding a separate LCR Product Policy for each LCR Provider.
For users with multiple LCR Products, LCR Provider Policies must be created to select which LCR Providers should be considered for each LCR Product. A LCR Provider may be shared across multiple LCR Products.
LCR Product | LCR Provider | Comment |
---|---|---|
Gold LCR Product | LCR Provider 1 | |
Gold LCR Product | LCR Provider 2 | |
Gold LCR Product | LCR Provider 3 | |
Silver LCR Product | LCR Provider 4 | |
Silver LCR Product | LCR Provider 3 |
In the above example, the Gold LCR Product allows routing through either LCR Provider 1, LCR Provider 2, or LCR Provider 3. The Silver LCR Product only allows routing through either LCR Provider 3 or LCR Provider 4.
LCR Provider Exclusions
The LCR Provider Exclusions page allows calls to be disabled from being routed to specific providers. Call routing to specific providers can be disabled based on the called LATA, SPID, or number prefix. The excluded provider’s LCR destinations are not returned in the Contact header for the specified calls. This feature can be used if a provider is temporarily unavailable or if a provider gives poor performance (e.g. high post dial delay) for specific destinations.
LCR Provider Exclusion rules are effective until the rule is deleted from the table. ClearIP cannot be used to create LCR Provider Exclusion rules that expire after a set time. The rule must be deleted when no longer needed.
LCR Provider | LATA | SPID | Prefix | Comment |
---|---|---|---|---|
LCR Provider 3 | Remove LCR Provider 3 from LCR | |||
LCR Provider 2 | 1678949 | Do not return LCR Provider 2 for calls to LRN starting with 1678949 |
In the first example rule, LCR Provider 3 is completely removed from being returned in LCR. When LCR Provider 3 should be added back into LCR, then this rule can be deleted.
In the second example rule, ClearIP prevents returning LCR Provider 2 only for calls to a specific Prefix for the LRN starting with 1678949.
LCR Destinations
Each LCR Provider may have multiple destinations used for normal routing and failover.
These destinations can be prioritized for each provider by listing the destinations under Primary, Secondary, and Tertiary Route Destinations. In addition, each Route Destination priority level may contain a list of route destinations used for load balancing. For example, a provider may have two IP address destinations in a preferred geographic location and two IP address destinations in a backup location. The destinations in the preferred location would be entered into the Primary Route Destinations, and the destinations in the backup location would be entered into the Secondary Route Destinations.
Route destinations may be entered as an IP address, domain name, or trunk group number. See Contact Header section for examples of routing based on trunk group.
The Destinations per Route controls the maximum number of routes that ClearIP should return in the Contact header from each Route Destination priority level. This can be used to determine routing failover.
If the Destinations per Route is 1, then ClearIP returns one destination from the Primary Route Destinations, one destination from the Secondary Route Destinations, and one destination from the Tertiary Route Destinations. ClearIP returns up to 3 routes in the Contact header for the selected LCR provider. The destination is selected randomly from the available route destinations in each destination priority level for load balancing. After the first routing failure at the preferred location, the route fails over to the backup location.
If the Destinations per Route is 2, then ClearIP returns two destinations from the Primary Route Destinations, two destinations from the Secondary Route Destinations, and two destinations from the Tertiary Route Destinations. ClearIP returns up to 6 routes in the Contact header for the selected LCR provider. After the first routing failure at the preferred location, the route fails over to another destination at the preferred location before trying the backup location.
LCR Rate Plans
The LCR Rate Plans page lists the names of entered provider rate plans. Each rate plan contains the name of the LCR provider and the effective date. Rate plans can be created with effective dates in the past or future. The effective date and time shown are based on local time.
When looking at which rate plan to use, ClearIP looks at all rate plans with dates that are effective on the current day or earlier, ignoring rate plans with dates in the future. ClearIP chooses the most recent rate plan for each LCR provider to use for calculating the least cost route.
Each rate plan must contain a unique name, which can simply be the effective date and the name of the provider.
Provisioning LCR Rate Plans
To provision a rate deck, specify the rate deck format to ClearIP by entering in the row and column numbers for different values. Rates decks must be uploaded as a tab-delimited text file.
This rate deck contains rows for the NPANXX for US numbers and columns for Interstate and Intrastate rates.
A | B | C | |
---|---|---|---|
1 | NPANXX | InterstateRate | IntrastateRate |
2 | * | 0.02 | 0.01 |
3 | 201201 | 0.007 | 0.005 |
4 | 201202 | 0.007 | 0.005 |
5 | 201203 | 0.007 | 0.005 |
6 | 201204 | 0.007 | 0.005 |
When provisioning this rate deck, use the following settings:
- Starting Row: 3
- LATA Column: blank
- SPID Column: blank
- Prefix Column: A
- Prefix Prepend: 1
- International Rate Column: B
- Domestic Rate Column: B
- Intrastate Rate Column: C
- Local Rate Column: C
This rate deck contains rows with LATA, OCN, and the NPA and NXX split into two separate columns and columns for Interstate, Intrastate, and Local rates.
A | B | C | D | E | F | G | H | I | J | K | L | |
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | TERM_LATA | TERM_LATA_NAME | TERM_OCN | TERM_OCN_NAME | TERM_CATEGORY | NPA | NXX | RATE_INTER | RATE_INTRA | RATE_LOCAL | EFF_DT | |
2 | Alaska Default | 0.1 | 0.1 | 0.1 | 2020-01-01 | |||||||
3 | Canada Default | 0.1 | 0.1 | 0.1 | 2020-01-01 | |||||||
4 | US48 Default Rate | 0.01 | 0.01 | 0.01 | 2020-01-01 | |||||||
5 | Other Default (710 NPA) | 0.01 | 0.01 | 0.01 | 2020-01-01 | |||||||
6 | Puerto Rico Default | 0.01 | 0.01 | 0.01 | 2020-01-01 | |||||||
7 | Hawaii Default | 0.01 | 0.01 | 0.01 | 2020-01-01 | |||||||
8 | 12345 | Example | 1234 | Example | LEC | 201 | 201 | 0.007 | 0.005 | 0.003 | 2020-01-01 | =CONCAT(F8,G8) |
9 | 12345 | Example | 1234 | Example | LEC | 201 | 202 | 0.007 | 0.005 | 0.003 | 2020-01-01 | =CONCAT(F9,G9) |
10 | 12345 | Example | 1234 | Example | LEC | 201 | 203 | 0.007 | 0.005 | 0.003 | 2020-01-01 | =CONCAT(F10,G10) |
11 | 12345 | Example | 1234 | Example | LEC | 201 | 204 | 0.007 | 0.005 | 0.003 | 2020-01-01 | =CONCAT(F11,G11) |
Combine the NPA and NXX values into a single column with the combined NPANXX which we added in column L. Leave all non-required columns and rows in the file, and ClearIP ignores those values if those columns and rows are not referenced in the provisioning modal.
When provisioning this rate deck, use the following settings:
- Starting Row: 8
- LATA Column: blank
- SPID Column: blank
- Prefix Column: L
- Prefix Prepend: 1
- International Rate Column: H
- Domestic Rate Column: H
- Intrastate Rate Column: I
- Local Rate Column: J
This rate deck contains rows for the 1NPANXX for US numbers and columns for Interstate and Intrastate rates.
A | B | C | |
---|---|---|---|
1 | DestCode | InterstateRate | IntrastateRate |
2 | 1800 | 0 | 0 |
3 | 1833 | 0 | 0 |
4 | 1844 | 0 | 0 |
5 | 1855 | 0 | 0 |
6 | 1866 | 0 | 0 |
7 | 1877 | 0 | 0 |
8 | 1888 | 0 | 0 |
9 | 201201 | 0.007 | 0.005 |
10 | 201202 | 0.007 | 0.005 |
11 | 201203 | 0.007 | 0.005 |
12 | 201204 | 0.007 | 0.005 |
When provisioning this rate deck, use the following settings:
- Starting Row: 9
- LATA Column: blank
- SPID Column: blank
- Prefix Column: A
- Prefix Prepend: blank
- International Rate Column: B
- Domestic Rate Column: B
- Intrastate Rate Column: C
- Local Rate Column: C
Routes for toll free calls can be created in the Outbound Routes pages and do not need to be uploaded into the LCR platform. An example Outbound Route for toll-free calls can be seen in the Outbound Routes section.
Delete Existing LCR Rate Plans
LCR Rate Plans with an older effective date for a given LCR Provider do not have to be immediately deleted if more recent rate plan data was uploaded. ClearIP does not look at older LCR Rate Plans to make LCR routing decisions if there is a more recent LCR Rate Plan available for a given LCR Provider where the effective date is not in the future.
ClearIP allows a rate upload limit of 1,000,000 rates per LCR Provider total across all LCR Rate Plans for a single LCR Provider. ClearIP returns an error if an attempt is made to upload a rate deck that exceeds the 1,000,000 rate limit per LCR Provider. To resolve this, older rate decks must be deleted.
To delete an existing LCR Rate Plan, the Clear button for the LCR Rate Plan must be clicked. ClearIP takes a few minutes to delete the LCR Rates within the LCR Rate Plan and sends an email to confirm completion. Once the email confirmation is received, the LCR Rate Plan record can be selected and deleted.
LCR Rates
When rate decks are provisioned using the LCR Rate Plans page, the rate data is loaded into the LCR Rates page. The LCR Rates page shows data from across all rate plans and all providers in the same table. Each record in the table must be associated with a predefined provider and specific rate plan name. Each record represents a row in a carrier rate deck spreadsheet.
In the LCR Rates, a specific Prefix value can be filtered upon. This shows the rates for the prefix within all rate plans for all LCR providers.
ClearIP chooses the least cost route by first looking at which providers are available to route a call (by looking at the applicable LCR product). Then it finds the best matching prefix and/or LATA, SPID record within each active rate plan per available provider. ClearIP compares each best matching prefix rate across all available providers and lists the cheapest routes (up to 12) in the Contact header with the cheapest route listed first.
LCR Rate Plan Management
For LCR, it’s best to understand fundamentally how ClearIP processes calls in LCR and how the Rate Plans work. If this is understood, then the process to make any additions or changes will become clear.
How Clear IP processes calls in Least Cost Routing
When a SIP INVITE is received, ClearIP performs least-cost routing in real-time as follows:
- Determines which LCR Product to use to route the call from the LCR Product Policies page.
- Identifies the LCR Providers who participate in the chosen LCR Product from the LCR Provider Policies page.
- Excludes any Providers listed in the LCR Provider Exclusions page.
- Collects the routes to be returned for the selected LCR Providers from the LCR Destinations page.
- Searches the LCR Rates to find the best matching prefix, LATA or SPID for each selected LCR Provider
- Returns the least expensive routes in order with the lowest cost route first (up to 12 routes).
How ClearIP determines which Rates are applicable for each LCR Provider
ClearIP determines which Rate Plan has the most recent effective date and uses it. The process is as follows:
- Sort the Rate Plans for each LCR provider by effective date.
- Disregard Rate Plans with an effective date greater than today.
- Select the Rate Plan with the latest effective date - the “active Rate Plan”.
Rules to follow when managing Rate Plans
Rate Plan Rules:
- Uploading and Provisioning a rate deck to a Rate Plan is a tool to bulk add multiple Rates, like clicking the Add button on the LCR Rates page.
- Provisioning a rate deck uploaded to a Rate Plan is additive only (i.e., any duplicate rates in the new Rate Plan will not overwrite any existing Rates for a given Prefix value).
- Clearing a Rate Plan removes all the Rates currently in that Rate Plan, like deleting a Rate on the LCR Rates page.
- To delete a Rate Plan, it must be cleared first.
- Adding a Rate Plan, uploading and provisioning a rate deck, clearing Rates or deleting a Rate Plan whose effective date is in the future or is older than the most recent Rate Plan does not affect the active Rate Plan.
- Changing the Effective Date on a Rate Plan that will make it the most recent, will set that Rate Plan as the active Rate Plan immediately.
- When making a change (e.g., Provisioning a rate deck or Clearing a Rate Plan) always wait to get the email notification that ClearIP has completed the task before making another change to the same LCR Provider.
- Try to keep the number of Rate Plans for each LCR Provider at 3 or less to stay under the 1M rate entry limit.
Example Procedures for managing Rate Plans
Based on the above functionality and rules, procedures for making changes should be intuitive. For example:
- For updating a Rate Plan in ClearIP after receiving a new rate deck from a service provider:
- Create a new Rate Plan for that LCR Provider with an Effective Date in the future. It is good practice to include the effective date in the name of the Rate Plan.
- Upload and Provision the new rate deck.
- An error is discovered in a new rate deck that has been provisioned in a future-dated Rate Plan:
- Repair the rate deck, Clear the Rate Plan and provision the repaired rate deck.
- An error is discovered in the most recent (active) Rate Plan:
- Repair the rate deck.
- Change the Effective Date of the active Rate Plan such that it is no longer the active Rate Plan. For example, change the Effective Date to a date in the future or to a date in the past that is older than the oldest Rate Plan. Either way, this will cause the next oldest Rate Plan to become the active Rate Plan.
- Clear the Rates of the erroneous Rate Plan and Provision the repaired rate deck.
- Change the repaired Rate Plan’s Effective Date so that it becomes the active Rate Plan.
- For bulk adding new records into an existing, active Rate Plan:
- On the LCR Rate Plans page, click Provision on the LCR Provider record that entities need to be added to, and upload the rate deck. Note this is additive only and risks conflicts, the main risk being duplicates. Think of clicking Provision as the same as clicking Add on the LCR Rates page for every record in the new file, i.e., a bulk Add.