Dialogic ControlSwitch Maintenance Guide

Type
Maintenance Guide
Dialogic® ControlSwitch™ System
Maintenance Guide
Revision 2
Release 5.10.2
July 2015
www.dialogic.com
Copyright and Legal Notice
Copyright © 2013-2015 Dialogic Corporation. All Rights Reserved. You may not reproduce this document in whole or in part without permission
in writing from Dialogic Corporation at the address provided below.
All contents of this document are furnished for informational use only and are subject to change without notice and do not represent
a commitment on the part of Dialogic Corporation and its affiliates or subsidiaries (“Dialogic”). Reasonable effort is made to ensure
the accuracy of the information contained in the document. However, Dialogic does not warrant the accuracy of this information and
cannot accept responsibility for errors, inaccuracies or omissions that may be contained in this document.
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH DIALOGIC® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY
ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN A SIGNED
AGREEMENT BETWEEN YOU AND DIALOGIC, DIALOGIC ASSUMES NO LIABILITY WHATSOEVER, AND DIALOGIC DISCLAIMS ANY EXPRESS OR
IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF DIALOGIC PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS
FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHT OF A THIRD PARTY.
Dialogic products are not intended for use in certain safety-affecting situations. Please see http://www.dialogic.com/company/terms-of-
use.aspx for more details.
Due to differing national regulations and approval requirements, certain Dialogic products may be suitable for use only in specific countries,
and thus may not function properly in other countries. You are responsible for ensuring that your use of such products occurs only in the
countries where such use is suitable. For information on specific products, contact Dialogic Corporation at the address indicated below or on
the web at www.dialogic.com.
It is possible that the use or implementation of any one of the concepts, applications, or ideas described in this document, in marketing
collateral produced by or on web pages maintained by Dialogic may infringe one or more patents or other intellectual property rights owned by
third parties. Dialogic does not provide any intellectual property licenses with the sale of Dialogic products other than a license to use such
product in accordance with intellectual property owned or validly licensed by Dialogic and no such licenses are provided except pursuant to a
signed agreement with Dialogic. More detailed information about such intellectual property is available from Dialogic’s legal department at
6700 de la Cote-de-Liesse Road, Suite 100, Borough of Saint-Laurent, Montreal, Quebec, Canada H4T 2B5. Dialogic encourages all users of its
products to procure all necessary intellectual property licenses required to implement any concepts or applications and does not condone or
encourage any intellectual property infringement and disclaims any responsibility related thereto. These intellectual property licenses may
differ from country to country and it is the responsibility of those who develop the concepts or applications to be aware of and comply with
different national license requirements.
Dialogic, Dialogic Pro, Dialogic Blue, Veraz, Brooktrout, Diva, BorderNet, PowerMedia, ControlSwitch, I-Gate, Network Fuel, Mobile Experience
Matters, Video is the New Voice, Making Innovation Thrive, Diastar, Cantata, TruFax, SwitchKit, Eiconcard, NMS Communications, SIPcontrol,
Exnet, EXS, Vision, inCloud9, NaturalAccess and Shiva, among others as well as related logos, are either registered trademarks or trademarks of
Dialogic Corporation and its affiliates or subsidiaries. Dialogic's trademarks may be used publicly only with permission from Dialogic. Such
permission may only be granted by Dialogic’s legal department at 6700 de la Cote-de-Liesse Road, Suite 100, Borough of Saint-Laurent,
Montreal, Quebec, Canada H4T 2B5. Any authorized use of Dialogic's trademarks will be subject to full respect of the trademark guidelines
published by Dialogic from time to time and any use of Dialogic’s trademarks requires proper acknowledgement.
The names of actual companies and products mentioned herein are the trademarks of their respective owners.
This document discusses one or more open source products, systems and/or releases. Dialogic is not responsible for your decision to use open
source in connection with Dialogic products (including without limitation those referred to herein), nor is Dialogic responsible for any present
or future effects such usage might have, including without limitation effects on your products, your business, or your intellectual property
rights..
Document History
Revision#
Version Date
Comments
1
Feb. 2013
Updated for Release 5.9.1
2
July 2015
Updated for Release 5.10.2.
Uticom related topics are removed.
Refer to www.dialogic.com for product updates and for information about support policies, warranty
information, and service offerings.
ControlSwitch (v.5.10.2) Maintenance Guide
Dialogic Inc. Proprietary Page 3
Table of Contents
PREFACE ........................................................................................................................................................ 6 1.
1.1 Audience ...................................................................................................................................................... 6
1.2 Assumptions ................................................................................................................................................ 6
1.3 Abbreviations ............................................................................................................................................... 6
1.4 References ................................................................................................................................................... 7
1.5 Contact Us ................................................................................................................................................... 7
DIGIT ANALYSIS QUICK REFERENCE ............................................................................................................... 8 2.
2.1 Creating a New Digit Analysis Template ...................................................................................................... 8
2.2 Modifying an Existing Digit Analysis Template ............................................................................................ 9
2.3 Creating an Incoming/Outgoing Digit Rule ................................................................................................ 10
2.4 Modifying an Incoming/Outgoing Digit Rule ............................................................................................. 10
2.5 Composite Template Creation ................................................................................................................... 11
2.6 Applying Digit Rules in Routing .................................................................................................................. 11
2.7 Script Summary.......................................................................................................................................... 11
DA AND DC RULES ....................................................................................................................................... 12 3.
3.1 Overview .................................................................................................................................................... 12
3.2 Template and Rule Differences ................................................................................................................. 12
3.3 Digit Rule Script Format ............................................................................................................................. 12
XML Tags ............................................................................................................................................... 13 3.3.1
XML Elements ........................................................................................................................................ 13 3.3.2
XML Attributes ...................................................................................................................................... 13 3.3.3
3.4 Script Usage ............................................................................................................................................... 14
3.5 Trouble Shooting Hints .............................................................................................................................. 14
3.6 Supported DA/Message Transformation Parameters ............................................................................... 15
ISUP ....................................................................................................................................................... 15 3.6.1
3.6.1.2 Message Transformation .................................................................................................................. 16
PRI ......................................................................................................................................................... 17 3.6.2
CAS Protocols (R1, R1.5, R2) .................................................................................................................. 19 3.6.3
SIP .......................................................................................................................................................... 19 3.6.4
H.323 ..................................................................................................................................................... 20 3.6.5
SIP-I........................................................................................................................................................ 20 3.6.6
Service Node ......................................................................................................................................... 21 3.6.7
BACKING UP THE SYSTEM ........................................................................................................................... 22 4.
4.1 Backing up Databases ................................................................................................................................ 22
4.2 CDR Files Cleaning and Back up ................................................................................................................. 22
Backing up and Deleting CDR Files Manually ........................................................................................ 22
4.2.1
Re-transferring BAF CDR Files ............................................................................................................... 23 4.2.2
Backing up and Deleting BAF CDR Files ................................................................................................. 24 4.2.3
4.3 Backup and Recovery................................................................................................................................. 24
ControlSwitch (v.5.10.2) Maintenance Guide
Dialogic Inc. Proprietary Page 4
Menu Structures .................................................................................................................................... 25 4.3.1
4.4 Database Backup ....................................................................................................................................... 26
Edit backup configuration parameters .................................................................................................. 26 4.4.1
Schedule database backup .................................................................................................................... 28 4.4.2
Hot Backup ............................................................................................................................................ 29 4.4.3
Cold Backup ........................................................................................................................................... 30 4.4.4
RMAN Backup ........................................................................................................................................ 32 4.4.5
Archive Logs Only Backup ..................................................................................................................... 34 4.4.6
Database Recovery ................................................................................................................................ 35 4.4.7
Recover Database from Backup ............................................................................................................ 36 4.4.8
Instance Maintenance ........................................................................................................................... 39 4.4.9
Restore Database from Cold Backup ................................................................................................ 41 4.4.10
4.5 Parameter List............................................................................................................................................ 44
Common Section ................................................................................................................................... 44 4.5.1
ArchiveLog Backup Section ................................................................................................................... 45 4.5.2
Cold Backup Section .............................................................................................................................. 45 4.5.3
Hot Backup Section ............................................................................................................................... 46 4.5.4
RMAN Backup Section ........................................................................................................................... 46 4.5.5
4.6 Alarm Report ............................................................................................................................................. 47
4.7 Traffic Report ............................................................................................................................................. 48
TEMPLATES FOR DIGIT ANALYSIS ................................................................................................................ 51 5.
ELEMENT ATTRIBUTES AND ATTRIBUTE VALUES ......................................................................................... 55 6.
XML ELEMENTS FOR DIGIT RULE SCRIPTS .................................................................................................... 64 7.
XML ATTRIBUTES FOR DIGIT RULE SCRIPTS ................................................................................................. 86 8.
EXAMPLES ................................................................................................................................................. 116 9.
9.1 Example 1 - Digit Analysis Rule for ISUP Calls .......................................................................................... 116
9.2 Example 2 - Digit Analysis Rule ................................................................................................................ 118
9.3 Example 3 - Digit Analysis Rule for PRI Calls ............................................................................................ 118
9.4 Example 4 - Digit Collection Rule ............................................................................................................. 121
9.5 Example 5 - Digit Analysis DTD File .......................................................................................................... 125
9.6 Example 6 - Digit Collection DTD File ....................................................................................................... 133
9.7 Example 7 - isup-egress-1.xml ................................................................................................................. 135
9.8 Example 8 - isup-ingress-1.xml ................................................................................................................ 136
9.9 Example 9 - pri-egress-1.xml ................................................................................................................... 138
9.10 Example 10 - pri-ingress-1.xml ................................................................................................................ 138
9.11 Example 11 - nanp-casfgd-incoming.xml ................................................................................................. 140
9.12 Example 12 - nanp-casfgd-outgoing.xml ................................................................................................. 145
Country Codes ................................................................................................................................. 146 9.12.1
World Zone 1 Npa ........................................................................................................................... 148
9.12.2
9.13 Example 13 Digit Analysis Language Specification .................................................................................. 148
9.14 Example 14 Digit Collection Language Specification ............................................................................... 157
TABLES .................................................................................................................................................. 160 10.
ControlSwitch (v.5.10.2) Maintenance Guide
Dialogic Inc. Proprietary Page 5
MANAGING TEMPLATES ....................................................................................................................... 165 11.
DA LOCALIZATION ................................................................................................................................. 166 12.
12.1 Overview .................................................................................................................................................. 166
12.2 Syntax ...................................................................................................................................................... 166
12.3 Constraints ............................................................................................................................................... 166
ControlSwitch (v.5.10.2) Maintenance Guide
Dialogic Inc. Proprietary Page 6
Preface 1.
The ControlSwitch System Maintenance Guide provides the following information:
Detailed instructions for the periodic maintenance activities, such as back-up and initial setup
modifications.
Descriptions and reference information for XML attributes and parameters.
Detailed instructions on creating digit rules and managing the digit rule templates.
For system maintenance also refer to Daily, Hourly, and Resfreshing reports. For deyails on theses
reports refer to ControlSwtich Management Tools Users Manual, Standard Reports.
1.1 Audience
This guide is written for system administrators, engineers, and operators who operate the CS, and l
create digit rules and digit analysis.
1.2 Assumptions
Users who maintain the ControlSwitch should be familiar with the following tasks:
Running web servers, telecommunications networks, and monitoring equipment
Configuring NT and Sun Solaris platforms
Using Extensible Markup Language (XML), and Oracle Database
1.3 Abbreviations
For the purposes of this document the following abbreviations apply:
Term
Abbreviation
DA
Digit Analysis
DC
Digit Collection
LATA
Local Access Transport Area (LATA)
Table: Abbreviations
ControlSwitch (v.5.10.2) Maintenance Guide
Dialogic Inc. Proprietary Page 7
1.4 References
1. ControlSwitch Elements and Resources User's Manual
2. ControlSwitch CDR Guide
3. ControlSwitch Business Services and Advanced Routing User's Guide
4. ControlSwtich Management Tools Users Manual
1.5 Contact Us
You can contact us for more information and assistance at:
Telephone:
Sales:
Technical Support:
ControlSwitch (v.5.10.2) Maintenance Guide
Dialogic Inc. Proprietary Page 8
Digit Analysis Quick Reference 2.
This section describes how to create and edit digit templates and rules for call routing. For Digit Rules,
also refer to ControlSwitch Business and Advanced Routing Services User's Manual, section Digit Rules.
2.1 Creating a New Digit Analysis Template
Use the following instructions to create new digit rules Templates:
5. Contact your switch engineer or network manager to obtain the incoming and the outgoing call
type information, such as digit formats and call types.
6. Record the required information for your network in the left half of Table 1 for incoming rules and
in the right half of Table 2 for outgoing rules. Use separate copies of each table for different
protocols (ISUP or PRI), trunk types (international, national or subscriber), and numbering plans
(NANP or UK). Make these distinctions if they are relevant to your network. Each trunk group may
use different digit rule types. See Examples section for examples of trunk group rules.
Your Requirements (Before Digit Analysis)
Dialogic Internal Format (After Digit Analysis)
ISUP National Incoming
ISUP National Incoming
Numbering Plan
Indicator
Called Number
NOA
Input
Format
RDE Form at
Type
Numbering
Plan Indicator
Called Number
NOA
Output
Format
Table 1: Sample Incoming Template Table
Dialogic Internal Format (Before Digit Analysis)
Your Requirements (After Digit Analysis)
ISUP National Outgoing
ISUP National Outgoing
RDE Form
at Type
Numbering
Plan Indicator
Called Number
NOA
Input
Format
Numbering
Plan Indicator
Called Number
NOA
Output
Format
Table 2: Sample Outgoing Template Table
7. Compare your call type requirements to the call types supported by existing templates.
If all of your calls types are supported by one of the existing templates then make a copy of the
existing template, edit the parameters to suit the new template, and save.
If any of your call types are not supported by the templates, then go to step 4.
8. Record the Rules to be used for each trunk group in Table 3. Samples are listed in Table 4.
Trunk Group Name
Incoming Rule Name
Outgoing Rule Name
Table 3: Your Rules for Trunk Groups
ControlSwitch (v.5.10.2) Maintenance Guide
Dialogic Inc. Proprietary Page 9
Trunk Group Name
Incoming Rule Name
Outgoing Rule Name
trunkgroup1
nanp-isup-incoming-408
nanp-isup-outgoing
trunkgroup2
uk-isum-national-incoming
uk-isup-national-outgoing
Table 4: Sample Rules for Trunk Groups
9. Open a terminal session to the EMS platform.
Note:
Alternatively, telnet or ssh commands may be used in this step, as appropriate for the security of your network
environment.
> tip hardwire
10. Log in to the EMS as the ics user.
hostname console login: ics
11. Enter the ics user password.
Password:
12. Change to the version-4 directory.
{ics} % cd version-4
13. Open the desired digit rule file with a command line text editor, such as vi. For example, to open a
digit rule file named digitrule.xml, type the following:
{ics} % vi digitrule.xml
14. Type the desired XML statements.
15. Save and close the file.
16. Type the parserule command, to verify the syntax and compile the rule. If the syntax is correct,
then the parserule script will generate two files, one with the .rule extension, and the other
with the .info extension. If the compile is successful, the rule will be written to the EMS
database.
{ics} % parserule digitrule
17. Exit the ics account.
{ics} % exit
18. Use the EMS GUI to assign digit rules to channel groups or subscribers. The following three types of
rules must be assigned:
incoming digit analysis rule
outgoing digit analysis rule
digit collection rule
2.2 Modifying an Existing Digit Analysis Template
Use the following instructions to modify an existing digit rules Template:
1. Open a terminal session to the EMS platform.
Note:
Alternatively, telnet or ssh commands may be used in this step, as appropriate for the security of your network
environment.
ControlSwitch (v.5.10.2) Maintenance Guide
Dialogic Inc. Proprietary Page 10
> tip hardwire
2. Log in to the EMS as the ics user.
hostname console login: ics
3. Enter the ics user password.
Password:
4. Change to the version-4 directory.
{ics} % cd version-4
5. Open the desired digit rule file with a command line text editor, such as vi. For example, to open a
digit rule file named digitrule.xml, type the following:
{ics} % vi digitrule.xml
6. Edit the desired XML statements.
7. Save and close the file.
8. Type the parserule command, to verify the syntax and compile the rule. If the syntax is correct,
then the parserule script will generate two files, one with the .rule extension, and the other
with the .info extension. If the compile is successful, the rule will be written to the EMS
database.
{ics} % parserule digitrule
9. Exit the ics account.
{ics} % exit
10. Use the EMS GUI to assign digit rules to channel groups or subscribers. The following three types of
rules must be assigned:
incoming digit analysis rule
outgoing digit analysis rule
digit collection rule
2.3 Creating an Incoming/Outgoing Digit Rule
Create a Digit Analysis/Digit Collection Rule for a selected incoming or outgoing trunk group that
requires digit rule.
See ControlSwitch Elements and Resources User's Manual, section Creating a Digit Rule.
Note:
Digit Collection rule is not applied to an ISUP trunk group.
2.4 Modifying an Incoming/Outgoing Digit Rule
Create a Digit Analysis/Digit Collection Rule for a selected incoming or outgoing trunk group that
requires digit rule.
See ControlSwitch Elements and Resources User's Manual, section Modifying Digit Rule Parameters.
Note:
Digit Collection rule is not applied to an ISUP trunk group.
ControlSwitch (v.5.10.2) Maintenance Guide
Dialogic Inc. Proprietary Page 11
2.5 Composite Template Creation
The Template Manager in the EMS GUI allows you to construct composite templates that can be used
by a rule assigned to the network element. A composite template is a named list of templates in the
desired order that can be assigned to multiple network elements. A Rule could reference either a
Composite or a non-composite (base) template.
The Template Manager allows the user to create composite templates in the desired order that is
available for use during Rule creation.
A non-composite template may or may not have parameters and there is no provision in the GUI to
introduce new rule parameters. Parameter values entered by the user in the GUI are the actual
Parameter arguments used in the rule's template calls. The user can specify / modify Parameter values.
The rule needs to be created only once no matter how many elements share the assignment. If a similar
rule already exists, a warning message prompts the user that the existing rule will be assigned to the
element.
To create a composite template, Refer to ControlSwitch Business and Advanced Routing Services User's
Manual, section Creating a Composite Template (use the View XML tab to display the template's
content).
2.6 Applying Digit Rules in Routing
A digit rule is applied after all digits have been collected. See the Modify Treatment Parameters section
in ControlSwitch Policies and Routing User's Manual. Select Route as a treatment type. Click on the
Egress Properties tab and select the preconfigured Digit Analysis Rule/Digit Collection Rule.
Note:
This operation overrides digit rule set in trunk group window.
2.7 Script Summary
The following table describes the actions completed by each script used in this chapter.
Script
Completes the Following Operations
parserule
Verifies the syntax of a digit rule file.
Compiles the rule.
Creates a filename.rule file.
Creates a filename.info file.
Calls the tmplmgr script and executes it on the newly created file. If the -w option has
been used, then this action is not completed.
gencw
Generates a new rule to select CODEC using a input data file.
Calls the parserule script and executes it on the newly created file.
Calls the tmplmgr script and executes it on the newly created file. If the -w option has
been used, then this action is not completed.
ControlSwitch (v.5.10.2) Maintenance Guide
Dialogic Inc. Proprietary Page 12
DA and DC Rules 3.
This chapter describes additional information on Digit Analysis (DA) and Digit Collection (DC) rules.
3.1 Overview
Digit rules are primarily used to translate the telephone number of a call that is received by the CS. The
telephone number is translated into an internal Dialogic canonical format (E.164 format). Using digit
rules, any received format can be translated and the call type identified for enforcing call routing
policies. The number received can also be translated into any other internal representation, not only the
Dialogic canonical format.
Digit rules can modify many more call parameters than the telephone number. There are two types of
digit rules, digit analysis rules and digit collection rules. In this document, “digit rule” refers to both digit
analysis rules and digit collection rules. Digit collection rules are used to determine when a telephone
number is complete. Digit analysis rules are used to:
Verify the phone numbers of an incoming call request
Put phone numbers in a form acceptable to the RE
Separate phone number attributes such as carrier codes
Put outgoing phone numbers in a form required by the entity receiving the call
Define trunk group properties that are not built-in to the EMS GUI
3.2 Template and Rule Differences
Digit templates are created in XML and stored on the EMS. The user can then assign digit rules by using
the EMS GUI. The following types of digit rules can be used:
Templates are either included in the CS software, (for example nanp-pri-incoming or uk-isup-
national-outgoing) or are created by the user. The templates are managed by the tmplmgr
program.
Rules pass specific parameters to an existing template, executed with the designated parameters.
Rules are created in the EMS GUI.
A rule can be assigned to a trunk group but the templates cannot. A rule is generated for an installed
template, and calls the template with no parameters, taking that name of the template followed by the
suffix -rule”.
The Templates for Digit Analysis section lists this release's templates, which are automatically entered
into the EMS database upon installation.
3.3 Digit Rule Script Format
A digit rule script is a text file that uses a subset of the Extended Markup Language (XML) to structure
file content. The syntax for an XML file is described in a Document Type Definition (DTD) file.
ControlSwitch (v.5.10.2) Maintenance Guide
Dialogic Inc. Proprietary Page 13
XML Tags 3.3.1
A digit rule script starts with two tags that specify the XML version and the DTD file to be used for syntax
analysis. In the following example, the XML version is 1.0 and the DTD file name is digitanalysis.dtd:
<?xml version="1.0" ?>
<!DOCTYPE digit-rule SYSTEM "digitanalysis.dtd">
Only tags are used in digit rule scripts. No information exists outside of the tags. Tags are delineated
with angle brackets. There are three types of tags, a start tag, an end tag, and a start-end tag. The start-
end tag is a start tag combined with an end tag. All tags contain a digit rule XML element name. The
three tag types are distinguished by the placement of the forward slash character. The end tag has a
forward slash immediately after the opening angle bracket and before the digit rule XML element name.
The start-end tag has a forward slash just before the closing angle bracket. The start tag has no slash
characters outside of the attribute values. Each start tag has a corresponding end tag. In the following
example, the sample xml-element-name1 element includes a start tag and an end tag. The sample xml-
element-name2 element consists of only a start-end tag.
<xml-element-name1 attribute-name1="value" attribute-name2="value">
<xml-element-name2 attribute-name3="value"/>
</xml-element-name1>
XML Elements 3.3.2
XML elements are used to represent the statements and declarations of the digit rule language.
Detailed descriptions of digit rule XML elements are provided in XML Elements for Digit Rule Scripts.
XML Attributes 3.3.3
Attributes are the options or parameters of an XML element. An attribute may be used in more than
one element; however it has the same general meaning in all elements where it used. Start and start-
end tags may have attributes. Attributes follow the element name and consist of an attribute name
followed by an equal sign followed by an attribute value enclosed in quotes. Attributes may be optional
as specified in the DTD file. There are three attribute value types, String Reference, Number Reference
and Context String Reference, that may refer to either call data, table data, rule variables or rule
parameters.
Table 5 provides details on these attributes. The first column shows all possible initial text for these
attribute values. The next column shows the text after the initial text. The last three columns show
which attribute value text are allowed in each attribute value type.
Detailed descriptions of digit rule XML attributes are provided in XML Attributes or Digit Rule Scripts.
Initial Text
Text after Colon
String Ref.
Number
Ref.
Context
String Ref.
parameter:
A parameter name defined in the “parameter” element.
X
X
X
variable:
A variable name defined in the “variable” element.
X
X
X
string:
Any text.
X
X
data:
A context name.
X
X
byte:
A string represented by the two digit hexadecimal ACSII
value of each character.
X
X
table:
A table name defined in the “table” element. A colon and
a column name optionally follow the table name. If no
X
X
X
ControlSwitch (v.5.10.2) Maintenance Guide
Dialogic Inc. Proprietary Page 14
column name is given, it refers to the first column in the
table.
<context
name>:
Nothing.
X
X
Value
without colon
Nothing.
string
number
context
name
Table 5: Attribute Value Summery
3.4 Script Usage
The script generated, CodecCheck-dn.xml for example is in an incoming digit analysis script. It is must be
called from all the normal incoming digit analysis scripts, such as nanp-isup-incoming, to get the effect
of both scripts. This accomplished by including the following statement in the incoming script.
<call-rule rule-reference=”CodecCheck-dn”/>
It should be called at the end of the main rule, just before any procedure definitions. Hence it is only
called if the call numbers are valid and have been converted to E.164 format. It could instead be called
from another script that calls it and the standard incoming script.
For example,
<?xml version=”1.0”?>
<!DOCTYPE digit-rule SYSTEM “digitanalysis.dtd”>
<digit-rule rule-name=”cw-isup-incoming-408”>
<call-rule rule-reference=”nanp-isup-incoming”>
<argument argument-value=”408”/>
</call-rule>\
<call-rule rule-reference=”CodecCheck-dn”/>
</digit-rule>
The order of the rule calls is important. The first rule puts the calling and dialed numbers into E.164
format.
3.5 Trouble Shooting Hints
Codec selection DA rule is applied only in ingress selection. It can be applied on both Trunk Group
and VCE ingress DA rule selection.
Why does the call get rejected with ServiceOptionNotImplementedOrSupported even though call
tracing shows that the codec is selected by above DA rules?
Make sure that the egress trunk group has the codec selected by DA as one of the allowed codecs.
How can I use my existing DA rules in conjunction with Codec selection DA rules?
The existing DA rule should refer to the rule generated by the codec selection DA rule. See THE
example in Script Usage.
ControlSwitch (v.5.10.2) Maintenance Guide
Dialogic Inc. Proprietary Page 15
3.6 Supported DA/Message Transformation Parameters
ISUP 3.6.1
3.6.1.1 Digit Analysis
Digit rule is applicable to only setup messages.
Ingress DA is invoked for incoming IAM (network to CS).
Egress DA is invoked for outgoing IAM (CS to network).
Ingress Digit Analysis
Egress Digit Analysis
Calling Party Number
Charge Number
Called Party Number
Generic Address Parameter
Calling Party Category
Forward Call Indicator
Original Called Number
Presentation Number
Redirecting Number
Jurisdiction Parameter
Nature Of Connection
Original Line Info
Transmission Med Req
Transmission Med Prime
Transit Network Selection
Cause Value
Redirection Info
IRI
ORI
Generic Data
User Service Info
Access Transport
User Service Info Prime
Additional Calling Party Number
Carrier Code
Protocol
Type Of Call
Vpn Id Info
Internal Cause Code
Carrier Selection Info
Trunk Group Number
Partition Number
C U G Supported For Service Reference
Calling Party Number
Charge Number
Called Party Number
Generic Address Parameter
Calling Party Number
Charge Number
Called Party Number
Generic Address Parameter
Network Routing Number
Directory Number
Calling Party Category
Carrier Code
Forward Call Indicator
Original Called Number
Presentation Number
Redirecting Number
Jurisdiction Parameter
Nature Of Connection
Original Line Info
Transit Network Selection
Cause Value
Redirection Info
IRI
ORI
User Service Info Prime
Transmission Med Req
Transmission Med Prime
Additional Calling Party Number
Called IN Number
Generic Data
User Service Info
Access Transport
Bearer Capability
ControlSwitch (v.5.10.2) Maintenance Guide
Dialogic Inc. Proprietary Page 16
Charge Service Reference
Bearer Capability
Bearer Capability Prime
Exchange Type
Bearer Capability Prime
Protocol
Type Of Call
Internal Cause Code
Carrier Selection Info
Remote Protocol
Trunk Group Number
Partition Number
Charge Service Reference
C U G Supported For Service Reference
Exchange Type
Table 6: ISUP Ingress and Egress Digit Analysis
3.6.1.2 Message Transformation
Message Transformation is applicable to all the messages.
Ingress MTR is invoked for all incoming messages (network to CS).
Egress MTR is invoked for all outgoing messages (CS to network).
Message
Incoming DA Parameters
Outgoing DA Parameters
IAM
Generic Data
Cause Value
Access Transport
Non Ported Gaps
Additional Calling Party Number
Parameter Compatibility Array
Non Ported Gaps
Additional Calling Party Number
Generic Data
Cause Value
Access Transport
Parameter Compatibility Array
ACM
Generic Data
Cause Value
Access Transport
Parameter Compatibility Array
Connected Number
Notification Indicator
Opt Backward Call Indicator
Generic Data
Cause Value
Access Transport
Parameter Compatibility Array
Connected Number
Notification Indicator
Opt Backward Call Indicator
ANM
Generic Data
Access Transport
Parameter Compatibility Array
Connected Number
Notification Indicator
Additional Connected Number
Opt Backward Call Indicator
Additional Connected Number
Generic Data
Access Transport
Parameter Compatibility Array
Connected Number
Notification Indicator
Opt Backward Call Indicator
GENERIC
Generic Data
Parameter Compatibility Array
Generic Data
Parameter Compatibility Array
CPG
Event Indicator
Event Indicator
ControlSwitch (v.5.10.2) Maintenance Guide
Dialogic Inc. Proprietary Page 17
Progress Indicator
Generic Data
Cause Value
Access Transport
Parameter Compatibility Array
Notification Indicator
Opt Backward Call Indicator
Progress Indicator
Generic Data
Cause Value
Access Transport
Parameter Compatibility Array
Notification Indicator
Opt Backward Call Indicator
REL
Generic Data
Cause Value
Parameter Compatibility Array
Notification Indicator
Access Transport
Generic Data
Cause Value
Access Transport
Parameter Compatibility Array
Notification Indicator
RLC
--NA--
Generic Data
Cause Value
Parameter Compatibility Array
Table 7: Incoming and Outgoing DA Parameters
3.6.1.3 Digit Collection
Digit Collection is applicable for ETSI ISUP and its variants. The rule works based on Called Party Number
and waits for additional digits to be collected.
PRI 3.6.2
3.6.2.1 Digit Analysis
PRI DA is applicable to all messages.
Ingress DA is invoked for message related to ingress half leg of call
Egress DA rules is applicable to egress half leg of call.
Message
Incoming DA Parameters
Outgoing DA Parameters
SETUP
Calling Party Number
Charge Number
Called Party Number
Bearer Capability
Calling Party Cat
Forward Call Indicator
Redirecting Number
Cause Value
Redirection Info
Original Called Number
Generic Message Data
Access Transport
Call Type
Carrier Code
Calling Party Number
Charge Number
Called Party Number
Bearer Capability
Calling Party Cat
Forward Call Indicator
Redirecting Number
Cause Value
Redirection Info
Original Called Number
Generic Message Data
Access Transport
Call Type
Carrier Code
ControlSwitch (v.5.10.2) Maintenance Guide
Dialogic Inc. Proprietary Page 18
Internal Cause Code
Signaling Protocol
Vpn Id Info
Trunk Group Number
Partition Number
Type Of Call
Remote Protocol
Connected Number
Progress Indicator
Backward Call Indicators
Opt Backward Call Indicators
Event Indicator
OLI
Notification Indicator
Internal Cause Code
Signaling Protocol
Vpn Id Info
Trunk Group Number
Partition Number
Type Of Call
Remote Protocol
Connected Number
Progress Indicator
Backward Call Indicators
Opt Backward Call Indicators
Event Indicator
OLI
Notification Indicator
ALERTING
Backward Call Indicators
Optional Backward Call Indicators
Cause Value
Progress Indicator
Connected Number
Notification Indicators
Access Transport (raw bytes only)
Progress Indicator
Notification Indicator
Access Transport (raw bytes only)
PROGRESS
Backward Call Indicators
Optional Backward Call Indicators
Cause Value
Progress Indicator
Notification Indicators
Event Indicator
Access Transport (raw bytes only)
Cause Value
Progress Indicator
Notification Indicators
Access Transport (raw bytes only)
CONNECT
Backward Call Indicators
Optional Backward Call Indicators
Connected Number
Notification Indicators
Access Transport (raw bytes only)
Connected Number
Progress Indicator
Notification Indicators
Access Transport (raw bytes only)
DISCONNECT
Cause Value
Notification Indicators
Access Transport (raw bytes only)
Cause Value
Progress Indicator
Notification Indicators
Access Transport (raw bytes only)
RELEASE
Cause Value
Notification Indicators
Access Transport (raw bytes only)
Cause Value
Notification Indicators
Access Transport (raw bytes only)
Table 8: PRI Incoming and Outgoing DA Parameters
ControlSwitch (v.5.10.2) Maintenance Guide
Dialogic Inc. Proprietary Page 19
3.6.2.2 Digit Collection
Digit Collection is applicable for ETSI PRI. The rule works based on Called Party Number and waits for
additional digits to be collected.
CAS Protocols (R1, R1.5, R2) 3.6.3
3.6.3.1 Digit Analysis
Digit rule is applicable to only setup messages.
Ingress DA is invoked for incoming Setup (network to CS)
Egress DA is invoked for outgoing Setup. (CS to network)
CAS incoming and outgoing DA parameters are as following:
Calling Party Info
Charge Number
Called Party Info
Feature Id Info
Bearer Capability
Bearer Capability Prime
Call Type
Calling Party Category
Carrier Code
Caller Preferred Carrier Local
Caller Preferred Carrier Intra LATA
Caller Preferred Carrier Inter LATA
Caller Preferred Carrier International
Forward Call Indicator
Original Called Party Number
Presentation Number
Redirecting Number
Jurisdiction Parameter
Caller LATA Info
Nature of Connection
Original Line Info
Signaling Protocol
Transit Network Selection
Treatment Type
Type of Call
Cause Value
Internal Cause Code
Redirection Information
Trunk Group Number
Vpn Id Info
Partition Number*
CAS Information Parameters*
zz Code**
Country Address Type**
Country Code**
Cas Digit Analysis State**
* Not in CAS-FGD
** Only in CAS-FGD
3.6.3.2 Digit Collection
The rule works based on Called Party Number and waits for additional digits to be collected.
SIP 3.6.4
Note:
Only DA is supported.
3.6.4.1 Digit Analysis
Digit rule is applicable only for setup messages.
Ingress DA is invoked for incoming Setup (network to CS)
Egress DA is invoked for outgoing Setup (CS to network)
SIP incoming and outgoing DA parameters are as following:
Calling Party Number
Charge Number
Trunk Group Number
Carrier Code
Transmission Medium Request
User Service Info
ControlSwitch (v.5.10.2) Maintenance Guide
Dialogic Inc. Proprietary Page 20
Called Party Number
Bearer Capability
Calling Party Category
Forward Call Indicator
Original Called Party Number
Cause Value
Internal Cause Code
Gateway IP Address
Partition Number
Signaling Protocol
Generic Address Parameter
Transit Network Selection
Original Line Info
Access Transport
Bearer Capability Prime
Jurisdiction Param
User Service Info Prime
Nature of Connection
Directory Number
Network Routing Number
Generic Message Data
Additional Calling Number
H.323 3.6.5
Note:
Only DA is supported.
3.6.5.1 Digit Analysis
Digit rule is applicable only for setup messages.
Ingress DA is invoked for incoming Setup (network to CS)
Egress DA is invoked for outgoing Setup (CS to network)
H.323 incoming and outgoing DA parameters are as following:
Calling Party Number
Charge Number
Called Party Number
Bearer Capability
Calling Party Category
Forward Call Indicator
Original Called Party Number
Cause Value
Internal Cause Code
Gateway IP Address
Trunk Group Number
Carrier Code
Partition Number
Signaling Protocol
Generic Address Parameter
Transit Network Selection
Original Line Info
User Service Info
SIP-I 3.6.6
Note:
Only DA is supported.
3.6.6.1 Digit Analysis
Digit rule is applicable to all only setup messages.
Ingress DA is invoked for incoming Setup. (network to CS)
Egress DA is invoked for outgoing Setup. (CS to network)
SIP-I incoming and outgoing DA parameters are as following:
Calling Party Number
Charge Number
Called Party Number
Bearer Capability
Calling Party Category
Trunk Group Number
Carrier Code
Partition Number
Signaling Protocol
Generic Address Parameter
Transmission Medium Request
User Service Info
User Service Info Prime
Nature of Connection
Directory Number
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24
  • Page 25 25
  • Page 26 26
  • Page 27 27
  • Page 28 28
  • Page 29 29
  • Page 30 30
  • Page 31 31
  • Page 32 32
  • Page 33 33
  • Page 34 34
  • Page 35 35
  • Page 36 36
  • Page 37 37
  • Page 38 38
  • Page 39 39
  • Page 40 40
  • Page 41 41
  • Page 42 42
  • Page 43 43
  • Page 44 44
  • Page 45 45
  • Page 46 46
  • Page 47 47
  • Page 48 48
  • Page 49 49
  • Page 50 50
  • Page 51 51
  • Page 52 52
  • Page 53 53
  • Page 54 54
  • Page 55 55
  • Page 56 56
  • Page 57 57
  • Page 58 58
  • Page 59 59
  • Page 60 60
  • Page 61 61
  • Page 62 62
  • Page 63 63
  • Page 64 64
  • Page 65 65
  • Page 66 66
  • Page 67 67
  • Page 68 68
  • Page 69 69
  • Page 70 70
  • Page 71 71
  • Page 72 72
  • Page 73 73
  • Page 74 74
  • Page 75 75
  • Page 76 76
  • Page 77 77
  • Page 78 78
  • Page 79 79
  • Page 80 80
  • Page 81 81
  • Page 82 82
  • Page 83 83
  • Page 84 84
  • Page 85 85
  • Page 86 86
  • Page 87 87
  • Page 88 88
  • Page 89 89
  • Page 90 90
  • Page 91 91
  • Page 92 92
  • Page 93 93
  • Page 94 94
  • Page 95 95
  • Page 96 96
  • Page 97 97
  • Page 98 98
  • Page 99 99
  • Page 100 100
  • Page 101 101
  • Page 102 102
  • Page 103 103
  • Page 104 104
  • Page 105 105
  • Page 106 106
  • Page 107 107
  • Page 108 108
  • Page 109 109
  • Page 110 110
  • Page 111 111
  • Page 112 112
  • Page 113 113
  • Page 114 114
  • Page 115 115
  • Page 116 116
  • Page 117 117
  • Page 118 118
  • Page 119 119
  • Page 120 120
  • Page 121 121
  • Page 122 122
  • Page 123 123
  • Page 124 124
  • Page 125 125
  • Page 126 126
  • Page 127 127
  • Page 128 128
  • Page 129 129
  • Page 130 130
  • Page 131 131
  • Page 132 132
  • Page 133 133
  • Page 134 134
  • Page 135 135
  • Page 136 136
  • Page 137 137
  • Page 138 138
  • Page 139 139
  • Page 140 140
  • Page 141 141
  • Page 142 142
  • Page 143 143
  • Page 144 144
  • Page 145 145
  • Page 146 146
  • Page 147 147
  • Page 148 148
  • Page 149 149
  • Page 150 150
  • Page 151 151
  • Page 152 152
  • Page 153 153
  • Page 154 154
  • Page 155 155
  • Page 156 156
  • Page 157 157
  • Page 158 158
  • Page 159 159
  • Page 160 160
  • Page 161 161
  • Page 162 162
  • Page 163 163
  • Page 164 164
  • Page 165 165
  • Page 166 166

Dialogic ControlSwitch Maintenance Guide

Type
Maintenance Guide

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI