Global Screening Database Table
Document Release History
Publication Date
Comments
01/16/03
Initial version of the document.
Feature History
Release
Modification
9.3(2)
Introduced in the MGC software in 9.3(2) patch CSCOgs005
(CSCuk37673).
9.4(1)
Baselined in the MGC software.
The Global Screening Database Table Feature is described in the following sections:
•
Feature Overview, page 1
•
Supported Platforms, page 3
•
Prerequisites, page 3
•
Configuration Tasks, page 3
•
Glossary, page 5
Feature Overview
This featurette provides a single global screening table that is accessible from every dialplan without
specific definition. It allows you to handle screening from a single database table instead of using
multiple copies of screening tables by constructing a global database with a customer group id (GLBL)
that can be searched from any dialplan.
Various tables in the global dialplan, such as NOA, Cause, Result, and NPI cannot be edited. Screening
results (stored in the TimesTen database) can be added and deleted from the global dialplan.
For existing customers (customers with existing screening entries), the file digitanalysis.dat must be
updated so that the engine acknowledges the new (GLBL.dialplan) dialplan file.
Note
This feature was introduced in release 9.3(2) patch CSCOgs005 (CSCuk37673) and will be baselined in
release 9.4(1).
Cisco MGC Software Release 9.4(1)
1
Global Screening Database Table
Feature Overview
Benefits
The Global Screening Database Table has the following benefits:
You can use the new global screening database table and the old database dialplan method to process screening
requests.
You can continue to use screening with multiple dialplans or you can use the global screening database
table.
The Global Screening Database Table provides a single global screening table that is accessible from every
dialplan without specific definition.
Previously, when defining a screening table (for example, BWHITE) for a dialplan, that screening table
was specific to that particular dialplan. It was not possible to check numbers in a screening table that
was defined by another dialplan. A customer using screening with multiple dialplans was required to
duplicate the screening database for each dialplan and to define every subscriber in multiple screening
tables.
The Global Screening Database Table allows you to handle screening from a single database table instead of
using multiple copies of screening tables.
This featurette allows you to construct a global database with a customer group id (GLBL) that can be
searched from any dialplan.
The Global Screening Database Table allows you to construct a global database with a customer group id that can
be searched from any dialplan.
Previously, a customer using screening with multiple dialplans was required to duplicate the screening
database for each dialplan because the customer group id that identifies the dialplan is passed to
TimesTen as part of the key for the screening record.
Restrictions
The following restrictions apply when using the Global Screening Database Table featurette:
Provisioning commands with a Customer Group Id of GLBL fail.
A reserved customer group id named GLBL has been created. Therefore, you cannot create a dialplan
with the name GLBL.dialplan.
GLBL.dialplan cannot be deleted.
This empty dialplan (GLBL.dialplan) is shipped with the system and cannot be deleted.
Some tables in the global dialplan, such as NOA, Cause, Result, and NPI cannot be edited.
Related Documents
This document contains information that is related strictly to the Global Screening Database Table
Feature. The documents that contain additional information related to the Cisco Media Gateway
Controller (MGC) are listed below:
•
Release Notes for Cisco Media Gateway Controller Software Release 9.3(2)
•
Release Notes for Cisco Media Gateway Controller Software Release 9.4(1)
Cisco MGC Software Release 9.4(1)
2
Global Screening Database Table
Supported Platforms
•
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
•
Cisco Media Gateway Controller Software Release 9 Provisioning Guide
•
Cisco Media Gateway Controller Software Release 9 Dial Plan Guide
•
Cisco Media Gateway Controller Software Release 9 MML Command Reference Guide
•
Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and
Troubleshooting Guide
Supported Platforms
The hardware platforms supported for the Cisco MGC software are described in the Cisco Media
Gateway Controller Software Release 9 Installation and Configuration Guide.
Prerequisites
There are no prerequisites.
Configuration Tasks
Migration For Customers Without Screening Entries
There are no migration issues for new customers (customers without screening entries). The new
dialplan file, GLBL.dialplan is automatically added to your system starting with release 9.4(1).
Migration For Customers With Screening Entries
Existing customers may have multiple dialplans with duplicated sets of screening data in the TimesTen
database. The difference in the records in the database is the customer group id that links the record to
a specific dialplan.
Complete the following procedure to migrate your data for global screening use:
Step 1
Using an active PGW system, login.
Step 2
Using the prov-export command, export the screening data from each dialplan.
prov-exp:all:dirname=”save-config-2”
Note
Step 3
If you have dial plans T001 and T002 using T001.bwhite and T002.bwhite screening, after prov-export
you will have 2 files, T001.Bwhite and T002.Bwhite.
Copy T001.bwhite to GLBL.bwhite as follows:
cd /opt/CiscoMGC/etc/cust_specific/save-config-2
cp T001.bwhite GLBL.bwhite
more GLBL.bwhite
Cisco MGC Software Release 9.4(1)
3
Global Screening Database Table
Configuration Tasks
Step 4
Import GLBL.bwhite as follows:
prov-add:files:name=”bwhitefile”,file=”GLBL.bwhite”, action=”import”
numan-rtrv:bwhite:custgrpid="GLBL",cli="x"
Step 5
Modify the screening type dw1 to ”dw3” for one resulttable in T001 dialplan.
Step 6
Make a test call from a test phone with the CLI listed in GLBL.bwhite.
Step 7
Modify the screening type dw1 to ”dw3” for one resulttable in T002 dilaplan.
Step 8
Make a test call from a test phone with the CLI listed in GLBL.bwhite.
Step 9
Modify all screening type dw1 to “3” for both T001 and T002 dialplan as follows:
Edit both T001.bwhite and T002.bwhite:
vi T001.bwhite or vi T002.bwhite
:1,$s/1 /2 /g to replace all 1s in the first column to 2s
Step 10
Save your changes and quit the editor as follows:
:wq!
Step 11
Import both T001.bwhite and T002.bwhite back and verify they are empty afterwards using:
prov-add:files:name=”bwhitefile”,file=”T001.bwhite”,action=”import”
prov-add:files:name=”bwhitefile”,file=”T002.bwhite”,action=”import”
numan-rtrv:bwhite:custgrpid="T001",cli="x"
numan-rtrv:bwhite:custgrpid ="T002",cli="x"
Step 12
Caution
Make a test call from a test phone with the CLI listed in GLBL.bwhite.
Configuration of the Cisco MGC software requires that the system software be shut down. In a simplex
system, calls cannot be processed during system shut down. In a continuous service system, your system
loses the ability to maintain calls during a critical event while the system software on one of the
PGW hosts is shut down.
For more information on configuring the rest of the Cisco MGC software, refer to the Cisco Media
Gateway Controller Software Release 9 Installation and Configuration Guide.
Modified MML Commands
This section contains the MML commands that were modified for the Global Screening Database Table
Feature.
prov-export
The prov-export command has been modified to extract global screening data (if any exists) from the
TimesTen database after all dialplans are processed.
Global screening data is stored in the following files:
•
GLBL.awhite
•
GLBL.ablack
•
GLBLbwhite
Cisco MGC Software Release 9.4(1)
4
Global Screening Database Table
Glossary
•
GLBLbblack
Screening includes the following new values:
•
dw1 value 3—global whitelist screening
•
dw1 value 4—global blacklist screening
These values indicate that the global database table is being used to process a screening request. The
customer group id submitted to TimesTen is GLBL regardless of the customer group id of the active
dialplan. These values are verified during provisioning validation.
If the data word value indicates that global screening is used, then the current customer group id is
ignored and the request is submitted with the customer group id of GLBL.
Glossary
The following table contains definitions of acronyms and technical terms used in this document.
Table 1
Glossary
Acronym
Description
DPNSS
Digital Private Network Signaling System
GTD
Generic Transparency Descriptor
ISUP
Isdn User Part
ITU
International Telecommunication Union
PGW
PSTN Gateway
PTCC
Packet Telephony Call Control
TDM
Time Division Multiplexing
UCM
Universal Call Model
Cisco MGC Software Release 9.4(1)
5
Global Screening Database Table
Glossary
Cisco MGC Software Release 9.4(1)
6