Cisco PXM Version 1.1 User manual

Corporate Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: [phone]
800 553-NETS (6387)
Fax: [phone]
Cisco Carrier Sensitive Routing User Guide
Version 1.1

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED ORIMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco Carrier Sensitive Routing User Guide
Copyright © 2002, Cisco Systems, Inc.
All rights reserved.

iii
Cisco Carrier Sensitive Routing User Guide
CONTENTS
Preface vii
Overview vii
Who Should Use This Guide vii
Document Organization viii
Document Conventions viii
Related Documentation and References ix
Obtaining Documentation ix
World Wide Web ix
Documentation CD-ROM ix
Ordering Documentation ix
Documentation Feedback x
Obtaining Technical Assistance x
Cisco.com x
Technical Assistance Center x
Contacting TAC by Using the Cisco TAC Website xi
Contacting TAC by Telephone xi
CHAPTER 1Overview of Cisco Carrier Sensitive Routing 1-1
Prerequisites 1-1
CSR Components 1-2
CSR Basics 1-2
PostgreSQL Database 1-3
CSR Application 1-3
Ingress Rejection Rules 1-4
Egress Rejection Rules 1-4
Selection Rules 1-4
CSR GUI 1-4
CSR Limitations 1-5
CHAPTER 2PostgreSQL Database Operations and Functionalities 2-1
Database Operations 2-1
Activating the Database 2-1
Exiting the Database 2-2
Reactivating the Database 2-2

Contents
iv
Cisco Carrier Sensitive Routing User Guide
Exporting a Database 2-2
Reintializing a Database 2-3
Database Functionalities 2-3
Database Tables 2-4
Configuration Tables 2-4
Dataset Tables 2-10
PostgreSQL Database Command Summary 2-17
CHAPTER 3Cisco Carrier Sensitive Routing Application Operations 3-1
Activating CSR 3-1
Single Instance 3-1
CSR as a Daemon 3-1
CSR as a User Process 3-2
Multiple Instances 3-2
Deactivating CSR 3-3
CHAPTER 4CSR GUI Functionalities 4-1
Activating the GUI 4-1
Configuring CSR with the GUI 4-2
Changing Configuration Settings 4-2
Changing Log Levels 4-3
Changing App Priority 4-4
Changing Connection Port 4-4
Enabling Test Routes Accounting 4-4
Saving Configuration Settings 4-4
Adding, Modifying, and Removing Gatekeepers 4-5
Adding Gatekeepers 4-5
Modifying Gatekeepers 4-9
Removing Gatekeepers 4-10
Setting Threads for Processing Calls and Call Queue Size 4-11
Swapping Datasets 4-12
Updating Active Datasets 4-12
Creating, Modifying, and Deleting Carriers 4-13
Creating Carriers 4-14
Modifying Carriers 4-15
Deleting Carriers 4-16
Creating, Modifying, and Deleting Contacts 4-17
Creating Contacts 4-17
Modifying Contacts 4-18

Contents
v
Cisco Carrier Sensitive Routing User Guide
Deleting Contacts 4-18
Creating, Modifying, and Deleting Contact Lists 4-19
Creating Contact Lists 4-19
Modifying Contact Lists 4-20
Deleting Contact Lists 4-21
Creating, Modifying, and Deleting Egress Route Attributes 4-21
Creating Egress Route Attributes 4-21
Modifying Egress Route Attributes 4-23
Deleting Egress Route Attributes 4-25
Creating, Modifying, and Deleting Ingress Route Attributes 4-26
Creating Ingress Route Attributes 4-26
Modifying Ingress Route Attributes 4-28
Deleting Ingress Route Attributes 4-29
Creating, Modifying, and Deleting Match Patterns 4-30
Creating Match Patterns 4-30
Modifying Match Patterns 4-31
Deleting Match Patterns 4-31
Creating, Modifying, and Deleting Routes 4-32
Creating Routes 4-32
Modifying Routes 4-33
Deleting Routes 4-34
Creating, Modifying, and Deleting Rules 4-35
Creating Rules 4-35
Modifying Rules 4-37
Deleting Rules 4-38
Verifying Datasets 4-39
Updating Inactive Datasets 4-39
Destroying Inactive Datasets 4-40
Activating Inactive Datasets 4-41
CSR Commands 4-41
Sending Test Route Request Commands to an Active CSR Application 4-42
Updating Logging Level 4-44
Loading the Active Dataset 4-44
Resetting Call Accounting 4-45
Updating Gatekeepers 4-45
Cleaning Test Results 4-45
Checking CSR Version 4-46
Multiple GUI Operation 4-46

