This document provides an operator's manual for the Class 4 Fusion V4.0 VoIP platform from DENOVOLAB LIMITED. It describes the system's architecture, which includes a switching engine, billing engine, web server, and database. The switching engine handles call signaling and routing, while the billing engine generates call detail records. The system supports intelligent least-cost routing, customized routing policies, number translation, and real-time call statistics. It is designed for high performance with scalability and fault tolerance. The document outlines the call processing sequence and configuration options for carriers, trunks, hosts, routing plans, and rate tables.

1. © DENOVOLAB
LIMITED
2011
Class 4 Fusion V4.0
Operator's manual

2. © DENOVOLAB
LIMITED
2011
Class 4 Fusion V4.0
Class 4 VoIP Platform
Document №: 1
Document type: Operator's manual
Date of issue: 01.04.2010
Responsible employee: Technical writer
Copyright ©
Copyright © 2011 DENOVOLAB LIMITED
All rights reserved.
DENOVOLAB LIMITED reserves the right to change any information contained in this document
without prior notice.
COPYRIGHT INFORMATION
The information contained in this document is the property of DENOVOLAB LIMITED
No part of this publication may be reproduced or copied in any form or by any means - graphic,
electronic or mechanical including photocopying, recording, taping, or any other information
storage and retrieval system - without written consent of DENOVOLAB LIMITED. No third party,
organization or individual, is authorized to grant such permission.

3. © DENOVOLAB
LIMITED
2011
Terms and acronyms
ACD
ASR
CDR
CSV
Client
Vendor

4. © DENOVOLAB
LIMITED
2011

5. © DENOVOLAB
LIMITED
2011
Introduction
1. INTRODUCTION
1.1. DOCUMENT
PROFILE
This
document
provides
an
overview
of
the
C4
Fusion
application,
a
carrier-­‐grade
solution
for
efficient
policy
routing
of
VoIP
traffic.
1.2. AUDIENCE
This
document
is
intended
for
Internet
telephony
service
providers
interested
in
finding
a
resolution
to
complex
transit
problems
and
administrators
responsible
for
deployment,
operation
and
maintenance
of
C4
Fusion
systems.
1.3. DOCUMENT
STRUCTURE
This
document
comprises
the
following
sections:
Section
1
Introduction
contains
general
information
about
this
document,
its
structure
and
the
conventions
used
in
explanation.
Section
2
System
overview
provides
a
description
of
the
system
functionality,
specifications,
architecture,
hardware
and
software
requirements
Section
3
C4
Fusion
operation
sequence
details
basic
operating
procedures
for
the
system.
Section
4
Web-­‐interface
provides
overview
of
the
web-­‐interface
and
details
standard
operation
procedures.

6. © DENOVOLAB
LIMITED
2011
2. System
Overview
D’Novo C4 Fusion is a system for comprehensive management of VoIP Network between multiple egress
and ingress partners. D’Novo C4 is designed to efficiently handle high call-per-second and concurrent
calls.
2.1. SYSTEM
ARCHITECTURE
AND
NETWORKING
ARRANGEMENTS
The D’Novo C4 Fusion system includes two main components: a switching engine responsible for
switching and a billing engine responsible for real-time accounting and CDR generation.
The entire system composes of a web server, database server, a switching engine, and a billing engine. The
database is the central data source for all routing and partner information. Administrators perform
configuration of the switch via web browser. The switching and billing engines synchronize the data with
the database on a periodically basis.
The DNL C4 Platform performs authentication and authorization of VoIP equipment, determine call
routing, call analysis, validation and transformation of call numbers, and QoS control. DNL C4 Platform
comprises two constituents:
o Database based on the Postgres X.X. The DB is a repository of data necessary for call routing and
analysis of statistics.
o Web server (WS) provides a easy-to-user graphical interface for administration tasks and
customer access.
2.2. SWITCHING Engine
The switching engine handles SIP and H.323 calls and perform two-way conversion of signaling protocols
when necessary. It is a full-featured session border controller with the following functionalities:
• Signaling provides two-way conversion of SIP/H.323 signaling protocols. The list of RFC
Supported are:
o RFC 2837
o RFC 3
• Media proxy – DNL C4 Switch provides high performance RTP tunneling between ingress and
egress partners and a back-to-back user agent. Both full proxy and signaling proxy operation are
supported
• Command line interface - DNL C4 Switch has a built-in telnet server that allows users to log on
to a switching host using any telnet client.
• Intelligent routing - DNL C4 Switch is able to determine routing dynamically based on Least-
Cost-Routing, ASR Maximization, and ACD Maximization
DNL C4 Switch is an all-in-one intelligent routing and switch module featuring advanced call routing
mechanism, elaborate network analysis and reporting tools. DNL C4 Switch has a fully distributed
architecture that assures almost unlimited scalability and flexibility in terms of fault-tolerance and
redundancy.
Key features include:

7. © DENOVOLAB
LIMITED
2011
o Determine the routing sequence based on costs, ASR, and ACD
o Enable administrator to implement customized routing policies using static routing
o The Platform allows the administrator to impose partner-level, destination-level, and time-based
call restriction
o The Platform performs translation of source and destination numbers according to configured
number transformation patterns
o The Platform keeps various statistical parameters (number of calls, ASR, ACD, QoS, etc.) at
ingress and egress level, and for each individual host.
o The Platform allows for creation and modification of customers’ rate plans
o The Platform provides graphical and tabular representation of operational statistics: peak and
current total number of calls, total call duration, ACD, ASR, QoS, etc
o The Platform supports number portability, inter/intrastate routing and jurisdictional-based routing.
2.3. Specifications and requirements
2.3.1. Hardware and software requirements
DNL C4 Switch and Billing Engine runs on CentOS 5.6 xxxx. The hardware requirements for the platform
depends on the projected system performance and the required method of redundancy.
The Postgres DB software runs on Red Hat Enterprise AS/ES 5
The following are recommended browsers for the platform:
Microsoft Internet Explorer v. 8
Mozilla Firefox v. 3
Opera 9
2.3.2. Capacity
Switching Engine
The System capacity varies with the number and type of CPUs in the system. The following tables show
expected performance for the different hardware specification.
Hardware Specification Performance Benchmark
• Up to 3500 concurrent call sessions
• Traffic growth rate up to 50 new calls per
second
• Post Dial Delay: 30 ms and below
• Up to 1000 calls during proxy operation
without codec conversion
• XXX Billing Records per second
•
Billing Engine
Hardware Specification Performance Benchmark
• Up to 3500 concurrent call sessions
• Traffic growth rate up to 50 new calls per
second
• Post Dial Delay: 30 ms and below

8. © DENOVOLAB
LIMITED
2011
• Up to 1000 calls during proxy operation
without codec conversion
• XXX Billing Records per second
•
Database Engine
Hardware Specification Performance Benchmark
• Up to 3500 concurrent call sessions
• Traffic growth rate up to 50 new calls per
second
• Post Dial Delay: 30 ms and below
• Up to 1000 calls during proxy operation
without codec conversion
• XXX Billing Records per second
•
2.3.3. Scalability
The capacity of a DNL C4 Switch can be scaled up by having multiple switching nodes across
multiple servers. Performance can be greatly improved in Database, Billing Engine, and
Switching Engine can be installed on individual hardware.
2.3.4. Fault tolerance
DNL C4 Platform features a background auto-recovery service designed to restore the operation
of the switching and/or billing engines in case of a failure. If the switching engine goes down, all
the existing RTP stream will not be impacted. DNL C4 Platform also provides live-call-migration,
enabling calls to be migrated from one server to another in the case of hardware failure.
1. Hot Stand-By
2.3.5.Cold Stand-By

9. © DENOVOLAB
LIMITED
2011
3. DNL C4V4 Platform Call Processing Sequence
When a call request hits the platform, the following call sequence will take place.
Step 1 Authentication and Authorization The system will verify the IP to ensure the call is
coming from an authorized host. Once that is
determined, the platform can determine the ingress
trunk.
Step 2 Determine Routing Plan Based on the tech-prefix appears in the DNIS, the
platform determines the routing plan and
corresponding rate table for ingress billing.
Step 3 Ingress Action The platform will check if there is any ANI or DNIS
digit modification that should be performed and if so,
the modification will be processed before the
platform starts to hunt for routes.
Step 4 Egress Selection The modified DNIS will be used for egress route
selection. The Platform will filter out the egresses
that do not meet the minimum profitability criteria.
Step 5 Routing After the list of potential routes is recognized, the
Platform will set routing priority according to LCR
and the QoS criteria selected by the Administrator.
If an egress returned with specific codes, the
Platform will automatically fail over to the next
egress or host based on the criteria that the
Administrator specifies in the UI.
Step 6 Call Setup During the Call Setup phase, the switching engine
sends a SIP INVITE to the egress host and the billing
engine will start to record the beginning of a call
session. When the call session is ended with success
or failure, the billing engine will
Step 7 Failover This stage is only needed if the egress host returns
with error code and if there are additional egress
hosts in the list of routing that can be failed over to.
The administrator can specify which return codes
when received should cause the platform to fail over
to the next egress host or stop hunting.
Step 8 CDR generation and Accounting When the call processing is completed, a call detail
record is generated.

