4-86
Cisco PGW 2200 Softswitch Release 9.8 Software Installation and Configuration Guide
OL-18083-01
Chapter 4 Configuring the Cisco PGW 2200 Softswitch Software
Initializing the Call Screening Database
where activehost is the name (not IP address) of your active host. In the example below, the active host
is hostx and the standby host is hosty.
Caution Do not use IP addresses when setting up database replication. If you do, replication will fail.
Example 4-2 Initializing Database Replication on the Standby Host
Configuring replication for DSN=howdydb
Restoring file /opt/TimesTen4.1/datastore/howdydb.ds0 from backup
Restoring file /opt/TimesTen4.1/datastore/howdydb.log0 from backup
RAM Residence Policy :inUse
Manually Loaded In Ram :False
Replication Agent Policy :manual
Replication Manually Started :True
Oracle Agent Policy :manual
Oracle Agent Manually Started :False
Replication setup completed.
Note If the replication setup on the standby host fails, you must run delete_replication.sh on both active and
standby hosts. Then change the value of the TTREPPORT variable from 2890 to 2891 in the
setup_replication.sh script on both active and standby hosts and save your changes. Perform the whole
procedure again.
Step 5 Start the both active and standby Cisco PGW 2200 Softswitch as root:
# /etc/init.d/CiscoMGC start
Proceed to “Verifying Database Replication”.
Verifying Database Replication
To verify that replication is working, perform the following steps:
Step 1 Log in to the active host and start an MML session by entering mml.
Step 2 Add a test entry into the B white list database using the numan-add MML command. For example:
mml> numan-add:bwhite:custgrpid="S018",svcname="testsvc",cli="9998"
Text similar to the following is displayed:
VSC-01 - Media Gateway Controller 2000-08-30 11:31:25
M COMPLD
"bwhite"
;
Step 3 Delete the test entry using the numan-dlt MML command.
mml> numan-add:bwhite:custgrpid="S018",svcname="testsvc",cli="9998"
Step 4 Log in to the standby host and start an MML session by entering mml.