Contents
vi
Cisco Carrier Sensitive Routing User Guide
AP PEN DIX ALogging A-1
Configuring Syslog A-1
Examples A-2
Viewing Logs A-2
Sample logs A-3
AP PEN DIX BData Schema B-1
Configuration Data Schema B-1
Dataset Schema B-5
AP PEN DIX CError Conditions and Recoveries C-1
Database Connectivity Loss C-1
Gatekeeper Connectivity Loss C-2
GLOS SARY
IN DEX

vii
Cisco Carrier Sensitive Routing User Guide
Preface
This preface describes the objective, audience, organization, and conventions of the Cisco Carrier
Sensitive Routing User Guide.
It contains the following information:
•Overview, page-vii
•Who Should Use This Guide, page-vii
•Document Organization, page-viii
•Document Conventions, page-viii
•Related Documentation and References, page-ix
•Obtaining Documentation, page-ix
•Obtaining Technical Assistance, page-x
Overview
The CiscoCarrier Sensitive Routing User Guide provides information on operations and functionalities
of Carrier Sensitive Routing (CSR) application, its graphical user interface (GUI) and the databases
associated with it.
Who Should Use This Guide
Users of this guide should have knowledge of the following:
•UNIX operating system and commands
•SQL commands
•TCP/IP network that the CSR is connected to
•Sun/Solariscomputer system

viii
Cisco Carrier Sensitive Routing User Guide
Preface
Document Organization
Document Organization
This guide is organized as follows:
Document Conventions
Following are conventions that might be used in this document.
Chapter1, “Overview of Cisco Carrier Sensitive
Routing”Provides an overview of the postgreSQL database, CSR application, and CSR graphical
user interface (GUI).
Chapter2, “PostgreSQL Database Operations and
Functionalities”Describes the operations and functionalities of the postgreSQL database.
Chapter3, “Cisco Carrier Sensitive Routing
Application Operations”Describes the operations and functionalities of the CSR application.
Chapter4, “CSR GUI Functionalities”Describes the CSR graphical user interface
functionalities.
AppendixA, “Logging”Describes the configuration of syslog and viewing
logs.
AppendixB, “Data Schema”Describes the configuration data schema and
dataset schema.
AppendixC, “Error Conditions and Recoveries”Describes database and gatekeeper connectivity
loss.
Table1
Convention Description
boldface Commands and keywords are in bold face.
italic Arguments for which you supply values are in italic.
[] Keywords or arguments that appear within square brackets are optional.
{x|y|z}Alternative, mutually exclusive, keywords are grouped in braces and
separated by vertical bars.
^ orCtrl Represent the key labeled Control. For example, when you read^D or
Ctrl-D, you should hold down the Control key while you press the D key.
screen font Terminal sessions and information the system displays are in screen
font.
boldface screen font Information you must enter is in boldface screen font.
<> Nonprinting characters, such as passwords, appear in angled brackets.
[] Default responses to system prompts are in square brackets.

ix
Cisco Carrier Sensitive Routing User Guide
Preface Related Documentation and References
Related Documentation and References
•Carrier Sensitive Routing Installation Guide
For Sun/Solaris, Java, and postgreSQL database information, go to the following URLs:
•http://www.sun.com
•http://java.sun.com
•http://www.postgresql.org
Obtaining Documentation
These sections explain how to obtain documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at this URL:
http://www.cisco.com
Translated documentation is available at this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM
package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may
be more current than printed documentation. The CD-ROM package is available as a single unit or
through an annual subscription.
Ordering Documentation
You can order Cisco documentation in these ways:
•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from
the Networking Products MarketPlace:
http://www.cisco.com/cgi-bin/order/order_root.pl
•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription
Store:
http://www.cisco.com/go/subscription
•Nonregistered Cisco.com users can order documentation through a local account representative by
calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408526-7208 or, elsewhere
in North America, by calling 800553-NETS (6387).

x
Cisco Carrier Sensitive Routing User Guide
Preface
Obtaining Technical Assistance
DocumentationFeedback
You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click
the Fax or Email option in the “Leave Feedback” section at the bottom of the page.
You can e-mail your comments to [email protected].
You can submit your comments by mail by using the response card behind the front cover of your
document or by writing to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can
obtain online documentation, troubleshooting tips, and sample configurations from online tools by using
the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete
access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open
access to Cisco information, networking solutions, services, programs, and resources at any time, from
anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a
broad range of features and services to help you with these tasks:
•Streamline business processes and improve productivity
•Resolve technical issues with online support
•Download and test software packages
•Order Cisco learning materials and merchandise
•Register for online skill assessment, training, and certification programs
If you want to obtain customized information and service, you can self-register on Cisco.com. To access
Cisco.com, go to this URL:
http://www.cisco.com
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to all customers who need technical
assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco
TAC WebSite and the Cisco TAC Escalation Center.

