Oracle® Communications
Offline Mediation Controller

Nortel DMS SMDR Cartridge Pack User Guide

Release 6.0

E39480-01

June 2015

Oracle Communications Offline Mediation Controller Nortel DMS SMDR Cartridge Pack User Guide, Release 6.0

E39480-01

Copyright © 2015, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Downloading Oracle Communications Documentation

- Related Documents

- Documentation Accessibility

1 About this Guide

- About the Cartridges

- Cartridge Pack Content

2 Cartridge Pack Overview

- New Features

- Version 6.0.0

- Architecture

- Alarms

- Behavior

3 Installing the Cartridge Pack

- Pre-Installation Tasks

- Installation Instructions

- Installing on a Solaris or Linux Workstation

- Post Installation Instructions

- Testing the Cartridge Pack Installation

4 Configuring the Nodes

- Creating and Configuring the DMS SMDR CC

- Creating and Configuring the DMS SMDR AP

- Creating and Configuring the Customer Specific EP

- Creating and Configuring the DMS SMDR ASCII DC

- DMS SMDR ASCII DC Data Output - Non-billable

- Creating and Configuring the DMS SMDR ASCII Fixed Width File DC

- DMS SMDR ASCII Fixed Width DC data output - billable

- Creating and Configuring the JDBC DC

5 Configuring the Node Chains

- SMDR Collection With ASCII Distribution

- Configuring Directed Routing For the Non-billable Stream

- SMDR Collection With ASCII Fixed Width File Distribution

- Configuring Directed Routing For the Billable Stream

- SMDR Collection With Database Distribution

- SMDR Collection With NAR Distribution

6 Database Storage and Reporting

- Installing and Configuring

- Loading the Offline Mediation Controller Schema

7 Uninstalling the Cartridge Pack

- Uninstalling the Cartridge Pack from a Solaris or Linux Workstation

- Removing Scripts From the Database

Preface

This document contains guidelines for installing and setting up Oracle Communications Offline Mediation Controller Nortel DMS SMDR cartridge pack.

Audience

This document is intended for solution designers who configure Offline Mediation Controller cartridges.

Downloading Oracle Communications Documentation

Product documentation is located on Oracle Help Center:

http://docs.oracle.com

Additional Oracle Communications documentation is available from the Oracle software delivery Web site:

https://edelivery.oracle.com

Related Documents

For more information, see the following documents:

- Offline Mediation Controller Cartridge Development Kit Developer's Guide: For information about how to develop a cartridge.

- Offline Mediation Controller Cartridge Development Kit NPL Reference Guide: For information about how to use the Node Programming Language for developing or extending a cartridge.

- Offline Mediation Controller System Administrator's Guide: For administrating Oracle Communications Offline Mediation Controller.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

1 About this Guide

This chapter contains an overview about Oracle Communications Offline Mediation Controller cartridges.

The scope of this guide includes Offline Mediation Controller as it pertains to the use of this cartridge pack. It is not intended to be a complete Offline Mediation Controller reference guide.

About the Cartridges

Offline Mediation Controller cartridge packs are discrete software components that are developed for the Offline Mediation Controller product. An Offline Mediation Controller cartridge pack offers specific domain behavior on top of the core Offline Mediation Controller software.

An Offline Mediation Controller cartridge pack is not a standalone component; it operates in conjunction with the Offline Mediation Controller core product. Offline Mediation Controller cartridge packs offer the following benefits:

- Reduced time to market: Time to market of new services is reduced through simplified development, implementation, and extension of cartridges on customer sites.

- Extendable: Cartridges can be extended to include additional services and components that deliver business value, without requiring changes to the original cartridge.

- Simplified effort: The effort and technical knowledge that is required to perform customizations is reduced.

- Ease of installation: Cartridges can be installed into an Offline Mediation Controller environment without interfering with the existing install base.

Note:
Cartridges are designed for a specific technology, software load, and service.

For more information on creating and extending a cartridge, refer to the following documents:

- Offline Mediation Controller Cartridge Development Kit Developer's Guide: For information on how to develop a cartridge.

- Offline Mediation Controller Cartridge Development Kit NPL Reference Guide: For information on how to use the Node Programming Language for developing or extending a cartridge.

Cartridge Pack Content

An Offline Mediation Controller cartridge contains the following:

- JAR file: Contains the cartridge software.

- Cartridge Pack User Guide: Contains a description of cartridge pack functionality and installation and configuration instructions.

