Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If you would like to notify administrator and/or vendor about drop in quality you have to use Factors Watcher in the same way as before. 

DID Routing

We've improved how the DID routing is configured through the system to simplify things for a user. With this version, the The routing to DIDs have been simplified in two ways:

  • "All destinations" option

...

  • has been removed in favor of default "Full DID" match,

...

Screenshot: Routing plan. DID routing

Image Removed

Additionally, if an account has multiple DIDs assigned with the same prefix, there's no need now to add full DID to the termination rate table. A rate for prefix can be added instead. It will save time and be more convenient during the import process.

Tip
titleUseful Tip

Let's assume we have one DID 38067101 assigned to the entity that has a rate for 38067. If the call will be placed for 38067102, the client will be among terminators, as it has a rate for 38067 (a.k.a. can terminate this kind of call). The workaround would be as follows:

  • create a code deck with all existing DIDs;
  • using Traffic Processing rules, assign the tag did to the calls that are going to DIDs;
  • when adding the above-mentioned rate, add tag did.

It will ensure the vendor with assigned DID will terminate a call only if it goes to a real DID, not to some other 38067 destinations.

Routing Analysis

The Routing Analysis section has been visually reworked to make it more efficient for the client to analyze the query results. The new Output filtration options include:

...

Lets you control the routes' output based on them being accepted or rejected by the system:

  • Accepted and Rejected - outputs all the possible routes;
  • Accepted Only - outputs only the rules that may be accepted during the actual routing.

...

Lets you control, which rejected routes to exclude from the output list. Available options are Reseller Mismatch, Blocked Reseller, Blocked Client, Blocked Account, Vendor Qty, Stop Hunting, Party ID Length, Profit Margin, Rate Increments, Orig Tags, Term Tags, Traffic Processing, Reseller Capacity, Client Capacity, Account Capacity, Rule Capacity, Quality.

Screenshot: Routing Analysis settings

Image Removed

Now it is possible to define the routes to be skipped in results to avoid massive details on non-relevant routes (i.e. Reseller Mismatch). Additionally, if there are multiple reasons for rejecting a certain rule, all of them will be displayed, not only single or few as before.

As to the query result, it's more representative to enable the configuration check for the entities like Client, Account, or Rate.

Screenshot: Routing Analysis query

Image Removed

  • now you can simply add a rule with "Type" DID and highest priority (typically = 0), to give the Routing Plan ability to route to DIDs
  • In the scenario when customer has multiple DIDs with same prefix it is now possible to set single rate for that prefix in the Termination Rate Table instead of listing all of the DIDs (please check notes below for details)

Screenshot: Routing plan. DID routing

Image Added

Tip
titleNotes on DID Rates

Let's assume your customer has 2 DIDs (801001 and 801002). Now instead of adding rates for both DIDs you can set a single rate for code 801. However if the call will be placed for a number with 801 prefix that is not assigned to any customer, this specific customer will be selected as a vendor for this code not under DID rule, but under regular Dynamic rules if they are present. To avoid this scenario we suggest to:

  • Create a Code Deck with all existing DIDs in your system and set the same name "DID" for all of them;
  • Use Traffic Processing with this Code Deck configured to match by Code Name "DID" and set tag "did";
  • When adding abovementioned rate to the customer set tag "did" on it, to match only in case the number is actual DID. 

Billing Increment Check

To improve profitability check we've added Billing Increments matching between Customers' and Vendors' rates in the routing. To use the feature set Match Increments field under the Rules Processing section of the Routing Plan. If selected, it will exclude vendors with increments that do not match customers' rates from the routing list.

...

The option checks that Customers' increments proportionally overlap Vendors' increments. Following table shows sample scenarios:

Customer RateVendor RateResultNotes
Min TimePay InternalMin TimePay Interval
60606060OKExact match
306301OKFull overlap
30666OKFull overlap
11306FAILVendor Increments are higher
7766FAILEven though Customers increments are higher, with call duration of 7 seconds this case will lead to 7 seconds billed on customer and 12 seconds billed on vendor

Stop Hunting Rework

The option "Stop Hunt" on the rules of the Routing Plans have been reworked according the industry requirements. Before current version it was considered by the system only if the route under the rule was accepted. Now it will work in all cases, even if the route has been rejected due to some checks.

ADD SCREENSHOT HERE FOR CONVENIENCE

Source Code routing

New version includes improvement in the Routing Map building for the rates with defined Src Code. Previous versions considered only rates without Src Code when building Routing Map. This leads to the improved Profit Margin checks. While running Routing Analysis do not forget to set Src Party ID in the filter section for correct analysis.

Maybe screenshot of Routing Analysis with defined Src Party ID

Routing Analysis

The Routing Analysis section has been visually reworked to make it more efficient for the client to analyze the query results. The new Output options include:

  • Verbosity - let's you control the routes' output based on them being accepted or rejected by the system:
    • Accepted and Rejected - outputs all the possible routes;
    • Accepted Only - outputs only the rules that will be accepted during the actual routing.
  • Skip Reasons - let's you control routes under which checks should be removed from the result
    • As an example you may want to remove routes that failed due to "Reseller Mismatch" to remove overwhelming output if you have many resellers in the system
    • Another example would be to remove routes failed under "Vendor Qty" check, if you have vendors with dozens of accounts

Screenshot: Routing Analysis settings

Image Added

Other improvements are related to the columns shown in the Routing Analysis:

  • Status - for rejected routes with column shows all reasons of route rejection (in a tooltip), not only a single one as before
  • Routing Rule - rule details including Routing Code, Priority, Balancing, ASR/ACD filters if used and others
  • Vendor - both Vendor and its Account name, both entities are now clickable leading to the details of either Vendor or its Account
  • Account - Account Identification, including technical details such as Gateway, Protocol, Capacity, etc
  • Code - Code and Code Name according to the Vendor's Rate Table
  • Rate - Vendor's Rate (marked in red for unprofitable routes) - this column (as well as customer's rate in header) include massive details:
    • The rate itself is clickable leading to the specific rate details
    • If future rate is available it will be shown right below the current rate
    • If current rate has end date specified, it will be also shown right below the rate
    • The tooltip include details on Profit Value and Margin, future and current rate details, if present
  • Dst Party ID - Destination Number as it will be sent to the vendor, including details on all Traffic Processing performed and Tech Prefix added
  • Appeal - the value calculated based on the Routing Policy defined (for dynamic rules), used for comparison on the result values and testing of different Routing Policies
  • Reject Reasons - list of all reasons by which the route has been rejected (useful for export)

The last improvement is related to grouping of the results:

  • Output Type Grouped - will split results into two sections - Accepted and Rejected, while Rank column will show the actual rank of the routes independent from the group they fell into
  • Output Type Plain - will show results according to their Rank and mark their status accordingly

Screenshot: Routing Analysis query

Image Added

Multipartitioning routing

...

Code Block
titleCode Example

Routing

Source Code routing

???????????

Currently routing map has only dst_code and while we creating it we are taking only rates with src_code = ''.
As result we may use incorrect rate during profit margin check. So we have to add src_code to the routing map, so that we will be able to check correct vendor rate and profitability.

Stop Hunt checkbox

...


Traffic Processing

Improvements in UI

...