Professional Documents
Culture Documents
Release 10.0.1
825-0735-010 Rev 01
PrePay IN
To order additional copies of Lightbridge documentation, or to request documents in electronic (read-only) format, please contact your Lightbridge account manager or relationship manager. The information used as examples in this document, including consumer or business names, identification numbers, addresses, and telephone numbers, is fictitious. Any resemblance to actual names, addresses, telephone numbers, or other forms of identification is unintentional and purely coincidental. LIGHTBRIDGE, and the Lightbridge logo are registered trademarks of Lightbridge, Inc. PrePay IN is a trademark of Lightbridge, Inc. All other trademarks or registered trademarks are the property of their respective owners. Software Version: Order Number: Print Date: Release 10.0.1 825-0735-010, Revision 01 October 13, 2005
2005 by Lightbridge, Inc. All rights reserved. This Updated Guide Book and the software described in it are the property of Lightbridge, Inc., and its licensors and contain their confidential trade secrets. Use, examination, copying, transfer and disclosure to others, in whole or in part, are prohibited except with the express prior written consent of Lightbridge, Inc. Lightbridge, Inc. 30 Corporate Drive Burlington, MA 01803 USA TEL: +1-781-359-4000 FAX: +1-781-359-4500 http://www.lightbridge.com
Contents
Chapter 1.
1.1 1.2 1.3 1.4
Preface.......................................................................................................10
Upgrading from Earlier Releases ............................................................ 10 Required Materials .................................................................................. 10 Disk Space Requirements ....................................................................... 12 Time Estimate for Upgrading to PrePay 10.0.1 ....................................... 12
Chapter 2.
2.1 2.2
Preparation of Solaris 2.8 ........................................................................ 15 2.2.1 Kernel 29 ........................................................................................ 15 2.2.2 Recommended and Required Patches........................................... 15 2.2.3 64-bit Mode Solaris......................................................................... 16 Preparation for Veritas 4.x Upgrade ........................................................ 16 Pre-upgrade Database Conversion Analysis........................................... 17 Prepare the Upgrade Staging Directory .................................................. 17 2.5.1 Load the Upgrade Toolkit and Application Files ............................. 17 2.5.2 Pre-Stage CD Contents to Disk ...................................................... 18 Confirm the Directory Locations for Application Packages...................... 19 2.6.1 Create the /udr File System ............................................................ 20 Estimate the Upgrade Space Requirements ........................................... 20 2.7.1 Estimating the Space for PrePay 10.0.1 Operation ........................ 21 Estimating the Space for Database Table Changes................................ 21 2.8.1 Table Changes Requiring a Review of Tablespaces...................... 22 2.8.2 Determine Freespace in Each Tablespace..................................... 22 Acquire the PrePay 10.0.1 License Files for Optional Features .............. 23 Note on configuration files in PrePay 10.0.1 ........................................... 24 Prepare the Switch Configuration Files ................................................... 24 2.11.1 All Interfaces ................................................................................... 25 2.11.1.1 switchInterface.cfg.sample ........................................................ 25 2.11.1.2 capSwitchInterface.cfg.sample.................................................. 25
2.11.1.3 profileFile.prf.sample ................................................................. 26 2.11.1.4 denyAnnouncementTable.cfg.sample ....................................... 26 2.11.2 IS-41EE .......................................................................................... 26 2.11.3 WIN-II.............................................................................................. 27 2.11.4 GSM................................................................................................ 27 2.11.5 ISUP ............................................................................................... 27 2.11.6 IS-41P............................................................................................. 27 2.12 Review and Prepare D7 Configuration .................................................... 28 2.12.1 NOTE: PrePay 10.0.1 requires D7 version 1.4.0.2........................ 28 2.12.2 Upgrading from Distributed7 1.3.1.x ............................................... 28 2.12.3 Prepare New D7 Configuration Files .............................................. 28 Note on the Emergency Number Table (Lucent Only) ............................ 29
2.13
Chapter 3.
3.1 3.2 3.3 3.4 3.5 3.6 3.7
Shutdown and Disable PrePay, Oracle and SS7 .................................... 31 3.4.1 Shutdown PrePay ........................................................................... 32 Disable CRON Jobs ................................................................................ 32 Create a Link for Perl Scripts................................................................... 32 Upgrading to SS8 Networks D7 1.4.0.2................................................... 33 3.7.1 Review /var/sadm/install/admin/default for pkgadds....................... 33 3.7.2 Set the System to Boot in 64-bit mode ........................................... 33 3.7.3 Update the /etc/system file ............................................................. 34 3.7.4 Upgrading from a Previous Version of D7 ...................................... 35 3.7.5 Copy apmconfig file ........................................................................ 39 3.7.6 Monitoring D7 Process States ........................................................ 39 Truncate PEG_COUNTER and DAILY_REVENUE ................................ 40 Upgrade to Oracle 9.2.0.6 ....................................................................... 40 Start the Upgrade Using the ppupgrade Script........................................ 41 Backing Up the PrePay Application Directories....................................... 42 Upgrading Configuration Files ................................................................. 43
Update the serviceDirectory file............................................................... 44 Apply the Application Upgrade Package ................................................. 44 Execute setupMultAccessRaters.ksh ...................................................... 45 Reconfigure Database Rollback Segments............................................. 46 3.16.1 Save Current Rollback Configuration ............................................. 46 3.16.2 Convert to One Large Rollback Segment ....................................... 46 Upgrade the Database Schema to PrePay 10.0.1 .................................. 47 3.17.1 Known Issues ................................................................................. 48 Review the Upgrade Log Files ................................................................ 49 Restore Original Rollback Segment Configuration .................................. 49 Install the License File ............................................................................. 49 Restore startup files................................................................................. 50 Apply Any Required Patches for PrePay 10.0.1...................................... 51 Install any Tailored Switch Configuration Files........................................ 51 Rerun setupSoftLinks.ksh........................................................................ 51 Verify Non-Standard PPADM or Oracle passwords ................................ 53 Update SMS Configuration (if used)........................................................ 54 Install the PrePay Client Application........................................................ 55 Configure Emergency Number Table (Lucent Only) ............................... 55 3.28.1 Potential Impacts ............................................................................ 56 Application Startup .................................................................................. 57 status_ppay Application Testing.............................................................. 57
3.17 3.18 3.19 3.20 3.21 3.22 3.23 3.24 3.25 3.26 3.27 3.28 3.29 3.30
Chapter 4.
4.1 4.2 4.3 4.4 4.5 4.6 4.7
Notes for 922 users on major changes introduced with PrePay 10.0 ..58
New startup, shutdown, status, list, and restart scripts ........................... 58 Obsolete configuration files (prepay.cfg, prepay.default, etc.) ................ 59 New configuration files introduced in $PPHOME/etc .............................. 59 Existing ini, prf, cfg, and dat configuration/data files ............................... 60 Modifications to prepay_profile................................................................ 60 Configuration of XML file prepay_process_control_entities.xml .............. 61 Configuration of XML file prepay_global_entities.xml.............................. 65
4.8 4.9
Converting from old rating configuration to new XML rating configuration66 Modified Default Entity Variables............................................................. 67 4.9.1 Username/Password for ppadm (prepay_global_entities.xml) ....... 67 4.9.2 System Phone Length (prepay_system_entities.xml)..................... 67 4.9.3 Launcher......................................................................................... 68 4.9.4 Specifying Number of Client Funnel Processes (prepay_system_entities.xml)........................................................................ 68 4.9.5 Specifying PPAS ID (prepay_system_entities.xml) ........................ 69 4.9.6 Specifying Minimum Card Number Width (prepay_system_entities.xml)........................................................................ 69 4.9.7 Specifying Phone Card Access Code Width (prepay_system_entities.xml)........................................................................ 69 4.9.8 Specifying Host Entities (prepay_global_entities.xml, prepay_host_entities.xml) ............................................................................. 69 4.9.9 Specifying Service Entities (prepay_services_entities.xml)............ 71 4.9.10 Obsoleted Priority Variables ........................................................... 71 4.9.11 CC Network Variables .................................................................... 71 4.9.12 PreRater Entities (prepay_voice_rating_entities.xml)..................... 71 4.9.13 Configure Dialing Plan Entity Variables .......................................... 71 4.9.14 IVR Entities (prepay_ivr_entities.xml)............................................. 72 4.9.15 IVR-ROUTER Entities (prepay_ivr_entities.xml) ............................ 72 4.9.16 IPM Entities (prepay_provision_entities.xml).................................. 72 4.9.17 BulkActivation Variables (prepay_api_entities.xml) ........................ 73 4.9.18 Extracts Entities (prepay_ivr_entities.xml)...................................... 73 4.9.19 Card Expiration Variables (prepay_phone_card_entities.xml)........ 73
4.10 Review purging parmeters in purgeCreditCardTables.xml, purgeDataTables.xml, and purgeMNPTables.xml .................................................... 73 4.11 4.12 4.13 4.14 4.15 4.16 Mapping of prepay.cfg sections to XML entity files ................................. 74 Modifying Tracing/Logging Levels ........................................................... 78 Reconfigure /etc/services file................................................................... 79 Incorporate New ppadm Crontab File...................................................... 79 New alarmCollectors.cfg configuration file .............................................. 79 Sample Configuration Files ..................................................................... 79 4.16.1 serviceDirectory.sample ................................................................. 79 4.16.2 switchInterface.cfg.sample ............................................................. 79 4.16.3 winDefault.prf.sample ..................................................................... 79
4.17
New Features/Functionality in PrePay 10.0 ............................................ 79 4.17.1 Credit Card processing configuration parameters .......................... 79 4.17.2 API AutoPayment Feature .............................................................. 79 4.17.3 API PaymentAwards Feature ......................................................... 79 4.17.4 API EmailNotify Feature ................................................................. 79 4.17.5 Multiple Funds/Included Usage ...................................................... 79 4.17.6 Rewritten Access Rater .................................................................. 79 4.17.7 Mobile Number Portability............................................................... 79 4.17.8 System Startup/Shutdown Architecture .......................................... 79 4.17.9 Nortel TDMA HLR Provisioning ...................................................... 79 4.17.10 CTPv3.6.......................................................................................... 79 4.17.11 Subscriber Awards.......................................................................... 79 4.17.11.1 Credit Awards based on single payments ............................ 79 4.17.11.2 Discount Awards based on cumulative payments ................ 79 4.17.11.3 prepay_process_control_entities.xml variables: ................... 79 4.17.11.4 PrePay license browser option: ............................................ 79 4.17.11.5 Process in API subsystem: ................................................... 79 4.17.11.6 prepay_voice_rating_entities.xml (for awdDaemon)............. 79 4.17.12 INAP/CS1R Interface...................................................................... 79 4.17.13 GUI/Crystal Reports........................................................................ 79 4.17.14 API XML Username/Passwords ..................................................... 79 Log files in 10.0.x..................................................................................... 79 Installation and configuration of 10.0.1 EAM ........................................... 79 Start up PrePay, Oracle, and SS7........................................................... 79 Back up the New PrePay and Oracle ...................................................... 79
Chapter 5. Chapter 6.
6.1 6.2 6.3 6.4 6.5
Configuration for Data Billing using the General Charging Interface79 Post-Upgrade Steps..................................................................................79
Tailor File and Table Purging Scripts ...................................................... 79 Review other sample files........................................................................ 79 Restore CRON Entries ............................................................................ 79 Purge Obsolete Configuration Files......................................................... 79 Roll Out the Client Workstation ............................................................... 79
6.6
Appendix A. Upgrading Veritas Volume Manager and File System to 4.x ..............79
A.1 A.2 A.3 A.4 A.5 A.6 A.7 A.8 A.9 Preface .................................................................................................... 79 Required Materials .................................................................................. 79 Upgrade Veritas VxVM and VxFS to 3.5 ................................................. 79 Save the Veritas Volume information for safekeeping............................. 79 Load the Volume Manager (VxVM) 3.5 CD ............................................. 79 6.6.1 Unencapsulate the boot disk and save the VxVM info ................... 79 Remove the Veritas File System (VxFS) packages................................. 79 Remove the VxVM packages .................................................................. 79 Load the Volume Manager (VxVM) 3.5 CD ............................................. 79 Individual patches for VxVM with MP2 and VxFS with MP2.................... 79
Appendix B. Changes to PrePay XML Configuration Files.......................................79 Appendix C. Changes to PrePay Database Tables ......................................................79 Appendix D. Switch Interface Configuration Files .....................................................79
D.1 D.2 D.3 D.4 D.5 D.6 D.7 D.8 D.9 switchInterface.cfg.sample ...................................................................... 79 capSwitchInterface.cfg.sample................................................................ 79 denyAnnouncementTable.cfg.sample ..................................................... 79 profileFile.prf.sample ............................................................................... 79 is41eeDefault.prf.sample......................................................................... 79 CapDefault.prf.sample............................................................................. 79 isupDefault.prf.sample............................................................................. 79 winDefault.prf.sample .............................................................................. 79 pplError.English.Sample.......................................................................... 79
Appendix E. Performing a Solaris Rollback................................................................79 Appendix F. Upgrading from Oracle 9.2.0.4 to version 9.2.0.6 on Solaris 8 ............79
F.1 Preparation Steps for Oracle 9.2.0.6 ....................................................... 79 F.1.1 Check Solaris is Running in 64-bit Mode........................................ 79 F.1.2 Check Available Space in $ORACLE_HOME File System............. 79 F.1.3 Record the Database Character Set............................................... 79 F.1.4 Record the Database Block Size .................................................... 79 F.1.5 Check for use of N-type Columns................................................... 79 F.1.6 Check for Corruption in the Dictionary............................................ 79 F.1.7 List All Objects that are not VALID ................................................. 79 F.1.8 Create a Script to Compile All Invalid Objects ................................ 79 F.1.9 List the Grants ................................................................................ 79 F.1.10 Ensure No Files Need Media Recovery.......................................... 79 F.1.11 Ensure No Files are in Backup Mode ............................................. 79 F.1.12 Prepare the System Rollback Segment.......................................... 79 F.1.13 Ensure Freespace in Rollback Tablespace .................................... 79 F.1.14 Ensure SYS and SYSTEM have SYSTEM as Default Tablespace79 F.1.15 Record the Locations of All Control Files........................................ 79 F.1.16 Ensure NLS_LANG Variable is Set Correctly ................................. 79 F.1.17 Disable All Oracle Related Batch and Cron Jobs ........................... 79 Upgrade Oracle to 9.2.0.6 ....................................................................... 79 PreParation Tasks ................................................................................... 79 F.3.1 Maintenance window tasks............................................................. 79
F.2 F.3
Appendix G. initppay.ora...............................................................................................79
G.1 Obsolete parameters for Oracle 9i .......................................................... 79
Preface
The upgrade to PrePay release 10.0.1 requires that your system be at PrePay Release 9.2.22P1, 9.2.2P2, 9.2.2P3 or 10.0. This document does not lay out the steps to upgrade to any of those versions. If needed, please see the appropriate upgrade documents to get your system to one of these versions. Additionally, see the note below.
1.1
Customers upgrading from PrePay 5.5.8, 5.5.9, or 6.0 to release 10.0.1 must first upgrade their servers to release 7.0 or release 8.0 on Solaris 2.8. From there you can upgrade to PrePay 10.0.1.x.
The only upgrade paths for 10.0.1 is from 9.2.2X and 10.0 . Not sure of whether the above will be relevant.
1.2
Required Materials
PrePay 10.0.1 Client Software CD, P/N ????.
PrePay 10.0.1 Server Upgrade Software CD that contains the application upgrade package and upgrade toolkit, P/N ???? PrePay 10.0.1 Server Software Distribution CD, P/N ???? SS8 Networks Distributed7 version 1.4.0.2 Software license conversion is required when upgrading from NewNet Access Manager to SS8 Distributed7. Contact Lightbridge support to convert your existing license. Suggestion: All customers would be already on Distributed 7 when upgrading to 10.0.1 so no migration from Access manager to D7 will take place
Note: the SS8 Networks Distributed7 software package is included on the PrePay 10.0.1 Server Software Distribution CD, P/N 870-0584-001. Oracle 9.2.0.6 Upgrade CD, P/N ???. Solaris Patches Feb. 18, 2004 CD. This would need to be changed to the Solaris kernel patch May 2005
Note: Kernel patch 108528-29 is the highest level supported by D7 and PrePay 10.0.1. This could need to be changed as Kernel patch for May 2005 is 117350-25 Note: The Solaris Recommended Patches and kernel patch 108528-29(patch id should be changed to 117350-25) are on the Solaris Patches CD and the document 'Solaris Patch Upgrade Kernel 29.pdf' should be used to install them. If desired, a separate maintenance window can be scheduled to install Solaris patches. Be sure to have the local system administrator check for other patches that may be required for system-specific hardware support. Solaris 8 patch 117000-05 or later. (This lines needs to be updated if 117350-25 is going to be recommended) Veritas Volume Manager and File System Version 4.x, P/N ???.
Note: The Veritas software CDs may also be used: Veritas Storage Solutions V4.x CD containing Volume Manager and File System, P/N ???, ???. SS8 Distributed7 User Manual, P/N ??? dated ??? PrePay 10.0.1 license file for any licensed features. Tape cartridges for backup
1.3
To install PrePay 10.0.1, you must meet the following minimum disk space availability requirements.
Disk Space Requirements /<temparea>/work 150 MB available for the PrePay 10.0.1 Upgrade Package and 500 MB minimum (depending upon the size of /prepay) Instructions for calculating temporary working space are provided in the section Estimating the Upgrade Space Requirements in this document. /<temparea>/cd_sw /oracle 2GB available Approximately 2GB available is required for the uncompressed Oracle 9.2.0.6 package. An additional 2GB available is required for the installed 9.2.0.6 Oracle Home.
Recommend that several days, at a minimum, before upgrade are scheduled to test, review, and correct data. Backups Preparation time Start of application downtime Shut down application System dependent. Shutdown time depends on the number of processes on the PPAS platform. Approx 1-2 hours System dependent 3-4 hours
Upgrade to Solaris 8.0, Feb. 2004 (Solaris version may need to be changed as Chirags suggestion below)w/ patches, and Veritas Volume Manager 4.x, Veritas File System 4.x Note: These upgrades can be scheduled to be performed in a maintenance window before the PrePay upgrade, if desired. Upgrade Oracle to version 9.2.0.6 Upgrade to SS8 Distributed7 1.4.0.2 Perform PrePay 10.0.1 Application Upgrade Perform PrePay 10.0.1 Schema Upgrade (option 4) Perform 9.2 DB Data Conversion will it be 9.2? (Is there really a DB conversion from 9.2.2.X to 10.0.1?)
60 minutes 60 minutes 30 minutes 60 minutes Varies depending on size of database. Plan on at least 2-3 hours. Minimum 1 hour
End of application downtime Upgrade training environment (no application downtime) (What is training environment? We dont have the training/training user anymore in 10.0.1) Perform post-upgrade cleanup steps. 30 minutes
30 minutes
Pre-Upgrade Procedures
2.1 Review the PrePay ReadMe Notes
Obtain and review the readme notes accompanying the PrePay software for any known issues that were documented after the publishing of this document. There may be manual changes or patches required before performing the upgrade and/or conversion. You may need to review the ReadMe notes for Release 9.2.2P1, 9.2.2P2, 9.2.2P3, 10.0 and then 10.0.1 depending on your current PrePay version.
2.2
2.2.1
Solaris kernel level 29 is the supported version for PrePay 10.0.1 and beyond. Patch 108528-29 updates the operating environment to level 29 and is included in the Feb. 18th, 2004 Solaris recommended patches We would need to put the May 2005 Kernel patch here . patch id is 117350-25
2.2.2
Using the Solaris Patches CD, execute the instructions found in the Solaris Patch Upgrade Guide.pdf. For recommended patches, select only the 8_Recommended_20040218.zip. Do NOT install any 8_Recommended patch file other than this one. (If 117350-25 is going to be
recommended then this paragraph needs to be updated and next paragraph omitted because 117350-25 obsoletes 1117000-05.) Install Solaris 8 patch 117000-05 or later. This corrects a problem where vmstat reports the incorrect number of blocked processes with kernel level 29. This patch must be installed in single-user mode and requires a reboot immediately after installation. Install the SAN Foundation Kit if not already installed. If using a Sun A5x00 disk array then install the individual patches following the same guide.
2.2.3
The SS8 D7 software should be ran using a booted Solaris 64-bit kernel if the physical SS7 boards are PCI and not SBUS. Prior to installing D7, the system should be checked to see if PCI cards are being used and the Solaris 64-bit packages are installed. If PCI boards are being used but the 64-bit packages are not installed, install them but continue to boot the 32-bit kernel until D7 is installed. During the D7 installation, the NVRAM setting will be modified to boot the 64-bit kernel. To confirm if 64-bit packages are installed, use the pkginfo command and filter on 64-bit. At a minimum, the core packages should be installed. Contact your local Sun Support to determine if others packages are required. pkginfo | grep 64-bit system SUNWcarx system SUNWcslx system SUNWcsxu Core Architecture, (Root) (64-bit) Core Solaris Libraries (64-bit) Core Solaris (Usr) (64-bit)
When PrePay is upgraded to 10.0.1, the Solaris Operating Environment must be booted in 64-bit mode. This is required because the 64-bit version of Oracle will be installed.
2.3
If needed, Veritas Volume Manager and File System can and should be upgraded before PrePay 10.0.1 and in a separate maintenance window.
For the procedures needed to upgrade Veritas Volume Manager and File System, see Appendix A, (As of verification, there is no procedure created yet to upgrade to Veritas 4.x. We only have straight Veritas 4.x installation procedure.)
2.5
Identify a file system and directory with sufficient space for upgrade working files (application, table exports). Create a working directory called work in that file system. This directory path will be referenced as /<temparea>/work in all installation instructions. WARNING: Do not use the /prepay or /tmp file system. Example: If you are using the file system /spare, the working directory /<temparea> would refer to /spare. su ppadm cd /spare mkdir work
2.5.1
1. Copy the upgrade toolkit tar file and the PrePay 10.0.1 application tar.gz file from the CD-ROM to the file system upgrade work directory by typing the following: cp -pf /cdrom/cdrom0/* /<temparea>/work
2. Untar the upgrade tool kit by executing the following commands as user ppadm. Note that the build and revision references on the tar package may vary. cd /<temparea>/work tar xvf PrePay100_1.upgrade_tool.<buildid>.<rev>.tar Example: tar xvf PrePay100_1.upgrade_tool.tar
2.5.2
The purpose of this task is to copy the contents of all required CDs to disk so that downtime during the production upgrade can be minimized. 1. Copy the PrePay 10.0.1 Upgrade CD : Insert the CD labeled PrePay 10.0.1 Upgrade CD mkdir p cd cp r /<temparea>/cd_sw/prepay100_1_upgrade /<temparea>/cd_sw/prepay100_1_upgrade /cdrom/cdrom*/* .
2. NOTE: The Oracle 9.2.0.6 package requires Solaris 8 64-bit kernel. If the result of running isainfo vn does not return 64-bit sparcv9 applications then installation can not continue until the system is running in 64-bit mode. If Oracle server is to be upgraded to 9.2.0.6 then: The oracle information mentioned below needs to be modified below for 9.2.0.6 Insert the CD labeled Lightbridge Oracle 9.2.0.6 into the CD drive Su - oracle mkdir p $ORACLE_BASE/patches cd $ORACLE_BASE/patches cp /cdrom/cdrom*/*.zip . 3. Veritas Volume Manager or File System are to be upgraded to 4.x then: Insert the CD labeled PrePay Veritas VXVM4.x/VXFS4.x mkdir p cd tar xvf /<temparea>/cd_sw/veritas /<temparea>/cd_sw/veritas /cdrom/cdrom*/VOLUME_MANAGER/VOLUME_MANAGER.TAR
tar xvf
/cdrom/cdrom*/FILE_SYSTEM/FILE_SYSTEM.TAR
4. Copy the Solaris patches to disk: Insert the CD labeled Solaris Patch Upgrade Kernel 29 this should be the solaris version needed if it is 117350-25 then it will be 25 mkdir p cd cp r /<temparea>/cd_sw/solaris_patches /<temparea>/cd_sw/solaris_patches /cdrom/cdrom*/* .
Directory Locations for Applications Packages Directory /newnet Description Directory where NewNet Access Manager or SS8 D7 software is installed. Home directory for administrative user of the NewNet or D7 software (ss7admin). Directory where bytestream data for call data is kept. Directory where If not the same, then review and change the following files: There are no files to change, but the actual directory name must be used when installing the D7 application.
/home/ss7admi n
There are no files to change, but the actual directory name must be used when installing the D7 application.
/cdr
There are no files to change, but must use the actual directory name when deleting bytestream files There are no files to change, but must use the
/udr
Directory Locations for Applications Packages Directory Description bytestream data for data billing is kept. /logs /prepay All log files Directory where PrePay application is installed. Directory where Oracle software is installed. If not the same, then review and change the following files: actual directory name when deleting bytestream files All errors and warnings generated from the PrePay application are stored here. $PPHOME/etc/prepay_profile
/oracle
2.6.1
If data billing is to be implemented then a separate file system called /udr should be created to hold byte-stream files similar to the /cdr file system. This new file system should have its mountpoint owned by the ppadm Unix user and prepay group. Create this file system prior to upgrading to PrePay 10.0.1.
To estimate the amount of space required in the working directory (/<temparea>/work for saving $PPHOME directories, use the following commands: su - ppadm cd /<temparea>/work ./calc_saveprepay.ksh Executing this command will return a report of the amount of space required, and a message stating whether or not there is currently sufficient space to save the $PPHOME directories. The total working space required in the working directory (/<temparea>/work) is: Save copy of $PPHOME: ___ MB
If there is not sufficient space in the current working directory, either clear sufficient space, or else move the upgrade packages to a different location.
2.7.1
The size of the $PPHOME/bin, $PPHOME/libs, and $PPHOME/inqload directories increased between the 9.2.2.x and 10.0.1 releases. An additional 40 MB of space will be used in the $PPHOME directory for binaries and libraries. Verify that the $PPHOME file system has sufficient space to support the increased program sizes. The following command can be used to determine the space available in the $PPHOME file system. The df command lists used and available space in kilobytes. df -k $PPHOME
DDATA02, IINDEX02 Used for CALL_CHARGE, CALL_DETAIL tables and indices DDATA03, IINDEX03 Growing tables DDATA04, IINDEX04 Reference tables
2.8.1
There are no significant table growth areas in this release. The largest potential impact comes from optional use of Fund Bundles in Prepay 10.0.1. If you plan to use Fund Bundles, potential storage increases will be based on a percentage of subscribers who use Fund Bundles basis. Please consult with Lightbridge support to estimate any storage increases.
2.8.2
Review the amount of freespace currently available in each tablespace. The query below will show total freespace within each tablespace but does not show the number or size of freespace segments within the total. Adequate freespace to fit the initial extent of new tables and indexes must be made available prior to the production database conversion. sqlplus system/{system_password} set echo on; select b.tablespace_name "Tablespace name", b.bytes "# bytes ", (b.bytes - sum(nvl(a.bytes,0))) "# used ", sum(nvl(a.bytes,0)) "# free ", round((sum(nvl(a.bytes,0))*100)/(b.bytes), 1) "%free" from sys.dba_free_space a, sys.dba_data_files b where a.file_id(+) = b.file_id group by b.tablespace_name, b.file_id, b.bytes order by b.tablespace_name;
2.9 Acquire the PrePay 10.0.1 License Files for Optional Features
There are several new feature options that can be enabled in PrePay 10.0+. These are: MobileToMobileCustom False CreditCardProcessing False CS1R False CTP False The following features can be specified in the PrePay license file: PhoneCardOwnRegion False RegionalPhoneCards False CallingCircleCustom False DatabaseRetrievalInterval 300 SubscriberAward False CallingPartyPays False IntelligentCallingCard False SubscriberLimit 1000000 SmsCreditBalance False CallingCircle False SubscriberHistoryAPI False MobileToMobileCustom False CreditCardProcessing False ActiveSubscriberStates 1 2 3 4 SubscriberWarningPercentage 10 SubscriberProfileAPI False GlobalPhoneCards False SubscriberAccountAPI False PrePaySNMPMonitor False ProvisionSubscriptionAPI False Note: The CallingCircleCustom option is a billable option that requires additional software. Further installation and configuration are required for this licensed feature. Prepare the 10.0.1 license file before the 10.0.1 upgrade and install into /prepay/data post upgrade. The host Id of the server must be provided for generating the license file. The files will be installed in the appropriate directory during the upgrade.
Important: If the customer has purchased or changed any licensed features as part of upgrading to PrePay 10.0.1 or wishes to use Credit Card Processing, a new / replacement license file is required. This file must be built and installed by Lightbridge Technical Support before these features can be enabled. Type the licenseBrowser command to get the license details.
2.11.1.2 capSwitchInterface.cfg.sample
This is a sample master switch interface configuration file for Camel protocol. This file needs to be configured if camelIntf is going to be used. Configuration is the same as the switchInterface.cfg above but using capDefault.prf profile. All switches that are going to be interfacing with the camelIntface need to be defined in this file. There are three ways to configure this file. Using point code, E.164, and wild card. Examples below: Point Code Based Configurations 0-57-1 profile capDefault.prf E.164 (GT Address) based configurations
16003005001 profile capDefault.prf Wild Card configuration 0-57-* profile capDefault.prf *-*-* profile capDefault.prf * profile capDefault.prf 1600300* profile capDefault.prf
2.11.1.3 profileFile.prf.sample
This a sample profile file for the switch configuration. The values defined in this file are picked up as default values if they are not defined in a switch-specific configuration file. For example, this file might be used to define error routing actions for specific failure cases that would be used, regardless of the switch protocol in use.
2.11.1.4 denyAnnouncementTable.cfg.sample
This file contains the announcement IDs for configured denial reasons. Review and change if required for the switch configuration. . The format of this file has changed and must be edited if the file $PPHOME/etc/denyAnnouncementTable.cfg currently exists. This file has an additional column added to support switch-based and IVR-based announcements. Compare this to your previous release and set the column Announcement Type to an appropriate value for your installation. The current file $PPHOME/etc/denyAnnouncementTable.cfg must be edited such that an additional column is provided for each denial reason. The value in the third column may be set to '0' for no announcement, 1 for switch-based announcement, or 2 for IVRbased announcement. The settings must match what is defined with the customer's switch.
2.11.2 IS-41EE
is41eeDefault.prf.sample
This file contains default error routing actions and announcement IDs for IS41EE signaling. Review and change if required for the switch configuration.
2.11.3 WIN-II
winDefault.prf.sample Caution: Changes have been made to the sample file in this release. If you are using the WIN II/IS-826 protocol, review this new file carefully and update your existing file with new parameters. This file contains default information for the WINII configuration, including announcement IDs and error routing actions. Review and change if required for the switch configuration.
2.11.4 GSM
capDefault.prf.sample This file contains sample default setup information for GSM configuration, including announcement IDs and error routing actions. Review and change if required for the switch configuration.
2.11.5 ISUP
isupDefault.prf.sample This file contains sample default setup information for ISUP signaling, including switch ID, other miscellaneous setup parameters, announcement IDs, and trunk block configurations. At a minimum, switch IS and trunk block information must be modified/defined if this protocol is being used. pplError.english.sample This file contains the English text of error messages for the ppl server. It should not normally require modification.
2.11.6 IS-41P
is41pDefault.prf.sample
This file contains sample default setup information for IS-41P signaling, including switch ID, and other miscellaneous setup parameters. At a minimum, switch IDs must be modified/defined if this protocol is being used.
ppas_ansi.mml -change the value of the HOSTNAME, SCP, and DPC parameters, add/change links and link sets
sccp.mml
For ITU/CCITT configurations, the required files are listed with their editing requirements. pci3xpq.mml -change the value of the HOSTNAME parameter
ppas_itu.mml -change the value of the HOSTNAME, SCP, and DPC parameters, add/change links and link sets sccp.mml -change the value of the SCP and SSN parameters
3.1
Obtain and review the readme notes accompanying the PrePay software for any known issues that were documented after the publishing of this document. There may be manual changes or patches required before performing the upgrade and/or conversion.
3.2
To support a rollback of the PrePay or Oracle upgrades, a complete backup of both subsystems must be completed. For PrePay, backup all file systems owned or used by the ppadm UNIX user. For Oracle, backup all file systems used for tablespaces, redos, rollbacks, archive, temp, /var/opt/oracle, etc. Ensure the backup is valid in terms of being a recoverable backup set with archived redo logs.
3.3
Miscellaneous backup
licenseBrowser > licenseBrowser.922.txt
2. For 922 upgrades, capture a snapshot of the current rating configuration to be used in configuring the new XML files after the installation of the PrePay 10.0.1 software. /prepay/bin/ratingConfig t \ /<temparea>/cd_sw/prepay101_upgrade/ prepay922.rating.config.txt 3. Enable write privileges on the $PPHOME/phonecard directory. chmod chmod chmod chmod R R R R u+w u+w u+w u+w /prepay/phonecard /prepay/conversion /prepay/oracle/cfg /prepay/sql
4. Add privileges to the prepay database user (by default ppadm). You must do this as the Oracle system user. sqlplus system/manager SQL> GRANT EXECUTE ON DBMS_AQADM TO ppadm; SQL> GRANT EXECUTE ON DBMS_AQ TO ppadm; SQL> exit
3.4.1
Shutdown PrePay
If upgrading from a 9.2.2.X system: su ppadm ppstop system ps ef | grep ppadm kill 9 {any remaining PrePay processes that may not have shut down} If upgrading from a 10.0 system: su ppadm stop_ppay ps ef | grep ppadm kill 9 {any remaining PrePay processes that may not have shut down}
3.5
Save the current cron entries before removing them. They will be restored after the upgrade has passed acceptance testing.
3.6
1. Create a link for execution of Perl scripts. 2. Execute the following command for creating the link for Perl. su 3. Check for any links by typing the following command: ls -l /usr/local/bin/perl 4. If a file or link exists, skip the rest of the link step.
5. Look for Perl in other directories by typing the following command: ls -l /bin/perl /usr/bin/perl 6. If not found, try the following command: which perl 7. If /bin/perl exists, type: ln -s /bin/perl /usr/local/bin/perl 8. If /usr/bin/perl exists, type: ln -s /usr/bin/perl /usr/local/bin/perl
WARNING: If Perl is not installed on the system, contact Lightbridge Technical Support for assistance in acquiring and installing Perl.
3.7
3.7.1
The upgrade to D7 uses the pkgadd command. It may have problems installing the new software if the contents of /var/sadm/install/admin/default do not have the following line: Instance=unique Review the contents of this file and add/modify the above line as the root user if it is not already present.
3.7.2
During the preparation phase, the system should have been checked to verify it has the Solaris 64-bit versions of the Core packages. If the system does not have these, then do not continue with this process until Solaris has been updated with these packages. 1. Use the eeprom command to set the system to boot in the 64-bit mode.
If the eeprom command does not return a value for the boot-file it is already set for 64-bit mode and this section can be skipped. su eeprom boot-file boot-file: data not available. If the eeprom command returns a value for boot-file: eeprom boot-file boot-file=kernel/unix Use the following commands to clear the boot-file value. eeprom boot-file= eeprom boot-file
3.7.3
Note: This section is not talking about a /prepay/etc/system file. Such a file does not exist. Note: These changes should already have been made if Oracle has been upgraded to version 9 previously. Use these values to confirm your settings in this event. The following entries should be checked in /etc/system. Based upon the Lightbridge installation process, all of these values should be equal to or higher than the values required by the third-party software packages installed in this release. If changes are required, notify Lightbridge support, as there may be other related system impacts. A reboot is required if changes are made to this file. Settings: * * Shared Memory (shm) * set shmsys:shminfo_shmmax=4294967295 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=512 set shmsys:shminfo_shmseg=512 * * Semaphores (sem) *
* Obsolete *set semsys:seminfo_semmap=128 * * Message Parameters (msg) * set msgsys:msginfo_msgmax=4096 set msgsys:msginfo_msgmnb=16384 set msgsys:msginfo_msgmni=1024 set msgsys:msginfo_msgtql=1024 * Obsolete *set msgsys:msginfo_msgssz=16 *set msgsys:msginfo_msgseg=1024 * * Other * * "Hard" limit on file descriptors (ulimit -Hn) set rlim_fd_max=1024 * "Soft" limit on file descriptors (ulimit -n) set rlim_fd_cur=1024 set maxusers=1024 set pt_cnt=256 * Streams setting for D7 set strctlsz=4096 set sq_max_size=32
3.7.4
Use these steps to upgrade to the 1.4.0.2 version of Distributed7 if Distributed7 was previously installed.
Pre-upgrade instructions: 1. Obtain D7 1.4.0.2. It is named as Distributed7_1.4.0.2.tar.gz. 2. unzip and untar the file. Untarring will create a folder named "packages" which contains D7 1.4.0.2 packages. 3. As user ppadm, issue command "/newnet/access/bin/getcfg" and collect the output for later verification of instance number of D7 boards. Backup license and configuration: NOTE: The upgrade process will not overwrite the license or configuration files. Making backup copies of up these files is only required if you intend to remove the previous version of D7. As Root: 1) 2) 3) 4) 5) cd /newnet mkdir -p backup/1_4_0_1/etc cp access/etc/license.dat backup/1_4_0_1/etc mkdir -p backup1_4_0_1/RUN/config/PMGR cp access/RUN/config/PMGR/apmconfig backup/1_4_0_1/RUN/config/PMGR
Live Upgrade of Distributed7 User Considerations The following list describes system operations and user choices at the time of installation of the new release of the Distributed7 software: pkgadd results in the full installation/activation of the Distributed7 software the very first time it installed. No additional action is necessary.
If a version of Distributed7 is already installed on the target machine, pkgadd results in a passive installation of the new release. The release that is already installed on that machine is not removed or deactivated. In this case, users are required to run the ebs_setrelease command to activate the newly installed release. The ebs_setrelease command allows users to switch between different Distributed7 releases installed on the same machine When multiple versions of Distributed7 system software are installed on one machine, an access tree is created under the base product installation directory for each new version, e.g., access.1.3.1.5, access.1.4.0, access.1.4.0.1, access.1.4.0.2. To make it easy to switch between the different versions of Distributed7, $EBSHOME/access entry is maintained as a symbolic link, i.e., to the Distributed7 version that is currently in use. When multiple versions of a Distributed7 software package co-exist: The pkginfo command lists all such packages. Users should issue the ebs_setrelease -i command to find out which Distributed7 version is currently running. It is possible to remove obsolete versions using the pkgrm command. Alternately, the ebs_pkgrm command removes all software packages associated with a particular Distributed7 version. Procedure Note: You must run this procedure as 'root'
1. Use the pkgadd utility to install version 1.4.0.2 of Distributed7 software on one of the host machines. Note that since version 1.3.1.x is already in use, installation of this new version is passive, i.e., the newly installed version is not activated until the ebs_setrelease is run to explicitly choose it. 2. After installing the new release, use pkginfo to list all UNIX software packages installed on that host, and verify that both version 1.3.1.x and version 1.4.0.2 are listed. This ensures that the passive installation process was successful. 3. Run the ebs_setrelease utility to activate the newly installed version of software on that host: $EBSHOME/access/install/ebs_setrelease 1.4.0.2 Answer "Y" (yes) when asked to convert databases. This shuts down the Distributed7 software on that host, and upgrades all necessary system components, i.e., drivers, executables, configuration/database files, to version 1.4.0.2. 4. Run the ebs_setrelease command again to confirm which software release is currently in use: $EBSHOME/access/install/ebs_setrelease -i 5. Run "start_ppay D7" to start up the 1.4.0.2 release software. Wait until all appropriate Distributed7 daemons are started before starting any
application layer software. Note: ===== The ebs_setrelease script will copy and convert the runtime databases and license files as necessary. No action is required on your part. However, it does not copy the apmconfig file. To complete the upgrade: 1) cd /newnet/backup/1_4_0_1/RUN/config/PMGR 2) cp apmconfig /newnet/access/RUN/config/PMGR
3.7.5
If this is DA installation, on SPT nodes, copy /prepay/allhome/ss7admn/config/apmconfig.d7.1.2.0.dist to /newnet/access/RUN/config/PMGR directory as apmconfig. $ cd /newnet/access/RUN/config/PMGR $mv apmconfig apmconfig.{mmddyyy} $ cp -p $PPHOME/allhome/ss7admn/config/apmconfig.d7.1.2.0.dist /newnet/access/RUN/config/PMGR/apmconfig For non-DA installations, copy /prepay/allhome/ss7admn/config/apmconfig.d7.1.2.0 to /newnet/access/RUN/config/PMGR directory as apmconfig. $ cd /newnet/access/RUN/config/PMGR $mv apmconfig apmconfig.{mmddyyy} $ cp -p $PPHOME/allhome/ss7admn/config/apmconfig.d7.1.2.0 /newnet/access/RUN/config/PMGR/apmconfig
3.7.6
A monitoring tool is provided with Distributed7 that can be used to monitor the status of the Distributed7 stack as it is started. This tool is further described in the SS8 Distributed7 User Manual.
Usage (Korn shell): su - ss7admin exec ksh o vi export DISPLAY=IPaddress:0.0 AccessMonitor <signalingpt>
Example: (of monitoring signaling point 0 from IP address 1.2.3.4): su - ss7admin ksh export DISPLAY=192.168.3.4:0.0 AccessMonitor 0
3.9
WARNING: DO NOT run Option 4 unless you have run Options 2 and 3. Otherwise, you will have fatal failures when you run the Options 2 and 3.
ERROR Unable Warning cannot create 8. The following files and directories are backed up under /prepay ($PPHOME): bin data etc inqload ppadm aeenv libs 9. These directories should exist on customer systems. If they do not exist, the following error message will display: tar command failed The backup will still be successful and contain the other existing directories. 10. Review the log file for any warnings.
minutes to complete. Review the log file for any errors or warnings that may occur. more /<temparea>/work/<version>/logs/ upgrade_prepay.YYYYMMDD
499
999999999 26-OCT-04
499
The last instance defines that all subscribers with a sequence number > 499 will be handled by the fourth instance.
cd /<temparea>/work create_upgrade_rbs_script.ksh {system password} Modify the generated script for the following items: Remove non-SQL statements if any. Set initial and next extent so that a multiple of this value fits into the smallest datafile used for the rollback tablespace. Set initial and next extent to be of equal values. Set minextents to a multiple of the initial extent and large enough to use as much of the rollback tablespace as possible.
For example, if the RBS tablespace uses 10 datafiles and the smallest is 2000MB then a workable CREATE ROLLBACK SEGMENT statement would appear as: create rollback segment HUGE tablespace RBS storage (initial 900m next 900m minextents 18 maxextents unlimited ); Make the changes: vi upgrade_rbs_config.sql (make changes noted above) :wq! Run the modified script to create one large rollback segment. sqlplus system/{system password} < upgrade_rbs_config.sql > upgrade_rbs_config.lst
cd /<temparea>/work ./ppupgrade.ksh <fromversion> 2. Execute Option 3 in the PrePay Upgrade menu. The post-upgrade procedures are also automatically executed by this option. 3. Review the error log file in: /<temparea>/work/<version>/logs/ convert_schema.YYYYMMDD for any errors where YYYYMMDD is the system date. Execute the following command to review the log file for any errors or warnings that may have occurred. more /<temparea>/work/<version>/logs/ convert_schema.YYYYMMDD You may also examine the contents of this file with the vi editor looking for the following keywords (capital sensitive): Error ERROR Unable Warning cannot create 4. To enable the user to choose the appropriate amount of tablespace, the script displays the available tablespaces and their associated free space on the screen.. 5. Answer the prompts that follow according to the values in the figures below. The list of tables to be upgraded will differ depending on whether the application is being upgraded from PrePay 9.2.2 or PrePay 10.0 to PrePay 10.0.1.
cd /prepay/bin ls l |grep ^l lrwxrwxrwx 1 ppadm prepay 23 /prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 23 /prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 21 /prepay/bin/scilaunch lrwxrwxrwx 1 ppadm prepay 21 /prepay/bin/depositor lrwxrwxrwx 1 ppadm prepay 23 /prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 26 -> /prepay/bin/postCallWriter lrwxrwxrwx 1 ppadm prepay 21 /prepay/bin/postRater lrwxrwxrwx 1 ppadm prepay 20 /prepay/bin/gceRater lrwxrwxrwx 1 ppadm prepay 21 /prepay/bin/depositor lrwxrwxrwx 1 ppadm prepay 23 /prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 26 -> /prepay/bin/postCallWriter lrwxrwxrwx 1 ppadm prepay 21 /prepay/bin/postRater lrwxrwxrwx 1 ppadm prepay 20 /prepay/bin/gceRater lrwxrwxrwx 1 ppadm prepay 23 /prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 21 /prepay/bin/depositor lrwxrwxrwx 1 ppadm prepay 23 /prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 26 > /prepay/bin/postCallWriter lrwxrwxrwx 1 ppadm prepay 21 /prepay/bin/postRater lrwxrwxrwx 1 ppadm prepay 21 /prepay/bin/depositor lrwxrwxrwx 1 ppadm prepay 23 /prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 26 > /prepay/bin/postCallWriter lrwxrwxrwx 1 ppadm prepay 21 /prepay/bin/postRater lrwxrwxrwx 1 ppadm prepay 20 /prepay/bin/gceRater lrwxrwxrwx 1 ppadm prepay 23 /prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 23 /prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 23 /prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 23 /prepay/bin/apf_process
Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct
1 10:04 ainIccIntf -> 1 10:04 camelIntf -> 1 10:04 cfgLaunch -> 1 10:04 ctp1Depositor -> 1 10:04 ctp1Intf -> 1 10:04 ctp1PostCallWriter 1 10:04 ctp1PostRater -> 1 10:04 ctp1Rater -> 1 10:04 ctp3Depositor -> 1 10:04 ctp3Intf -> 1 10:04 ctp3PostCallWriter 1 10:04 ctp3PostRater -> 1 10:04 ctp3Rater -> 1 10:04 dataExport -> 1 10:04 gciDepositor -> 1 10:04 gciIntf -> 1 10:04 gciPostCallWriter 1 10:04 gciPostRater -> 1 10:04 gcpDepositor -> 1 10:04 gcpIntf -> 1 10:04 gcpPostCallWriter 1 10:04 gcpPostRater -> 1 10:04 gcpRater -> 1 10:04 inNwi -> 1 10:04 inSrv -> 1 10:04 inapcs1Intf -> 1 10:04 iniIntf ->
lrwxrwxrwx
1 ppadm prepay 23 /prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 22 /prepay/bin/ivrHandler lrwxrwxrwx 1 ppadm prepay 30 /prepay/monitor/mon_control.pl lrwxrwxrwx 1 ppadm prepay 21 /prepay/bin/scilaunch lrwxrwxrwx 1 ppadm prepay 24 -> /prepay/bin/ppXmlService lrwxrwxrwx 1 ppadm prepay 23 /prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 21 /prepay/bin/scilaunch lrwxrwxrwx 1 ppadm prepay 24 /prepay/bin/ss7Intf-ANSI lrwxrwxrwx 1 ppadm prepay 30 /prepay/bin/ss7TcapParser-ANSI lrwxrwxrwx 1 ppadm prepay 24 /prepay/bin/wmmMain-ANSI PREPAY /prepay/bin $
Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct
1 10:04 ipIntf -> 1 10:04 ivrHandl -> 1 10:04 mon_control.pl -> 1 10:04 neqLaunch -> 1 10:04 ppXmlServiceDaemon 1 10:04 ppayProcessCtrl -> 1 10:04 pqiLaunch -> 1 10:05 ss7Intf -> 1 10:05 ss7TcapParser -> 1 10:05 wmmMain ->
purgeMNPTables.xml
Use the following to re-validate passwords are consistent and match your needs. cd /prepay/etc/xml grep i password= * | more
The pre-rater looks for the emergency file at startup time, or when requested to re-load information using the 'daemonControl' tool. The file location is determined by a new entry 'preRater.emergencyNumberTbl', in the $PPHOME/etc/prepay.default file. If the prepay.default entry does not exist, or the referenced file does not exist, an informational message is written to the preRater.log file by the pre-rater process and is no change to pre-rater functionality. If the file is configured and does exist, the pre-rater will compare the dialed digits of mobile originating calls with the list of emergency numbers that have been configured. If there is a match, the call is allowed as a free call for the maximum allowed call duration. Call charge details are recorded as they are in any free call. This dialed digit comparison for emergency numbers is performed very early in the prerating process, in order to turn around potential emergency calls as quickly as possible. No pre-call or mid-call announcements are played during the call. Note: The maximum allowed call duration is configured in the file $PPHOME/etc/xml/prepay_voice_rating_entities.xml file as the parameter 'preRater.maxCallingTime'. Its default value is 28800 seconds or 8 hours. If any call duration exceeds this value, regardless of how it is charged, the call is torn down. Note: This feature should not be used as a replacement for the 'Special Number' feature for dialed digits. The intent of the feature is as stated, where certain dialed numbers should be accepted for immediate routing, such as emergency numbers. If the same number is listed both in the emergency number list, and the special number table, emergency number handling will take priority. IMPORTANT: This file should be created and protected regardless of whether information is populated in it.
Security recommendation: Create the emergency number configuration file regardless of whether or not the feature is being used. The file may be secured for read-only permission and owned by the super-user to minimize potential unauthorized changes. Regular review of file contents is also recommended.
Availability: When certain rating subsystem components, specifically the switch interface, Timing Mediation Server, and pre-rater processes are down, emergency calls will be denied.
Availability comments: This feature is a temporary work-around fix to expedite the ability to provide this functionality. Lightbridge cannot be held liable for the loss of emergency services during a PrePay outage on any system where this feature is used.
Notes for 922 users on major changes introduced with PrePay 10.0
The start_ppay.xml and start_ppay_batch.xml files define the processes that will start and how there are started, stopped and monitored. You must not modify these files, but If you are interested, start with /prepay/etc/xml/start_ppay.xml. Just like in prepay_global_entities, this file includes all the other subsystem files it needs. Start_ppay.xml defines the processes that make up the real-time PrePay system. Start_ppay_batch.xml defines the processes that are run in batch, usually out of the crontab.
gsmHlr.cfg tdmaHlr.cfg The two configuration files below are specific for a INAP/CS1R switch interface. Refer to the specific section on configuring a CS1R interface if that applies to the environment being upgraded. inapCs1RDefault.prf.sample inapCs1RInterface.cfg.sample
4.5
Modifications to prepay_profile
If specific client customizations were made to the 9.2.2 prepay_profile configuration file in $PPHOME/etc, you should add those customizations to the new 10.0.1 version of prepay_profile. Do NOT carry forward any references to the old prepay configuration files (prepay.cfg, prepay.default). Do NOT carry forward the following variable as it is now in the XML configuration file prepay_ivr_entities.xml. MSISDN_COUNTRY_CODE=`getcfg "IVR" "MSISDN Country Code"` export MSISDN_COUNTRY_CODE
<!ENTITY gci.enabled "FALSE"> Controls the enabling of the GCI data processes (e.g. gciIntf, gceRater, gciPostRater, gciPostCallWriter, gciDepositor) <!ENTITY gcp.enabled "FALSE"> Controls the enabling of the GCP data processes (e.g. gcpIntf, gcpRater, gcpPostRater, gcpPostCallWriter, gcpDepositor) <!ENTITY ctp1.enabled "FALSE"> Controls the enabling of the CCI Version 1 data processes (e.g. ctp1Intf, ctp1Rater, ctp1PostRater, ctp1PostCallWriter, ctp1Depositor) <!ENTITY ctp3.enabled "FALSE"> Controls the enabling of the CCI Version 3 data processes (e.g. ctp3Intf, ctp3Rater, ctp3PostRater, ctp3PostCallWriter, ctp3Depositor) <!ENTITY camelIntf.enabled "FALSE"> Controls the enabling of the camelIntf switch process. <!ENTITY ainIccIntf.enabled "FALSE"> Controls the enabling of the ainicc process group in prepay_voice_rating_processes.xml (process ainIccIntf) <!ENTITY inapcs1Intf.enabled "FALSE"> Controls the enabling of the inapcs1 process group in prepay_voice_rating_processes.xml (process inapcs1Intf) <!ENTITY ivr.enabled "TRUE"> Controls the enabling of the ivrHandl process group in prepay_ivr_processes.xml (process ivrHandl and ivrRouter) <!ENTITY ivrRouter.enabled "FALSE"> Controls the enabling of the ivrRouter process in prepay_ivr_processes.xml (ivr.enabled must be true) also. <!ENTITY ipIntf.enabled "FALSE"> Controls the enabling of the ipintf process group in prepay_ip_processes.xml (process ipIntf). <!ENTITY iniIntf.enabled "FALSE">
Controls the enabling of the in process group in prepay_in_processes.xml (processes in inNwi, inIntf, inSrv) <!ENTITY inSrv.enabled "TRUE"> Controls the enabling of the inSrv process in prepay_in_processes.xml (part of in process group controlled by iniIntf.enabled) <!ENTITY inNwi.enabled "FALSE"> Controls the enabling of the inNwi process in prepay_in_processes.xml (part of in process group controlled by iniIntf.enabled) <!ENTITY provision.enabled "FALSE"> Controls the enabling of the provision process group in prepay_provision_processes.xml (processes cfgLaunch, pqiLaunch, neqLaunch, etc.) <!ENTITY spatch.enabled "FALSE"> Controls the enabling of the spatch process group in prepay_data_processes.xml (process SpatchConv, etc.) <!ENTITY alcatelMMS.enabled "FALSE"> Controls the enabling of the Alcatel MMS process group in alcatel_mms.xml (batch process alcatelMMS) <!ENTITY alarms.enabled "TRUE"> Controls the enabling of the alarm process group in prepay_alarm_processes.xml (processes almDaemon, almUserAlarmServer, almFileWriter) <!ENTITY monitors.enabled "TRUE"> Controls the enabling of the monitor process group in prepay_monitor_processes.xml (processes crsm, ersm, guism, ivrsm, ipmsm, snmpMonitor) The ss7Intf.enabled and ss7TcapParser.enabled parameters must both be TRUE <!ENTITY ss7Intf.enabled "TRUE"> <!ENTITY ss7TcapParser.enabled "TRUE"> Controls the enabling of the ss7tcap process group in prepay_voice_rating_processes.xml (part of switch process group which is part of voice process group, handles processes ss7Intf and ss7TcapParser)
<!ENTITY wmm.enabled "FALSE"> Controls the enabling of the isup process group in prepay_voice_rating_processes.xml (process wmmMain) <!ENTITY awdDaemon.enabled "FALSE"> Controls the enabling of the awdDaemon process in the voice process group in prepay_voice_rating_processes.xml <!ENTITY paymentAwards.enabled "FALSE"> Controls the enabling of the PaymentAwardsMonitor process in the api process group in prepay_api_processes.xml <!ENTITY autoPayment.enabled "FALSE"> Controls the enabling of the AutoPaymentMonitor process in the api process group in prepay_api_processes.xml <!ENTITY emailNotify.enabled "FALSE"> Controls the enabling of the EmailNotifyMonitor process in the api process group in prepay_api_processes.xml <!ENTITY sms.enabled "FALSE"> Controls the enabling of the sms process group in prepay_sms_processes.xml (process smsHandler) <!ENTITY mnp.enabled "FALSE"> Controls whether the partitioned table maintenance occurs in start_ppay_batch.xml when the batch tasks are executed (applies to mobile number portability feature) <!ENTITY ccPayment.enabled "FALSE"> Controls whether the partitioned table maintenance occurs in the start_ppay_batch.xml when the credit card management feature is enabled <!ENTITY dataExport.enabled "FALSE"> Controls whether the data export batch processes are enabled in start_ppay_batch.xml when the batch tasks are executed
<!ENTITY PAYMENT_GATEWAY
"SPECIFY_GATEWAY_URL_HERE">
Modify the default ppadm login/password if different from the default. <!ENTITY PPDBUSER <!ENTITY PPDBPASSWD "ppadm"> "ppadm">
All entities files are included in the main entities file: /prepay/etc/xml/prepay_global_entities.xml. Start in this file and search for the words, "INCLUDE_SEARCH". All other entities files will be listed in this file this way.
4.8 Converting from old rating configuration to new XML rating configuration
After upgrading to 10.0.1, execute /prepay/bin/showRatingConfig to display the currently configured rating configuration: hobbes /prepay/etc/xml $ /prepay/bin/showRatingConfig SS7_CAMEL_NUM=2 Entity variable: camelIntf.totalCamelNumber SS7_AIN_ICC_NUM=1 Entity variable: ainIccIntf.totalAinIccNumber SS7_INAPCS1_NUM=1 Entity variable: inapcs1Intf.totalInapCs1Number WMM_MAIN_NUM=1 (always 1) No entity variable available, hardcoded value of 1 required. SS7_TCAP_PARSER_NUM=2 Entity variable: ss7TcapParser.totalTcapNumber SS7_TMDS_NUM=3 Entity variable: numberOfTmdsIntf SS7_PRE_RATER_NUM=2 Entity variable: preRaterNumber SS7_POST_CALL_WRITERS_PER_TMDS=2 Entity variable: postCallWriterNumber SS7_POST_CALL_WRITER_NUM=6 Calculated value: number of TMDS * number of postCallWriters per TMDS SS7_POST_RATERS_PER_POST_CALL_WRITER=2 Entity variable: postStreamNumber SS7_POST_RATER_NUM=12
Calculated value: number of postCallWriters * postRaters per postCallWriter SS7_DEPOSITOR_NUM=3 Entity variable: depStreamNumber Use the 9.2.2 rating configuration snapshot you saved before the upgrade to review differences and make process count modifications where appropriate. These process count changes will be made in prepay_process_control_entities.xml.
4.9
is now specified as entity variables in prepay_global_entities.xml <!-Oracle database information --> <!ENTITY PPDBUSER "ppadm"> <!ENTITY PPDBPASSWD "ppadm"> Modify the entity password for the ppadm oracle user as required for the installation. If the report or shareplex username/passwords need to be changed modify the appropriate entity variables in this XML file also.
4.9.2
The 9.2.2 SYSTEM variable System Phone Length was modified in 10.0 to have a default of 10. From 9.2.2 prepay.cfg.master System Phone Length 8 pool/access numbers # length of free
New entity variable in prepay_system_entities.xml <!-- length of free pool/access numbers --> <!ENTITY SYSTEM.System_Phone_Length "10">
4.9.3
Launcher
The launcher process has been removed in PrePay 10.0+. The functionality is replaced by watchDog (ppayProcessCtrl) process which is part of the ADMIN subsystem. Configuration of the watchDog process is done in prepay_admin_processes.xml. By default the D7 processes are not managed by watchDog. If you wanted to specify additional processes NOT to be monitored by watchDog add the process name (as defined by the XML process hierarchy) as an argument to the ignore parameter,
To specify additional funnel processes in 10.0.1, modify the prepay_system_entities.xml configuration file and add similarly lines as follows: Specify the desired total number of funnel processes in prepay_process_control_entities.xml <!ENTITY client.Number_of_Production_User_Funnel "2"> Then if more than two, add additional declarations in prepay_system_entities.xml For example, the third funnel process would be defined by adding these lines:
<!-- for any subsequent user funnel, increase number as format listed below --> <!ENTITY SYSTEM.Production_User_Funnel_3_Start_Flag "true"> <!ENTITY SYSTEM.Production_User_Funnel_3_Port "3044">
4.9.5
The 9.2.2 SYSTEM variable PPAS ID is now specified in the prepay_system_entities.xml file. Modify to retain the 9.2.2 value after the 10.0.1 upgrade.
# # Format = <server name> <host name> [HOSTS] Provision localhost the Provision server IVR localhost the IVR server process IVR Router localhost IVR Router server process ALARM User Server localhost alarm user server END In PrePay 10.0.1 these entities are defined in the XML configuration file prepay_global_entities.xml but referenced in prepay_host_entities.xml. prepay_global_entities.xml: <!ENTITY <!ENTITY <!ENTITY <!ENTITY PROV_HOSTS IVR_HOSTS IVR_ROUTER_HOSTS ALARM_HOSTS "&SDP_HOSTS;"> "&SDP_HOSTS;"> "&SDP_HOSTS;"> "&SDP_HOSTS;"> # host for # host for # host for # host for
prepay_host_entities.xml: <!-- host for the Provision server <!ENTITY HOSTS.Provision <!-- host for the IVR_server_process <!ENTITY HOSTS.IVR <!-- host for IVR_Router_server_process <!ENTITY HOSTS.IVR_Router "&IVR_ROUTER_HOSTS;"> <!-- host for alarm user server <!ENTITY HOSTS.ALARM_User_Server Modify as appropriate for the specific installation environment. --> "&PROV_HOSTS;"> --> "&IVR_HOSTS;"> --> --> "&ALARM_HOSTS;">
Dialing Plan Id 1 Local Home Location Area Y location area location area END
Are now defined in the prepay_voice_rating_entities.xml configuration file. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Dialing Plan Configs %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% --> <!-- Name of the customer --> <!ENTITY DIALING-PLAN.Customer_Name "CorsairUSA"> <!ENTITY DIALING-PLAN.Dialing_Plan_Id "1"> <!-- Y: use home location area, N: use serving location area --> <!ENTITY DIALING-PLAN.Local_Home_Location_Area "Y"> <!-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% NOTE: Ensure that you have modified this file with the correct dialing plan name and dialing plan id number to match what was configured in the 9.2.2 environment.
There are a number of drivers for IPM. First in prepay_process_control_entities.xml there is "provision.enabled" Which turns on the IPM subsystem as a whole. In prepay_provision_entities.xml I want to have all possible interfaces configured. The number "7" indicates the number of possible interfaces, allowing the startup tool to find/parse them all. Each individual interface must be enabled by flipping FALSE to TRUE.
client environment if the Credit Card Management functionality is to be used. At a minimum, review the defaults if this functionality will be enabled. The configuration file purgeDataTables.xml contains partition parmeters for the USAGE_CHARGE, RATE_COMPONENT_USAGE, and USAGE_DETAIL partitioned tables and should be configured for the client environment if PrePay data interfaces are being used (e.g. GCI,CTP,GCP). At a minimum, review the defaults if this functionality will be enabled. If you are upgrading an environment where data processing by PrePay is already enabled, review the settings in purgeTables.xml and modify this XML file accordingly. The configuration file purgeMNPTables.xml contains partition parmeters for the PORTED_NUMBER_LOG partitioned table and should be configured for the client environment if the Mobile Number Portability functionality is to be used. At a minimum, review the defaults if this functionality will be enabled. The ppadm crontab file should be modified to enable daily invocations of the required purging depending on which of these functional pieces are in use. # Partitioning /purging # # May require update of $PPHOME/etc/xml/purgeTable.xml to set tablespace and # retention information. # 30 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.partitionDataTables >> $PPLOGS/partitionDataTables.log 2>&1)' 30 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.partitionCreditCardTables >> $PPLOGS/partitionCreditCardTables.log 2>&1)' 30 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.partitionMNPTables >> $PPLOGS/partitionMNPTables.log 2>&1)
corresponding prepay_<subsystem>_entities.xml configuration file, unless the section was no longer needed.
XML Entity File prepay_system_entities.xml (launcher replaced by watchDog in prepay_process_control_entities.xml) prepay_host_entities.xml prepay_services_entities.xml prepay_voice_rating_entities.xml (most entries not carried forward) ss7 and ss7TcapParser options enabled in prepay_process_control_entities.xml, other entries are obsolete (enabled in prepay_process_control_entities.xml, most entries not carried forward) prepay_voice_rating_entities.xml, exact entries not carried forward prepay_voice_rating_entities.xml, exact entries not carried forward Obsolete Obsolete Obsolete prepay_voice_rating_entities.xml prepay_voice_rating_entities.xml prepay_voice_rating_entities.xml prepay_voice_rating_entities.xml Obsolete
[SS7-INTF] [CAMEL-INTF] [AINICC-INTF] [SS7-BSWR] [SS7-WMM] [PPL] [CC] [PRE-RATER] [DIALING-PLAN] [POST-RATER] [BPC]
[IVR] [IVR-ROUTER] [IPM] [PROVISION] [SMS] [ACCESS-RATER] [BULK-ACTIVATIONLOADER] [EXTRACTS] [CALL-ANALYSIS] [CARD-EXPIRATION] [PROCESS-MONITOR] [EXTRACT-ROAMER] [PHCRD-EXTRACTUPDATE] [ACCESS-NUMBERCONVERSION] [PHCRD-TO-PRINT] [RATED-CALL-DEPOSITOR] [ALARM-DAEMON] [ALARM-USER-SERVER] [ALARM-FILE-WRITER] [SYSTEM-MONITORINGTOOL]
prepay_ivr_entities.xml prepay_ivr_entities.xml prepay_provision_entities.xml prepay_provision_entities.xml prepay_sms_entities.xml Obsolete prepay_api_entities.xml prepay_reporting_entities.xml Obsolete prepay_phone_card_entities.xml Obsolete Obsolete Obsolete Obsolete prepay_phone_card_entities.xml prepay_voice_rating_entities.xml prepay_alarm_entities.xml prepay_alarm_entities.xml prepay_alarm_entities.xml prepay_monitor_entities.xml
[CALL-RATINGSUBSYSTEM-MONITOR] [EVENT-RATINGSUBSYSTEM-MONITOR] [IVR-SUBSYSTEMMONITOR] [GUI-SUBSYSTEMMONITOR] [PROVISION-SUBSYSTEMMONITOR] [EARLY-ALERT-MONITOR] [API-GATEWAY] [API-SOCKET-SERVER] [C-API] [FEATURE-CONTROL] [PHONE-CARD-LOAD] [PHONE-CARD-CONV] [AWARDS-DAEMON] [PC-RECONCILIATOR] [PHONE-CARD] [CALLING-CIRCLE] [SUBSCRIBER-AWARD] [TMDS] [FUND-EXPIRATION-DAYS]
prepay_monitor_entities.xml prepay_monitor_entities.xml prepay_monitor_entities.xml prepay_monitor_entities.xml prepay_monitor_entities.xml prepay_admin_processes.xml prepay_api_entities.xml prepay_api_processes.xml prepay_api_processes.xml (global values) prepay_process_control_entities.xml prepay_phone_card_entities.xml prepay_phone_card_entities.xml prepay_voice_rating_entities.xml prepay_phone_card_entities.xml prepay_phone_card_entities.xml prepay_voice_rating_entities.xml prepay_voice_rating_entities.xml prepay_voice_rating_entities.xml prepay_voice_rating_entities.xml
[IROAM] [GCE-RATER] [GCE-POST-RATER] [GCE-BSWR] [GCE-CALL-DEPOSITOR] [GCI] [CCI] [GCP] [INI] [INSRV] [INNWI] [IPINTF] [SNMP-MONITOR] [PURGE-ICC]
TBD prepay_data_rating_entities.xml prepay_data_rating_entities.xml prepay_data_rating_entities.xml prepay_data_rating_entities.xml prepay_data_rating_entities.xml prepay_data_rating_entities.xml prepay_data_rating_entities.xml prepay_process_control_entities.xml prepay_process_control_entities.xml prepay_process_control_entities.xml prepay_process_control_entities.xml prepay_monitor_entities.xml prepay_voice_rating_entities.xml
cci_gce_9
10019
The 9.2.2 entry 40 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; accstrt.crond >> $PPLOGS/accstrt.out 2>&1)' has been replaced by the 10.0.1 entry 0 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.ACCRATER >> $PPLOGS/access_rater.out 2>&1)' c. phone card expiration The 9.2.2 entry 0 5 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; cardexpstrt >> $PPLOGS/cardexpstrt.out 2>&1)' has been replaced by the 10.0.1 entry 0 5 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.cardexpstrt >> $PPLOGS/cardexpstrt.out 2>&1)' d. restart of client subsystem processes The 9.2.2 entries 01 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; ppstop client >> $PPLOGS/ppstop_client.out 2>&1)' 02 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; ppstart client >> $PPLOGS/ppstart_client.out 2>&1)' have been replaced by the 10.0.1 entry 01 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; restart_ppay CLIENT >> $PPLOGS/restart_client.out 2>&1)' e. training subsytem is obsolete The 9.2.2 entries
05 00 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; trastop.crond >> $PPLOGS/trastop.out 2>&1)' 06 00 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; trastrt.crond >> $PPLOGS/trastrt.out 2>&1)' have been obsoleted in the 10.0.1 release f. purge files, tables, provisioning The 9.2.2 entries 20 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; purgeFile.sh >> $PPLOGS/purgeFile.out 2>&1)' 40 2 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; purgeTable.sh -f $PPHOME/etc/purgeProvConfig >> $PPLOGS/purgeProv.out 2>&1)' 10 4 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; purgeTable.sh >> $PPLOGS/purgeTable.out 2>&1)' have been replaced by the 10.0.1 entries 20 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.PURGE.purgeFiles >> $PPLOGS/purgeFile.out 2>&1)' 40 2 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.PURGE.purgeProv >> $PPLOGS/purgeProv.out 2>&1)' 10 4 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.PURGE.purgeTables >> $PPLOGS/purgeTable.out 2>&1)' 10 4 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.PURGE.purgeReservations >> $PPLOGS/purgeReservations.out 2>&1)' The purge of Reservations is new to the 10.0 release. g. batch activations and batch sms
The 9.2.2 entries 0 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; batch_activate_nightly >> $PPLOGS/batch_activate.out 2>&1)' 0 7 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; batch_sms_nightly >> $PPLOGS/batch_sms_nightly.out 2>&1)' have been replaced by the 10.0.1 entries 0 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.batch_activate_nightly >> $PPLOGS/batch_activate.out 2>&1)' 0 7 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.batch_sms_nightly >> $PPLOGS/batch_sms_nightly.out 2>&1)' h. reset free pool The 9.2.2 entry 21 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; resetSelectedFreepool.ksh >> $PPLOGS/resetSelectedFreepool.out 2>&1)' has been replaced by the 10.0.1 entry 21 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.resetSelectedFreepool >> $PPLOGS/resetSelectedFreepool.out 2>&1)' i. reload of preRaters and raters The 9.2.2 entries 10 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; reloadPreRater >> $PPLOGS/reloadPreRater.out 2>&1)' 10 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; reloadGceRater >> $PPLOGS/reloadGceRater.out 2>&1)'
10 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; reloadPostRater >> $PPLOGS/reloadPostRater.out 2>&1)' have been replaced by the 10.0.1 entries 10 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.REFRESH.preRater >> $PPLOGS/reloadPreRater.out 2>&1)' 10 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.REFRESH.gceRater >> $PPLOGS/reloadGceRater.out 2>&1)' 10 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.REFRESH.gcpRater >> $PPLOGS/reloadGcpRater.out 2>&1)' 10 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.REFRESH.ctp1Rater >> $PPLOGS/reloadCtp1Rater.out 2>&1)' 10 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.REFRESH.ctp3Rater >> $PPLOGS/reloadCtp3Rater.out 2>&1)' 10 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.REFRESH.postRater >> $PPLOGS/reloadPostRater.out 2>&1)' j. phone card reconciliator The 9.2.2 entry 30 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; pcReconciliator >> $PPLOGS/pcReconciliator.out 2>&1)' has been replaced by the 10.0.1 entry 30 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.pcReconciliator >> $PPLOGS/pcReconciliator.out 2>&1)' k. service usage reset
The 9.2.2 entry 20 4 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; serviceUsageReset $PPLOGS/serviceUsageReset.out 2>&1)' has been replaced by the 10.0.1 entry 20 4 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.serviceUsageReset $PPLOGS/serviceUsageReset.out 2>&1)' l. Alcatel MMS retrieval A new entry has been added in 10.0+ for invoking the Alcatel MMS batch task. 20 4 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.alcatelMMS $PPLOGS/alcatelMMS.out 2>&1)' m. restart of api subsystem processes The 9.2.2 entry 15 0 * * 0 ksh -c '(. $HOME/.profile > /dev/null 2>&1; ppstart api >> $PPLOGS/ppstart_api.out 2>&1)' has been replaced by the 10.0.1 entry (NOTE: the entry is commented out by default) #15 0 * * 0 ksh -c '(. $HOME/.profile > /dev/null 2>&1; restart_ppay API >> $PPLOGS/restart_api.out 2>&1)' n. insertion of defaul cell site data The 9.2.2 entry 0 1 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; insert_deflt_cell.ksh >> $PPLOGS/insert_deflt_cell.log 2>&1)' Has been replaced by the 10.0.1 entry
30 1 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.insert_deflt_cell >> $PPLOGS/insert_deflt_cell.log 2>&1)' o. partition table management (credit card, data usage, mobile number portability) The 9.2.2 data billing entries # Uncomment the following job if enabling data billing. # May require update of $PPHOME/etc/xml/purgeTable.xml to set tablespace and # retention information. # Set value of 'zone' according to correct corresponding entry in # the file $PPHOME/etc/xml/timezones.xml in lines matching 'TIMEZONE name="zone" # Example: TIMEZONE=PacUsa (sets Pacific standard time # 30 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; $PPHOME/bin/apf_process -name purgeTable -root $PPHOME/etc/xml -file purge Tables.xml -entity TIMEZONE=zone >> $PPLOGS/createDataBillingUsagePartitions.log 2>&1)' #-# Add the Prepay Data Export jobs using the following pattern. #35 15 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; $PPHOME/bin/dataExport -class InNwi name InNwi -root /prepay/etc/xml -fil e prepay_data_export_main.xml -debug 0 -entity PPHOME=PPAY -entity INSTANCE=0 -entity PPLOGS=/prepay/logs -entity MSG_LEVEL=0 -entit y PP_DATA_EXPORT_FILE_SIZE="2" -entity PP_DATA_EXPORT_SCHEDULE="R" -entity PP_DATA_EXPORT_PPASID="777" -entity PP_DATA_EXPORT_TYPE=" CDR" -entity PP_DATA_EXPORT_PERIOD="MONTHLY" -entity PP_DATA_EXPORT_SUBSCRIPTION_TYPE=1 -entity PP_DATA_EXPORT_FILE_TYPE="ASN" >>/pr epay/logs/dataExport.out 2>&1)' #Valid values for PP_DATA_EXPORT_TYPE are: CDR, UDR, FEE, PAYMENT, ADJUSTMENTS
#Valid values for PP_DATA_EXPORT_PERIOD are: DAILY, WEEKLY, MONTHLY #Valid values for PP_DATA_EXPORT_SUBSCRIPTION_TYPE are: 1(PREPAY), 2(ICC), 3(PREPAY OVERDRAFT) #Valid values for PP_DATA_EXPORT_FILE_TYPE are: ASN have been replaced with these 10.0.1 entries # Partitioning /purging # # May require update of $PPHOME/etc/xml/purgeTable.xml to set tablespace and # retention information. # 30 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.partitionDataTables >> $PPLOGS/partitionDataTables.log 2>&1)' 30 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.partitionCreditCardTables >> $PPLOGS/partitionCreditCardTables.log 2>&1)' 30 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.partitionMNPTables >> $PPLOGS/partitionMNPTables.log 2>&1)' p. data export The following cron entries can be configured to support the data export functionality at a daily, weekly, monthly frequency. # Add the Prepay Data Export jobs using the following pattern. #35 15 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch DAILY.dataExport >>/prepay/logs/dataExportDaily.out 2>&1)' #35 15 0 * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch WEEKLY.dataExport >>/prepay/logs/dataExportWeekly.out 2>&1)' #35 15 0 1 * ksh -c '(. $HOME/.profile > /dev/null 2>&1; start_ppay_batch MONTHLY.dataExport >>/prepay/logs/dataExportMonthly.out 2>&1)' # see /prepay/etc/xml/start_ppay_batch.xml for export types
Once the crontab template for 10.0.1 has been customized as desired, load it. cp $PPHOME/bin/ppadm.crontab crontab.pp10 vi crontab.pp10 crontab crontab.pp10 crontab -l
4.16.1 serviceDirectory.sample
Use the 10.0.1 serviceDirectory.cfg.sample file to create a 10.0.1 serviceDirectory configuration file. Use the 9.2.2 version as a reference when creating the 10.0.1 file. For all Simplex configurations, substitute the hostname of the PrePay server for all occurrences of localhost in this file. For all Distributed Architecture configurations, use the serviceDirectory.sample.da configuration file template as the starting file to then modify with installation specific information. The hostname to enter can be different from the default hostname of the server if a private LAN has been established within the rack using secondary network interface cards. For example, if an SDP has a default hostname of sunlab3 but uses a secondary NIC called sunlab3-ce1 for private connections to the SPT and SCP, specify sunlab3-ce1 as the hostname in this file.
4.16.2 switchInterface.cfg.sample
There were three commented out entries added to the 10.0.1 switch interface configuration template, switchInterface.cfg.sample. #0-57-1 profile capDefault.prf
4.16.3 winDefault.prf.sample
There were some minor modifications made to the 10.0.1 winDefault.prf.sample configuration file. If this interface is active on the system being upgraded, compare the 9.2.2 winDefault.prf with this new template and determine if changes are required.
This feature is optional and does not require purchase of a license option. To enable this functionality, review and configure as appropriate. Business configuration setup of credit card parameters for company/operating unit (Refer to the Business Configuration Guide for detailed information) API entity variables as defined in prepay_api_entities.xml
There are several entities that should be reviewed and modified if appropriate for the credit card functionality. Port to connect to payment gateway server. The value here is currently ignored. Default HTTP and HTTPS ports are used (80 and 443 respectively). <!ENTITY CREDIT-CARD-PROCESSING.Payment_Gateway_Server_Port "9081"> Value of true will activate any test features implemented by a specific payment gateway interface. When enabled for the payment gateway, the x_test_request field of the payment gateway request will be set to true. <!ENTITY CREDIT-CARDPROCESSING.Payment_Gateway_Server_Test_Mode "false"> Amount of time in seconds to wait before timing out on the response from the payment gateway. <!ENTITY CREDIT-CARDPROCESSING.Payment_Gateway_Response_Timer "10"> Type of payment gateway. Value of Stub indicates use the stub payment gateway. Value of Aim instructs to use Authorize.Net AIM payment gateway. <!ENTITY CREDIT-CARD-PROCESSING.Payment_Gateway_Type "Aim"> Types of credit cards accepted by carrier. Values are VS, MC, DC, AX. Format is a comma separated list with no spaces. If a credit card request is submitted with of a type of anything other than the types contained in this list, the request is rejected. <!ENTITY CREDIT-CARD-PROCESSING.Accepted_Credit_Card_Types "MC,VS,DC,AX"> Indicates to the GUI if it should require a postal code to be entered as part of payment gateway validation. <!ENTITY CREDIT-CARD-PROCESSING.Postal_Code "OFF"> Indicates to the GUI if it should require the credit cards security code to be entered as part of payment gateway validation.
<!ENTITY CREDIT-CARD-PROCESSING.Card_Code "OFF"> The URL of the payment gateway is specified in $PPHOME/etc/xml/prepay_global_entities.xml. <!ENTITY PAYMENT_GATEWAY HERE"> "<SPECIFY PAYMENT GATEWAY URL
SQL scripts to enable/disable the feature /ppay/sql/AutoPayment_Schema_Upgrade.sql /ppay/sql/AutoPayment_Schema_Revert.sql Instructions to ENABLE the AutoPayment feature ============================================== 1.Run the script 'ppay/sql/AutoPayament_Schema_Upgrade.sql' (to getdatabase schema ready) 2.Update the value 'autoPayment.enabled' to "TRUE" in /prepay/etc/xml/prepay_process_control_entities.xml 3.Start the daemon AutoPayamentMonitor (start_ppay API.AutoPayamentMonitor) Instructions to DISABLE the AutoPayment feature =============================================== 1.Stop the daemon AutoPayamentMonitor (stop_ppay API.AutoPayamentMonitor) 2.Update the value 'autoPayment.enabled' to "FALSE" in /prepay/etc/xml/prepay_process_control_entities.xml 3.Please run the script 'ppay/sql/AutoPayament_Schema_Revert.sql'
SQL scripts to enable/disable the feature /ppay/sql/PaymentAwards_Schema_Upgrade.sql /ppay/sql/PaymentAwards_Schema_Revert.sql Instructions to ENABLE the PaymentAwards feature ================================================ 1.Run the script 'ppay/sql/PaymentAwards_Schema_Upgrade.sql' (to getdatabase schema ready) 2.Update the value 'paymentAwards.enabled' to "TRUE" in /prepay/etc/xml/prepay_process_control_entities.xml 3.Start the daemon PaymentAwardsMonitor (start_ppayAPI.PaymentAwardsMonitor) Instructions to DISABLE the PaymentAwards feature ================================================ 1.Stop the daemon PaymentAwardsMonitor (stop_ppay API.PaymentAwardsMonitor) 2.Update the value 'paymentAwards.enabled' to "FALSE" in /prepay/etc/xml/prepay_process_control_entities.xml 3.Run the script 'ppay/sql/PaymentAwards_Schema_Revert.sql'
Instructions to ENABLE the EmailNotification feature ===================================================== 1.Run the script '/ppay/sql/EmailNotify_Schema_Upgrade.sql' first to get the database schema ready 2.Update the access_rater.xml (/prepay/etc/xml).Change the value of the attribute "enabled" of Tag 'TASK' identified by name="EmailNotifyExpiringAcctsTask"; to "TRUE" 3.Update the value 'emailNotify.enabled' to "TRUE" in /prepay/etc/xml/prepay_process_control_entities.xml 4.Start the daemon EmailNotifyMonitor (start_ppay API.EmailNotifyMonitor) Instructions to DISABLE the EmailNotification feature ===================================================== 1.Stop the EmailNotifyMonitor daemon (stop_ppay API.EmailNotifyMonitor) 2.Update the value 'emailNotify.enabled' to "FALSE" in /prepay/etc/xml/prepay_process_control_entities.xml 3.Update the access_rater.xml (/prepay/etc/xml).Change the value of the attribute "enabled" of Tag 'TASK' identified by name="EmailNotifyExpiringAcctsTask"; to "FALSE" 4.Run the script'/ppay/sql/EmailNotify_Schema_Revert.sql'
4.17.10 CTPv3.6
Releases prior to 10.0 supported CTP version 1. With the release of PrePay version 10.0, the architecture can now support an installation where a CTP version 1 AND/OR CTP version 3 interfaces are running concurrently or separately. CTP version 1 provides basic data billing support. As clients wish to provide many different types of data-based services, more robust data billing support will be needed. CTP version 3 provides this and is now supported in the 10.0+ releases of PrePay. For an existing client where CTP v1 is configured, the following steps will need to be performed to enable this under the new 10.0.1 XML configuration. Modify prepay_process_control_entities.xml and change the entity value to TRUE <!ENTITY ctp1.enabled "FALSE">
Modify /etc/services as mentioned in a previous section. Modify $PPHOME/etc/serviceDirectory as mentioned in a previous section. Modify prepay_process_control_entities.xml to specify desired data rating process counts.
To enable for CTP v3 execute the following steps: Modify prepay_process_control_entities.xml and change the entity value to TRUE <!ENTITY ctp3.enabled "FALSE">
Modify /etc/services as mentioned in a previous section. Modify $PPHOME/etc/serviceDirectory as mentioned in a previous section. Modify prepay_process_control_entities.xml to specify desired data rating process counts. Refer to the Business Configuration Guide to configure the desired User Defined Services. Note the configuration of the user defined service's service ID to be a composite of the APN service key and rate ID.
If both interfaces are to run concurrently, set both enable flags to TRUE and ensure distinct ports are used. Refer to the serviceDirectory configuration file and /etc/services file for examples.
Awards may be either credits or discounts, as configured in the Subscriber Awards service.
<!ENTITY awdDaemon.enabled
"FALSE">
================================================================= ============== VOICE.TMDS.timingMedServer.0 28712 UP 1-11:34:43 0:29 VOICE.PRERATE.preRater.0 28716 UP 1-11:34:43 1:43 VOICE.PRERATE.preRater.1 28717 UP 1-11:34:43 1:43 VOICE.POSTRATE.postRater.0 28720 UP 1-11:34:43 0:25 VOICE.POSTRATE.postRater.1 28721 UP 1-11:34:43 0:24 VOICE.POSTRATE.postRater.2 28722 UP 1-11:34:43 0:27 VOICE.POSTRATE.postRater.3 28723 UP 1-11:34:44 0:27 VOICE.POSTCALL.postCallWriter.0 28726 UP 1-11:34:44 0:14 VOICE.POSTCALL.postCallWriter.1 28727 UP 1-11:34:44 0:12 VOICE.DEP.depositor.0 28728 UP 1-11:34:44 0:29 VOICE.SWITCH.D7.apmd DOWN VOICE.SWITCH.D7.spmd NONE VOICE.SWITCH.D7.upmd NONE VOICE.SWITCH.D7.scmd NONE VOICE.SWITCH.D7.tcmd NONE VOICE.SWITCH.D7.netd NONE VOICE.SWITCH.D7.alarmd NONE VOICE.SWITCH.D7.mlogd NONE VOICE.SWITCH.D7.dsmd NONE VOICE.SWITCH.D7.dkmd NONE VOICE.SWITCH.D7.isupd NONE -
VOICE.SWITCH.SS7TCAP.ss7Intf 1:13 VOICE.SWITCH.SS7TCAP.ss7TcapParser.0 0:12 VOICE.SWITCH.SS7TCAP.ss7TcapParser.1 0:13 VOICE.SWITCH.CAMEL.camelIntf.0 393 VOICE.SWITCH.AINICC.ainIccIntf.0 2:50 VOICE.SWITCH.INAPCS1.inapcs1Intf.0 4 VOICE.SWITCH.ISUP.wmmMain VOICE.awdDaemon 0:12 -
28760 UP
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 100
Pprp0110.rpt PrePay Free Pool Assignment Report Pprp0120.rpt PrePay Free Pool Unassignment Report Pprp0130.rpt Call Analysis Report - Obsolete Pprp0140.rpt Roamer Reconciliation Summary Report Obsolete Pprp0150.rpt - Ported Number Report (new in 10.0) Pprp0160.rpt - MDN Utilization Report (new in 10.0) Pprp0170.rpt - MIN Utilization Report (new in 10.0) Pprp0180.rpt - Failed Credit Card Transaction Report (new in 10.0) Pprp0190.rpt - Credit Card Transaction Report (new in 10.0) Pprp0900.rpt - Active Subscriber Revenue Report (new in 10.0)
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 101
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 102
Verify no errors appear in the logs before continuing on to apply PrePay patches.
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 103
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 104
For CCI, refer to $PPHOME/etc/etc_service_cci.sample. For GCP, refer to $PPHOME/etc/etc_service_gcp.sample. For INI, refer to $PPHOME/etc/etc_service_ini.sample. su edit /etc/services $re /prepay/etc/etc_service_XXX.sample wq 2. Create a separate file system called /udr for the bytestream files generated by the GCE processes. Sizing guidelines: bytestream data will require approximately 1.4 GB per million billing events. 3. Modify the following entries in the file $PPHOME/etc/prepay.default: Change the file system for byte-stream files from /cdr to /udr. Make this change for all data billing postCallWriter processes. Do NOT change the voice billing process *.postCallStream from using the /cdr file system. gciPostCallWriter.PostCallBSPath gciPostCallWriter.UsageDetailBSPath cciPostCallWriter.PostCallBSPath cciPostCallWriter.UsageDetailBSPath gcpPostCallWriter.PostCallBSPath gcpPostCallWriter.UsageDetailBSPath iniPostCallWriter.PostCallBSPath iniPostCallWriter.UsageDetailBSPath Change the *.totalNwiNumber to the desired number of general charging interface processes for each specific protocol. For example, if 3 GCI processes are to be running and listening on the first three GCI ports, set gci.totalNwiNumber to 3. Possible entries include: gci.totalNwiNumber cci.totalNwiNumber gcp.totalNwiNumber ini.totalNwiNumber
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 105
4. Modify the following entries in the file $PPHOME/etc/purgeFileConfig to reference the new /udr file system. By default, the location is /cdr, but should be changed if data billing is implemented. Entries to update, changing cdr to udr: BYTE_DATA 10 /cdr/*/byte_stream.*/data @YYYYMMDD.*.attr RATED_DATA 10 /cdr/*/rated.*/data @YYYYMMDD.*.attr @YYYYMMDD.*.dat @YYYYMMDD.*.dat
5. Review the location of the tables created for data billing (RATE_COMPONENT_USAGE, USAGE_CHARGE, USAGE_DETAIL). During the upgrade, the default tablespace was set as DDATA02 and IINDEX02. Consider re-creating these tables in a new tablespace if data billing is implemented. Review the contents of the file $PPHOME/etc/xml/purgeTables.xml. The tablespace references in this file should be updated to match the tablespace being used for these tables. 6. Add a new cron entry for the ppadm user to regularly create new and drop old partitions of these tables. Review the file $PPHOME/etc/xml/timezones.xml and select an appropriate timezone name, for example PacUSA to use as a timezone reference in the batch command. Run the command at the UNIX prompt as a preparation step to create initial table partitions before generating billing messages into the GCI/GCE subsystem. 7. This following example cron entry runs this job at 12:30am each night and is set for a system on US Pacific Time. (Insert it as one long single line. This cron entry can also be copied and modified from the file $PPHOME/bin/ppadm.crontab.) Example (of a cron entry): 30 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1; $PPHOME/bin/apf_process -name purgeTable -root $PPHOME/etc/xml -file purgeTables.xml -entity TIMEZONE=PacUSA >> $PPLOGS/createDataBillingUsagePartitions.log 2>&1)'
Note: For balance query messages, a User Defined Service with the following service identifier must be configured in the database: External Node ID ='BALANCEQUERYNODE'
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 106
Node Service ID ='GCIBALANCEQUERY' For new plan offerings, if this User Defined service is added at time of plan definition, and is made a required service, then all subscribers activated using that plan will have the service initially. For existing plan offerings, where this User Defined service is added after plan creation, a determination must be made for each subscriber of whether or not to add the service. These steps are the same for any new User Defined service; subscribers on existing plans do not automatically acquire the service when the plan is modified.
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 107
Post-Upgrade Steps
Caution: Continue with this section only if you are NOT rolling back.
6.1
1. Review the files that configure the purging schedule for files and tables. Modify these files to reflect any changes that may be required by the customer for data retention. Lightbridges recommended retention periods are specified in the released configuration files: $PPHOME/etc/purgeFileConfig $PPHOME/etc/purgeTableConfig $PPHOME/etc/purgeProvConfig 2. Login as ppadm user to make any changes: su ppadm
6.2
Example: cp
Review and update any other .sample files provided in $PPHOME/etc and copy them into place if appropriate. lineRangeTable.dat.sample lineRangeTable.dat
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 108
Sample files: jmbSrvcMapFile.sample lineRangeTable.dat.sample (IVR Router) MCnnn.CAPII.cfg.sample MCnnn.SMPP.cfg.sample emergencyNumberTable.cfg.sample -Used for specific HLR -Used for payments on multiple servers -Use for SMS option -Use for SMS option Use for specific MSC type
6.3
Review the new PrePay 10.0.1 ppadm.crontab and compare to the previous copy saved during preparation. Add custom entries and modify existing jobs to meet the needs of the client. A new crontab entry has been added for purging old partitions from the data billing tables. This entry requires a timezone be entered. Read the comments in the ppadm.crontab file and set appropriately. cd $PPHOME/bin diff /<temparea>/work/ppadm.crontab.pre10_0_1 ppadm.crontab vi ppadm.crontab {make customizations} crontab ppadm.crontab
6.4
cd rm rm rm rm rm rm rm rm rm
The following files, if they exist, may be purged from the $PPHOME/etc directory when the upgrade is completed:
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 109
6.5
If the verification step is successful and no rollback is required, upgrade the remaining client workstations to the 10.0.1 version.
6.6
When the upgrade is complete and there is no plan to perform a rollback, the upgrade working directory may be removed. Perform this step on the server where the PrePay service group is ONLINE. su cd /<temparea> rm -rf work *** This completes the PrePay 10.0.1 Upgrade. ***
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 110
A.1
Preface
All PrePay systems should have Veritas Foundation Suite installed. This consists of Volume Manager (VxVM) and Veritas File System (VxFS). Some clients may also have the Veritas Database Edition for Oracle installed. This product is not covered by these instructions and is the responsibility of the client to coordinate its upgrade with Foundation Suite. Veritas Cluster Server (VCS) is not covered in this document. After Foundation Suite has been upgraded to version 4.2, Maintenance Patch ? (MP?) must be installed. This consists of several Solaris patches that are installed individually. A pre-requisite to MP? is the installation of Suns SAN Foundation Kit. This can be installed before upgrading Foundation Suite to 4.x. [End of DrW changes for Veritas stuff. I dont know the details enough to continue.] PrePay systems running on older Sun StorEdge A5x00 disk arrays will need to have firmware reviewed and upgraded prior to installing the SAN Foundation Kit. Packages and patches to apply include:
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 111
Veritas Volume Manager 3.5 Veritas File System 3.5 Individual patches for VxVM with MP2 and VxFS with MP2.
A.2
Required Materials
Clients may choose to acquire their own Sun and/or Veritas software. Lightbridge provides CDs with these packages. The following materials are needed for installing the above-mentioned software in the system. Veritas Volume Manager 3.5 CD Veritas File System 3.5 CD Veritas VxVM with MP2 and VxFS with MP2
A.3
The instructions below show how to upgrade Veritas using the CD drive. These steps can be replaced by using the staging area created during the preparation phase. Reboot the system in single-user mode. You must be using the servers console to continue working on the upgrade after switching to single-user mode. su init S
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 112
If the command errors, try a different disk from the rootdg disk group: 2. Repeat step one above but for each disk group. Specify a different disk that is a member of the desired disk group. 3. Save /rootdgdb.out to a safe place. 4. Use the tar command to save the Veritas license and volume definitions. cd /etc/vx tar cvf vxsave.tar reconfig.d volboot elm 5. Check the tar file contents by using the command: tar tvf vxsave.tar
A.5 CD
Insert the VxVM CD. Load and mount the CD-ROM by starting the volmgt daemon. /etc/init.d/volmgt start
6.6.1
1. Run the upgrade_start -check script to find any problems that exist which could prevent a successful upgrade. This script reports errors if found. Otherwise, it reports success and you can proceed with running the upgrade_start script. /cdrom/cdrom0/volume_manager/scripts/upgrade_start -check 2. Run the upgrade_start script to prepare the previous release of VxVM for its removal using the following command: /cdrom/cdrom0/volume_manager/scripts/upgrade_start 3. When the scripts successfully completes, execute a df k command. Notice the disk partition names for root, usr (if it is a separate file system), and var. If the upgrade_start script worked correctly, after the reboot, these will change to regular disk partition names.
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 113
df -k Example output: Filesystem /dev/vx/dsk/rootvol /dev/vx/dsk/usr /proc fd mnttab /etc/mnttab /dev/vx/dsk/var swap # kbytes used 1765324 1538533 1373432 991949 0 0 0 0 0 0 2055705 2435464 avail capacity 173832 90% 326546 76% 0 0% 0 0% 0 0% 18% 0% Mounted on / /usr /proc /dev/fd /var /var/run
4. Reboot the system in single-user mode. reboot -- -s 5. Execute a df k command to verify that Volume Manager does not control the boot disk. # df -k 6. Example output: Filesystem /dev/dsk/c0t0d0s0 /dev/dsk/c0t0d0s6 /proc fd mnttab /etc/mnttab /dev/dsk/c0t0d0s7 swap # kbytes used 1765324 1538529 1373432 991949 0 0 0 0 0 0 2055705 409568 avail capacity 173836 90% 326546 76% 0 0% 0 0% 0 0% 18% 0% Mounted on / /usr /proc /dev/fd /var /var/run
7. Reboot the system again in single-user mode. su reboot -- -s Note: You will need to mount /opt manually before you can run pkgrm to remove the VxVM packages if /opt is on its own partition.
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 114
A.7
A.8 CD
1. Insert the VxVM CD. Load and mount the CD-ROM by starting the volmgt daemon. /etc/init.d/volmgt start The Veritas Licensing package is the same for VxFS, VCS, and VxVM. If it has already been loaded by one of the other packages, then this step can be skipped. Add the VxVM 3.5 licensing package with the following command: pkgadd -d /cdrom/cdrom0/volume_manager/pkgs VRTSvlic
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 115
Example output: Processing package instance <VRTSvlic> from </cdrom/storage_solutions_solaris_3.5cd1/volume_manager/p kgs> VERITAS License Utilities (sparc) 3.00.007d VERITAS Software Corp VERITAS License Utilities 3.00.007d Using </> as the package base directory. ## Processing package information. ## Processing system information. 6 package pathnames are already properly installed. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts that will be executed with superuser permission during the process of installing this package. Do you want to continue with the installation of <VRTSvlic> [y,n,?]y Installing VERITAS License Utilities as <VRTSvlic> ## Installing part 1 of 1. /etc/vx/licenses/db/dbacoralkl.txe /etc/vx/licenses/db/dbeddb2lkl.txe . . . . /sbin/vxlicrep /sbin/vxlictest [ verifying class <none> ] ## Executing postinstall script. Installation of <VRTSvlic> was successful. 2. Add the VxVM 3.5 package with the following command: pkgadd -d /cdrom/cdrom0/volume_manager/pkgs VRTSvxvm
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 116
Example output: Processing package instance <VRTSvxvm> from </cdrom/storage_solutions_solaris_3.5cd1/volume_manager/p kgs> VERITAS Volume Manager, Binaries (sparc) 3.5,REV=06.21.2002.23.14 Copyright 1996-2002 VERITAS Software Corp. All rights reserved. VERITAS, VERITAS SOFTWARE, the VERITAS logo and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the USA and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. This package, VxVM 3.5, is supported on Solaris 2.6, 7, 8, and 9. You appear to be running Solaris 8. Press ENTER to install VxVM 3.5 for Solaris 8, or enter another Solaris version number if you are certain that you want to install the drivers for a different release of Solaris. Install for which version of Solaris? [9, 8, 7, 2.6] (default: 8): Installing VxVM for Solaris 8 Using </> as the package base directory. ## Processing package information. ## Processing system information. 21 package pathnames are already properly installed. ## Verifying package dependencies. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts that will be executed with superuser permission during the process of installing this package. Do you want to continue with the installation of <VRTSvxvm> [y,n,?]y Installing VERITAS Volume Manager, Binaries as <VRTSvxvm> ## Executing preinstall script.
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 117
## Installing part 1 of 1. /etc/init.d/vras-vradmind.sh /etc/init.d/vxnm-vxnetd... /etc/rcS.d/S86vxvm-reconfig <linked pathname> ## Executing postinstall script. Copy /kernel/drv/vxio.SunOS_5.8 to /kernel/drv/vxio... Copy /kernel/drv/vxspec.SunOS_5.8 to /kernel/drv/vxspec... Copy /kernel/drv/sparcv9/vxio.SunOS_5.8 to /kernel/drv/sparcv9/vxio... Copy /kernel/drv/sparcv9/vxspec.SunOS_5.8 to /kernel/drv/sparcv9/vxspec... Copy /sbin/vxconfigd.SunOS_5.8 to /sbin/vxconfigd... Copy /kernel/drv/vxdmp.SunOS_5.8 to /kernel/drv/vxdmp... Copy /kernel/drv/sparcv9/vxdmp.SunOS_5.8 to /kernel/drv/sparcv9/vxdmp... Adding vxdmp driver for SunOS version 5.8... ## Executing postinstall script. Copy /kernel/drv/vxio.SunOS_5.8 to /kernel/drv/vxio... Copy /kernel/drv/vxspec.SunOS_5.8 to /kernel/drv/vxspec... Copy /kernel/drv/sparcv9/vxio.SunOS_5.8 to /kernel/drv/sparcv9/vxio... Copy /kernel/drv/sparcv9/vxspec.SunOS_5.8 to /kernel/drv/sparcv9/vxspec... Copy /sbin/vxconfigd.SunOS_5.8 to /sbin/vxconfigd... Copy /kernel/drv/vxdmp.SunOS_5.8 to /kernel/drv/vxdmp... Copy /kernel/drv/sparcv9/vxdmp.SunOS_5.8 to /kernel/drv/sparcv9/vxdmp... Adding vxdmp driver for SunOS version 5.8... Adding vxio driver for SunOS version 5.8... Adding vxspec driver for SunOS version 5.8... Adding vxspec lines to /etc/devlink.tab... Adding vxdmp lines to /etc/devlink.tab... Running /usr/sbin/devlinks -t /etc/devlink.tab ... Adding vxio vxspec vxdmp lines to /etc/system... Copy liba5k.so.2 to /etc/vx/slib/liba5k_stub.so.2 . . . Copy libc_psr.so.1 to /etc/vx...
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 118
Adding vid=SEAGATE to the list of JBODs... Adding vid=SUN pid=SESS01 (Vicom) to the list of JBODs... Allocating port for Volume Replicator... Port 4145 has been allocated for Volume Replicator use To change, see vrport(1M) command Installation of <VRTSvxvm> was successful. If warnings are displayed that include the string '/etc/vx', ignore them and continue. 3. Add the VxFS packages: pkgadd -d /cdrom/cdrom0/file_system/pkgs VRTSvxfs VRTSfsdoc Example output: Do you want to continue with installation [y,n,?] n 2 packages were not processed! devclust-1# pkgadd -d /cdrom/cdrom0/file_system/pkgs VRTSvxfs VRTSfsdoc Processing package instance <VRTSvxfs> from </cdrom/storage_solutions_solaris_3.5cd1/file_system/pkgs > VERITAS File System (sparc) 3.5,REV=GA06 Copyright (c) 1991 - 2002 VERITAS SOFTWARE CORP. ALL RIGHTS RESERVED. THIS SOFTWARE IS THE PROPERTY OF AND IS LICENSED BY VERITAS SOFTWARE, AND/OR ITS SUPPLIERS. ## Executing checkinstall script. Using </> as the package base directory. ## Processing package information. ## Processing system information. 32 package pathnames are already properly installed. ## Verifying package dependencies. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs.
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 119
The following files are being installed with setuid and/or setgid permissions: /opt/VRTSvxfs/sbin/qioadmin <setuid root> /opt/VRTSvxfs/sbin/qiomkfile <setuid root> /opt/VRTSvxfs/sbin/vxdump <setuid root setgid tty> /opt/VRTSvxfs/sbin/vxquota <setuid root> /opt/VRTSvxfs/sbin/vxrestore <setuid root setgid bin> Do you want to install these as setuid/setgid files [y,n,?,q] y This package contains scripts that will be executed with superuser permission during the process of installing this package. Do you want to continue with the installation of <VRTSvxfs> [y,n,?]y Installing VERITAS File System as <VRTSvxfs> ## Installing part 1 of 1. /dev/fdd <symbolic link> . . . /usr/kernel/drv/sparcv9/qlog [ verifying class <s28b64> ] ## Executing postinstall script. VRTSvxfs: You must reboot the system after pkgadd. Installation of <VRTSvxfs> was successful. Processing package instance <VRTSfsdoc> from </cdrom/storage_solutions_solaris_3.5cd1/file_system/pkgs > VERITAS File System Documentation (sparc) 3.5,REV=GA06e Copyright (c) 1991-2002 VERITAS SOFTWARE CORP. ALL RIGHTS RESERVED. THIS SOFTWARE IS THE PROPERTY OF AND IS LICENSED BY VERITAS SOFTWARE, AND/OR ITS SUPPLIERS. Using </opt> as the package base directory. ## Processing package information. ## Processing system information. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs.
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 120
Installing VERITAS File System Documentation as <VRTSfsdoc> ## Installing part 1 of 1. /opt/VRTSfsdoc/vxfs_ag.pdf /opt/VRTSfsdoc/vxfs_ig.pdf [ verifying class <all> ] Installation of <VRTSfsdoc> was successful. Note: If the pkgadd command returns an error stating patch 108901-03 has not been applied and then exits, the Veritas compressed tar file must be applied. Copy the VxFS package to a work area: mkdir /tmp/vxfs cd /tmp/vxfs cp r /cdrom/cdrom0/file_system/pkgs/VRTSvxfs . cd /tmp Download the file vxfs35-sol8-0204-fix.tar.Z from the Lightbridge CD or ftp://ftp.veritas.com/pub/support/vxfs35-sol8-0204fix.tar.Z. Uncompress and un-tar the file using the command: zcat vxfs35-sol8-0204-fix.tar.Z | tar xf cd vxfs35-sol8-0204-fix ./fix /tmp/vxfs/VRTSvxfs Proceed with the Veritas File System installation: pkgadd d /tmp/vxfs/VRTSvxfs pkgadd -d /cdrom/cdrom0/file_system/pkgs VRTSfsdoc 4. Complete the upgrade typing the following command: /cdrom/cdrom0/volume_manager/scripts/upgrade_finish 5. Perform reconfiguration reboot: reboot -- -r 6. Execute a df k command. Notice the disk partition names for root, usr (if it is a separate file system), and var. If the upgrade_finish script worked correctly, then after the reboot, these will change back to the Volume Manager names. df k Filesystem kbytes used avail capacity Mounted on
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 121
1765324 963113 749252 1373432 1008033 310462 0 0 0 0 0 0 0 0 0 2055705 724916 1269118 2478688 0 2478688
7. During boot, the /etc/init.d/vxvm-startup1 script starts all rootdg volumes listed in /etc/vfstab (which are considered special volumes). This occurs very early in the bootup stage, when only rootdg disk group is imported. If the volume entry in /etc/vfstab does NOT belong to rootdg disk group, then this volume will fail to start and the user is notified of this with the following warning messages: vxvm: Volume <volname> for mountpoint <mnt_point> is not in rootdg disk group; <Cannot start the volume early> The message shown above is repeated for every non-rootdg volume in /etc/vfstab. The volumes fail to start because they are not in the rootdg disk group. Later in the boot process, after the non-rootdg disk groups are imported, the non-rootdg volumes are safely started and mounted. These warning messages occur in VxVM 3.5 only. The warning messages can be safely ignored. After the system completes booting, all volumes are actually started and mounted. (This issue is reported in VERITAS Incident 102047 and will be fixed in VxVM 3.5 Patch 01.) 8. Using the pkgadd command, install the additional packages: VRTSvmdoc,VRTSvmman, VRTSvmpro, VRTSfspro, VRTSob, and VRTSobgui. pkgadd -d /cdrom/cdrom0/volume_manager/pkgs VRTSvmdoc VRTSvmman VRTSob VRTSobgui VRTSvmpro VRTSfspro
A.9 Individual patches for VxVM with MP2 and VxFS with MP2.
Apply Veritas 3.5 MP2 Patch su cd /<temparea>/cd_sw/solaris_patches/Patches zcat 112392-06.tar.Z | tar xvf -
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 122
unzip 113206-10.zip unzip 113203-03.zip unzip 113595-04.zip unzip 113596-03.zip unzip 113210-03.zip patchadd 112392-06 patchadd 113206-10 patchadd 113203-03 patchadd 113595-04 patchadd 113596-03 patchadd 113210-03
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 123
File (.xml)
Variable
in/in_server
checkForPoundInd icator
False if entire dialed digits should be checked for Special Number. True if only check dialed digits starting with #.
prepay_ivr_entities prepay_ivr_entities
New New
New
Y = Default = True post stream values for DATA changed to always be 1:1
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 124
File (.xml)
Variable
prepay_data_rating_ entities prepay_process_con trol_entities prepay_in_processe s prepay_ip_processe s prepay_voice_rating _processes gci_rating_invoke_m essage prepay_data_rating_ entities MDN Rate_Only_Updat es_Accum_Usage New
Now a required parm. Y = RATE-ONLY updates N = RATE-ONY does not update No entry = Assumed Y
Removed redundant entry 1234 3031234567 data format explicitly stated as DD-MON-YYYY HH24:MM:SS
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 125
File (.xml)
Variable
EventstartTimesta mp prepay_voice_rating _processes cap_main prepay_provision_en tities prepay_voice_rating _entities prepay_process_con trol_entities (comments) ss7Intf.qualityOfSe rvice inSrvMsgCtr.enabl ed inIntfMsgCtr.enabl es gceMC.totalNwiNu mber gceMCRater.total GceRaterNumber gceMCDepositor.d epStreamNumber gceMCPostCallWri ter.postStreamNu mber gceMCPostRater. depStreamNumbe r gceMCPostRater. postStreamNumbe r New Added support of multiple camelIntf instances and trace levels 0-10. added comments for DEC3.8 option in provisioning ESN 5 Cleanup unused entries and set gceMC items to 1
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 126
File (.xml)
Variable
SWITCH group moved before TMDS group Added provisioning flags to enable/disable record insertion
New
(as needed)
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 127
Table
Column
Piu_gl_code
New column
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 128
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 129
## WARNING ## # This file is a sample file, showing how to configure different point-codes for # switch interface. # Refer to document, " Pre-pay 10.0 Switch Configuration Consolidation" for more # detailed information related to the configuration. # Configuration for one point-code (or wild-card entry) should be defined on # one line. Continuation char backslash "\" should be used to continue one line. ## Max length of a line is 4096 characters. ## There should be no duplicate entries for any point-code. ## The names of profile files can contain the absolute path - For example, ## /prepay/etc/myWinDefault.prf
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 130
## One sample "profile" is defined for reference. see profileFile.prf.sample # # Examples: # ======== # Default entry - any switch not mentioned shall read from the default.prf profile *-*-* profile default.prf # Network 1 overrides some values in isupDefault.prf with isupNetwork1.prf. #1-*-* profile isupDefault.prf profile isupNetwork1.prf # This switch uses the isupDefault profile, overridden with isupNetwork2.prf, # and specifies a specific switchId in the top level file. #2-2-2 profile isupDefault.prf profile isupNetwork2.prf switchId 25888001 # In this case, all values are specified in the top-level - not recommended. #2-2-3 switchId 25888002 "isupTrunkBlock 22 0" "32 42 0" "isupTrunkBlock 1 1" "32 43 0" "isupTrunkBlock 3 2" "24 44 2" switchProtocolType ISUP isupEricssonNativeTriggerSupport YES #isupDefault profile overridden by isupSingleSwitch profile. #10-20-135 profile isupDefault.prf profile isupSingleSwitch.prf # winDefault.prf defines most of the configuration for this switch, but it # overrides a couple of them (i.e. switchId and winCCDirTimeOut) here. #10-20-136 profile winDefault.prf switchId 233345 winCCDirTimeOut 5
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 131
D.2
capSwitchInterface.cfg.sample
################################################################# ############### # # CAMEL CONFIGURATIONS # ################################################################# ############### # # The configurations for the PPAS CAMEL Switch Interface processes are contained # in profile files. There can be as many profile files as desired. Each profile # should be contained in a separate file (e.g. capDefault.prf). # # Profile configurations can be done on a per MSC level. The association of a # profile configuration to an MSC can be done on the following basis. # # 1. Point Code # Point Code contained in the Calling Party address in the SCCP portion of the # incoming message when the routing mechanism is "ROUTE ON SSN". # # 2. E.164 address # GT Address Signal contained in the Calling Party address in the SCCP portion # of the incoming message when the routing mechanism is "ROUTE ON GT". # # 3. Wild Card # When no specific point code or E.164 GT Address need be specified and default # configuration may be loaded. The wild card characters that are supported are * # and .(dot). * matches zero or more characters while . matches just one character. # # In all these configurations - whether point code or GT address, the association
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 132
# # # # # # # # # # # # # # # # # # # # # # # # # #
is always on an MSC level. Examples: Point Code Based Configurations -------------------------------------0-57-1 profile capDefaultMsc1.prf 0-57-2 profile capDefaultMsc2.prf -------------------------------------E.164 (GT Address) based configurations --------------------------------------16003005001 profile capDefaultMsc3.prf 16003005002 profile capDefaultMsc4.prf --------------------------------------Wild Card configuration -------------------------------------0-57-* profile capDefault1.prf *-*-* profile capDefault2.prf * profile capDefault3.prf 1600300* profile capDefault4.prf 1600.005* profile capDefault5.prf --------------------------------------
D.3
denyAnnouncementTable.cfg.sample
# # denyAnnouncementTable.cfg # # Purpose: # Translate denial announcement codes received by TMDS from preRater to # values in callTreatmentMessage understood by the switch interfaces. # Further evaluation and protocol specific behavior is driven by the # individual protocol configuration files: *.prf
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 133
# # Format : # Denial_reason Announcement_id Announcement_Type # # # Where: # # Denial_reason: (input): The reason for denial assigned by the preRater. # Announcement_id: (output) The announcement identifier mapped to a .prf # file specific to the switch interface handling this # call. # Announcement_type: (output) The announcement type to be used by the # switch interface handling this call. # # The combination of announcement_id and announcement_type indicates to # the switch interface which exact announcement to play. # # For example: # # INPUT: DENIAL REASON INSUFFICIENT BALANCE = 1 # OUTPUT: ANNOUNCEMENT ID INSUFFICIENT BALANCE = 3 # OUTPUT: ANNOUNCEMENT TYPE IVR BASED = 65 # switch config file: winDefault.prf.sample # # Will match the following entry in winDefault.prf.sample: # # "winIvrAnnouncementId 3" "IVR_BASED 3334445555" # # See Also: # winDefault.prf.sample # is41eeDefault.prf.sample # isupDefault.prf.sample # is41pDefault.prf.sample # ... # # Possible values for each for these fields are given below: # # Denial_reason: # =============== # DENIAL REASON NONE = 0
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 134
# # # # # # # # # # # # # # # # # # # # # #
DENIAL REASON INSUFFICIENT BALANCE = 1 below minimum threshold DENIAL REASON INACTIVE = 2 not in active DENIAL REASON BELOW BILLABLE = 3 balance is below billing increment DENIAL REASON BELOW SETUP = 4 balance below required for call duration Announcement ID: =============== ANNOUNCEMENT ANNOUNCEMENT ANNOUNCEMENT ANNOUNCEMENT
# subscriber is # balance
ID ID ID ID
= = = =
0 3 10 11
Announcement Type: ================== ANNOUNCEMENT TYPE NONE ANNOUNCEMENT TYPE SWITCH BASED hard coded # ANNOUNCEMENT TYPE IVR BASED Do not try # values # # ======== # 0 0 0 1 3 16 2 11 16 3 3 16 4 0 0
= 0 = 16 = 65
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 135
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 136
D.4
profileFile.prf.sample
## WARNING## # There should be only one name-value pair per line ## continuation char backslash "\" should be used to continue one line ## see document : "Pre-pay 10.0 Switch Configuration Consolidation" for details# "errorRoutingAction SYSTEM_FAILURE" ROUTE_CALL "errorRoutingAction RESOURCE_SHORTAGE" ROUTE_CALLisupEricssonNativeTriggerSupport YESswitchProtocolType ISUP"isupErrorRoutingAction RESOURCE\_SHORTAGE" ROUTE_CALL" "isupTrunkBlock 1 0" "32 1 0" "isupTrunkBlock 23 1" "24 67 9" "isupTrunkBlock 1 1" "24 2 0" "isupTrunkBlock 29 0" "32 35 1" "isupTrunkBlock 229 1" "31 512 1"
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 137
D.5
is41eeDefault.prf.sample
# The Switch (MSC) protocol types supported by the MSC. # Format: switchProtocolType " <protocolType> " # <protocolType> could be any one of the following: # - "IS41EE" # - "IS41EE ISUP" # switchProtocolType "IS41EE" #%%PROMPTUSER%% modify at installation # IS41EE AnnouncementID # Format: # "is41eeAnnouncementId <announcementID>" "<setupCode>" # # <announcementID> could be any one of the following. # # 1 - Call Duration Info. # 2 - Low Balance Warning # 3 - Insufficient Balance # 4 - Call End Warning (i.e. to indicate call will be disconnected soon). # 5 - Disconnect Warning (i.e. Call is being be disconnected. # 6 - 1 minute Warning (i.e. Call will be disconnected in 1 minute). # 7 - 2 minute Warning (i.e. Call will be disconnected in 2 minutes). # 8 - 3 minute Warning (i.e. Call will be disconnected in 3 minutes). # 9 - 5 minute Warning (i.e. Call will be disconnected in 5 minutes). # 10 - Subsequent Low Balance # 11 - Subsequent Expired. # 12 - First Expiration Warning (The first time expiration warning is hit). # # NOTE: # 1, 2, 3, 10, 11 and 12 are MANDATORY - they must be present. # # PREPAY WOULD DECIDE TO ROUTE THE CALL OR DENY THE CALL.
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 138
# #
<setupCode> :- This parameter is used by the SCP to direct the call setup treatment to be applied by the MSC.
# #This contains the value of the announcement related fields of the SetupCode parameter sent in the response message to the IS41ee Pre-Call Query. # # <setup Digits> Could be any one of the following: # # 00 "00" Do Not play announcement; route the call. # 10 "16" Call duration announcement; Play MSC or IVR announcement; # route the call. # 11 "17" Low balance; Play MSC or IVR announcement and route the call. # 20 "32" Call duration announcement; Play MSC or IVR announcement; # terminate the call on MSC announcement completion or IVR # release. # 21 "33" Low balance; Play MSC or IVR announcement and terminate the call on MSC announcement completion or IVR release. # 30 "48" Call duration announcement; Play IVR announcement; # terminate the call on IVR release. # 31 "49" Low balance announcement; Play IVR announcement; # terminate the call on IVR release. # 40 "64" Call duration announcement; Play IVR announcement; # route the call on IVR release. # 41 "65" Low balance announcement; Play IVR announcement; route the call on IVR release. # "is41eeAnnouncementId 1" "16" "is41eeAnnouncementId 2" "65" "is41eeAnnouncementId 3" "32" "is41eeAnnouncementId 4" "32" "is41eeAnnouncementId 10" "49" "is41eeAnnouncementId 11" "32" "is41eeAnnouncementId 12" "00" #
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 139
# Configuration to determine the Routing Action on prepay rating errors. # Format: # "errorRoutingAction <errorCause>" "<RoutingAction> [announcement ID]" # # <errorCause> - Could be one of the following: # # 1 = RESOURCE_SHORTAGE : A resource for rating the call is temporarily unavailable. # # 2 = SYSTEM_FAILURE : A temporary failure has occurred while the call was being rated. # # 3 = UNKNOWN_SUBSCRIBER : Subscriber is NOT a valid Prepay subscriber. # # <RoutingAction> - The configured routing action. Could be one of the following: # # ROUTE_CALL : Route/Terminate the call. # # DENY_CALL : Deny call routing/termination. # # PLAY_ANNC_AND_ROUTE_CALL : Play an announcement and then Route/Terminate the call. # # PLAY_ANNC_AND_DENY_CALL : Play an announcement and then deny call Routing/Termination.
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 140
D.6
# # # # # #
CapDefault.prf.sample
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%% This file contains a description of the "Switch Interface" configurable parameters for CAP2. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%
# # The Switch (MSC) protocol types supported by the MSC. # Format: switchProtocolType "<protocolType>" # # <protocolType> could be any one of the following: # - "CAP2" # switchProtocolType "CAP2" #%%PROMPTUSER%% modify at installation # # CAP Announcement ID definitions. CAP announcements are IVRbased only. # # Formats: # # 1. IVR-Based Announcement # ====================== # # "cap2AnnouncementId <prepayAnncID>" "IVR_BASED <IVRDigits> <maxTime>" # # 2. No Announcement - No announcement is to be played for specified Announcement ID, <prepayAnncID> # =============== # # "winAnnouncementId <prepayAnncID>" "NO_ANNOUNCEMENT" # # # <prepayAnncID> Could be one of the following:
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 141
# # # # # # # # # #
1 2 3 4 5 6 7 8 9
# 10 # 11 # 12 # # # # # #
Call Duration Information Low Balance Warning Insufficient Balance Call End Warning (i.e. to indicate call will be disconnected soon). Disconnect Warning (i.e. Call is being be disconnected. 1 minute Warning (i.e. Call will be disconnected in 1 minute) 2 minute Warning (i.e. Call will be disconnected in 2 minutes) 3 minute Warning (i.e. Call will be disconnected in 3 minutes) 5 minute Warning (i.e. Call will be disconnected in 5 minutes) Subsequent Low Balance Warning Subsequent Expiration Warning First Expiration Warning (The first time expiration warning is hit). Identifies the IVR Routing digits.
<IVRDigits>
<maxTime> - Identifies the maximum time for this announcement Examples of IVR-Based announcements are:
# "cap2AnnouncementId 1" "IVR_BASED 4445556666 20" # "cap2AnnouncementId 2" "IVR_BASED 5556667777 30" # "cap2AnnouncementId 0" "IVR_BASED 0001112222 10" "cap2AnnouncementId 1" "IVR_BASED 1112223333 11" "cap2AnnouncementId 2" "IVR_BASED 2223334444 60" "cap2AnnouncementId 3" "IVR_BASED 3334445555 13" "cap2AnnouncementId 4" "IVR_BASED 3334445555 14" "cap2AnnouncementId 5" "IVR_BASED 3334445555 15" "cap2AnnouncementId 6" "IVR_BASED 3334445555 16" "cap2AnnouncementId 10" "NO_ANNOUNCEMENT" "cap2AnnouncementId 11" "NO_ANNOUNCEMENT" "cap2AnnouncementId 12" "IVR_BASED 5554445555 19" #This value is checked against the 'RemainingTime' parameter received in #the MidCallAnnouncement message "cap2MaxCallPeriodDuration" "30"
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 142
#The cause sent in the 'ReleaseCall' message on Forced Disconnect "cap2ReleaseCause" "47" # # Configuration to determine the Routing Action on prepay rating errors. # # Format: # "errorRoutingAction <errorCause>" "<RoutingAction> <prepayAnncID>" # # <errorCause> - Could be one of the following: # # 1 = RESOURCE_SHORTAGE : A resource for rating the call is # temporarily unavailable. # # 2 = SYSTEM_FAILURE : A temporary failure has occurred # while the call was being rated. # # 3 = UNKNOWN_SUBSCRIBER : Subscriber is NOT a valid Prepay # subscriber. # # <RoutingAction> - The configured routing action. Could be one # of the following: # # ROUTE_CALL : Route/Terminate the call. # # DENY_CALL : Deny call routing/termination. # # PLAY_ANNC_AND_ROUTE_CALL : Play an announcement and then # Route/Terminate the call. # # PLAY_ANNC_AND_DENY_CALL : Play an announcement and then # deny call Routing/Termination. # # NOTE : Default <RoutingAction> is set to "DENY_CALL". # --------------------------------------------# # If <RoutingAction> is PLAY_ANNC_AND_ROUTE_CALL or PLAY_ANNC_AND_DENY_CALL, then # <prepayAnncID> specifies the announcement to be played. The announcement # could be either Switch-based or IVR-based. (See <prepayAnncID> above ).
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 143
# # # NOTE:: If <RoutingAction> is either PLAY_ANNC_AND_ROUTE_CALL or PLAY_ANNC_AND_DENY_CALL and <prepayAnncID> is "NO_ANNOUNCEMENT" then default routing action would be either ROUTE_CALL or DENY_CALL. # #"errorRoutingAction 1" "PLAY_ANNC_AND_ROUTE_CALL 2" "errorRoutingAction 1" "ROUTE_CALL" "errorRoutingAction 2" "DENY_CALL" "errorRoutingAction 3" "ROUTE_CALL" # Other error routing action examples are given below: #"errorRoutingAction 1" "ROUTE_CALL" #"errorRoutingAction 1" "DENY_CALL" #"errorRoutingAction 1" "PLAY_ANNC_AND_DENY_CALL 2" #"errorRoutingAction 2" "ROUTE_CALL" #"errorRoutingAction 2" "PLAY_ANNC_AND_ROUTE_CALL 1" #"errorRoutingAction 2" "PLAY_ANNC_AND_DENY_CALL 2" #"errorRoutingAction #"errorRoutingAction #"errorRoutingAction #"errorRoutingAction 3" 3" 3" 3" "ROUTE_CALL" "DENY_CALL" "PLAY_ANNC_AND_ROUTE_CALL 2" "PLAY_ANNC_AND_ROUTE_CALL 5"
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 144
D.7
isupDefault.prf.sample
## WARNING## # There should be only one name-value pair per line# # continuation char backslash "\" should be used to continue one line# # see document : "Pre-pay 10.0 Switch Configuration Consolidation" for details# # ISUP AnnouncementID # # Format: # "isupAnnouncementId <announcementID>" "<IVRDigits>" # # <announcementID> could be any one of the following. # # 1 Call Duration Information # 2 Low Balance Warning # 3 Insufficient Balance # 4 Call End Warning (i.e. to indicate call will be disconnected soon). # 5 Disconnect Warning (i.e. Call is being be disconnected. # 6 1 minute Warning (i.e. Call will be disconnected in 1 minute) # 7 2 minute Warning (i.e. Call will be disconnected in 2 minutes) # 8 3 minute Warning (i.e. Call will be disconnected in 3 minutes) # 9 5 minute Warning (i.e. Call will be disconnected in 5 minutes) # 10 Subsequent Low Balance Warning # 11 Subsequent Expiration Warning # 12 First Expiration Warning (The first time expiration warning is hit). # # NOTE: 1, 2, 3, 4, 5, 10, 11 and 12 are MANDATORY - they must be present. # ==== "isupAnnouncementId 0" "#0399902" "isupAnnouncementId 1" "#0399901"
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 145
"isupAnnouncementId 2" "#0399901" "isupAnnouncementId 3" "#0399902" "isupAnnouncementId 4" "#0399902" "isupAnnouncementId 5" "#0399902" "isupAnnouncementId 6" "" "isupAnnouncementId 7" "" "isupAnnouncementId 8" "" "isupAnnouncementId 9" "" "isupAnnouncementId 10" "#0399902" "isupAnnouncementId 11" "#0399902" "isupAnnouncementId 12" "#0399902" "isupErrorRoutingAction SYSTEM_FAILURE" "DENY_CALL 55" "isupErrorRoutingAction RESOURCE_SHORTAGE" "ROUTE_CALL" # # # # # # # The Switch (MSC) protocol types supported by the MSC. Format: switchProtocolType " <protocolType> "
<protocolType> could be any one of the following: - "ISUP" - "ISUP-ROAM" where ISUP-ROAM is used only for Terminating calls and for SMSCs switchProtocolType "ISUP" #%%PROMPTUSER%% modify at installation # ID of the switch for this point code. this is 8 digit no. switchId 24588001 # configuration to indicate whether switch supports both prepay and # non-prepay subscribers in originating calls. # Format: # isupNonPrepayOrigination "<YES/NO> <REL Cause>" # isupNonPrepayOrigination "YES 20" # configuration to indicate whether switch supports both prepay and # non-prepay subscribers in Termination calls. # Format: # isupNonPrepayTermination "<YES/NO> <REL Cause>" isupNonPrepayTermination "YES 21" #configuration parameter to indicate whether switch is Ericsson Native # Trigger capable. # Format: # isupEricssonNativeTriggerSupport <YES/NO>
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 146
#NOTE: if Switch ProtocolType is ISUP-ROAM, it will have this configuration only isupEricssonNativeTriggerSupport YES #Configuration parameter specifies whether WMM should release incoming call # handled by GMSC if isupEricssonNativeTriggerSupported is YES # Format: # isupGatewayReleaseForEricssonNativeTrigger "<YES/NO> <REL Cause>" isupGatewayReleaseForEricssonNativeTrigger "YES 23" # configuration parameter that indicates what action to be taken if PPL # server return Error. # Format: # "pplErrorMap <errorIndicator>" "<Error Action> <REL Cause>" "pplErrorMap PPL_SERVER_DOWN" PPL_ERROR_ACTION_CONTINUE "pplErrorMap PPL_ERROR_RESPONSE" PPL_ERROR_ACTION_CONTINUE # configuration Parameters that define set of trunk groups from/to which WMM # receives/sends ISUP Messages. These Trunk Groups refers to the trunk group # configuration of Newnet # Format: # "isupTrunkBlock <MO Trunk Grp> <MO Base CCT>" "<No of CCTs> <MT Trunk Grp> # <MT Base CCT>" "isupTrunkBlock 1 0" "32 3 0" "isupTrunkBlock 5 0" "32 7 0" "isupTrunkBlock 9 0" "32 11 0" "isupTrunkBlock 13 0" "32 15 0" "isupTrunkBlock 17 0" "32 19 0" "isupTrunkBlock 21 0" "32 23 0" "isupTrunkBlock 25 0" "32 27 0" "isupTrunkBlock 29 0" "32 31 0" "isupTrunkBlock 33 0" "32 35 0" "isupTrunkBlock 37 0" "32 39 0" "isupTrunkBlock 41 0" "32 43 0" "isupTrunkBlock 45 0" "32 47 0" "isupTrunkBlock 49 0" "32 51 0" "isupTrunkBlock 53 0" "32 55 0" "isupTrunkBlock 57 0" "32 59 0" "isupTrunkBlock 61 0" "32 63 0"
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 147
# The following 4 parameters must be configured properly for ISUP incoming # calls to be handled properly. These settings may be switch vendor type # and/or carrier dependent. # # This is an example of the settings for an Ericsson MSC configured for # loopbacks # isupTerminationIndicator "HOME 4 PRESENT" # isupTldnTerminationParameterId "4 4" # isupSubscriberTerminationParameterId 235 235 # isupDefaultTldn DEFAULT # # This is an example of the settings for a generic switch with TLDN present # only for roaming calls # isupTerminationIndicator "ROAM 40 PRESENT" # isupTldnTerminationParameterId "NONE 4" # isupSubscriberTerminationParameterId 4 40 # In the following line, DEFAULT should be substituted with a value in the TLDN # table, to be used as the TLDN for home incoming calls: # isupDefaultTldn DEFAULT # This is an example of the settings for a generic switch with no TLDN # passed to PPAS, where all incoming calls are rated as home calls # isupTerminationIndicator "HOME 4 PRESENT" # isupTldnTerminationParameterId "NONE NONE" # isupSubscriberTerminationParameterId 4 4 # In the following line, DEFAULT should be substituted with a value in the # TLDN table, to be used as the TLDN for home and roam incoming calls: # isupDefaultTldn DEFAULT # The field in the IAM message used to differentiate home or roam incoming # calls. # Format: # isupTerminationIndicator "<indication> <iamParamId> <indicatorType> [<indicatorValue>]" # <indication> := HOME | ROAM
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 148
# <iamParamId> := IAM message parameter number. Valid numbers are 4 := CALLED_PARTY_NUM # 10 := CALLING_PARTY_NUM # 40 := ORIG_CALLED_NUM # 235 := CHARGE_NUMBER # <indicatorType> := PRESENT | MISSING # <indicatorValue>:= Optional. String with no white spaces. # Used only when <indicatorType> = PRESENT. isupTerminationIndicator "HOME 4 PRESENT" # The field in the IAM message containing the TLDN number for home # and roam incoming calls. # Format: # isupTldnTerminationParameterId "<homeParamId> <roamParamId>" # <homeParamId> := NONE | <iamParamId> (see isupTerminationIndicator) # <roamParamId> := NONE | <iamParamId> (see isupTerminationIndicator) isupTldnTerminationParameterId "NONE NONE" # The field in the IAM message containing the subscriber number for # home and roam incoming calls. # Format: # isupSubscriberTerminationParameterId "<homeParamId> <roamParamId>" # <homeParamId> := NONE | <iamParamId> (see isupTerminationIndicator) # <roamParamId> := NONE | <iamParamId> (see isupTerminationIndicator) isupSubscriberTerminationParameterId "4 4" # Default TLDN used in case isupTldnTerminationParameterId is "NONE". # Format: # isupDefaultTldn <tldn> # WARNING!! <tldn> must exist in the TLDN table. isupDefaultTldn DEFAULT
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 149
D.8
# # # # # #
winDefault.prf.sample
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%% This file contains a description of the "Switch Interface" configurable parameters for WIN-II. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%
# # The Switch (MSC) protocol types supported by the MSC. # Format: switchProtocolType "<protocolType>" # # <protocolType> could be any one of the following: # - "WIN2" # - "WIN2 ISUP" #switchProtocolType "WIN2" #%%PROMPTUSER%% modify at installation # # WIN Announcement ID definitions for Switch-based as well as for IVR-based. # # Formats: # # 1. IVR-Based Announcement # ====================== # # "winAnnouncementId <prepayAnncID>" "IVR_BASED <IVRDigits>" # # Or, # # 2. Switch-Based Announcement # ========================= # # "winAnnouncementId <prepayAnncID>" "SWITCH_BASED <winAnncCodeID_LABEL-1> <winAnncCodeID_LABEL-2>" #
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 150
# # Or, # # 3. No Announcement - No announcement is to be played for specified Announceme nt ID, <prepayAnncID> # =============== # # "winAnnouncementId <prepayAnncID>" "NO_ANNOUNCEMENT" # # # <prepayAnncID> Could be one of the following: # # 1 Call Duration Information # 2 Low Balance Warning # 3 Insufficient Balance # 4 Call End Warning (i.e. to indicate call will be disconnected soon). # 5 Disconnect Warning (i.e. Call is being be disconnected. # 6 1 minute Warning (i.e. Call will be disconnected in 1 minute) # 7 2 minute Warning (i.e. Call will be disconnected in 2 minutes) # 8 3 minute Warning (i.e. Call will be disconnected in 3 minutes) # 9 5 minute Warning (i.e. Call will be disconnected in 5 minutes) # 10 Subsequent Low Balance Warning # 11 Subsequent Expiration Warning # 12 First Expiration Warning (The first time expiration warning is hit. # # NOTE: 1, 2, 3, 4, 5, 10, 11 and 12 are MANDATORY - they must be present. # ==== # # <IVRDigits> - Identifies the IVR Routing digits. # # Examples of IVR-Based announcements are: # # "winAnnouncementId 1" "IVR_BASED 4445556666" # "winAnnouncementId 2" "IVR_BASED 5556667777" #
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 151
<winAnncCodeID_LABEL> - Is a label/identifier to a list of one or more of # WIN/ANSI41 AnnouncementCode parameter values (These identify the switch-based # tone/announcement). e.g. "ANNC_CODE_SET1 ANNC_CODE_SET2" # # The format of the config. parameter that contains the <winAnncCodeID_LABEL> is as follows: # # "winAnnouncementMsgId <winAnncCodeID_LABEL>" "<ListOfAnncCodes>" # # <ListOfAnncCodes> - One or more WIN/ANSI41 AnnouncementCode parameter values . # These identify a switch-based tone/announcement. # The format of the <ListOfAnncCodes> field is: # # Format: # <Tone Value> <ClassOfAnnc> <StandardAnnc Value> <CustomAnnc Value> # # <Tone Value>, and <StandardAnnc Values> are those specified in IS-826. # NOTE: <StandardAnnc Value> and <CustomAnnc Value> may or may not be # present. # # <Tone Values> examples are: # 192 PipTone # 20 Pre-Paid Charging, Insufficient Funds Tone # 21 Pre-Paid Charging, Warning Tone 1 # 22 Pre-Paid Charging, Warning Tone 2 # 24 Pre-Paid Charging, Disconnect Tone # # <ClassOfAnnc> contains one of the following: # - CONCURRENT Play announcements concurrently with any call routing. # - SEQUENTIAL Play all announcements before all call termination or # routing. # # <StandardAnnc Values> examples are: # 152 Pre-Paid Charging, Insufficient Account Balance # 153 Pre-Paid Charging, 5-minute warning
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 152
# # # # # # #
# # Examples of <ListOfAnncCodes> are: # # "20 CONCURRENT" # "21 SEQUENTIAL 152" # # Some examples of Switch-Based announcements are: # # "winAnnouncementId <prepayAnncID>" "SWITCH_BASED <winAnncCodeID_LABEL-1> <win AnncCodeID_LABEL-2>" # # "winAnnouncementId 4" "SWITCH_BASED ANNC_CODE_SET1 ANNC_CODE_SET2" # # "winAnnouncementMsgId ANNC_CODE_SET1" "192 CONCURRENT 154" # "winAnnouncementMsgId ANNC_CODE_SET2" "21 SEQUENTIAL 152" # "winAnnouncementMsgId ANNC_CODE_SET3" "21 SEQUENTIAL 152 244", where # 244 is <CustomAnnc.> # # "winAnnouncementId 0" "IVR_BASED 0001112222" "winAnnouncementId 1" "IVR_BASED 1112223333" "winAnnouncementId 2" "IVR_BASED 2223334444" "winAnnouncementId 3" "IVR_BASED 3334445555" "winAnnouncementId 4" "SWITCH_BASED ANNC_CODE_SET1 ANNC_CODE_SET2 ANNC_CODE_SET3 " "winAnnouncementId 5" "SWITCH_BASED 3" "winAnnouncementId 6" "SWITCH_BASED 5" "winAnnouncementId 10" "NO_ANNOUNCEMENT" "winAnnouncementId 11" "NO_ANNOUNCEMENT" "winAnnouncementId 12" "IVR_BASED 5554445555" "winAnnouncementMsgId ANNC_CODE_SET1" "winAnnouncementMsgId ANNC_CODE_SET2" "192 CONCURRENT 154" "21 SEQUENTIAL 152"
<CustomAnnc Values> identifies Custom announcement codes. These are determined by bilateral agreement with the MSC vendor.
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 153
"21 SEQUENTIAL 152 244" "3 CONCURRENT 30 33" "195 SEQUENTIAL 152" "20 SEQUENTIAL 153" "21 SEQUENTIAL 152" "21 SEQUENTIAL 152"
# # WIN/ANSI-41 DMH_ServiceID parameter value # # Format: winDmhServiceId "<MarketID MarketSegmentID DMH_ServiceID value>" # winDmhServiceId "30 33 30" # # CCDIR Timer value in seconds. If not specified, a default value will be used. # This is the time for which the PPAS will wait for a response from the MSC to # the CallControlDirective Invoke (CCDIR) message. # # In cases where the CCDIR is used to play a mid-call announcement, the MSC # will send the CallControlDirective Result message after the announcement has # been completed - so the value should be large enough to take care of the # time the MSC takes to play the announcement(s) specified in the CCDIR # message. # winCCDirTimeOut "30" # UnRelCallData Timer value in seconds. If not specified, a default value will # be used. # This is the time for which the PPAS will wait for a response from the MSC to # the UnRelCallData Invoke message or CallRecoveryReport Response message. # winUnRelCallDataTimeOut "30" # This is the value of maximum number of times, the ss&TcapParser will try to
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 154
# send UnRelCallData Invoke message, if it does not receives a response, before # the UnRelCallData Timer expires. winMaximumNumberOfRetryAttemptsForUnRelCallData "3" # 'winWinCapabilityRequired' indicates whether PPAS should log an error # message upon receipt of an Analyzed Information message without the # mandatory WinCapability parameter. winWinCapabilityRequired "FALSE" # # # # # # 'winAcgEnabled' indicates whether the PPAS should send one ACG Directive to the MSC, when the PPAS determines that it is in congestion. Format: winAcgEnabled "<value>" <value> contains TRUE or FALSE. Default is FALSE (i.e. do not send ACG Directive, after congestion).
# # See prepay.default for the configuration parameters that determine when PPAS is in congestion. winAcgEnabled "FALSE"
# 'winGapDuration' indicates the length of the time an ACG control should remain in force, before it is removed. # Format: winGapDuration "<value>" # <value> should be one of the following: # 0 IS41_GAP_DURATION_UNKNOWN # 1 IS41_GAP_DURATION_1_SECOND # 2 IS41_GAP_DURATION_2_SECONDS # 3 IS41_GAP_DURATION_4_SECONDS # 4 IS41_GAP_DURATION_8_SECONDS # 5 IS41_GAP_DURATION_16_SECONDS # 6 IS41_GAP_DURATION_32_SECONDS # 7 IS41_GAP_DURATION_64_SECONDS # 8 IS41_GAP_DURATION_128_SECONDS # 9 IS41_GAP_DURATION_256_SECONDS # 10 IS41_GAP_DURATION_512_SECONDS # 11 IS41_GAP_DURATION_1024_SECONDS # 12 IS41_GAP_DURATION_2048_SECONDS # 13 IS41_GAP_DURATION_INFINITE winGapDuration "6"
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 155
# 'winGapInterval' indicates the minimum amount of time that the MSC under # ACG control must wait before sending another query to PPAS. # Format: # # # # # # # # # # # # # # # # # # # winGapInterval "<value>"
<value> should be one of the following: 0 IS41_GAP_INTERVAL_0_SECONDS 1 IS41_GAP_INTERVAL_3_SECONDS 2 IS41_GAP_INTERVAL_4_SECONDS 3 IS41_GAP_INTERVAL_6_SECONDS 4 IS41_GAP_INTERVAL_8_SECONDS 5 IS41_GAP_INTERVAL_11_SECONDS 6 IS41_GAP_INTERVAL_16_SECONDS 7 IS41_GAP_INTERVAL_22_SECONDS 8 IS41_GAP_INTERVAL_30_SECONDS 9 IS41_GAP_INTERVAL_42_SECONDS 10 IS41_GAP_INTERVAL_58_SECONDS 11 IS41_GAP_INTERVAL_81_SECONDS 12 IS41_GAP_INTERVAL_112_SECONDS 13 IS41_GAP_INTERVAL_156_SECONDS 14 IS41_GAP_INTERVAL_217_SECONDS 15 IS41_GAP_INTERVAL_300_SECONDS 16 IS41_GAP_INTERVAL_REMOVE_GAP_CONTROL 17 IS41_GAP_INTERVAL_ONE_HUNDREDTH_OF_A_SECOND # 18 IS41_GAP_INTERVAL_ONE_FOURTH_OF_A_SECOND # 19 IS41_GAP_INTERVAL_HALF_A_SECOND # 20 IS41_GAP_INTERVAL_1_SECONDS # 21 IS41_GAP_INTERVAL_2_SECONDS winGapInterval "2" # 'winPcSsnType' indicates the type of functional entity (e.g. HLR, VLR, MSC) # Format: winPcSsnType "<value>" # <value> should be one of the following: # 0 IS41_PC_SSN_TYPE_UNKNOWN # 1 IS41_PC_SSN_TYPE_SERVING_MSC # 2 IS41_PC_SSN_TYPE_HOME_MSC # 3 IS41_PC_SSN_TYPE_GATEWAY_MSC # 4 IS41_PC_SSN_TYPE_HLR # 5 IS41_PC_SSN_TYPE_VLR # 6 IS41_PC_SSN_TYPE_EIR # 7 IS41_PC_SSN_TYPE_AC # 8 IS41_PC_SSN_TYPE_BORDER_MSC
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 156
IS41_PC_SSN_TYPE_ORIGINATING_MSC
winPcSsnType "9" # # WIN Response Timer value in seconds. # This is the time for which the PPAS will wait for a ConnectionFailureReport # Invoke message (CONNFAILRPT) from the MSC after the . The MSC will send the # CONNFAILRPT message when its IVR call gets disconnected (i.e. mainly, after # the IVR announcement has been completed). # So the value should be large enough to take care of the time the # MSC takes to play the IVR announcement(s). # winResponseTimeOut "30" # # 'winMinMdnEquivalenceFlag' - Indicator to determine whether MIN parameter # value is to be copied into the MobileDirectoryNumber (MDN) if MDN does # not arrive in the message from the MSC. # Format: winMinMdnEquivalenceFlag "<flag>" # <flag> contains YES or NO. Default is YES. # winMinMdnEquivalenceFlag "NO" # 'winSendCcdirOnceToDisconnect' indicates whether the PPAS should send # one CCDIR to the MSC to disconnect a call, or should the PPAS send # one CCDIR (CallControlDirective Invoke) for each call leg. # Format: winSendCcdirOnceToDisconnect "<value>" # <value> contains TRUE or FALSE. # Default is FALSE (i.e. send CCDIR, one for each call leg). # # Note: # This parameter has been added to take care of MSCs that disconnect # the all legs in a call (i.e. the entire call) when PPAS requests it # to disconnect a specific one call leg.
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 157
# winSendCcdirOnceToDisconnect
"FALSE"
# # Configuration to determine the Routing Action on prepay rating errors. # # Format: # "errorRoutingAction <errorCause>" "<RoutingAction> <prepayAnncID>" # # <errorCause> - Could be one of the following: # # 1 = RESOURCE_SHORTAGE : A resource for rating the call is # temporarily unavailable. # # 2 = SYSTEM_FAILURE : A temporary failure has occurred while the # call was being rated. # # 3 = UNKNOWN_SUBSCRIBER : Subscriber is NOT a valid Prepay subscriber. # # <RoutingAction> - The configured routing action. Could be one # of the following: # # ROUTE_CALL : Route/Terminate the call. # # DENY_CALL : Deny call routing/termination. # # PLAY_ANNC_AND_ROUTE_CALL: Play an announcement and then # Route/Terminate the call. # # PLAY_ANNC_AND_DENY_CALL : Play an announcement and then deny call. # Routing/Termination. # # # NOTE : Default <RoutingAction> is set to "DENY_CALL". # --------------------------------------------# #
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 158
# If <RoutingAction> is PLAY_ANNC_AND_ROUTE_CALL or PLAY_ANNC_AND_DENY_CALL, then <prepayAnncID> specifies the announcement to be played. The announcement could be either Switch-based or IVR-based. (See <prepayAnncID> above ). # # # NOTE: If <RoutingAction> is either PLAY_ANNC_AND_ROUTE_CALL or PLAY_ANNC_AND_DENY_CALL and <prepayAnncID> is "NO_ANNOUNCEMENT" then default routing action would be either ROUTE_CALL or DENY_CALL. # "errorRoutingAction 1" "PLAY_ANNC_AND_ROUTE_CALL 2" "errorRoutingAction 2" "DENY_CALL" "errorRoutingAction 3" "PLAY_ANNC_AND_DENY_CALL 10" # Other error routing action examples are given below: #"errorRoutingAction 1" "ROUTE_CALL" #"errorRoutingAction 1" "DENY_CALL" #"errorRoutingAction 1" "PLAY_ANNC_AND_DENY_CALL 2" #"errorRoutingAction 2" "ROUTE_CALL" #"errorRoutingAction 2" "PLAY_ANNC_AND_ROUTE_CALL 1" #"errorRoutingAction 2" "PLAY_ANNC_AND_DENY_CALL 2" #"errorRoutingAction #"errorRoutingAction #"errorRoutingAction #"errorRoutingAction 3" 3" 3" 3" "ROUTE_CALL" "DENY_CALL" "PLAY_ANNC_AND_ROUTE_CALL 2" "PLAY_ANNC_AND_ROUTE_CALL 5"
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 159
D.9
-1001 -1002 -1003 -1004 -1005 -1006 -1007 -1008 -1009 -1100 -1101 -1102 -1103 -1104 -1105 -1106 -1107 -1108 -1109 -1110 -1200 -1201 -1202 -1203 -1204 -1205 -1300 -1301 -1302 -1400 -1401 -1402 -1403 -1404 -1420 -1421 -1422 -1423 -1424
pplError.English.Sample
"Read on the socket failed" "Write on the socket failed" "Connect on the socket failed" "Accept on the socket failed" "Invalid Request" "Invalid Response" "Signal caught error" "Association down error" "Socket creation failed" "Database connect failed" "Database disconnect failed" "Database select error" "Database commit error" "Database rollback error" "Database fetch complete error" "Database fetch Update Count error" "Database load complete error" "Database load update error" "Database fetch TLDN count error" "Database load TLDN error" "ERROR_THREAD_COMPLETESYNC_CREATION" "ERROR_THREAD_UPDATESYNC_CREATION" "Thread Startup creation error" "TLDN thread creation error" "Subscriber Handler Thread creation error" "Error initializing thread request writer" "Get element in a Q failed" "Put element in the Q failed" "Q is empty "Invalid state of the object "Memory Allocation Error" "Invalid date interval" "Invalid interval" "Invalid date" "Connection State error" "Listener state error" "Error initializing listener" "Error running listener" "Connection initialization Error"
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 160
-1500 -1501 -1502 -1503 -1504 -1505 -1506 -1507 -1508 -1600 -1601 -1602 -1603 -1700 -1800 -1801 -1900 -1901 -1902 -1903 -1904
"Table creation error" "Error Populating table" "Table load time error" "Error finding element in a table" "Error inserting element in a table" "Error removing element from a table" "Error destroying element from a table" "Destroy and clear table error" "Table not Set" "Association state error" "Association initialization error" "Association run error" "Association not set" "Error adding element at the tail" "Error processing TLDN request" "Subscriber request processing error" "Failed to initialize statistics thread" "Failed to create statistics thread" "Error statistics file name is empty" "Could not open statistics file" "Failed to terminate statistics thread"
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 161
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 162
5. Write-protect the tapes. 6. Use the ufsrestore command to restore the root file system. This command uses tape drive 0 (/rmt/mnt/0). ufsrestore rvf /dev/rmt/0 7. The level 0 tape is restored. 8. Verify the file system is restored. ls 9. Remove the restoresymtable file. This file is created and used by ufsrestore to check-point the restore. rm /restoresymtable 10. Change to the root (/) directory. cd / 11. Unmount the newly created file system. umount /mnt 12. Check the new file system for consistency. fsck /dev/rdsk/c0t0d0s0 13. Create the boot blocks on the root partition by using the installboot (1M) command. installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk \ /dev/rdsk/c0t0d0s0 14. Repeat steps 4 through 14 for the /var file system. 15. Reboot the system with the new drive. The following example shows all of the commands used to perform a Solaris rollback.
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 163
Example: (of restoring the root (/) file system) mount /dev/dsk/c0t0d0s0 /mnt cd /mnt ufsrestore rvf /dev/rmt/0 ls rm restoresymtable cd / umount /mnt fsck /dev/rdsk/c0t0d0s0 installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk \ /dev/rdsk/c0t3d0s0 ufsdump 0uf /dev/rmt/0 /dev/rdsk/c0t0d0s0 init 6
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 164
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 165
WARNING: Before upgrading Oracle to version 9.2.0.6, make sure that a complete backup of the database has been made. WARNING: PrePay and Oracle application downtime are required for this work. Estimated down time is 90 minutes to perform the upgrade. Note: Except where explicitly stated otherwise, all steps are to be performed as the 'oracle' Unix user. Note: All instructions and examples assume the use of the Korn shell (ksh). Use of another shell may cause some commands to fail or to work incorrectly.
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 166
F.1
For Distributed Architecture configurations, upgrade the Oracle software on the SCP and SDP servers. The database conversion should only be run on the SDP.
F.1.1
Run the command eeprom and review the values returned for the boot-file parameter. The output should say data not available which means it will boot up in 64-bit mode by default. eeprom | grep boot-file boot-file: data not available.
F.1.3
Run the following commands to record database options in case theyre needed later:
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 167
F.1.4
Run the following commands to record database block size for later:
F.1.5
Check to see if any user tables use N-type columns. If so, refer to Oracles Migration documentation for potential upgrade issues. To determine if N-type columns are being used, execute the SQL query below. If no rows are returned then continue with this migration. select distinct owner, table_name from dba_tab_columns where data_type in (NCHAR,NVARCHAR2,NCLOB) and owner not in (SYS,SYSTEM);
F.1.6
Run the following query to obtain data dictionary information: sqlplus / as sysdba set verify off space 0 feedback off pages 0 termout off spool analyze.sql select 'Analyze '||object_type||' '||object_name||' validate structure;' from dba_objects where owner='SYS' and object_type in ('INDEX','TABLE','CLUSTER'); spool off quit This creates a script called analyze.sql, which in turn will have to be executed. This script (analyze.sql) should not return any errors. sqlplus / as sysdba spool analyze.lst
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 168
@analyze.sql quit
F.1.7
After the upgrade is complete, all objects will be invalid. For future comparison, execute this query to list all objects that are not valid. This list will be used to compare against the list of invalid objects when the install is complete. sqlplus / as sysdba spool invalid_pre.lst select substr(owner,1,12) owner, substr(object_name,1,30) object, substr(object_type,1,30) type, status from dba_objects where status <>'VALID'; spool off quit
F.1.8
To create a script to compile all invalid objects, before upgrading, run the script called utlrp.sql in the $ORACLE_HOME/rdbms/admin directory. This script recompiles all invalid PL/SQL in the database including views. cd $ORACLE_HOME/rdbms/admin sqlplus / as sysdba @utlrp.sql quit Run the script and then rerun the query from above to get invalid objects.
F.1.9
If the upgrade fails and the dictionary was already rebuild, grants are lost. If you want to go back it is advisable to have a list of grants. Create and run the following script: cd /home/oracle/pre9206 vi list_grants.ksh #!/bin/ksh #
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 169
# list_grants.ksh #--: #--: generates DDL of database #--: exp userid=$1/$2 file=struct compress=no full=y rows=n imp userid=$1/$2 file=struct full=y show=y 2> contents.lst rm struct.dmp awk ' BEGIN { prev=";" } / \"CREATE / { N=1; } / \"ALTER / { N=1; } / \"ANALYZE / { N=1; } / \"GRANT / { N=1; } / \"REVOKE / { N=1; } / \"COMMENT / { N=1; } / \"AUDIT / { N=1; } N==1 { printf "\n/\n\n"; N++ } /\"$/ { prev="" if (N==0) next; s=index( $0, "\"" ); if ( s!=0 ) { printf "%s",substr( $0,s+1,length( substr($0,s+1))-1 ) prev=substr($0,length($0)-1,1 ); } if (length($0)<78) printf( "\n" ); }' < contents.lst > struct1 rm contents.lst sed /^$/d < struct1 > struct2 grep ^GRANT struct2 | fold s w75 > ppay.sql rm struct1 struct2 :wq! chmod 755 list_grants.ksh ./list_grants.ksh system {system_password}
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 170
This should return no rows. If rows are returned you must check with the DBA responsible for the system you are upgrading.
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 171
select username, default_tablespace from dba_users where username in ('SYS','SYSTEM'); To modify use: alter user sys default tablespace SYSTEM; alter user system default tablespace SYSTEM;
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 172
F.2 F.3
1. Check for post-release updates. Go to metalink.oracle.com and click on the Advanced tab. Then enter 189908.1 in the document id field and hit Submit. As of May 11, 2005 the following bugs were introduced in 9.2.0.6. After reviewing the details of each, only a subset was determined to be necessary. 2. Review the latest list of bugs introduced in 9.2.0.6 against the list below. If any new bugs are relevant to the clients own application, download the patch and apply it after these necessary patches. 4071941 Necessary; 32 bit JDBC library not installed as part of 9206 patch 4080972 Necessary; Bug can produce incorrect results 4074633 N/A; AIX only 4074603 N/A; Data Guard only 4066495 N/A; RAC only 3691672 Necessary if using JavaVM 4254094 N/A; Unless client uses DB Links 4197078 N/A; Fixed in 9.2.0.6. 4172170 N/A; Low risk of occurrence. Still under investigation. No patch 4165093 N/A; Unless client uses DB Links 4157713 Necessary; Bug can produce ORA-600 under heavy load. 4154591 Necessary; No patch. Set event 38047 until 9.2.0.7 is available. 4142932 Necessary; For LMT and ASSM 4131501 N/A; For star transformations 4116896 N/A; Low risk of occurrence and impact 4112324 N/A; Problem still under investigation 4101485 N/A; Low risk of occurrence and impact 4098853 N/A; Low risk of occurrence and impact 4082618 N/A; Low risk of occurrence and impact; no patch 4058160 N/A; Gateway interfaces only 4047527 N/A; ODM only 4039237 Necessary; Bug can produce incorrect results 4016802 N/A; Not using composite partitioned tables 4015165 Necessary; Bug can produce ORA-6502 from PL/SQL 3998408 N/A; RAC only 3963167 N/A; Low risk of occurrence. Conflicts with 4080972. 3949307 Necessary; Bug can produce SGA corruption 3945578 N/A; Linux only 3926058 N/A; Low risk of occurrence and impact 3901170 N/A; initppay.ora should not set 10235 or 10501 events
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 173
3844015 N/A; initppay.ora should not set 38044 or 38056 events 3777178 N/A; RAC only 3256015 N/A; Low risk of occurrence and impact 3228560 N/A; Low risk; Can wait for 9.2.0.7 availability 3. Check if SUNWuiu8 is installed. If not, install it first. a. pkginfo SUNWuiu8 4. Verify $ORACLE_HOME has at least 300MB of free space. 5. Verify /tmp has at least 80MB of free space. 6. Verify swap space has at least 150MB of free space. 7. mkdir $ORACLE_BASE/patches 8. Copy the oraInventory9204.tar.gz file for 9.2.0.4 to the patches directory 9. Copy the following 9206 patches to $ORACLE_BASE/patches: a. p2617419_10102_GENERIC.zip (this is the OPatch patch) b. p3691672_9206_SOLARIS64.zip c. p3948480_9206_SOLARIS64.zip (this is the 9206 patchset) d. p3949307_9206_SOLARIS64.zip e. p4015165_9206_SOLARIS64.zip f. p4039237_9206_SOLARIS64.zip g. p4071941_9206_SOLARIS64.zip h. p4080972_9206_SOLARIS64.zip i. p4142932_9206_SOLARIS64.zip j. p4157713_9206_SOLARIS64.zip 10. Perform an on-line backup of the Oracle database. 11. Backup the Oracle 9.2.0.4 software. Include /oracle and /var/opt/oracle.
F.3.1
Before starting any upgrade activity, enable the logging of your session to a script file with an embedded date/timestamp after logging on as the oracle user. Recommended filename: ~/oracleupgrade_9206_yyyymmddhhmm.log Command: script ~/oracleupgrade_9206_<yyyymmddhhmm>.log *** Beginning of DOWNTIME *** 1. Stop Prepay and any other applications that access the database. 2. Install the oraInventory.tar file into $ORACLE_HOME
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 174
a. su oracle b. cd $ORACLE_HOME c. gunzip dc $ORACLE_BASE/patches/oraInventory9204.tar.gz | tar xvf 3. Delete statistics on SYSTEM objects if they exist. a. sqlplus /nolog b. connect / as sysdba c. execute dbms_stats.delete_schema_stats(SYS); d. execute dbms_stats.gather_schema_stats(SYS); e. quit 4. Set SESSION_CACHED_CURSORS since behavior has changed in 9.2.0.6: a. cd $ORACLE_HOME/dbs b. vi initppay.ora If OPEN_CURSORS > 1000 then If SESSION_CACHED_CURSORS < 1000 then Set SESSION_CACHED_CURSORS = OPEN_CURSORS Save changes. 5. Check the SYSTEM tablespace has at least 10MB freespace. a. select sum(bytes),max(bytes) from dba_free_space where tablespace_name=SYSTEM; 6. Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE. a. startup b. show parameter pfile; i. If the VALUE column is blank then an SPFILE is not being used. c. show parameter shared_pool_size d. show parameter java_pool_size If either parameter is below 150MB then If using an SPFILE then set shared_pool_size to at least 150MB set java_pool_size to at least 150MB else vi $ORACLE_HOME/dbs/initppay.ora add/update both parameters (for very small servers, both parameters can be set to 100MB)
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 175
restart the database endif 7. Shutdown the database and the listener: a. sqlplus /nolog b. connect / as sysdba c. shutdown immediate d. quit e. lsnrctl stop f. ps ef | grep i ora (look for additional listener processes) g. lsnrctl stop {listener_name} (if more than one listener is running)
Installation Tasks
1. 2. 3. 4. 5. 6. 7. 8. su oracle DISPLAY={X-Window PC}:0.0 export DISPLAY Start X-Windows on a PC cd $ORACLE_BASE/patches unzip p3948480_9206_SOLARIS64.zip cd Disk1 ./runInstaller a. If OUI fails to start and reports errors referring to checkdir then see Oracle Metalinks Document ID 294190.1 for a work-around. The details of this are included below. b. Warning messages on the Solaris server regarding Cannot convert string can be ignored. c. On the Welcome screen, click NEXT. d. On the Specify File Locations screen, click BROWSE next to the Path field in the Source section. e. Select the products.xml file from the stage directory where you unpacked the patch set files, then click Next. For example: /work/ora9206/Disk1/stage/products.xml f. In the Name field in the Destination section, select the name of the Oracle home that you want to update from the drop down list, then click Next. g. On the Summary screen, click Install. h. During the Linking XML Class Generator task, a window may appear with the message: i. Error in invoking target install_isqlplus install of makefile. j. This can be ignored. Click on Continue. k. When prompted, run the $ORACLE_HOME/root.sh script as the root user. l. On the End of Installation screen, click Exit, then click Yes to exit from the Installer.
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 176
Post-installation Tasks
Upgrade the Database 1. su oracle 2. lsnrctl start 3. sqlplus /nolog 4. connect / as sysdba 5. startup migrate 6. spool patch.log 7. @?/rdbms/admin/catpatch.sql 8. spool off 9. review the patch.log 10. if necessary, rerun the catpatch 11. shutdown 12. startup 13. @?/rdbms/admin/utlrp.sql 14. If using RMAN, then upgrade the catalog: a. rman catalog user/pass; b. upgrade catalog;
Install Patches for 9.2.0.6 1. Shutdown the database and all listeners: a. sqlplus /nolog b. connect / as sysdba c. shutdown d. lsnrctl stop (stop all listeners if more than one is configured) 2. Check for any Oracle processes. Stop if any are found. a. ps ef | grep i ora 3. Verify the Oracle Universal Installer (OUI) is at version 2.2.0.18. It is very important for future patches that the OUI version is at this release. a. cat /var/opt/oracle/oraInst.loc b. cat <directory identified above>/oui.loc c. look for the value of InstVer. It should be 2.2.0.18.0. If not, install the latest opatch from Metalinks. 4. Install latest version of OPatch: a. cd $ORACLE_HOME b. unzip $ORACLE_BASE/patches/p2617419_10102_GENERIC.zip (if prompted with: replace OPatch/docs/FAQ? [y]es, [n]o, [A]ll, [N]one, [r]ename: reply with All ) 5. Fix a bug in OPatch where it cannot determine Solaris8 64-bit correctly.
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 177
a. cd b. vi .profile i. Add to the end of the file and save the changes: ii. OPATCH_PLATFORM_ID=23 iii. export OPATCH_PLATFORM_ID c. . ~/.profile d. echo $OPATCH_PLATFORM_ID (verify it is set to 23) 6. For each bug/patch file listed below: 3691672 3949307 (directory created is 4060756) 4015165 (directory created is 4070695) 4039237 4071941 4080972 4142932 4157713 Perform the following steps. Note the patch directory may not match the bug id in the .zip file. Cd into the directory created when unzipping the patch file. a. cd $ORACLE_BASE/patches b. unzip p${file}_9206_SOLARIS64.zip c. cd {directory created by running unzip} d. $ORACLE_HOME/OPatch/opatch apply e. Enter Y after verifying no Oracle processes are running and $ORACLE_HOME is set correctly. 7. Bug 4154591: Modify $ORACLE_HOME/dbs/initppay.ora a. cd $ORACLE_HOME/dbs b. vi initppay.ora c. Add the following line to the bottom of the file and save it: d. set event 38047 # Workaround for bug 4154591 until 9207 is applied 8. Reset SHARED_POOL_SIZE AND JAVA_POOL_SIZE. a. cd $ORACLE_HOME/dbs b. vi initppay.ora c. Change SHARED_POOL_SIZE back to its original value. d. Change JAVA_POOL_SIZE back to its original value or delete if it was newly added for the 9.2.0.6 patchset. 9. Start the database and all listeners. a. startppay b. startsqlnet 10. Start PrePay
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 178
Workaround for runInstaller not running. See Oracle Metalinks Document ID 294190.1
Symptom When trying to start OUI 10.1.0.3, to install the 9.2.0.6 64-bit patchset on Solaris, it failed to start and reported errors like this:
checkdir error: cannot create /tmp/OraInstall2004-12-16_12-20-06PM/oui/bin checkdir error: cannot create /tmp/OraInstall2004-12-16_12-20-06PM/oui/guide
Cause Support have raised <Bug:4080902> for this issue with OUI 10.1.0.3 Note that this issue could not be reproduced by Support, and only seems to affect some customers.
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 179
Create a shell script called "fix.sh" with the following three lines: cd /tmp/OraInstall* mkdir -p oui/bin oui/guide chmod 777 oui/bin oui/guide
Note that step 2 needs to completed quickly, before OUI fails. If you perform step 2 quickly enough, OUI should start successfully.
If OUI is reporting the problem about another directory, modify the mkdir and chmod commands in fix.sh as appropriate.
References <BUG:4080902> - Oui 10.1.0.3.0 Reports Checkdir Errors And Fails To Start
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 180
initppay.ora
1. The following initppay.ora file is for Oracle 9.2.0.x only. # # # # # # # # ********************************************************* **************** * Copyright (c) 2003 Lightbridge, Inc. All Rights Reserved. * * Except as expressly authorized by Lightbridge, reproduction * of any portion or element of this computer program, including without * limitation any portion of any image, text or screen is strictly * prohibited and is a violation of Federal law.
********************************************************* **************** #@(#)$Filename: #@(#)$Revision: #@(#)$Date: # ********************************************************* **************** # # 2003-04-04 Kevin Jewell # Initial configuration file. # # 2003-04-07 Kamlesh Bans # Minor modifications #
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 181
# 2004-03-08 Kevin Jewell # Updated for Oracle 9i. # _trace_files_public = true audit_trail = false background_dump_dest = /temp/oradata/ppay/bdump #buffer_pool_keep = (buffers:n; latches:n) #buffer_pool_recycle = (buffers:n; latches:n) compatible = 9.2.0 control_files = (/u01/oradata/ppay/ctrl1ppay.ctl, /u02/oradata/ppay/ctrl2ppay.ctl, /redo/oradata/ppay/ctrl3ppay.ctl, /rollback/oradata/ppay/ctrl4ppay.ctl) core_dump_dest db_block_size = /temp/oradata/ppay/cdump = 8192 # Allocates # # # # model model model model S/A B C D
db_cache_advice = ready memory for later analysis. #db_cache_size #db_cache_size #db_cache_size #db_cache_size db_domain #db_file_multiblock_read_count #db_file_multiblock_read_count #db_files #db_files db_name #db_writer_processes #db_writer_processes = 256M = 512M = 768M = 1536M = world = 32 = 64 = 256 = 512 = ppay = 2 = 4
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 182
dbwr_io_slaves db_writers instead disk_asynch_io #dml_locks #dml_locks #enqueue_resources #enqueue_resources global_names hash_area_size models hash_join_enabled instance_name log_archive_dest log_archive_format log_archive_start archivelog mode #log_archive_start QA systems #log_buffer 1MB #log_buffer 2MB #log_buffer 4MB
# always use
# model S/A/B # model C/D # model S/A/B # model C/D # 20MB for all
= /temp/oradata/ppay/archive/ = arch_%s.arc = true # set to true for = false = 1048576 = 2097152 = 4194304 # set to false on # model S/A/B # model C # model D use time-based checkpoint limit trace application set to local set to local
log_checkpoint_interval = 0 # checkpoints log_checkpoint_timeout = 900 # every 15 minutes for all models log_checkpoints_to_alert = true max_dump_file_size = 10240 # file size to 5 Meg each #nls_date_format = DD-Mon-RR # handles dates correctly. may comment out. nls_language = "american" # language nls_sort = binary nls_territory = "america" # territory
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 183
open_cursors See Oracle BUG 1244182. optimizer_index_caching too low optimizer_index_cost_adj too low optimizer_mode os_authent_prefix
= 1024 # model S/A/B/C/D Fixed in 8.1.6.3. = 90 # defaults are = 50 = choose = ops$ # Set >0MB if # # # # model model model model S/A B C D # defaults are
pga_aggregate_target = 0 workarea_size_policy=auto. #processes #processes #processes #processes #remote_login_passwordfile during RMAN installation #remote_os_authent = = = = 200 300 400 500 = exclusive = false
# uncomment
rollback_segments = (r01,r02,r03,r04,r05,r06,r07,r08,r09,r10,r11,r12,r13,r14, r15,r16,r17,r18,r19,r20) service_names #sessions #sessions #sessions #sessions #session_cached_cursors #session_cached_cursors #session_cached_cursors #session_cached_cursors shared_pool_size models #shared_pool_reserved_size sort_area_retained_size models sort_area_size models = ppay.world = = = = = = = = 250 350 450 550 100 200 300 400 # # # # # # # # model model model model model model model model S/A B C D S/A B C D
= 94371840 = = 2097152
= 20971520
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 184
# 10 for all
= /temp/oradata/ppay/udump = * = manual
G.1
_average_dirties_half_life _lm_statistics allow_partial_sn_results always_anti_join always_semi_join arch_io_slaves b_tree_bitmap_plans backup_disk_io_slaves cache_size_threshold cleanup_rollback_entries close_cached_open_cursors compatible_no_recovery complex_view_merging cpu_count db_block_checkpoint_batch db_block_lru_extended_statisti db_block_lru_latches db_block_lru_statistics db_block_max_dirty_target db_file_simultaneous_writes delayed_logging_block_cleanout
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 185
discrete_transactions_enabled distributed_lock_timeout distributed_recovery_connectio fast_full_scan_enabled freeze_DB_for_fast_instance_re gc_defer_time gc_latches gc_lck_procs gc_releasable_locks gc_rollback_locks hash_multiblock_io_count instance_nodeset job_queue_interval job_queue_keep_connections large_pool_min_alloc lgwr_io_slaves lm_locks lm_procs lm_procs lm_ress lock_sga_areas log_block_checksum log_files log_simultaneous_copies log_small_entry_max_size ogms_home ops_admin_group ops_interconnects optimizer_percent_parallel optimizer_search_limit parallel_default_max_instances parallel_min_message_pool parallel_server_idle_time parallel_transaction_resource_ push_join_predicate row_cache_cursors sequence_cache_entries sequence_cache_hash_buckets shared_pool_reserved_min_alloc snapshot_refresh_interval snapshot_refresh_keep_connecti snapshot_refresh_processes sort_direct_writes sort_multiblock_read_count sort_read_fac
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 186
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 187
If any serious problems occur after upgrading to PrePay 10.0.1 it may be necessary to roll back the application and database changes. Coordinate the downtime for the rollback with the customer. *** Beginning of DOWNTIME *** 1. Stop the PrePay application. su ppadm stop_ppay 2. Rollback any patches according to the instructions in their README.TXT files. 3. Perform the following steps to roll back the application and database by executing Option 5 in the Prepay Upgrade menu. Type the following commands to start the upgrade script, replacing the string <fromversion> with either 922 or 100, depending on whether you are upgrading from the PrePay 9.2.2 or 10.0 release. cd /<temparea>/work ./ppupgrade.ksh <fromversion> 4. Execute Option 4 in the Prepay Upgrade menu.
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 188
5. Review the rollback.YYYYMMDD error log file for any errors (where YYYYMMDD is the system date): /<temparea>/work/<version>/logs/rollback.YYYYMMDD 6. Type the following command to review the log file for any errors or warnings that may have occurred: more /<temparea>/work/<version>/logs/rollback.YYYYMMDD 7. To roll back database changes, restore the database from the backup taken prior to the upgrade.
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 189
Answer "Y" (yes) when asked to convert databases. 3. Run the ebs_setrelease command again to confirm which software release is currently in use
Lightbridge Proprietary and Confidential All rights reserved. Lightbridge Inc. 190