2 Cartridge Pack Overview

This chapter contains an overview of Oracle Communications Offline Mediation Controller Nortel DMS SMDR cartridge pack.

The Nortel DMS SMDR Cartridge Pack provides the ability to collect SMDR records from DMS-100.

Switches according to the specification DMS100 Family North American DMS-100 Station Message Detail Recording Reference Guide, DMSCCM12 Standard 19.03 October 2000. The cartridge pack also filters, enhances and distributes SMDR records to multiple destinations, including a Billing Centre and an Oracle database.

New Features

This section lists the new features.

Version 6.0.0

This cartridge pack now works with Oracle Communications Offline Mediation Controller 6.0.

Architecture

Figure 2-1 displays the architecture of the SMDR solution.

Figure 2-1 Nortel DMS SMDR Cartridge Architecture

Alarms

All Offline Mediation Controller alarms are listed in the alarms.txt file located in the OMC_Home directory (OMC_Home is the directory in which you installed Offline Mediation Controller.) No new alarms are introduced in this cartridge pack. The following new alarms are introduced in this cartridge pack:

Fault category: Connectivity

- Specific Fault: FTP login problem - Device <IP Address> <Port number>

- Specific Fault: FTP error - Device <IP Address> <Port number>

Behavior

The following are known behaviors for this cartridge pack:

- The DMS SMDR CC raises a major alarm when it receives a file with a name longer than 30 characters.

The SMDR discard count parameter does not appear in the Offline Mediation Controller statistics report file.

3 Installing the Cartridge Pack

This chapter contains information on the requirements for installing and setting up Oracle Communications Offline Mediation Controller Nortel DMS SMDR cartridge pack.

Pre-Installation Tasks

Complete the following pre-installation tasks before installing the cartridge pack:

1. Ensure Offline Mediation Controller 6.0 is installed.

2. Stop Node Manager, Administration Server, and Administration Client.

3. Delete any existing DMS SMDR cartridge .jar files from the OMC_Home/cartridges directory, where OMC_Home is the directory in which Offline Mediation Controller is installed.

Installation Instructions

In a Solaris or Linux environment, you must install the cartridge pack on every UNIX server running Node Manager or Administration Server.

Installing on a Solaris or Linux Workstation

To install the cartridge pack on a Solaris or Linux workstation:

1. Download the smdr_r6_0_0.jar to the OMC_Home/cartridges directory.

2. Copy the smdr_r6_0_0.jar file to another directory - any directory except the OMC_Home/customization directory and unjar the file.

3. Restart Node Manager, Administration Server, and Administration Client.

Post Installation Instructions

After the Cartridge Pack has been installed, restart Node Manager, Administration Server, and Administration Client.

Testing the Cartridge Pack Installation

Verify that the Cartridge Pack has been properly installed by viewing Version Info from the Help menu in Administration Client. The Cartridge Pack name and version information should appear, along with the information about Node Manager, Administration Server, and Administration Client.

4 Configuring the Nodes

This chapter contains information on the requirements for creating and configuring the Oracle Communications Offline Mediation Controller Nortel DMS SMDR nodes for use in the SMDR node chains.

Creating and Configuring the DMS SMDR CC

The DMS SMDR CC is responsible for collecting SMDR files from DMS-100 switches. The CC uses FTP to periodically transfer SMDR/DIRP-encoded files from each switch. One DMS SMDR CC can poll and transfer files from many switches. The CC makes the Record Code attribute available for routing, which enables records to be separated into billable and non-billable streams.

To create and configure the DMS SMDR CC:

1. Log on to Offline Mediation Controller Administration Client.
The Node Hosts & Nodes (logical view) screen appears.

2. In the Mediation Hosts table, select a host.

3. In the Nodes on Mediation Host section, click New.
The Create a Node dialog box appears.

4. Select Voice over IP (VoIP) and click Next.

5. Select Collection Cartridge (CC) and click Next.

6. Select DMS SMDR and click Finish.

7. In the node configuration window, type a name for the node in the Name field.

8. Accept the default Rule File.

9. On the General tab, accept the default field settings, as shown in the sample below:

10. On the Settings tab, configure the fields as required. The field definitions are as follows:

- Directory for unprocessed files: Local directory to store unprocessed files from the device.

- Directory for bad data files: Local directory to store bad or invalid data files.

- Delete or Keep processed files: Select a button to delete or keep processed files.