10. © DENOVOLAB
LIMITED
2011
3.1. Carrier Model
The DNL Class 4 Platform supports unlimited number of carriers and each carrier can have any number of
ingress and egress trunks. Each ingress and egress trunks can have a number of hosts.
Within the platform, all administrative setting such as billing, invoicing and user authentication are
specified in the carrier level. All routing related setting is configured at the ingress or egress trunk level.
Each carrier can have any number of ingress and egress trunks. Within each trunk, there can be multiple
hosts. When defining multiple hosts for an egress trunk, it is possible to specify the routing rule against
multiple hosts within an egress trunk. The rule can be round robin or top down.
Host within an ingress trunk can’t be identical with any host within another ingress trunk.
3.2. Tech-Prefix
Within each egress trunk, there can be a lot of tech prefix. Each tech-prefix corresponds to a set of separate
routing plan and rate table. When a call hits the DNL Class 4 Platform, the switch determines which
ingress the incoming call belongs. After that is determined, the switching engine checks the DNIS to see if
it meets any of the tech-prefix or even no tech-prefix to determine the routing plan for routing this call and
rate table used to rate the call.
3.3. Rate Table
The Platform enables unlimited number of rate table to be created. Rate table can be applied for each

11. © DENOVOLAB
LIMITED
2011
ingress trunk’s tech-prefix and each egress. When applied in an ingress trunk’s tech-prefix, it specifies the
sell rate for the call. When applied in an egress, it specifies the buy rate for the call.
Each rate table can be specified as jurisdictional or non-jurisdictional. Normal A-Z is non-jurisdictional
only, whereas jurisdictional rate table is used in the case of US billing and rating. When a rate table is
configured as jurisdictional, a jurisdiction table defining the codes for each state must be specified. Also,
each rate entry within the jurisdictional rate table have three rate entries instead of one. These three entires
are: interstate rate, intrastate rate, and indeterminate rate.
3.4. Routing Plan
A Routing Plan defines the routing policy for each destination. Each routing plan can have many entries
with each entry defining the routing method. Example of a routing plan is as follow:
Routing Plan Name: RP_ABC
Prefix Static or Dynamic Routing Dynamic Routing Strategy Static Routing
52 Dynamic MX_DP
88 Static BD_STATIC
852 Static HK_STATIC
1 Dynamic US_NPANXX
Static Routing Table: HK_STATIC
Prefix Egress_1 Egress_2 Egress_3 Egress_4 Egress_5
8521 ABC_TELECOM DB_TELECOM
8523 WORLD_TELCO BD_TELCO
Dynamic Routing Strategy: MX_DP
Ranking Method Egress Trunks
Order by LCR ABC_TELECOM
DB_TELECOM
WORLD_TELECOM
In the above example, all 88xxxxx numbers will be routed based on the static routing table defined in
BD_STATIC whereas all 852xxxxxx numbers will be routed based on the static routing table defined in
HK_STATIC.
When a calls with prefix = 52 hits the switch, the switch will route based on MX_DP. In the example
above, the dynamic routing strategy MX_DP means that the switch will search for the cost for routing the
call via ABC_TELECOM, DB_TELECOM, and WORLD_TELECOM, and then it will use Least-Cost-
Routing to rank the order of each and route according. The cost for terminating each call via each egress
trunk is defined in the rate table corresponding to each egress trunk. The switch will calculate the cost of
terminate each call through each egress trunk and then rank the egress trunk.

12. © DENOVOLAB
LIMITED
2011
4. Web Interface
The web server provides a friendly graphical interface for convenient configuration and administration of
DNL Class 4 Platform.
4.1. ACCESSING
DNL
Class
4
Platform
THROUGH
WEB-­SERVER
To establish a link with the web server, enter the IP address or DNS name of the web server on the address
line of the web browser, such as http://192.168.1.10. Note that the working protocol must be HTTP. The
system will respond with a logon dialog similar to that shown in the figure below.
After logging onto the web-interface use the “admin” login name and password, you will be displayed with
the Carrier Listing screen. The Carrier Listing screen shows the list of carrier in the system, the remaining
balance, and all relevant information.
4.2. Carrier Management