xi
Cisco Carrier Sensitive Routing User Guide
Preface Obtaining Technical Assistance
Cisco TAC inquiries are categorized according to the urgency of the issue:
•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities,
product installation, or basic product configuration.
•Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably
impaired, but most business operations continue.
•Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects
of business operations. No workaround is available.
•Priority level 1 (P1)—Your production network is down, and a critical impact to business operations
will occur if service is not restored quickly. No workaround is available.
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of
service contracts, when applicable.
Cisco TAC Web Site
You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time.
The site provides around-the-clock access to online tools, knowledge bases, and software. To access the
Cisco TAC Web Site, go to this URL:
http://www.cisco.com/tac
All customers, partners, and resellers who have a valid Cisco service contract have complete access to
the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a
Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or
password, go to this URL to register:
http://www.cisco.com/register/
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco
TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC
WebSite.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level2 issues. These
classifications are assigned when severe network degradation significantly impacts business operations.
When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer
automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operationscenter to determine the level of Cisco support
services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network
Supported Accounts (NSA). When you call the center, please have available your service agreement
number and your product serial number.

xii
Cisco Carrier Sensitive Routing User Guide
Preface
Obtaining Technical Assistance

CHAPTER
1-1
Carrier Sensitive Routing User Guide
1
Overview of Cisco Carrier Sensitive Routing
The Cisco Carrier Sensitive Routing (CSR)application provides end users with the capability to
manipulate the routing of calls from the gatekeeper based on the ingress carrier and the DNIS. The
routing can be based on QoS along with many other attributes pertaining to a carrier. With CSR, you can
provision data specific to carriers that pertain to your network to maximize cost, QoS, and carrier
relations. CSR can run on a Sun/Solaris system that has a network connection to gatekeepers.
This chapter contains the following sections:
•Prerequisites, page 1-1
•CSR Components, page 1-2
•CSR Basics, page 1-2
•CSR Limitations, page 1-5
Prerequisites
•Root access to a UNIX machine for the following tasks:
– Create users
– Modify Syslog.conf
– Setting database security
•Configured Cisco gatekeeper and gateway
•Network that provides DNS capabilities
•Knowledge of the following:
– UNIX operating system and commands
– SQL commands
– TCP/IP network that the CSR is connected to
– Sun computer system

1-2
Carrier Sensitive Routing User Guide
Chapter1 Overview of Cisco Carrier Sensitive Routing
CSR Components
CSR Components
The three major components of CSR are as follows.
•postgreSQL Database
•CSR application
•CSR GUI
The CSR GUI and the CSR application are not directly connected. They are both connected to the
database. Figure1-1 illustrates these components.
Figure1-1 CSR Components
CSR Basics
This section describes the basic operation of CSR.
After CSR is started, it registers with the gatekeeper connected to a network. Any one or a combination
of the following registration messages are used:
•ARQ
•LRQ
•DRQ
•BRQ
•URQ
•RAI
•LCF
•LRJ
•IRR
The gatekeeper responds with any of the following messages:
•ANI
•DNIS
•Source carrier
•Destination carrier

1-3
Carrier Sensitive Routing User Guide
Chapter1 Overview of Cisco Carrier Sensitive Routing CSR Basics
CSR evaluates the predetermined selection and rejection criteria as part of the source carrier and DNIS
information to determine what routing information to return to the gatekeeper.
Note CSR can operate with multiple gatekeepers. CSR passes through the ANI, but its work is not based
on the ANI. If the CSR receives the destination carrier, it passes the call through with the same
information that it receives.
PostgreSQL Database
The postgreSQL database stores all the provisioned data associated with the CSR. The data can be
entered into the database by using the GUI or by importing. The database supports active dataset,
inactive dataset, and configuration data.
Information contained in the active and inactive datasets includes:
•Carrier Table—Contains a list of carriers and associated attributes.
•Contact List Table—Contains a relationship of contacts to a key.
•Contacts Table—Contains a list of RAS addresses (zones) and associated attributes.
•Egress Route Attributes Table—Contains a list of egress attributes and associated data.
•Egress Routes Table—Contains a list of egress attributes and associated routes.
•Ingress Route Attributes Table—Contains a list ingress attributes and associated data.
•Ingress Routes Table—Contains a list of ingress attributes and associated routes.
•Match Patterns Table—Contains a list of match patterns and associated routes.
•QoS Table—Contains a list of relative QoS values associated to route, ingress, and egress.
•Routes Table—Contains a list of routes and associated rules.
•Rules Table—Contains a list of rules and associated attributes (selection/rejection).
Configuration data contained in the database includes:
•Gatekeepers Table—Contains a list of gatekeepers and associated registration messages.
•Filters Table—Contains a list of gatekeepers and associated filters.
•Configuration Settings Table—Contains logging level, application priority, incoming connection
port and test routes accounting flag.
•TestRoutes—A record is added to this when a test route command is issued.
•TestOutputs—A set of records is added to this table after the test route command is complete.
•LogEntries—A set of records is added to this table after the test route command is complete.
•StringResources—Logging strings are located here.
CSR Application
The CSR application contains the logic (selection and rejection) to determine the proper routing for calls
based on inputs from the gatekeeper. CSR operates by the rules described in the following section.