- Directory for processed files: Local directory to store files that have been processed by the CC.

- Duration to keep each file: Amount of time the processed files are kept in the local directory. Enter a numeric value and select Days or Hours from the drop-down list.

- Unprocessed file prefix: File prefix of unprocessed files on the remote device.

- Rename Unprocessed to Processed: Select this checkbox if you want the CC to rename the files on the remote device after successful transfer via FTP.

- Processed file prefix: File prefix of processed files on the remote device.

- Retries per poll: Number of additional FTP attempts for each polling interval. If the node is unable to retrieve the files, it raises an alarm and will not attempt to re-poll the device until the next scheduled poll interval.

- Polling interval: Time interval between FTP polls.

- Process daily at fixed time: Select this checkbox if you want the CC to align its polling schedule to a specific time of day. Set the time of day using the drop-down lists.

11. On the Device List tab, click the Add button.

The Add Device window appears.

12. Configure the fields as required. The field definitions are as follows:

- Name: Enter a name for the device, if desired.

- IP Address: Enter the IP address of the device.

- Port: Enter the port you will connect to on the device.

- FTP User ID: Enter the user or account ID for the remote device.

- Password: Enter your password for the remote device.

- Confirm Password: Re-enter your password for the remote device.

- Disk Volumes: Enter the disk volume name and click Add to add it to the list.

13. Click Save.
The device appears in the list on the Device List tab.

Repeat steps 9 to 11 to add more devices to the list. You can also edit device profiles by clicking the Edit button or delete device profiles by clicking the Delete button.

You do not need to perform any tasks on the Destinations tab.

14. Click Save.

Creating and Configuring the DMS SMDR AP

The DMS SMDR AP allows the hexadecimal value of the following fields to be mapped to the corresponding text name:

- Console-Number = Attendant Console Name (from A records)

- Customer-Group-Number = Customer Group Name (from C records)

- Origination ID = Trunk Group CLLI (from K records) or Virtual Facility Group Name (from V records)

The DMS SMDR AP maps the customer-group translation records (C records), attendant console records (A records), virtual facility group name records (V records) and trunk-group-CLLI records (K records) for each DMS-100 switch. The AP tags SMDR records with the text names for each hexadecimal identifier. This allows you to direct records to specific locations based on the text names instead of the changeable hexadecimal identifier. The AP makes the following attributes available for routing: Office ID, Attendant Console Name, Customer Group Name, Trunk Group CLLI and Virtual Facility Group Name.

To create and configure the DMS SMDR AP:

1. Log on to Offline Mediation Controller Administration Client.
The Node Hosts & Nodes (logical view) screen appears.

2. In the Mediation Hosts table, select a host.

3. In the Nodes on Mediation Host section, click New.
The Create a Node dialog box appears.

4. Select Voice over IP (VoIP) and click Next.

5. Select Aggregation Processor (AP) and click Next.

6. Select DMS SMDR Aggregation and click Finish.

7. In the node configuration window, type a name for the node in the Name field.

8. Accept the default Rule File.

9. On the General tab, accept the default field settings, as shown in the sample below:

10. On the Aggregator tab, configure the settings as required. The field definitions are as follows:

- Flush time: Number of seconds before an aggregated NAR is sent to the next node in the chain. You may need to increase this value depending on how long it takes for the AP to process a single file.

- Compression threshold: Number of stale records the node allows before compressing the aggregation table.

You do not need to perform any tasks on the Destinations tab.

11. Click Save.

Creating and Configuring the Customer Specific EP

You must create and configure an EP that will enhance the NAR with the customer name. The customer name must be stored in the NAR using the NAR attribute ID 140157. The customer name value is used by the DMS SMDR ASCII Fixed Width File DC to populate the header and footer records.

Creating and Configuring the DMS SMDR ASCII DC

The DMS SMDR ASCII DC outputs all incoming fields for each record. These records can be used internally as non-billable information whereas the ASCII Fixed Width records can be used for billing purposes.

To create and configure the DMS SMDR ASCII DC:

1. Log on to Offline Mediation Controller Administration Client.
The Node Hosts & Nodes (logical view) screen appears.

2. In the Mediation Hosts table, select a host.

3. In the Nodes on Mediation Host section, click New.
The Create a Node dialog box appears.

4. Select Voice over IP (VoIP) and click Next.

5. Select Distribution Cartridge (DC) and click Next.

6. Select DMS SMDRASCII and click Finish.