13. © DENOVOLAB
LIMITED
2011
Name – Name of the Carrier
Login as Carrier – Click on to pop up a new screen which is automatically logged in using the specific
carrier’s identity.
Mutual Balance – Mutual Balance shows the difference between Payment made by Carrier and Invoice
created.
Mutual Balance ( ingress ) – Payment received by ingress subtract by Invoice created for the ingress
Mutual Balance ( egress ) - Payment sent to egress subtract by Invoice created for the egress
Mutual Balance ( balance ) – ingress balance subtract by egress balance
Actual Balance – Actual Balance shows the difference between Payment and actual usage
Actual Balance ( ingress ) – Payment received from ingress subtract by Actual usage of the ingress
Actual Balance ( egress ) – Payment sent to egress subtract by Actual usage of the egress.
Actual Balance ( balance ) - Actual Balance ( ingress ) subtract by Actual Balance ( egress )
Allowed Credit – Credit allowed for the carrier. When the actual balance falls below this amount, any
incoming calls for this carriers will be blocked.
Mode – This field shows whether this carrier is a prepay or postpay carrier.
Egress Trunk – The number shows the number of egress trunks configured for this carrier. When clicked
on the number, the list of carrier’s egress trunk will be displayed.
Ingress Trunk – The number shows the number of ingress trunks configured for this carrier. When clicked
on the number, the list of carrier’s ingress trunk will be displayed.
The list of icons and its corresponding explaination are as follows:
Icons Description
4.2.1. Create a New Carrier

14. © DENOVOLAB
LIMITED
2011
The fields and corresponding description for the carrier creation screen are as follows:
Section: System Info
Field Name Description
Name Name of the Carrier
Status Active or Inactive
Mode Prepay or Postpay
Allowed Credit The minimum allowed credit for this carrier
Minimal Profitability The minimum profitability for this carrier
Section: Company Info
Field Name Description
Name Name of the carrier
Address Address of the carrier
Main Email Main contact email
NOC Email Carrier’s NOC email contact
Billing Email Carrier’s billing contact
Rate Email Carrier’s rate contact
Tax ID Tax ID
Account Details This is a placeholder for the carrier’s description
Section: Billing Setting
Field Name Description
Currency Currency used in billing the carrier
Section: Short Call Charge
Field Name Description
Below This field defines the number of second and below which to be considered as
short duration calls
Percentage Percentage of Short Duration Calls to traffic additional charge
Additional Charge Additional charge for each calls that are classified as short duration
Section: Auto-Invoicing
Field Name Description
Payment Term A list of payment term can be defined under Configuration -> Payment Term.
This field let’s the administrated to choose one of the defined payment term.
Invoice Format Invoice can be HTML, EXCEL, or PDF format
Attach CDR This field specifies whether the email to carrier’s billing contact should include
the CDR.
Show Detail If this field is selected, the invoice will show the billing break-down by code
CDR Format CDR Format can be either CSV or Excel
Last Invoiced For This field specifies the last date that this carrier has been invoiced already. Any
new invoice should be created after this date.
Section: Low Balance Notification
Field Name Description

15. © DENOVOLAB
LIMITED
2011
Notify Carrier This field defines the credit amount that would trigger a low balance alert to the
carrier. The email will be sent to the carrier’s billing email contact.
Notify Admin This field defins the credit amount that would trigger a low balance alert to the
administrator. The email will be sent to the administrator’s email defined in the
Setting.
Section: Carrier Panel Address
Field Name Description
Username Username for the carrier to login
Password Password for the carrier to login
Configuration Administrator can specify the features that the carrier user can use once he or
she is logged in.
4.3. Carrier’s Ingress Trunk
There are two ways to create an ingress trunk for a carrier:
1. After a carrier is successfully created, a screen will pop up which prompt the administrator to
create an ingress trunk.
When clicks on “Add Ingress Trunk” the screen below will be displayed.
This quick wizard consists of the minimum information for an ingress trunk.
2. From the Carrier’s ingress listing screen, there is a button. Click on that button
and the complete ingress trunk creation screen will be shown.
4.3.1. Create Ingress Trunk

