Example 3: This example shows how the cost of a call is calculated if the call spans
over multiple time bands:
Assume a Cost Group, "CG Local" is configured with two time bands, as shown below:
Cost Group Time Band Start Time End Time
Connection
Cost
Minute Cost
CG Local
TB1 16:00 17:00 2 1
TB2 17:00 18:00 7 2
Assume that the call duration is 10 minutes, occurring between 16:55 and 17:05. In
other words, the first 5 minutes occurs in time band "TB1" and the next 5 minutes
occurs in "TB2", as shown below:
Figure 17-6: LCR using Multiple Time Bands (Example)
The device calculates the call using the time band in which the call was initially
established, regardless of whether the call spans over additional time bands:
Total call cost = "TB1" Connection Cost + ("TB1" Minute Cost x call duration) = 2 + 1
x 10 min = 12
17.2.2 Configuring LCR
The following main steps need to be done to configure LCR:
1. Enable the LCR feature and configure the average call duration and default call
connection cost - see 'Enabling LCR and Configuring Default LCR' on page 197.
2. Configure Cost Groups - see 'Configuring Cost Groups' on page 199.
3. Configure Time Bands for a Cost Group - see 'Configuring Time Bands for Cost
Groups' on page 200.
4. Assign Cost Groups to outbound IP routing rules - see 'Assigning Cost Groups to
Routing Rules' on page 202.
17.2.2.1 Enabling the LCR Feature
The procedure below describes how to enable the LCR feature. This also includes
configuring the average call duration and default call cost for routing rules that are not
assigned Cost Groups in the Outbound IP Routing table.
Note: The Routing Rule Groups table can also be configured using the table ini file
parameter, RoutingRuleGroups or CLI command, configure voip > services
least-cost-routing routing-rule-groups.
To Next Page
Loading...