7. In the node configuration window, type a name for the node in the Name field.

8. Accept the default Rule File.

9. On the General tab, accept the default field settings, as shown in the sample below.

10. On the Flat File Output tab, configure the settings as necessary. The default values are shown below.

11. On the FTP tab, configure the settings as necessary.

12. Click Save.

DMS SMDR ASCII DC Data Output - Non-billable

RecordCode,OfficeId,CustomerGroupNumber,OriginationType,OriginationIdentification,DataCallIdentification,InformationDigit1And2,ConsoleNumber,SubGroup,TerminationType,TerminationIdentification,RouteInformationDigit,StartTime,ElapsedTime,OriginatingFeatureCode,TerminatingFeatureCode,CalledNumber,Spare,RotationTime,NANI2,NANI,NONI2,NONI,NANIF2,NANIF,NANOF2,NANOF,NLNI2,NLNI,NLOI2,NLOI,NLIF2,NLIF,RestartType,OldTime,NewTime,RecordCode_D5,DigitsOutpulsed,DigitsMissing,RecordCode_D6_A,RecordType_A,NumOfAuthDigsInComb_A,Digits_A,RecordCode_D6_B,RecordType_B,NumOfAuthDigsInComb_B,Digits_B,RecordCode_DA,TrunkGroupId,Spare_DA,TrunkNumberId,NetworkCLID,RecordCode_DB,MSNOriginationType,MSNN00CallType,InformationDigits,ANINumber,ANISuffix,CarrierAccessCode,AccessDirectoryNumber,MSNANIMapping,Spare_DB,OriginationTime_DB,Treatment,Reorigination,BillingDigits,RecordCode_DC,PINOrTCNNumber,Description,Spare_DC,RecordCode_DD,BCType,BandWidth,RecordCode_DE,OriginationTime_DE,BillingNumber,MessageArea,LMNNumber,TreatmentCode,PayPhone,MobilePhone,NetworkIdentification,NetworkClassOfService,ContractSubscriberNumber,NotificationOfTimeAndCharge,CallbackAnswerTime,NoCharge,ISDNAccessIndicator,RecordCode_DF01,SMDRITC_CALLID,SMDRITC_TIME,RecordCode_DF02,SignalingType,MessageType,LengthCount,Information,RecordCode_DF03,AltBillingBumber_DF03,BusinessCustomerId_DF03,SignificantDigitsInNextField_DF03,AdditionalDigitsDialed_DF03,RecordCode_DF04,OriginalCallingNumber,AltBillingBumber_DF04,BusinessCustomerId_DF04,SignificantDigitsInNextField_DF04,AdditionalDigitsDialed_DF04,RecordCode_DF05,CarrierType,ATCValue,MessageDirection,DeferredCharge,CarrierId,AssociatedChargeArea,RecordCode_DF06,UnitChargeIndicator,ChargeInformationType,MessageDirection_DF06,DeferredCharge_DF06,MNA_L_Digits,RecordCode_DF07,AdditionalUserTypeName,MessageTypeCode,UserTypeValue,RecordCode_DF09,ClassFeatureCode,BillDN,EventYear,EventMonth,EventDay,EventHour,EventMinute,EventSecond,NumberAvailable,NumberUnavailable,NameAvailable,NameUnavailable,ConferencePegs,SCFListSize,SCAListSize,SCRJListSize,DRCWListSize,Spare1_DF09,Spare2_DF09,AttendantConsoleName,CustomerGroupName,TrunkGroupCLLI,VirtualFacilityGroupName
'd2','905509','003','0','4166608127a','a','00','ff','0','3','09ba0002aaa0','0','045142844','000006','0','0','6133358234aa','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','',''
'd2','905509','003','3','09ca0002aaa','a','00','ff','0','5','04aa0000aaaa','0','048151712','000004','0','0','84162911000a','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','',''
'd2','905509','003','5','04aa0000aaa','a','00','ff','0','3','0c6a0005aaa0','0','048151712','000004','0','0','14162911000a','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','',''
'd2','905509','003','3','09ca0001aaa','a','00','ff','0','5','04aa0000aaaa','0','048151904','000005','0','0','84162911000a','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','','',''

Creating and Configuring the DMS SMDR ASCII Fixed Width File DC

The DMS SMDR ASCII Fixed Width File DC outputs records in a fixed width format for billing purposes. The files are generated based on a customer name and office ID combination.