16. © DENOVOLAB
LIMITED
2011
The fields and corresponding description for the ingress trunk creation screen are as follows:
Field Name Description
Ingress Name Name of the ingress trunk.
Media Type Bypass Media – Media does not go through the system
Proxy Media – All media go through the system
Call Limit Maximum number of concurrent calls allowed
CPS Limit Maximum number of call per second allowed
Protocol Allowed selections are SIP, H323, and Both
PDD Timeout The number of milliseconds that the call will be held before the system will
return a 503 Service Unavailable
Ignore Early Media Ignore 180 only - The system will ignore only the 180 messages from egress
trunks
Ignore 183 only – The system will ignore only the 183 messages from egress
trunks
Ignore both 180 and 183 – The system will ignore both 180 and 183 messages
from egress trunks
Active True – This ingress trunk is operational
False – No call from this trunk will be routed.
T38 Enable – INVITE message with T38 SDP will be accepted
Disable – INVITE message with T38 SDP will be rejected
Codec All the codec allowed by this ingress trunk
Host All the hosts for this ingress trunk. Each trunk may have multiple hosts.
Resource Prefix Resource Prefix is for configuring multiple tech prefixes for each ingress trunk.
Rate Table and Route Plan must be specified for each entry or tech-prefix
whereas tech-prefix itself can be empty to implies no prefix needed.
4.3.2. Tech Prefixes for Ingress Trunk
Each ingress trunk can be setup with multiple tech prefixes. Each tech prefix correspond to one rate table (
sell side ) and routing plan. The rate table tells the system how to rate the sell rate of each call that comes
in using the specific tech-prefix and the routing plan tells the system how each call should be routed.

17. © DENOVOLAB
LIMITED
2011
4.3.3. Ingress Action
Click on the “Action” tab, you can specify action for ANI or DNIS of each incoming call.
Field Name Description
Time Profile The time profile for this action to be effective
Target DNIS – the action is to be done on the DNIS
ANI – the action is to be done on the ANI
Code The prefix for the DNIS or ANI that the action should apply
Action Add Prefix - Add digits to the prefix
Del Prefix - Remove a specified number of digits from the prefix
Add Suffix – Add digits to the suffix
Del Suffix – Remove a specified number of digits from the suffix
Chars to Add If Action is selected to be Add Prefix or Add Suffix, you will be able to enter
the characters that you would like to add
Num of chars to Del If Action is selected to be Del Prefix or Del Suffix, you will be able to specify
the number of characters to remove
Number Type This is where you specify the matching number of length of ANI/DNIS to be >,
=, or <
Number Length This is where you specify the length of characters to compare to if Number
Type is not “all”
4.3.4. Digit Mapping for Ingress Trunk
A digit mapping enables you to modify the ANI or DNIS based on pre-defined criteria. There are two steps
in defining a digit maps. The first step involves creating a digit map which multiple entries and the second
step is the actual assigning of the digit map to a specific ingress trunk.
To create a new digit map, select Routing > Digit Mapping from the main menu. Then, you will see a list
of digit maps that are already defined:

18. © DENOVOLAB
LIMITED
2011
When you click on the name of the digit map, you will see the list of entries that are already defined. You
may click on to create a new record.
Field Name Description
ANI The prefix for the calling number
DNIS The prefix for the called number
Translated ANI The ANI digits to be translated to
Translated DNIS The DNIS digits to be translated to
ANI Action Ignore: No Change
Compare: If the ANI matches with the call, then replace the matched portion of
the ANI with the Translated ANI
Replace: If the ANI matches with the call, then replace the entire ANI with the
Translated ANI
DNIS Action Ignore: No Change
Compare: If the DNIS matches with the call, then replace the matched portion
of the DNIS with the Translated DNIS
Replace: If the DNIS matches with the call, then replace the entire DNIS with
the Translated DNIS
After a digit map is defined, you can go back to the ingress trunk screen and click on the tab.
Then, you can specify the Digit Mapping to apply and for what Time Profile this digit map shall be
effective for this ingress trunk.
4.3.5. Disconnect Code for Ingress Trunk
Disconnect Code is where you can configure the return code for the different scenario. This section lets
you define the SIP error code and the SIP error message. To access this page, simply click on the
tab.

19. © DENOVOLAB
LIMITED
2011
Field Name Description
Response The error message to be returned
Code The SIP error code to be returned
4.3.6. Fail-over Rule for Ingress Trunk
Fail-over rules define when the call should stop routing to the next trunk or host upon receival of specific
codes returned from egress trunk. You can to have certain SIP error code and message to be returned to
ingress upon receiving of certain return code from egress.
To access the fail-over rule configuration page, click on the tab.
4.4. Carrier’s Egress Trunk
There are two ways to create an ingress trunk for a carrier:
1. Quick Wizard: After a carrier is successfully created, a screen will pop up which prompt the
administrator to create an egress trunk.

20. © DENOVOLAB
LIMITED
2011
When clicks on “Add Egress Trunk” the screen below will be displayed. Please note that this
screen only contains the minimum fields required for an egress trunk.
This quick wizard consists of the minimum information for an egress trunk. In the quick wizard
screen, you need to specify the egress trunk name, rate table for this egress trunk, and host(s). The
rate table in this case is the cost that the egress trunk is charging.
2. Full-featured egress Creation: From the Carrier’s egress trunk listing screen (below), there is a
button. Click on that button and the full-featured egress trunk creation screen will
be shown.
4.4.1. Create Egress Trunk
The screen below shows the egress trunk creation/modification panel.

21. © DENOVOLAB
LIMITED
2011
The fields and corresponding description for the ingress trunk creation screen are as follows:
Field Name Description
Ingress Name Name of the ingress trunk.
Media Type Bypass Media – Media does not go through the system
Proxy Media – All media go through the system
Call Limit Maximum number of concurrent calls allowed
CPS Limit Maximum number of call per second allowed
Protocol Allowed selections are SIP, H323, and Both
PDD Timeout The number of milliseconds that the call will be held before the system will
return a 503 Service Unavailable
Ignore Early Media Ignore 180 only - The system will ignore only the 180 messages from egress
trunks
Ignore 183 only – The system will ignore only the 183 messages from egress
trunks
Ignore both 180 and 183 – The system will ignore both 180 and 183 messages
from egress trunks
Active True – This ingress trunk is operational
False – No call from this trunk will be routed.
When this field is set to false, no call should be routed to this egress trunk.
T38 If this field is set to “DISABLE”, the switch will not send T38 calls to this
egress trunk.
If this field is set to “ENABLE”, the switch will allow T38 calls to be sent to
this trunk.
Codec All the codec allowed by this egress trunk. Any codecs not highlighted will not
be accepted to this trunk. When selecting egress trunk to process a call, the
switch will look at this field and send calls of the supported codec to the trunk.
If no codec is selected, the switch will not block calls to the egress trunk based
on codec.
Host All the hosts for this egress trunk. Each trunk may have multiple hosts. If
multiple hosts are specified, the user can also specify the routing method for
these hosts.
Route Strategy Top-down – Calls to this egress trunk will be distributed to each host using top-
down fashion.
Round Robin – Calls to this egress trunk will be distributed to each host using

22. © DENOVOLAB
LIMITED
2011
round robin fashion.

23. © DENOVOLAB
LIMITED
2011
4.4.2. Adding Tech-Prefix for Egress Trunk
This is where you can specify tech-prefix for each egress trunk. To access this page, click on tab
for the egress trunk.
Field Name Description
Time Profile The time profile for this action to be effective
Target DNIS – the action is to be done on the DNIS
ANI – the action is to be done on the ANI
Code The prefix for the DNIS or ANI that the action should apply
Action Add Prefix - Add digits to the prefix
Del Prefix - Remove a specified number of digits from the prefix
Add Suffix – Add digits to the suffix
Del Suffix – Remove a specified number of digits from the suffix
Chars to Add If Action is selected to be Add Prefix or Add Suffix, you will be able to enter
the characters that you would like to add
Num of chars to Del If Action is selected to be Del Prefix or Del Suffix, you will be able to specify
the number of characters to remove
Number Type This is where you specify the matching number of length of ANI/DNIS to be >,
=, or <
Number Length This is where you specify the length of characters to compare to if Number
Type is not “all”
4.5. Fail-over Rule for each Egress Trunk
You can define when the system should fail-over a call to the next host, the next trunk, or stop jumping to
next host/trunk at all. To access the screen for the fail-over rule for egress trunk, you can click on the
tab.
Field Name Description
Route Type Stop: Stop routing to the next host or trunk if the specified SIP Error Code is
received.
Fail to Next Host: If the specified SIP Error Code is received, fail over to the