1-4
Carrier Sensitive Routing User Guide
Chapter1 Overview of Cisco Carrier Sensitive Routing
CSR Basics
IngressRejectionRules
•Reject Max Origination Percentage
•Reject Max Ingress Units
•Reject Max Ingress Units per Route
EgressRejectionRules
•Reject Egress Cost Greater than Ingress
•Reject Insufficient QoS
•Reject Max Egress Units Exceeded
•Reject Max Egress Units per Route Exceeded
•Prevent ITSP to ITSP
Selection Rules
•Select Min Cost per Egress Route
•Select Best QoS
•Select Same Carrier
•Select Percentage Egress
•Select Preferred Carrier
CSR operates on an internal copy of the active dataset, which is loaded from the active dataset of the
postgreSQL database. CSR can also operate without the postgreSQL database running as long as it has
an active dataset. For more information on the active dataset, see the “Loading the Active Dataset”
section on page4-44.
CSR GUI
The CSR GUI provides an interface that can be used to enter, change, and modify provisioned data in
the postgreSQL database. You can import data into the database with the import capabilities provided
by postgreSQL. The CSR GUI can run on Sun/Solaris and Microsoft NT platforms.

1-5
Carrier Sensitive Routing User Guide
Chapter1 Overview of Cisco Carrier Sensitive Routing CSR Limitations
CSR Limitations
•When two rules are available (a rule associated with the carrier and a rule associated with a route),
the rule associated with the carrier is chosen first. If one of the rules (carrier’s rule) does not exist,
the rule associated with a route is used.
•When two contact lists are available (the contact list associated with the carrier and the contact list
associated with the EgressRouteAttribute), the carrier’s contact list is used first. If one of the contact
lists (carrier’s contact list) does not exist, then the contact list associated with the
EgressRouteAttribute is used.
•If a contact is provisioned with a DNS name and a DNS server is not found—that is, cannot get an
IP address—the dataset verification fails and the CSR cannot be started correctly.
•Static triggers are not supported by the CSR.
•Performance may deteriorate if more than five gatekeepers are connected to the CSR. This is also
related to hardware capabilities and call volume.

1-6
Carrier Sensitive Routing User Guide
Chapter1 Overview of Cisco Carrier Sensitive Routing
CSR Limitations

CHAPTER
2-1
Cisco Carrier Sensitive Routing User Guide
2
PostgreSQL Database Operations and
Functionalities
This chapter describes the operations and functionalities of the postgreSQL database and contains the
following sections:
•Database Operations, page 2-1
•Database Functionalities, page 2-3
The postgreSQL database is a relational database management system. A database in this management
system stores entities such as carriers, rules, contacts, routes, and the relationships among the entities.
The management system can manage many different databases simultaneously. The CSR creates a
database in this system and performs call routing based on the data in the database.
Database Operations
This section describes the following tasks:
•Activating the Database
•Exiting the Database
•Reactivating the Database
•Exporting a Database
•Reintializing a Database
Activating the Database
To activate the postgreSQL database, perform the following steps:
Step 1 Log in to the Solaris system by entering postgres as the user.
A “postgres” password prompt may appear.
Step 2 Enter the following command:
/etc/init.d/postgres_init start
This command calls postgreSQL command postmaster -S -i -B 40 -N 20 -D /usr/local/pgsql/data. The
parameters are described as follows:

2-2
Cisco Carrier Sensitive Routing User Guide
Chapter2 PostgreSQL Database Operations and Functionalities
Database Operations
•-S—Tells the postmaster to run in silent mode. This is not recorded to a log file.
•-i—Tells postmaster to allow network connections. If this is not set, the postmaster accepts
connections only from the local host.
Note This is needed for the GUI to connect to the database even when it is running on the same
machine.
•-B and -N—Set up shared memory segments.
•-D—Tells the postmaster the location of the database files.
Note For servers with console login, disable Xwindow in the file .profile, so the database can be restarted
from a reboot.
Exiting the Database
To exit the postgreSQL database, perform the following steps:
Step 1 Log in to the Solaris system by entering postgres as the user.
A “postgres” password prompt may appear.
Step 2 Enter the following command:
/etc/init.d/postgres_init stop
This command calls the postgreSQL command pg_ctl stop.
Reactivating the Database
To reactivate the postgreSQL database, perform the following steps.
Step 1 Log in into the Solaris system by entering postgres as the user.
A “postgres” password prompt may appear.
Step 2 Enter the following command:
/etc/init.d/postgres_init restart
This command calls the postgreSQL command pg_ctl restart. The parameters for this command are
described in “Activating the Database” section on page2-1.