To create and configure the DMS SMDR ASCII Fixed Width File DC:

1. Log on to Offline Mediation Controller Administration Client.
The Node Hosts & Nodes (logical view) screen appears.

2. In the Mediation Hosts table, select a host.

3. In the Nodes on Mediation Host section, click New.
The Create a Node dialog box appears.

4. Select Voice over IP (VoIP) and click Next.

5. Select Distribution Cartridge (DC) and click Next.

6. Select DMSSMDR ASCII Fixed Width File and click Finish.

7. In the node configuration window, type a name for the node in the Name field.

8. Accept the default Rule File.

9. On the General tab, accept the default field settings, as shown in the sample below.

10. On the File Output tab, configure the settings as necessary. The default values are shown below.

11. On the FTP tab, configure the settings as necessary. The default values are shown below.

12. Click Save.

DMS SMDR ASCII Fixed Width DC data output - billable

a141616902014040109040109
d1416169020143138a0074 4000015037a000b 00091133340003360099057755286 9999999999
d14161690201409058368721   4000003138a0079aaa0 00091138230000532099058580988                                                    9999999999
d14161690201409058361846   4000003138a006caaa0 00091138230000602099058572240                                                    9999999999
d1416169020143138a007b     4000015037a000c     00091139340000140099058953222                                                    9999999999
d14161690201409058361846   4000003138a006faaa0 00091138540000562099054777575                                                    9999999999
d1416169020143138a0072     4100015037a0001     00091138580000830099058536611                                                    9999999999
d1416169020143138a0079     4000013061a0068aaa0 00091139440000410097057264153                                                    9999999999
d1416169020143138a0077     4100015037a0013     00091138510001090099054765507                                                    9999999999
d1416169020143138a006e     4000015037a0000     00091138090001530099058536611                                                    9999999999
d14161690201409058368721   4000003138a0069aaa0 00091140060000362099058963333                                                    9999999999
d14161690201409058366584   4000003138a0065aaa0 00091138350001292094162596328                                                    9999999999
d1416169020143138a0073     4100015037a0005     00091139230000960099054761792                                                    9999999999
d14161690201409058362214   4000003138a0074aaa0 00091140180000442099057903737                                                    9999999999
d14161690201409058364857   4000003138a0076aaa0 00091140500000342099054703179                                                    9999999999
d14161690201409058362214   4000003138a0072aaa0 00091142260000162099054703179                                                    9999999999
d14161690201409058368721   4000003138a0075aaa0 00091141320000852099054707011                                                    9999999999
d1416169020143138a0070     4100013061a0069aaa0 00091142190001420097057264153                                                    9999999999
d1416169020143138a006      4000015037a0006     00091138330003810099058984657                                                    9999999999
d14161690201409058368721   4000003138a0068aaa0 00091144450000102099057294825                                                    9999999999
d1416169020143138a0076     4000015037a0004     00091141540001920099058950337                                                    9999999999
d1416169020143138a0069     4100015037a0007     00091142450001400099058360988                                                    9999999999
d1416169020143138a007c     4000015037a0010     00091137140004890099058984657                                                    9999999999
d14161690201409058366584   4000003138a006daaa0 00091144550000282099057965436                                                    9999999999
d14161690201409058364857   4000003138a007baaa0 00091144000000882099058295404                                                    9999999999
d1416169020143138a006c     4100015037a0008     00091145020000330099054765507                                                    9999999999
t141616902014040109040109                        000000025000000000000000000

Creating and Configuring the JDBC DC

The SMDR AP sends a copy of all SMDR records to the JDBC DC for storage in the database. The original file name of the SMDR file from which a CDR originated is stored in the database.

To create and configure the JDBC DC:

1. Log on to Offline Mediation Controller Administration Client.
The Node Hosts & Nodes (logical view) screen appears.

2. In the Mediation Hosts table, select a host.

3. In the Nodes on Mediation Host section, click New.
The Create a Node dialog box appears.

4. Select Cartridge Kit and click Next.

5. Select Distribution Cartridge (DC) and click Next.

6. Select JDBC DC.

7. Click Finish.

8. In the node configuration window, type a name for the node in the Name field.

9. You must create a Rule File for this DC. See the Offline Mediation Controller CDK Developer's Guide and NPL Reference Guide for more information.

10. On the General tab, refer to the online help for field definitions. The default field settings are shown in the sample below.

11. On the Database Info tab, use the following guidelines to configure the settings:

- Batch Size - number of records to transmit in one batch to the database.

- User - user name to connect to the database to which the node sends data.

- Password - alphanumeric string to log in to the database.

- Verify Password - type the password again to verify the accuracy.

- Host - IP Address of the database.

- Port - port number used to communicate with the database.

- SID - service instance of the database - the identification number for the database.

12. Click Save.

5 Configuring the Node Chains

This chapter contains information on the requirements for configuring the Oracle Communications Offline Mediation Controller Nortel DMS SMDR node chains that comprise the DMS SMDR solution. See Figure 2-1, "Nortel DMS SMDR Cartridge Architecture" to see the architecture diagram of the node chains.

SMDR Collection With ASCII Distribution

To configure the node chain for SMDR collection with ASCII distribution, you must create and configure a DMS SMDR CC, DMS SMDR AP and a DMS SMDR ASCII DC. Connect the CC to the AP using Directed routing with the Record Code attribute. You can connect the AP to the DC using Multicast routing. The DMS SMDR ASCII DC outputs all incoming fields for each record. These records can be used internally and not for billing since they are not in the fixed width format.

Configuring Directed Routing For the Non-billable Stream

To configure Directed routing:

1. Click on the DMS SMDR CC.

2. Drag the blue output handle to the first DMS SMDR AP.

3. The Routing Algorithm window appears.

4. Select Directed from the drop-down list and click OK.

5. The Routing Attribute window appears.

6. Select Record Code from the drop-down list and click OK.

7. The Directed Routing Parameters window appears.

8. In the Boolean Operator drop-down list, select Equals.

9. Click the Add button.

10. The Enter Explicit Value window appears.

11. Enter d2 and click OK.

12. Repeat steps 6 and 7 to add the values d4, fa, fb, fc, fd, fe, A, C, K and V.

13. In the Directed Routing Parameters window, click OK.

SMDR Collection With ASCII Fixed Width File Distribution

To configure the node chain for SMDR collection with ASCII fixed width file distribution, use the DMS SMDR CC you created for the previous chain, then create and configure an additional DMS SMDR AP and one or more DMS SMDR ASCII Fixed Width File DCs. Connect the CC to the AP using Directed routing with the Record Code attribute. You can connect the Customer specific EP to the DC using Multicast routing if you want the files to be output based on a customer and switch combination. You can connect the Customer specific EP to multiple DCs using Directed routing based on the available fields for routing. The DMS SMDR ASCII Fixed Width DC outputs records in a fixed width format for billing purposes.

Configuring Directed Routing For the Billable Stream

To configure Directed routing:

1. Click on the DMS SMDR CC.

2. Drag the blue output handle to the second DMS SMDR AP.

3. The Routing Algorithm window appears.

4. Select Directed from the drop-down list and click OK.

5. The Routing Attribute window appears.

6. Select Record Code from the drop-down list and click OK.

7. The Directed Routing Parameters window appears.

8. In the Boolean Operator drop-down list, select Equals.

9. Click the Add button.

10. The Enter Explicit Value window appears.

11. Enter d2 and click OK.

12. Repeat steps 6 and 7 to add the values d1, d3, A, C, K and V.

13. In the Directed Routing Parameters window, click OK.

SMDR Collection With Database Distribution

To configure the node chain for SMDR collection with database distribution, you must use the DMS SMDR CC and the EP you created previously, and create and configure a Database Storage and Reporting DC. Connect the EP to the DC using Multicast routing. The DC outputs records to the Oracle database for storage.

SMDR Collection With NAR Distribution

To configure the node chain for SMDR collection with NAR distribution, you must use the DMS SMDR CC and the EP you created previously, and create and configure a NAR DC. Connect the EP to the DC using Multicast routing. This DC outputs records using the Offline Mediation Controller internal NAR format. At this point, you can use the Oracle Communications Offline Mediation Controller Record Editor tool to correct any invalid records and then reintroduce them to the DMS SMDR CC for processing.

6 Database Storage and Reporting

This chapter contains information on the installation and setting up of Database and Reporting software for Oracle Communications Offline Mediation Controller Nortel DMS SMDR cartridge pack.

The Database Storage and Reporting functionality allows you to configure DMS-MSC node chains that can process and distribute data to both a billing system and an Oracle 11g database.

Installing and Configuring

To install and configure the database components, see Offline Mediation Controller 6.0 Installation Guide.