24. © DENOVOLAB
LIMITED
2011
next host in the trunk. If there is only one host or no more host to be retried, the
call should be reattempted with the next trunk.
Fail to Next Trunk: If the specified SIP Error Code is received, fail over to the
next trunk only.
Code SIP Error Code
Response The error code that should be returned by the ingress trunk if Route Type is
specified as “Stop”.
4.6. Media Handling
Each ingress and egress trunk can have different media setting and the following matrix shows how the
system will handle the media for the different combination:
Ingress Trunk Media Setting
Bypass Media Proxy Media
Bypass Media Bypass Media Proxy MediaEgress Trunk Media
Setting Proxy Media Proxy Media Proxy Media
The system will bypass media only if both the specific ingress and egress trunks utilized to route the call is
specified as “Bypass Media” in the media setting.
4.7. Time-based capacity setting for each host
Each host can be specified with different capacity setting. When click on , you will be brought to a
screen which allows you to specify the Call Limit and CPS Limit based on Time of Day setting. There can
be different CPS/Call Limit for each host. When one host has reached its capacity limit, the system will
immediately route call to the next hosts for the egress trunk.
4.8. Static Routing Table
Static Routing is a key component of a routing plan. Before creating a routing plan, the static routing table
must be defined first. To create a new static routing table, selects Routing-> Static Route Table. Then, the
screen showing the list of static route tables will be displayed as follows:

25. © DENOVOLAB
LIMITED
2011
The above screen shows the name of static routing table, the last modified date, and how many times the
static routing table is being used by ingress trunk. You can click on the number and see the list of ingress
trunks that are utilizing this static routing table.
4.8.1. Create a New Static Routing
In the static routing table listing screen, you can click on to create a new entry in the static table
listing.
After you enter the name of the static route table, and click submit, a new static table is created. At this
moment, the static routing table is still empty. You can click on the name of the static table and you will be
brought to the detail routing for that static table.
In this screen, you can click on to create a new entry.
If the Static Route Table is not empty, you can view the list of routing entry within a static routing table by
simply clicking on the name of the routing table. Then, you will be able to see the route listing below:
Within the static route table, you can define as many unique prefixes as you need.

26. © DENOVOLAB
LIMITED
2011
Field Name Description
Prefix The system uses the longest prefix search to select the trunk list to be used.
Strategy Top-Down: The system will select the trunk using top-down
Round-Robin: The system will route calls to each trunk in the trunk list using
round robin
Percentage: The system will route calls to each trunk based on a pre-defined
allocation
Time Profile Each prefix and time profile combination must be unique. There can be
multiple entries for each prefix but the time profiles selected must not overlap
with each other.
Trunk List The trunk list specifies the series of trunk that
4.8.2. Create a New Route within a Static Routing Table
To create a new entry within a static routing table, clicks on , then you will see a new routing record
as shown below.
Field descriptions for each record is defined as follows:
Field Name Description
Prefix The matching prefix for this record to be used. If the entry is empty, then
it serves as a default if other entry does not match the incoming call’s
DNIS.
Strategy The available selection can be:
Top-Down – When multiple egress trunks is presence, the switch will
always select the 1st
one and then the next one.
Round Robin - The switch will select the egress trunk that is the next to
the last egress trunk being selected.
Percentage – The switch will allocate calls to egress trunks based on a
pre-defined proportion
Time Profile The time when this routing will take place. For example, there can be
two different routing, one for the peak hour and one for the non-peak
hour. The Time Profile species the time frame within which this entry is
effective. If no time profile is specified, then this entry is effective for all
time.
Trunk List The list of trunks and its corresponding orders.

27. © DENOVOLAB
LIMITED
2011
4.9. Dynamic Routing Table
Dynamic Routing is a key component of a routing plan. Before creating a routing plan, the dynamic
routing table must be defined first. To create a new dynamic routing table, selects Routing-> Dynamic
Route. Then, the screen showing the list of dynamic route will be displayed as follows:
Field descriptions for each record is defined as follows:
Field Name Description
Name Name of the dynamic routing strategy
Routing Rule LCR – The system will send calls based on least cost routing
Longest ACD – The system will rank egress trunks for each call based on
ACD for the specific terminating code
Largest ASR – The system will rank egress trunks for each call based on
ASR for the specific terminating code
Time Profile The time profile that specifies when this routing plan should be effective
Usage Count The number of routing plan that is using this dynamic routing plan.
When clicking on the number, you will be brought to a page showing the
list of routing plan that is utilizing this dynamic route strategy.
To modify the dynamic route plan, you can click on to modify the dynamic route plan details:

28. © DENOVOLAB
LIMITED
2011
4.10. Routing Plan
A routing plan defines how a call should be handle based on the prefix. Each routing plan may have many
entries and each entry has a prefix specified.
To view a list of routing plan available in the system, clicks on Routing -> Routing Plan. Then following
screen will be displayed.
4.10.1. Create Routing Plan
In the Routing Plan Listing screen, click on and you will see a new entry in the listing.
After you enter a routing plan name and click submit, the routing plan is created. At this moment, the
routing plan is still empty. To enter into the routing plan and view the listing, you can click on the routing
plan name.
In the Routing Plan’s listing screen, you can specify how each individual prefix can be routed either by
Static Routing Plan or Dynamic Routing Plan.
4.10.2. Create Routing Plan Entry
To create a new entry within a routing plan, simply click on , you will see a new row:

29. © DENOVOLAB
LIMITED
2011
Each routing plan entry has a prefix and each prefix can be configured to route using one of the following
routing methods:
Static Routing – The call with the specific prefix as DNIS is going to be routed using one of static routing
plan selected.
Dynamic Routing – The call with the specific prefix as DNIS is going to be routed using one of dynamic
routing plan selected.
Dynamic Routing and then Static Routing – The call with the specific prefix as DNIS will be routed with
the selected dynamic routing plan and then if the call fails to complete, it will be routed to the selected
static routing plan.
4.11. Block List
Block List is where you can define what number to block for ingress/egress carrier/trunk. You can have the
scope of the block to be for the entire system, for a specific carrier or for a specific trunk.
Field Name Description
Prefix The prefix to be blocked
Egress Carrier The blocking prefix is to be applied for this egress carrier.
Egress Trunk The blocking prefix is to be applied for this egress trunk.
Ingress Carrier The blocking prefix is to be applied for this ingress carrier.
Ingress Trunk The blocking prefix is to be applied for this ingress trunk.
Time Profile The time profile that this block is to be effective.
4.12. Rate Table
The Rate Table is where you specify ingress rate and egress rate for each call. To access Rate Table,

30. © DENOVOLAB
LIMITED
2011
simply click on Switch > Rate Table from the main menu. Then, you will see the list of available rate
table.
Field Name Description
Name The name of the rate table
Code Deck Code deck that specified the codes allowed for the rate table
Currency Currency for the rate table
Usage Count Number of time the rate table is being used in ingress/egress trunk
Rate Type DNIS – Rate is determined based on DNIS
LRN – Rate is determined based on LRN
Jurisdiction Country The jurisdiction table used to determine whether the call is interstate-
billed or intrastate-billed. This feature is used only for US billing.
4.12.1. Add Rate to a Rate Table
To add rates into a rate table, you can simply click on the name of the rate table. Then you will see the list
of rates available:
To add a new rate record, simply click on , you will see a new row:

31. © DENOVOLAB
LIMITED
2011
When you click on the extra fields, you get to modify the extra details:
Field Name Description
Code Prefix
Code Name Code Name for the Prefix
Country Country for the Prefix
Rate Tariff
Effective Date Effective begin date of the rate
End Date End date of the rate
Setup Fee Charge for each call if connected
Min Time Minimum billed time for each call
Interval Billing interval
Grace Time Calls will not be billed if the duration is less than the grace time
Second Number of second to be counted as 1 minute
Profile Time profile for the rate to be effective. You may have one rate for peak
hour and another rate for non-peak hour.
4.12.2. Mass Edit for Rate Table
At the bottom of the Rate Table, you can use the Mass Edit feature to modify multiple rate entries at the
same time.
Mass Edit Type Description
Insert as new rates Expire the selected rates and insert new rates.
Update current rates Update rates that are selected
Delete Found Rates Delete the selected rates and create new rates.
Update All Rates Change all the rates in the rate table

32. © DENOVOLAB
LIMITED
2011
Once the mass edit criteria is specified, click on “Process” to actually execute the change and click on
“Preview” to preview the change without actually modifying the data.
4.13. Code Deck
A rate table can be associated with a code deck. When a rate table is associated with a code deck, the rate
table’s rate must comply with the code deck. To access the list of code deck defined, you can click on
Switch>Code Deck from the main menu. Then, you will see the list of code decks:
4.13.1. Create code deck entry
To view a list of codes in the code deck, you can click on the name of the code deck. Then, the listing
screen will appear:
To add a new rate record, simply click on , you will see a new row. You may also do a mass
import by clicking on the tab.
4.14. Time Profile
Inside the system, there are many places where you can set up configuration according to specific time of
day. For instance, you may want to setup rate or routing based on whether the call is made during peak or
non-peak hour.
You can select Switch > Time Profile from the main menu to access the list of already-defined time
profiles.

33. © DENOVOLAB
LIMITED
2011
4.15.