The Database Storage tasks are as follows:

- Creating an Oracle user and dba group

- Installing Oracle

- Verifying the Oracle installation

- Loading the Offline Mediation Controller schema

- Configuring Oracle

- Configuring UNIX executables

- Configuring and using the Repository Manager

- Installing the Oracle Client

- Modifying tnsnames.ora

- Installing the Oracle JDBC driver

- Configuring Oracle for automatic restart

- Verifying the Oracle automatic restart

Loading the Offline Mediation Controller Schema

Use the following procedure to load the Offline Mediation Controller schema.

To load the schema:

1. As the oracle user, run the Oracle Enterprise Manager by typing oemapp worksheet and pressing Enter.

2. Select connect directly to database.

3. For Username, type system.

4. For Password, type Oracle.

5. For Service, type NMCDRS.

6. For Connect, type normal.

7. Click OK.
You are now connected to the NMCDRS schema.

8. Navigate to the directory where the SMDR jar file was un-jarred.
For example: /opt/test/dbstorage/Oracle11g

9. As the oracle SYSTEM user, load the following tablespace: DDL_create_tblspc_SMDRS_MAIN
This is a default tablespace, and does not store daily CDRs.

10. After loading this script, modify the DATAFILE to match the directory structure on the machine where you installed Oracle
For example: Oracle_Home/oradata/dbf.filename

11. Set the SIZE parameter to a minimum of 10M (ten megabytes).

12. As the oracle SYSTEM user, load DDL_create_usr_NMUSER1.sql.

13. Disconnect as the SYSTEM user and connect as NMUSER1. The default password is NMUSER1.

14. Ensure you are in the directory where the SMDR jar file was un-jarred.
For example: /opt/test/dbstorage/Oracle11g

15. Load DDL_create_tbl_MSLV_SMDR_STORAGE.sql.

16. Go to: <directory where you un-jarred the SMDR jar file>/dbstorage/Oracle11g/RepoMan.

17. Load DDL_create_tbl_SMDR_REPOMAN_CONFIGURATION.sql.

18. Load PLSQL_SMDR_PKG.sql.

19. Load PLSQL_SMDR_LOGTOFILE.sql.

20. Load JAVA_UTIL.sql.

21. Load PLSQL_RUN_CMD.sql.

22. Load PLSQL_RC.sql.

23. Load PLSQL_SMDR_PARFILEWRITER.sql.

24. Load PLSQL_BUILD_SMDR_EXCHANGE.sql.

25. Load PLSQL_DROP_SMDR_PARTITIONS.sql.

26. Load PLSQL_BUILD_SMDR_PARTITIONS.sql.

27. Load PLSQL_MSLV_START_SMDR_REPOMAN.sql.

28. Load PLSQL_MSLV_STOP_SMDR_REPOMAN.sql.

All required Oracle objects are now loaded into Oracle database.

7 Uninstalling the Cartridge Pack

This chapter contains information on the requirements for uninstalling Oracle Communications Offline Mediation Controller Nortel DMS SMDR cartridge pack.

Uninstalling the Cartridge Pack from a Solaris or Linux Workstation

To uninstall the Real-Time ASCII File Collection CDK cartridge pack from a Solaris or Linux Workstation:

1. Go to the OMC_Home/cartridges directory, where OMC_Home is the directory in which Offline Mediation Controller is installed.

2. Run the following command, which removes the cartridge pack:

rm smdr_r6_0_0.jar

Removing Scripts From the Database

To remove the scripts from the database:

1. Execute Oracle_Home/bin/oemapp dbastudio&
The Oracle Enterprise Console appears.

2. Log on using the following information:

- User = system

- Password = oracle

- Service = NMCDRS

3. In the left-hand frame, expand the schema directory, then expand the NMUSER1 directory, which lists the subdirectories.

4. Expand the sub-directories one by one as follows:

- Tables

- Source Types

- Packages

- Procedures

- Functions

- Java Sources

- Java Classes

5. For each of the sub-directories, there are files related to the schema. Right-click on each file and select Remove.

6. Expand the Storage directory and then expand the TableSpace directory. It lists the following:

- SMDR_MAIN

- MSLV_<YYYYMMDD> (if partition table got created)

7. Right-click on each item and select Remove.

8. Execute the following command as the system user:

drop user nmuser1 cascade

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2016, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Alpha and Beta Draft Documentation Notice

If this document is in private preproduction status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your beta trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.