reliatel - tone software · 2019. 10. 7. · chapter 1 introduction 3 installing stepar note: if...

ReliaTel

®

STEPAR

Release 4.1.2

User Guide

Version 1

Copyright

Jan 2013STP412-01GA-USR

This document contains confidential and proprietary information. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, reducing, or by any information storage and retrieval system, without permission in writing from Tone Software Corporation.

The information in this document is subject to change without prior notice and does not represent a commitment on the part of Tone Software Corporation. Tone Software Corporation assumes no responsibility for any errors that may appear in this document.

This document and the software it describes are furnished under a license agreement and may be used or copied only in accordance with the terms of the agreement.

Restricted Rights Legend. Use, duplication or disclosure is subject to restrictions set forth in subparagraph (a) through (d) of the commercial Computer Software Restricted Rights clause at 52.227-19 and the limitations set forth in Tone Software's standard commercial agreement for this software.

Unpublished rights reserved under the copyright laws of the United States.

Copyright 1992 - 2013 by Tone Software Corporation. All rights reserved.

Tone Software Corporation1735 S. Brookhurst StreetAnaheim, CA 92804-6491Voice: (714) 991-9460Fax: (714) [email protected]

iv STEPAR User Guide

Trademarks

Adobe® Flash® Player and Adobe® Reader® are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Avaya® and Definity® are trademarks of Avaya, Inc. and may be regis-tered in certain jurisdictions. All trademarks identified by the ® or ™ are registered trademarks, service marks, or trademarks, respectively, of Avaya, Inc.

Linux® is a registered trademark of Linus Torvalds.

Microsoft® Internet Explorer 7® and Internet Explorer 8® are regis-tered trademarks of the Microsoft Corporation.

Mozilla® Firefox 3.5® and Firefox 3.6® are registered trademarks of the Mozilla Foundation.

Nortel® is a registered trademark of Nortel Networks, Inc.

Oracle®, Java, and Solaris are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective own-ers.

Red Hat® is a registered trademark of Red Hat, Inc. in the United States and other countries.

Windows®, Windows NT®, Windows 2000®, and Windows XP® are registered trademarks of Microsoft Corporation.

The following are trademarks or registered trademarks of Tone Soft-ware Corporation:

• Tone Software

• ReliaTel

• STEPAR

Other products mentioned in this publication may be trademarked, registered, or copyrighted by their respective owners.

Acknowledgement of third party licenses will be found in "Appendix B Third Party Licenses" on page 65.

vi STEPAR User Guide

Table of Contents

Introduction

Key Features ................................................................................................................................................... 1General Prerequisites .................................................................................................................................... 1Report Components ...................................................................................................................................... 2Installing STEPAR ......................................................................................................................................... 3

Installation Prerequisites ................................................................................................. 3Installation Procedure ..................................................................................................... 3Check Installation .......................................................................................................... 4Install Additional STEPAR Components............................................................................. 5

Centers and Entities

About Centers and Entities .......................................................................................................................... 7Edit a Trunk Group ....................................................................................................................................... 7Change an Entity’s Data Retention Time (“Setup”) ............................................................................... 12

Using and Customizing Reports

Running a Predefined Report .................................................................................................................... 15Selecting Output Format............................................................................................... 16Selecting Entity Names................................................................................................. 18Selecting Dates ........................................................................................................... 18Customizing a Predefined Report ................................................................................... 19Hiding a Report ........................................................................................................... 22Unhiding a Report ........................................................................................................ 22Saving a Customized Report.......................................................................................... 23

Predefined Reports

Base Reports ................................................................................................................................................. 25Alarm and Performance Composite Report ...................................................................... 25Alarm Reports ............................................................................................................. 25Performance Metrics Reports ........................................................................................ 26Capacity Reports ......................................................................................................... 27

Avaya Audit Reports .................................................................................................................................. 29Avaya Definity Traffic Reports ................................................................................................................. 31

Attendant Reports ....................................................................................................... 31Audit Reports.............................................................................................................. 32Blockage Study Reports................................................................................................ 33Call Rate Reports ......................................................................................................... 34Hunt Group Reports ..................................................................................................... 35Port Network Load Balance Reports ............................................................................... 35Processor Occupancy Reports ....................................................................................... 36

2 ReliaTel Administrator Guide

Trunk Reports ............................................................................................................. 36CDR Reports ................................................................................................................................................. 39

Raw CDR Data Report .................................................................................................. 39Most Used Extensions Report........................................................................................ 39Most Dialed Numbers Report......................................................................................... 39Switch Daily Report ..................................................................................................... 39Switch Summary Report ............................................................................................... 39Extension Daily Report ................................................................................................. 39Extension Summary Report ........................................................................................... 39Extension Detailed Report ............................................................................................. 40Extension Transfer Report............................................................................................. 40

Cisco CallManager Reports ........................................................................................................................ 41CallManager Report...................................................................................................... 41CDR Raw Data Report .................................................................................................. 41CMR Trend Chart......................................................................................................... 41CMR Raw Data Report ................................................................................................. 41Gateway Utilization Reports .......................................................................................... 41Information Status Reports ........................................................................................... 42Performance Reports.................................................................................................... 42

Ericson MD110 Reports .............................................................................................................................. 44Trunk Reports ............................................................................................................. 44

Lucent 5ESS Reports ................................................................................................................................... 45Plant 24 Hour Report ................................................................................................... 45Daily Report ................................................................................................................ 45Weekly Report............................................................................................................. 45Executive Report ......................................................................................................... 45Plant Monthly Report ................................................................................................... 45

Nortel Meridian Traffic Reports ................................................................................................................ 46Console Reports .......................................................................................................... 46Dial Tone Delay Reports ............................................................................................... 47Junctor Reports........................................................................................................... 48Networks Reports ........................................................................................................ 49Processor Load Reports ................................................................................................ 49Trunk Reports ............................................................................................................. 50

Nortel QoS IP Reports ................................................................................................................................. 51QoS IP Statistics Report ............................................................................................... 51

Nortel SL100 Traffic Reports ...................................................................................................................... 51Daily Traffic Report...................................................................................................... 51Traffic Summary Report ............................................................................................... 51

Appendix A - Glossary

Appendix B - Third Party Licenses

Syntax and Conventions

The following conventions are used in this manual:

Any text that appears on a display monitor or must be entered at the keyboard is shown within a box, for example:

A text line that may exceed the right boundary of the box is split and continued on one or more indented lines. Enter these lines as a single line and they will appear as a single line when displayed on the moni-tor.

Capital letters indicate literal text. Lower case letters indicate a vari-able field for which a value must be supplied.

Keyboard entries that require special function keys are indicated by enclosing the special function key within brackets. For example, an instruction advising you to “press F3” is printed as follows: “Press [F3].”

If a field can be filled with two or more optional values, the optional values are shown enclosed within a pair of braces, { }, and separated by a vertical bar, |. Only one of the listed values may be specified. If there is a default value, it is underlined.

Optional text is shown enclosed within a pair of brackets, []. A special, user-supplied value is represented by a word, abbreviation, or phrase describing the desired data and enclosed within a “greater-than” and “less-than” symbol pair (< >). For example, if the name of a month must be supplied, the request is indicated as:

Text within a paragraph that requires special attention is printed in bold italics.

Special information that is vital to the proper operation of this product are set off in a bold-faced paragraph, for example:

NOTE: Please look for these notes to ensure proper operation of this product. Within paragraphs, if there is something important that needs emphasis, then it will be in bold and/or italic.

browse file=actlog

Calendar=<month_name>

4 STEPAR User Guide

Chapter 1 Introduction

STEPAR is an optional reporting component for the ReliaTel Management Solution. It enables telecommunications professionals to quickly and easily produce comprehensive statistical reports detailing the activity of all ReliaTel-managed devices.

Key Features

• Pre-configured reports analyze and summarize conditions and activities of the monitored systems and devices.

• Convenient web interface provides report access through any standard web browser.

• Wide variety of available pre-configured reports including daily, weekly, geo-graphical, and executive-oriented statistics and trends.

• Pre-configured reports are easily customized for specific devices, time frames and events.

General Prerequisites

The data that STEPAR uses to compile reports & charts is supplied by the ReliaTel monitoring and data collection software, making ReliaTel a prerequisite. Devices and systems (referred to as “entities”) monitored by ReliaTel must first be configured in ReliaTel, as must the users who will work with STEPAR reports.

2 STEPAR User Guide

Report Components

Report components allow you to purchase only the capabilities you require for your STEPAR reports. The STEPAR application includes Base Reports only. All other report components are optional and must be purchased separately. The following report components are currently available for use with STEPAR:

NOTE: STEPAR requires an installed and configured ReliaTel, and the individual STEPAR report components require an installed and configured STEPAR. The mini-mum STEPAR package therefore requires ReliaTel, STEPAR, and at least one of the report components. See the illustration below.

The following Report Components are available:

• ReliaTel Base Reports• Avaya Definity Traffic Reports• Lucent 5ESS Reports• Call Detail Record Reports• Nortel Meridian Traffic Reports• Nortel SL100 Traffic Reports

Chapter 1 Introduction 3

Installing STEPAR

NOTE: If you are using the ReliaTel Remote Monitoring Service, installation has already been done for you. Skip this installation procedure and go directly to Chap-ter 2, “Centers & Entities.”

Prior to beginning the installation of a STEPAR optional component, make sure that the following conditions are met:

Installation Prerequisites

• ReliaTel must be installed and running. STEPAR and its optional compo-nents cannot be installed as stand-alone applications.

• Java 2 platform Standard Edition (“J2SE”) SDK version 1.4.2 or above installed. (Downloadable from:http://java.sun.com/j2se/1.4.2/download.html

• Red Hat Enterprise Linux - AS, or Sun SPARC Solaris 2.8, installed and operational.

• The user installing STEPAR must be root.

Installation Procedure

1. Stop the ReliaTel system:

2. Verify that ReliaTel has stopped:

If the system responds as above, with a header but not entries, this means that there are no processes (‘ps’) running for user (‘-fu’) ReliaTel (‘rlt’).

# /etc/init.d/ems stop

# ps -fu rltUID PID PPID C STIME TTY TIME CMD

4 STEPAR User Guide

3. Insert the STEPAR distribution CD-ROM in the CD reader and run Package installation:

4. The script searches for the J2SE SDK package:

NOTE: If the script does not find the J2SE SDK package or if it is the wrong ver-sion, the script will stop and display an error message.

5. The script shows the ReliaTel owner, group, and installation directory, then asks whether to proceed. Accept this by pressing <Enter>; a long list of packages will load, then file ownerships and permissions will be set:

Check Installation

Package installation is complete; follow the steps below to check that the installed programs are functional:

1. Start the ReliaTel application:

NOTE: It can take several minutes for STEPAR to start; if Step 2 does not indicate that the two components main and struct are installed, it may be because Step 1 has not completed yet; try waiting and checking again.

# mount /dev/cdrom# cd /mnt/cdrom# sh packages/RLTstepar-2.4-b120-linux.tpmunpacking.......[Reporting Solution/STEPAR Main Package]Installing STEPARmain 2.4/96 (linux)User? [rlt] <ENTER>

Locating java SDK ...### Using JVM /usr/java/j2sdk1.4.2/bin/java

### Installing as user "rlt", group "rlt" in /tone/reliatel.Proceed? [yes] <ENTER>...Setting file ownerships .............Setting file permissions ............#

[root@tesla distrib]# /etc/init.d/ems startStarting ReliaTel in /tone/reliatel[root@tesla distrib]#

Chapter 1 Introduction 5

At this point, you should be able to enter the URL:

http://tesla:8080/ems

in your web browser and view the ReliaTel reports listed. At least one report module must be added; we used Alarms (RLTalarm) in this example.

NOTE: In the URL above, the machine name “tesla” is used as an example; use the ReliaTel host name appropriate for your network.

Click the “Performance Reporting” tab in ReliaTel

Install Additional STEPAR Components

To install an additional STEPAR component:

1. Shutdown the ReliaTel application:

2. Insert the ReliaTel distribution CD-ROM in the CD reader, mount the CD-ROM and run

3. :

4. The script asks whether to proceed; accept this by pressing <Enter>; a long list of packages will load, then file ownerships and permissions will be set:

[root@tesla root]# /etc/init.d/ems stopShutting down server localhost:8080Shutdown complete[root@tesla root]#

# mount /dev/cdrom# cd /mnt/cdrom# sh packages/RLTalarm-2.4-b96-linux.tpmUnpacking.......[Reporting solution/ReliaTel Alarm Reports]Installing RLTalarm 2.4/1 (linux)

Enter Installation directory? [/tone/reliatel]reliatel### Installing as user "reliatel" group "reliatel" in /tone/reliatelProceed? [yes] <ENTER>

Setting file ownerships .......................Setting file permissions...................................#

6 STEPAR User Guide

5. Open a ReliaTel web page and click the Performance Reporting tab. The left part of the window should now show the added reports available.

NOTE: It can take several minutes for ReliaTel to start; if the web page link is not responding, it may be because ReliaTel has not completed the startup; try waiting and checking again.

Open a Web browser to the URL:

http://tesla:8080/ems/

The ReliaTel Login window should now appear, along with the Base Reports. Login with the user name and password for your ReliaTel system; Base Reports should now be functional.

NOTE: The default login for ReliaTel and STEPAR is:user = sadm; password = ems

Install any additional STEPAR Report components using the same steps as the example above for the Base Reports component.

Chapter 2 Centers and Entities

About Centers and Entities

• ReliaTel centers and entities must be defined and configured in ReliaTel. Cen-ters/entities are not created within STEPAR.

• STEPAR automatically populates its centers and entities lists with the names of the centers and entities defined in ReliaTel and the Data Collection Engine.

• If you are using the ReliaTel Remote Monitoring Service, contact your techni-cal representative to add new centers/entities or change existing ones.

• If ReliaTel is running at your facility, contact your ReliaTel System Administra-tor to add new centers/entities or change existing ones.

Edit a Trunk Group

NOTE: If you have not purchased a traffic reporting component, the instructions in this section are not relevant to your system.

A ReliaTel user with ADMIN permissions can edit some of the Trunk Group information.

8 STEPAR User Guide

On the main Performance Reporting window, select Entities:

In the resulting window, Centers and Sub-Centers are listed on the left part of the window. Click on a center or subcenter to display an additional column showing the names of the entities associated with the selected center/sub-center. In this example, we’ve selected the center “test”:

Chapter 2 Centers and Entities 9

and the entity “Nortel-Data”:

Click the Edit Trunk Groups link on the left side of the window.

NOTE: A ReliaTel user with ADMIN permissions can click the DELETE button to delete the entity. All the historical data for the deleted entity will be lost.

The Trunk Groups window is displayed:

10 STEPAR User Guide

Make changes to the information in the Trunk Description.


Trunk Group Numbers are listed in the left column, followed by description, Owner, Grade-Of-Service, and Traffic Formula fields.

All of the fields except Group number and Traffic Formula are over-typeable; make changes by typing the new information over the current information. For the Traffic Formula column, use the drop-down box to select either Poisson or Erlang-B.

When changes are complete, click Update to save the changes and exit, or click Cancel to ignore the changes and exit.


Change an Entity’s Data Retention Time (“Setup”)

To change the length of time (in days) that an entity’s data is retained in the ReliaTel database:

From the main performance reporting window, click the Entities tab; the Center/Subcenter window opens.

Select the center or sub-center; a list of entities in the selected center is displayed.

Select the entity to be changed.

Click the Change Setup link:


The Entity Setup window opens:

Overtype the number in the Data Lifetime field with the new value, then click the Update button.

Chapter 3 Using and Customizing Reports

Running a Predefined Report

NOTE: Chapter 4, Predefined Reports, contains a full list and description of the pre-defined reports.

Depending on which report components you’ve chosen to install for STEPAR, a screen similar to the one below appears when you start STEPAR and select the Reports tab.

This is the list of all reports available to you; the minimal installation will show only the Base Reports list associated with the ReliaTel system. (Users of the ReliaTel Remote Monitoring Service will see only this minimal report listing).

Any additional sets of reports are grouped by particular manufacturers and models of PBX devices, systems, and other devices. Initially, only the pre-defined reports that ship with STEPAR are displayed.


Although the predefined reports are extensive, you and/or your ReliaTel Administrator may add customized reports as well. All the reports, both predefined and customized, are displayed in this window.

Select an alarm report from the STEPAR window, or open one of the device lists by clicking the “+” box next to the PBX name, and selecting from the list of reports that is displayed. (Click the “-“box to collapse the list display.)

One of the advantages of STEPAR is the number and variety of predefined reports available. Another advantage is flexibility. Some pre-defined reports are as simple as the following example.

Selecting Output Format

The default output format for charts is pdf (portable document format). The output may be changed by clicking the down pointing arrow next to the drop down menu. The options are pdf, html, csv, and

Chapter 3 Using and Customizing Reports 17

The majority of predefined reports offer more flexibility, such as the following:


Selecting Entity Names

In general, predefined reports allow you to modify the date or range of dates that the report covers, and the entities (devices or switches) the report covers.

NOTE: If a report window shows a scrollable box listing device names, you can select more than one device name by holding down the <Ctrl> key, then clicking multiple selections; release the <Ctrl> key when selections are complete; all your selections should remain highlighted.

Selecting Dates

In the upper-right corner there are three ways to select a date or a range of dates for the report:

• For reports that are designed to display activities for the previous month, the previous week, the previous day, or the current day, select - “Last Month,” “Last Week,” “Yesterday,” or “Today” from the “Relative Range” drop-down menu. Note that you must click the radio button before select-ing the date range.

NOTE: All the date ranges are relative to the date they are selected. Therefore, if you wish to look at yesterday’s report two days from now, you will enter an exact date range.

• If you prefer a monthly calendar format, click the radio button for “Exact Range”, and then click the calendar icons to select date.

• Select the date from the calender, or enter the date information in mm/dd/yyyy format; use the left and right arrows on the calendar display to change the month.

When you’ve made the necessary selections, click the Run Report button.

NOTE: It is possible that some data cells in your report will contain an asterisk (“*”) rather than data. This indicates that there was not sufficient data to calculate the value for that cell.


Customizing a Predefined Report

To make more extensive modifications to an existing report and save it for subsequent use, use the procedure below.

Start by viewing a report that is similar to the report you’d like to create. In this procedure, the Alarm Report - Time to Respond is used as an example. Click Customize This Report. A window titled Customize Alarm Report - Time To Respond. It has three tabbed pages labelled General, Parameters, and Classes. These three tabs contain fields where you can make the changes necessary to customize the report.

Alarm Report - Time to Respond General tab:

Tab Name Field Name Description

General Report Name The name of the report being modified; change it to be descriptive of the new, customized report.

Report Description Similar to Report name above; change it to describe the new customized report.

Make report available for others

To allow others to use the new, modified report, check the “Make report available for other users.”


Alarm Report - Time to Respond Parameters tab.



Parameters Orientation Select Landscape or Portrait orientation for the report output.

Output Format Use the drop-down box to select from PDF (Adobe Acrobat), Excel, or CSV (Comma-Sepa-rated Values) output file format.

Date Range See the previous discussion “Selecting Dates.”

Entity Name Select the entity (switch or device) name(s) on which the report is to be based.

Entity Class Select the entity class name(s) on which the report is to be based. Note that in some reports, all entity classes may be selected or you may make multiple selections by using the <Ctrl> key and clicking on the individual items.

Centers Select the center name(s) on which the report is to be based. Note that in some reports, all entity classes may be selected or you may make multi-ple selections by using the <Ctrl> key and click-ing on the individual items.

Severity Level Alarm reports allow you to select the alarm sever-ity level to be displayed in the report. Click the desired severity level(s).

Alarm Text Enter the specific alarm message text on which the report is based.

Display Columns Some predefined reports allow you to select whether or not to display particular report data. For reports with this option available, you may also make the selections part of your customized report. Select using the checkboxes.

Hide Fields Most fields have an optional Hide checkbox; check the Hide check box of any report fields that you do not want to see when running this cus-tomized report.


Alarm Report - Time to Respond Classes tab:

Hiding a Report

A user with the ADMIN permission in ReliaTel can hide an entire pre-defined report; reports hidden this way do not show up in the list of reports available to STEPAR users.

To hide a report:

• Open the report • Select Customize This Report. • De-select the Make report available for other users checkbox.• Click the “Save” button.

Unhiding a Report

A user with the ADMIN permission in ReliaTel can unhide a previously hidden pre-defined report:


Classes <Various> Any equipment classes that have been defined in ReliaTel will appear in the “Applicable to” area with a checkbox. Use the check boxes to restrict the report results to only those classes with a check box checked.


• Open the “hidden” report• Check the Make report available for other users checkbox.• Click the Save button.

Saving a Customized Report

When report customization is complete:

• Make sure the Report Name field contains a name different than its original name.

• Click the Save as New button; the Report Name and Description for the cus-tomized report now appear in the same list as the report on which it was based.

Chapter 4 Predefined Reports

Base Reports

Alarm and Performance Composite Report

Provides an overall snapshot of the entity based on an interval.

Alarm Reports

Provides data for active, acknowledged, and cleared alarms. The date and time that the alarm was created is the basis for gathering this date.

Alarm Report - Time To Respond

Data gathered for this report pertains to alarms that have been acknowledged. It provides an analysis of the time taken to respond to each alarm and the average response time, for the selected entities.

The report date range will need to include the date and time when the alarm occurred, rather than when it was acknowledged, in order to view the time to respond data.

Alarm Report - Time To Resolve

Data gathered for this report pertains to alarms that have been cleared. Provides an analysis of the time taken to resolve each alarm and the average resolution time, for the selected entities.

The report date range will need to include the date and time when the alarm occurred, rather than when it was cleared, in order to view the time to resolve data.


Active Alarms Report

This report lists all active alarms for selected entities. An active alarm is defined as an alarm with a state of New or Acknowledged. Alarms with a state of Cleared will not appear in this report.

Active Alarms Chart

Using graphs and charts, all currently active alarms for selected entities are displayed. An active alarm is an alarm that has not been cleared.

Alarm Summary Daily Report

Shows the number of alarms, total time and average time to respond (acknowledge) and total time and average time to resolve (clear) for the specified entity, on a daily basis.

The report date range will need to include the date and time when the alarm occurred, rather than when it was acknowledged or cleared, in order to view summary data.

Alarm Summary Daily Chart

Graphs the number of alarms, total time and average time to respond (acknowledge) and total time and average time to resolve (clear) for the specified entity, on a daily basis.

The report date range will need to include the date and time when the alarm occurred, rather than when it was acknowledged or cleared, in order to view summary data.

Performance Metrics Reports

Monitor Report

Shows the monitor values for specified entities and date range.

Monitor Chart

Graphs the monitor values for specified entities and date range.

Chapter 4 Predefined Reports 27

Capacity Reports

Raw Data Report

Displays raw data as it is received from switches.

Busy Hour Report

Displays traffic metrics and statistical analysis for each busy hour of requested selection.

Average Hold Time per Site Chart

Displays inbound and outbound Average hold Time for each site based on aggregated traffic metrics for selected date range, platform, and sites.

Calls Rate per Site Chart

Displays inbound and outbound Calls per Second for each site based on aggregated traffic metrics for selected date range, platform, and sites.

Loading and Blocking per Site Chart

Displays percentage of loading and blocking for each site based on aggregated traffic metrics for selected date range, platform, and sites.

Daily Trend Chart

Displays changes of aggregated traffic metrics for selected data range, platform, and site on daily basis.

Interval Aggregated Report

Displays traffic metrics and statistical analysis aggregated over the selected period of time.

Site Aggregated Report

Displays traffic metrics and statistical analysis aggregated per site.


Platform Aggregated Report

Displays traffic metrics and statistical analysis aggregated per platform.


Avaya Audit Reports

Media Server Port County (TDM Ports) Report

Shows historical media server system configuration data grouped by entities and dates for the specified entities and date range.

Maximum Port Usage Statistics Report

Shows daily statistics on maximum resources used for the specified entities and date range.

Media Gateway Report

Shows historical media gateway data grouped by entities and dates for the specified entities and date range.

Media Server Survivable Processor Report

Shows historical survivable processor data grouped by entities and dates for the specified entities and date range.

Media Server Port Count Details (Licensed, IP, and ACD Ports) Report

Shows historical media server port count details data for the specified entities and date range. Groups data by entities.

Media Server Port Count Summary Report

Shows media server port count audit summary based on the most recent data for the specified entities. Groups data by entities.


Avaya Definity Traffic Reports

Attendant Reports

Attendant Group Data Analysis

Lists the values: 'Average Work Time (AWT)', 'Staffed Time', ‘Manned Positions', Attendant Offered Load (AOL)', '% Occupancy', '% Calls Queued', Speed of Answer (SOA)',% of Delayed Calls (PDC)' and 'Average Delay of Delayed Calls (ADDC)'. This report also lists estimates of Attendant Group performance for different numbers of agents. The report is generated for the specified device and date range on an hourly basis.

Attendant Group Data Analysis Chart

Displays daily performance averages for the attendant group as a whole, for each day in the date range.

Attendant Group Daily Report

Lists attendant group measurements for the specified devices in the specified date range.

Attendant Group Daily Chart

Displays daily measurements for the attendant group as a whole, for each day in the specified date.

Attendant Group Hourly Report

Lists attendant group hourly measurements for the specified devices in the specified date range.

Attendant Group Hourly Chart

Displays hourly measurements for the attendant group as a whole, for the specified date range.


Attendant Group Peak Chart

Displays daily peak measurements for the attendant group as a whole, for each day in the specified date range.

Attendant Group Peak Report

Lists attendant group measurements for the specified devices in the specified date range.

Attendant Group Totals Report

Lists attendant group totals for the specified devices in the specified date range.

Attendant Position Peak Report

Lists attendant position peak measurements for specified devices in the specified date range.

Attendant Position Hourly Report

Lists attendant position measurements for the specified devices in the specified date range.

Audit Reports

Media Server Port Count Details (TDM Ports) Report

Shows historical media server system configuration data grouped by entities and dates for the specified entities and date range.

Maximum Port Usage Statistics Report

Shows daily statistics on maximum resources used for the specified entities and date range.

Media-Gateway Report

Shows historical media gateway data grouped by entities and dates for the specified entities and date range.


Media Server Survivable Processor Report

Shows historical survivable processor data grouped by entities and dates for the specified entities and date range.

Media Server Port Count Details (Licenses, IP, and ACD Ports) Report

Shows historical media server port count details data for the specified entities and date range; groups data by entities.

Media Server Port Count Summary Report

Shows media server port count audit summary based on the most recent data for the specified entities; groups data by entities.

Blockage Study Reports

Switch Node Blockage Daily Chart

Displays usage and blockage daily measurements for the specified device, SN, and date range.

Switch Node Blockage Daily Report

Lists usage and blockage daily measurements for the specified devices in the specified date range.

Switch Node Blockage Hourly Chart

Displays usage and blockage hourly measurements for the specified device, SN, and date range.

Switch Node Blockage Hourly Report

Lists usage and blockage hourly measurements for specified devices in the specified date range.


Port Network Blockage Daily Chart

Displays TDM and PNL usage and blockage daily measurements for the specified device PN and date range.

Port Network Blockage Daily Report

Lists TDM and PNL usage and blockage daily measurements for the specified devices in the specified date range.

Port Network Blockage Hourly Chart

Displays TDM and PNL usage and blockage hourly measurements for the specified device PN and date.

Port Network Blockage Hourly Report

Lists TDM and PNL usage and blockage hourly measurements for the specified devices in the specified date range.

Call Rate Reports

Call Rate Hourly Report

Lists number of completed calls for the specified device and date range.

Call Rate Hourly Chart

Displays number of completed calls for the specified device and date.

Call Rate Daily Report

Lists completed calls daily totals for the specified device and date range.

Call Rate Daily Chart

Displays completed calls daily totals for the specified device and date range.


Hunt Group Reports

Hunt Group Busy Hour Report

Lists hunt group busy hour measurements for the specified device and date range.

Hunt Group Hourly Report

Lists hunt group hourly measurements for the specified device and date range.

Hunt Group Hourly Chart

Displays hunt group hourly measurements for the specified device, group number and date.

Hunt Group Daily Report

Lists hunt group daily totals for specified device and date range.

Hunt Group Daily Chart

Displays hunt group daily measurements for the specified device, group number and date range.

Port Network Load Balance Reports

Port Network Load Balance Hourly Report

Lists TDM and PNL usage, blockage and occupancy hourly measurements for the specified devices in the specified date range.

Port Network Load Balance Hourly Chart

Displays TDM and PNL usage blockage and occupancy hourly measurements for the specified device, PN, and date range.


Port Network Load Balance Daily Report

Lists TDM and PNL usage, blockage and occupancy daily measurements for the specified devices in the specified date range.

Port Network Load Balance Daily Chart

Displays TDM and PNL usage, blockage and occupancy daily measurements for the specified device, PN, and date.

Processor Occupancy Reports

Processor Occupancy Hourly Report

Lists processor occupancy for specified devices in the specified date range, on an hourly basis.

Processor Occupancy Hourly Chart

Displays processor occupancy measurements for each hour of the specified date.

Processor Occupancy Daily Report

Lists processor occupancy daily totals for specified devices in the specified date range.

Processor Occupancy Daily Chart

Displays processor occupancy daily totals for each day in the specified date range.

Trunk Reports

Trunk Group Data Analysis

Provides the values: 'Average Holding Time' and '% Group Blockage' for each trunk group. Estimates number of trunks required to handle traffic with the given value of 'GOS'.


Trunk Capacity Planning

Shows trends in trunk utilization for each trunk group for each month of the selected year

Trunk Group Busy Hour Report

Provides traffic measurements summary for each busy hour in the specified date range.

Trunk Group Busy Hour Chart

Displays trunk group measurements for the busy hour of each day in the date range.

Trunks Out of Service

Displays number of trunks out of service reported for the last hour. Shows number of Out of Service trunks per each trunk group reported within last hour.

Trunk Group Hourly Report

Provides the data necessary to validate the information in the Trunk Group Summary Report and to size the trunk groups.

Trunk Group Hourly Chart

Displays trunk group measurements for each hour of the specified day.

Trunk Group Summary Hourly Report

Provides traffic summary hourly measurements for the specified device and date range.

Trunk Group Summary Hourly Chart

Displays trunk group hourly measurements for the specified device, trunk group, and date range.


Trunk Group Summary Daily Report

Provides traffic summary daily totals for the specified device and date.

Trunk Group Summary Daily Chart

Displays trunk group daily totals for the specified device, trunk group and date range.

Trunk Outage Daily Report

Lists Trunk Outage measurements for the specified devices in the specified date range.

Trunk Lightly Used Daily Report

Lists Trunks lightly used measurements for the specified devices in the specified date range


CDR Reports

Raw CDR Data Report

Displays all CDR data available for the specified switches and date range.

Most Used Extensions Report

Lists the given number of extensions for selected switches and date range that originated or received the most number of calls.

Most Dialed Numbers Report

Lists the top-n numbers dialed for selected switches and date range.

Switch Daily Report

Lists the total duration and total number of calls for specified date range and switches on daily basis.

Switch Summary Report

Lists the total duration and total number of calls for specified date range and switches.

Extension Daily Report

Lists the total duration and total number of calls grouped by extensions for specified date range and switches on daily basis.

Extension Summary Report

Lists the total duration and total number of calls for specified date range and switches.


Extension Detailed Report

Lists call time, duration, number called and type of each call for date range extensions and switches.

Extension Transfer Report

Lists all CDR data for calls that were transferred.


Cisco CallManager Reports

CallManager Report

Lists daily totals grouped by centers and entities for specified date range and switches.

CDR Raw Data Report

Lists raw CDR data grouped by date for the selected switch and date range.

CMR Trend Chart

Displays CCM call quality metrics for the specified entity and date range.

CMR Raw Data Report

Lists raw CMR data grouped by date for the selected switch and date range.

Gateway Utilization Reports

Gateway Utilization Trend Chart

Displays 5-minute increment gateway utilization for the specified gateway, entity, and date range.

Gateway Utilization Report

Lists maximum calls allowed, number of calls, and maximum % utilization, grouped by switch and gateway based on the given granularity: 5 minutes, hourly, daily, and monthly.

Gateway Utilization Yearly Report

Lists maximum % utilization for each month of the given year.


Information Status Reports

Gatekeeper Status Report

Lists all Gatekeepers to which the local CallManager has tried to register at least once

Gateway Status Report

Lists entries in the gateway table, one for each gateway device in the CCM

Phone Failed Status Report

Lists all phones which attempted to register with the local call manager and failed. The entries which have not been updated and kept at least for the duration specified in the ccmPhoneFailedStorePeriod will be deleted. Reasons for these failures could be due to configuration error, maximum number of phones has been reached, lost contact, etc

Trunk Status Report

Lists all gateway trunks in a CCN system

Performance Reports

CPU Utilization Trend Chart

Displays CCM CPU utilization chart on hourly or daily basis for the specified entity and date range.

Number of Registered Devices Chart

Displays average number of registered devices chart on hourly or daily basis for the specified entity and date range.

Transcode Resources Chart

Displays Resource Total, Resource Available, Resource Active, and Out of Resources chart on hourly or daily basis for the specified entity and date range.


Memory Usage Chart

Displays CCM memory usage chart on hourly or daily basis for the specified entity and date range.

Attempted versus Completed Calls Chart

Displays CCM attempted and completed calls chart on 15 minute, hourly, or daily basis for the specified entity and date range.


Ericson MD110 Reports

Trunk Reports

Trunk Hourly Report

Displays trunk hourly measurements for the specified device and date range.

Trunk Daily Report

Displays trunk daily totals for the specified device and date range.

Trunk Busy Hour Report

Displays busy hour trunk measurements for the specified device and date range.


Lucent 5ESS Reports

Plant 24 Hour Report

The Plant 24 Hour Report provides a comprehensive summary of 5ESS device performance for the latest 24-hour period.

Daily Report

Summarizes the lengthy 5ESS Switch ROP output into a manageable form, and provides a summary showing how the 5ESS office is performing.

Weekly Report

Compiles the 5ESS Switch ROP output into a 7-day summarization, providing office personnel and management with a 5ESS Switch office performance report. Report covers all categories of the daily report in a 7-day format.

Executive Report

Provides a daily NSPMP analysis of the office performance, based on ROP data.

Plant Monthly Report

The report based on the 5ESS’ PLNTMO output.


Nortel Meridian Traffic Reports

Console Reports

Customer Console Queue Hourly Report

Lists the treatment of calls in customer queues: speed of response, number of calls delayed, number of calls abandoned, average wait time of delayed calls, and average wait time of abandoned calls for specified devices within specified date range.

Customer Console Queue Hourly Chart

Displays customer console queues measurements: speed of response, number of calls delayed, number of calls abandoned, average wait time of delayed calls, and average wait time of abandoned calls for specified devices, and a specific date, on an hourly basis.

Customer Console Queue Daily Report

Lists daily totals of calls in customer queues: speed of response, number of calls delayed, number of calls abandoned, average wait time of delayed calls, and average wait time of abandoned calls for specified devices within a specified date range.

Customer Console Queue Daily Chart

Displays customer console queues daily totals: speed of response, number of calls delayed, number of calls abandoned, average wait time of delayed calls, and average wait time of abandoned calls for specified devices within specified date range.

Individual Console Hourly Report

Lists the following hourly measurements per attendant: total number of calls, work time per call, total amount of time the console was attended, etc., for a specified attendant, customer and device, for a specified date.


Individual Console Hourly Chart

Displays the following hourly measurements: total number of calls, work time per call, total amount of time the console was attended, etc., for a specified attendant, customer and device, for a specified date.

Individual Console Daily Report

Lists daily totals per attendant: total number of calls, work time per call, total amount of time the console was attended, etc., for specified customer and devices within a specified date range.

Individual Console Daily Chart

Displays the following daily totals: total number of calls, work time per call, total amount of time the console was attended, etc., for specified attendant, customer and device within a specified date range.

Console Data Analysis

Provides values of Average Work Time (AWT), Offered Load (OL), Speed of Answer (SOA), Percentage of Delayed Calls (PDC) and Average Delay of Delayed Calls (ADDC) as well as estimates of Group performance for different numbers of agents. Report is generated for the specified device and date range on hourly basis.

Individual Console Daily Chart

Displays the following daily totals: total number of calls, work time per call, total amount of time the console was attended, etc., for specified attendant, customer and device within a specified date range.

Dial Tone Delay Reports

Dial Tone Delay Hourly Report

Lists an hourly report of the number of times users waited for dial tone for longer than the selected delay period, for the specified device and date range.


Dial Tone Delay Hourly Chart

Displays an hourly chart of the number of times users waited for dial tone for longer than the selected delay period, for the specified device and date range.

Dial Tone Delay Daily Report

Lists a daily report of the number of times users waited for dial tone for longer than the selected delay period, for the specified device and date range.

Dial Tone Delay Daily Chart

Displays a daily chart of the number of times users waited for dial tone for longer than the selected delay period, for the specified device and date range.

Junctor Reports

Junctor Busy Hour Report

Lists junctor busy hour measurements for the specified devices in the specified date range.

Junctor Busy Hour Chart

Displays junctor busy hour measurements for the specified device and junctor group within the specified date range.

Junctor Measurements Hourly Report

Lists junctor hourly measurements for the specified devices in the specified date range.

Junctor Hourly Chart

Displays junctor hourly measurements for the specified device on the specified date.


Networks Reports

System Networks Busy Hour Report

Lists system networks busy hour measurements for the specified device in the specified date range.

System Networks Busy Hour Chart

Displays system networks busy hour measurements for the specified device and loop in the specified date range.

System Networks Hourly Report

Lists system networks hourly measurements for the specified devices in the specified date range.

System Networks Hourly Chart

Displays system networks hourly measurements for the specified devices on the specified date.

System Networks Daily Report

Lists system networks daily totals for the specified devices in the specified date range.

System Networks Daily Chart

Displays system networks daily totals for the specified devices in the specified date range.

Processor Load Reports

Processor Load Hourly Report

Lists the load on the system, showing the peg count for CPU functions: idle cycle count (ICC), total CPU attempts (CA), load peak peg, input/output buffer


overflow, and call register overflow for devices within a specified date range on hourly basis.

Trunk Reports

Trunk Hourly Report

Lists trunk hourly measurements for the specified devices in the specified date range.

Trunk Hourly Chart

Displays trunk group measurements for each hour of the selected day.

Trunk Daily Report

Lists trunk daily totals for the specified devices in the specified date range.

Trunk Daily Chart

Displays trunk group daily totals for the specified device, trunk group, and date range.

Trunk Busy Hour Report

Lists trunk busy hour measurements for specified switches within a specified date range. The “Busy hour” is the one-hour period with the highest value of ‘Incoming Usage + Outgoing Usage.’

Trunk Busy Hour Chart

Displays trunk busy hour measurements for specific switch, route number, and date range.The “Busy hour” is the one-hour period with the highest value of ‘Incoming Usage + Outgoing Usage

Trunk Data Analysis

Lists the values of ‘Average Holding Time’ and’% Group Blockage’ for each trunk group. Estimates the number of trunks required to handle traffic with the given value of GOS (Grade of Service).


Nortel QoS IP Reports

QoS IP Statistics Report

Report lists IP Phone data at the zone level. The data is for intrazone and interzone basis for the selected date range and switches.

Nortel SL100 Traffic Reports

Daily Traffic Report

Daily traffic report of selected device measurements for a selected date range.

Traffic Summary Report

Summary traffic report of selected device measurements for a selected date range.

Appendix A Glossary

Table 1: Glossary Definitions

Term Typical Abbreviation

Definition

Abandoned Aband, Abd Calls that drop (i.e., the caller hangs up) before an atten-dant answers.

500/2500 OB Ovf 500/2500 Output Buffer overflow peg count

Acknowledge Ack To respond to an alarm generated by the system, inform-ing the system that an operator is aware of the alarm con-dition. Note that this does not clear the alarm.

Acknowledged Ack-ed The number of alarms acknowledged by an operator.

Alarm Alm An alarm is an indication generated by the system to notify an operator that a monitored entity (switch) has encountered a problem condition

All Loops Busy All local loops busy

Answered Ans The number of calls answered (i.e., completed).

All Trunks Busy ATB Counts the number of times all trunks in a multi-trunk operation are busy.

AOL AOL Attendant Offered Load = the sum of (Calls Answered + Calls Abandoned) * Average Work Time.

Attendant Attd An attendant is a person whose job includes answering telephone calls.

Attended Time The total time, in CCS, that the console is not in Night Service or Position Busy.

Attendant Group Two (2) or more attendants assigned to a named and/or numbered group for purposes of performance measure-ment.

Attendant Offered Load

AOL The Attendant Offered Load (AOL) is the sum of Calls Answered plus Calls Abandoned times Average Work Time.

(Calls Ans + Calls Ab) * AWT

Attendant Position Part of a report showing how individual attendants’ per-formance compares to the other members of the Atten-dant Group.

Auxiliary Identification

AUXID Identifies the TN of the originating telephone when the telephone has a multiple appearance Prime DN, and can-not be uniquely identified by ORIGID.


Average Delay of Delayed Calls

ADDC Average delay of calls that are delayed. It is the total Delay for all calls divided by the number of calls that had to wait in queue.

Average Hold Time The average time that the attendants have calls on hold.

Average Work Time AWT The average number of seconds it takes attendants to process calls. The number of calls answered and the total time the attendants are busy handling these calls (Talk Time) are used to determine the AWT.

Billing Line Identification

BLID Used to identify the billable party when a metered trunk or a non-metered trunk with CDRX set to YES in its Route Data Block has been routed via call modification to another Meridian Customer Defined Network (MCDN) node.

Busy Hour The hour-long period during which the greatest number of calls are received. Same as “Peak Hour”

Call Charge CALLCHG Call Charge is output for outgoing Periodic Pulse Metering (PPM) or Advice of Charge (AOC) Message Registration equipped trunks. The Call Charge (CALLCHG) field con-tains the call cost, or is used as a meter overflow

indication on TTY output.

Calling Line Identification

CLID Calling Line Identification is a feature provided with Inte-grated Services Digital Network (ISDN).

Calls Abandoned Calls Aband Number of calls that drop (i.e., the caller hangs up) before an attendant answers.

Calls Answered Calls Ans The number of calls answered by attendants

Calls Carried The number of calls carried is the total number of trunks seized (for all trunk groups) in the routing pattern.

[A routing pattern is a list of trunk groups and a set of parameters that define the conditions under which each trunk group should be chosen to route calls.]

Calls Held The number of calls that are answered by the attendant group and subsequently placed on hold by the attendant group.

Calls Held Abandoned Calls H-Aband, Calls H-Abd

The number of calls that are abandoned while the caller is on hold. Held calls which time out and re-alert are included in this count.

Calls Per Attendant Total number of calls handled by the attendant: All con-sole internal peg count + all console external peg count + abandoned call peg count.

Call Register Over-flow

CR Ovf The number of times call processing software fails to find an idle call register.


Appendix A Glossary 55

Calls Queued Calls Queued The total number of calls placed in the attendant queue because no attendants were available. Calls remain in the queue:

> until an attendant becomes available and the call is con-nected.

> until the caller waiting in the queue abandons the call before an attendant is available.

Call Seconds, Hundred

CCS 100 Call Seconds is a unit of call traffic. There are 3600 seconds per hour. The Roman numeral for 100 is the cap-ital letter C. The abbreviation for call seconds is CS. Therefore, 100 call seconds is abbreviated CCS. If a facil-ity is busy for an entire hour, it is said to have been busy for 36 CCS. 36 CCS also equals 1 Erlang. (See “Erlang,” below.

CDR Call Detail Record.

Charge Information CHRINFO Charge Information is output for outgoing Periodic Pulse Metering (PPM) or Advice of Charge (AOC) Message Reg-istration equipped trunks.

Cleared Clr An operator can remove an alarm by clearing it. Note that this does not necessarily remove the condition that caused the alarm.

Cleared By Username of the operator that cleared the alarm.

Customer Number CUSTNO The Customer Number (CUSTNO) field identifies the cus-tomer associated with the call. The field is a two-charac-ter field that identifies the customer number.

Dialed Number Identification Service

DNIS Dialed Number Identification Service (DNIS) is a number that (after translation within the Meridian 1) refers to a specific product line in a telemarketing environment.

Digits DIGITS The Digits (DIGITS) field identifies the digits dialed, digits outpulsed, Charge Account code, received Multi-Fre-quency Compelled Calling Number Identification digits, Authorization Code entered, or Scheduled Access Restric-tion Flexible Feature Code entered.

Digit Type Identifier DIGITYPE The Digits Type Identifier is used to identify the BARS/NARS routing used by an outgoing call or to indicate that the DIGITS field is storing Multi-Frequency Compelled (MFC) Calling Number Information (CNI) digits for an incoming call.

Direction Dir Identifies whether the assigned trunks or groups are out-going (out), incoming (inc) or 2-way (two).

Duration The amount of time an alarm was active.

Erlang A unit of traffic intensity, or load, used to express the amount of traffic needed to keep one facility busy for one hour. One Erlang is equal to 36 CCS. Also see “Call Sec-onds, One Hundred” (CCS)



Exceptions Exception peg count – number of measurements that con-tain information not related to call processing activity.

External Calls Number of external calls handled by an attendant

External Time Time required to handle the external calls

Feature Group D Automatic Number Identification

FGDANI CDR records of calls in which an incoming Feature Group D (FGD) trunk is involved can include (optionally) an ANI digits field.

Grade Of Service G.O.S. Grade of Service is the probability of meeting blockage during Busy Hour. This probability is symbolized by the letter p. A typical GOS is p=0.01, meaning that an aver-age of one call in 100 will be blocked or “lost” during the BH.

Group Grp A collection of “objects” (Attendants, Trunks, Hunt sta-tions, Modem Pools) for convenience in assigning and reporting on the groups.

Group Description Short text description of a particular group.

Group Number Grp No A unique number assigned by an administrator that identi-ties each trunk group. It is a number between one (1) and the maximum number of trunk groups supported by the system.

Group Overflow Grp Ovf The number of calls offered to a trunk group that are not carried or queued (if a queue is present).

Group Size Grp Size The number of trunks (or attendants) in the group.



Group Type Grp Type The type of trunk. The system allows these trunk types:

Type - Definition

access - Access

aplt - Advanced Private Line Termination

co - Central Office or Public Network Service

cpe - Customer Provided Equipment

dmi bos - Digital Multiplexed Interface-Bit Oriented Signal-ing

did - Direct Inward Dialing

diod - Direct Inward/Outward Dialing

fx - Foreign Exchange

isdn - Integrated Services Digital Network

rlt - Release Link Trunk

tand - Tandem

tie - Tie Trunk

wats - Wide Area Telecommunications Service

Held Hld Number of calls that are answered and subsequently placed on hold.

Hourly Count Number of hourly records used to calculate a particular daily record. In most cases, this should = 24.

HPIB Overflow count HPIB Ovf A count of the number of occurrences of a High Priority Input Buffer overflow.

In-Band Automatic Number Identification

IANI In-Band Automatic Number Identification (IANI) displays the ANI number of a call when it terminates on an ACD DN.

ID Unique alarm identification number assigned to each alarm by the system.

Idle Cycle Count ICC A measure of the real-time capacity used for call process-ing. As the load increases, the ICC decreases; as the load decreases, the ICC increases.

Incoming ISA peg count

Incoming ISA Incoming Integrated Services Access trunks

Incoming Seizures Inc Seize The number of incoming seizures carried on the trunk group.

Incoming Usage incoming trunk usage. When a path is established between any terminal and an incoming trunk, Incoming Usage accumulates.



Internal Calls Counts internal call disconnects from the console. Any internal call increments this count when it is removed from the console

Intra-Loop FTM Intra-Loop Failure To Match. Increments when an intra-loop connection cannot be made because all time slots are busy

Intra-Loop CCS Total time, in hundreds of call seconds, that two times-lots are busy in the same loop.

Intra-Loop Peg PC Counts number of intra-loop connections. Peg count increments when an intra-loop connection becomes idle.

Internal Time Time spent servicing internal requests. The total time, in CCS, that an attendant handles internal or outgoing calls from within the system.

ISA ISA Integrated Services Access (a type of trunk.)

Junctor A Junctor is a wire or circuit that links two network groups together so that any terminal in one network group can communicate with any other terminal in the other network group.

Junctor Usage This is a measurement of the total time (in CCS) that time slots of the junctor group were busy and unavailable for other use. Low usage is around 500 CCS per group; high usage is around 1700 CCS. Two-group network systems typically have higher usage than larger systems because fewer connections are available.

Junctor Peg The Junctor Peg is a count of the number of completed calls between network groups. The Junctor Peg count increments when a connection between network groups becomes idle.

Junctor FTM The Junctor FTM counts the failures to establish a con-nection between network groups. The Junctor FTM incre-ments the peg count at the originating loop, the junctor group, and the terminating loop. Blockage in a junctor group should not exceed 1%. Use the formula below to calculate junctor blockage:

Junctor FTM / (junctor peg count + FTM) * 100

Junctor Blockage, Percent

% Junctor Blockage

See Junctor FTM

Level Level A label assigned to each alarm to communicate the degree of severity of the alarm. Valid levels are: CRI (Crit-ical), MAJ (Major), MIN (Minor), and information only (FYI).

LLC1 Blk LLC1 Blk Line Load Control Blocking. A manual feature that denies calls from a designated group of stations.

LLC2 Blk LLC2 Blk Line Load Control Blocking. A manual feature that denies calls from two designated groups of stations.



LLC3 Blk LLC3 Blk Line Load Control Blocking. A manual feature that denies calls from three designated groups of stations.

Load Peak Load Peak A count of the number of times the CPU could not pro-cess a high-priority task within 128 milliseconds.

LPIB Ovf LPIB Ovf A count of the number of occurrences of a Low Priority Input Buffer overflow.

M911 Call Abandon M911 With the Call Abandon feature activated, a 911 caller who aborts a call is not lost. Instead, the call forwards to an ACD queue.

Manned Positions Man Pos Number of attendant positions actively accepting calls

MAX CCU Maximum CCU Maximum Call Capacity Used shows maximum value of CCU during the previous W hours

Max CCU Time Maximum CCU TIme

Shows the day and hour during which the maximum value of CCU occurred. Format is ddhh.

Originator Identifica-tion

ORIGID Identifies the apparatus that originated the call.

Originating Tenant

Number

ORIGTENO The Originating Tenant (ORIGTENO) field identifies the Tenant Number that is associated with the ORIGID field.

Out of Service Out Srv Number of trunks or trunk groups that were out of service during the reporting period.

Outgoing ISA peg count

Outgoing ISA Outgoing Integrated Services Access trunk peg count; increments when an outgoing ISA trunk goes idle.

Outgoing Usage Outgoing trunk usage. When a path is established between any terminal and an outgoing trunk, Outgoing Usage accumulates.

Outgoing Seize Out Seize Outgoing trunk peg count; increments when an outgoing trunk becomes idle

Outgoing Trunk Over-flow

Outgoing Over-flow

Outgoing trunk overflow is incremented when no idle, enabled trunk is available to respond to a trunk request.

Outages The number of times the trunk group member is sampled as out of service over the period covered by the report. Yesterday = the 24 hours beginning at midnight and end-ing at midnight. Today = the hours from midnight to the most recently completed hour. Last hour = the most recently completed hour.

Peak The greatest usage (Talk Time plus Hold Time) for a spec-ified day.

Peak Hour The hour within a 24-hour period that had the greatest usage (Talk Time plus Hold Time) for the specified day.

Peg A “peg” is a counter used to count events such as alarms, seizures, etc. These counts, together with other measure-ments, are useful for traffic analysis.



Percent Abandoned Calls

When a call is removed from the attendant queue, the Abandoned Calls peg count is incremented. The percent abandoned call is calculated with this formula:

Calls Delayed peg / (internal calls + external calls + abandoned calls)

Percent ATB % ATB (All Trunks Busy) Percentage of time that all trunks in a trunk group were simultaneously in use during the mea-surement interval.

Percent CCU %CCU Percent of Call Capacity Used is an indicator of the sys-tem for the current hour. Use the formula:

%CCU = (100 * Current number of Call Attempts) / RCC

Percent Delayed Calls PDC (Number of Delayed Calls / All Calls) * 100

Percent Calls Queued % Call Que The percentage of calls queued. As the percentage of calls queued increases, the Speed of Answer will also increase. Callers are more likely to abandon their calls, contributing to the perception that the level of service has decreased. Percent of Calls Queued is defined as:

Calls Queued / (Calls Answered + Calls Abandoned)

Percent Group Blocking

% Group Blk Percentage of blocking for outgoing and two-way trunk groups.

Percent Junctor Blockage

% Junctor Blockage

See Junctor FTM

Percent Manned Percentage of manned time for all attendants is calculated as follows:

Total manned time for every attendant / (36 * number of attendants manned)

Percent Occupancy % Occ The exact meaning if this term varies with the context. In general, it is the percentage of time that a given resource was busy doing some work.

Percent Out Blocking % Out Blk Percentage of outgoing calls that arrive when all trunks are busy (ATB).

Percent Toll Calls % Toll Calls The percentage of toll calls is calculated as follows:

(Toll peg count / Outgoing peg count) * 100

PNL Usage Port Network Link usage.

PNL Peak Port Network Peak: Sum of the allocated PN Link time-slots at the end of each 100 second interval in a measure-ment hour.

PNL Peg Port Network Link Peg: The total count of circuit-switched time-slot seizure attempts for the link(s) during the measurement hour.



PNL Blk Port Network Link Blockage: The total count of circuit-switched PN blockages, i.e., the total number of times a PN link time-slot is denied during the measurement hour. This count will include calls originating or terminating on this PN. This field should be zero for all configurations that don't use T1 remoting and are smaller than 16 PNs, since the center stage is non-blocking in these configura-tions.

PNL OCC PNL OCC: The percentage of Port Network Link Occu-pancy is computed as follows:

PN Link Usage/PNL Total Potential Usage) x 100

Queue Abandoned Que Abd The number of calls that were removed from the queue by: -the system because they have been in the queue for more than 30 minutes;-the user (for example, dialing the cancel code).

Queue Overflow Que Ovf The total number of calls that were not queued because the queue was full.

Queue Size Que Size A number (zero to 100) that identifies the number of slots assigned to the trunk group queue. This number repre-sents how many calls may be held in queue by the trunk group. If 0 is displayed, there is no queue.

Queued The total number of calls placed in the attendant queue because no attendants were available. Calls remain in the queue:

> until an attendant becomes available and the call is con-nected.

> until the caller waiting in the queue abandons the call before an attendant is available.

Rated Call Capacity RCC Rated Call Capacity is a function of the Idle Cycle Count and the number of Call Attempts, for every hour. RCC represents the maximum level at which the CPU can oper-ate and still maintain a high grade of service.

Record Number RECNO Identifies the number of the current record in the CDR sequence.

Record Type RECTYPE The Record Type (RECTYPE) field indicates the type of call record.

Service Time The total time that the path to the service loop was busy.

Speed of Answer Speed Ans, SOA

The average elapsed time from when a call terminates at the attendant group to when the call is answered by an attendant (measured in seconds).

Staffed Time The time that the attendant positions are active (ready for calls). If Staffed Time (per agent) equals 36 CCS, all agents were active for the full hour.



SL-1 OB Ovf Meridian -1Output Buffer overflow peg count. Measures the number of times signaling or output signals have been lost due to overflow.

Terminating Auxiliary Identification

TERMAUXID Identifies the TN of the terminating telephone when the telephone has a multiple appearance Prime DN, and can-not be uniquely identified by TERID.

Terminating Tenant

Number

TERTENO The Terminating Tenant field identifies the Tenant Num-ber that is associated with the TERID field.

Time Abandoned Time Aband; Time Abnd

Average time (in seconds) that calls spend in queue and/or ringing at the console before the callers hang up.

NOTE: Time abandoned does not include calls that over-flow the attendant group queue.

TDM Usage TDM Usage: The total TDM time-slot usage, in CCS, for the PN being measured, during the measurement hour. TDM Usage = Sum of the allocated TDM time slots at the end of each 100 second interval in a measurement hour.

TDM Peg TDM Peg: The total count of circuit switch TDM time-slot seizure attempts for the PN during the measurement hour.

TDM Peak TDM Peak: The maximum number of time-slots allocated at any one time during the measurement hour.

TDM Blk TDM Blk: The total count of TDM blockages, i.e., the total number of times a TDM time-slot request is denied for the PN being measured, during the measurement hour.

TDM OCC TDM OCC: The percent TDM Occupancy is computed as follows:

(TDM Usage / TDM Total Potential Usage) * 100

Terminator Identification

TERID The Terminating Identification field identifies the appara-tus on which a call is terminated.

Time Available Time Avail The time during which the attendants are not talking on calls but are available to handle new calls. Measured in Hundred Call Seconds (See Call Seconds, above).

Time Held The total amount of time (seconds) that attendants have calls on hold.

Time Talk The time (in CCS) an attendant is active on calls. Time Talk is measured from the time the attendant activates an attendant loop until the loop is released.

Time to Answer TTA Outputs CDR information indicating the length

of time taken to answer any given call.

Time to Acknowledge Time taken to acknowledge an alarm

Time to Respond Time taken to respond to an alarm



Time To Resolution / Time to Resolve

A report that lists (for the specified date range) Alarms, their level, peg number, data & time cleared, cleared by, and the time difference between the time the alarm started and the time it was cleared – the Time To Resolu-tion.

Toll Peg Count Toll Calls Counts the number of external calls made which begin with either a zero (“0”) or a one (“1”) (after any access digits).

AAA peg count Total AAA Attendant Alternative Answering (AAA) peg count. Counts the number of attempts to forward a call to AAA.

Total FTM Loop Failure-To-Match. Counts Loop FTMs caused by any number of reasons.

Total CCS Loop Usage: Gives the total amount of time that loop timeslots were busy. This measurement gives a rough indication of the condition of the switch.

Total Peg Total Peg Conference Loop peg count. Shows the total number number of people on a given conference. Increments when an established path between the connection point and the conference loop is idle.

Total Seizures Total Seize The number of incoming and outgoing seizures carried on the trunk group. This includes the number of times a trunk in the group was seized, including false starts, don’t answer, and busy.

Total Usage Total usage (in CCS) for all trunks in the trunk group. Rep-resents the total time the trunks are busy (with calls) dur-ing the one-hour measurement period. Total usage measures each time a trunk is seized for use by an incom-ing call (whether it is picked up or not) or an out going call (only

after digits have been dialed).

Trunk A dedicated telecommunications channel between two communications systems or Central Offices.

Trunk Group Telecommunications channels assigned as a group for certain functions that can be used interchangeably between two communications systems or Central Offices.

Trunks Equipped The number of trunks working in the route.

Trunks Out of Service List of trunk groups which had out-of-service trunks dur-ing the report interval.

Trunks Required Number of trunks required to deliver a specified Grade Of Service.

Trunks Working The number of trunks enabled in the route.

Visual Text Descriptive text associated with a particular level of alarm from a particular monitored entity (switch).

Wide Band Wideband trunks are annotated with a “W” in this col-umn.


Appendix B Third Party Licenses 65

Appendix B Third Party Licenses

Acknowledgement of the use of third party software is provided as follows:

Academic Free License

• voice 0Copyright Centre for Speech Technology Research, University of Edinburgh, UK, Copyright (c) 1995,1996, All Rights Reserved.

Permission is hereby granted, free of charge, to use and distribute this software and its documentation without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of this work, and to permit persons to whom this work is furnished to do so, subject to the follow-ing conditions:

- The code must retain the above copyright notice, this list of conditions and the following disclaimer.

- Any modifications must be clearly marked as such.

- Original authors' names are not deleted.

- The authors' names are not used to endorse or promote products derived from this software without specific prior written permission.

THE UNIVERSITY OF EDINBURGH AND THE CONTRIBUTORS TO THIS WORK DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUD-ING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL THE UNIVERSITY OF EDINBURGH NOR THE CONTRIBU-TORS BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAM-AGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Author: Paul Taylor

Date: February 1995

• flex++ 2.5.4Copyright © 1993 The Regents of the University of California, All rights reserved.

This code is derived from software contributed to Berkeley by Kent Williams and Tom Epperly.

Redistribution and use in source and binary forms with or without modification are permitted provided that:

- source distributions retain this entire copyright notice and comment, and;

- distributions including binaries display the following acknowledgement:

``This product includes software developed by the University of California, Berke-ley and its contributors'' in the documentation or other materials provided with the distribution and in all advertising materials mentioning features or use of this soft-ware.

Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior writ-ten permission.


THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

This file defines FlexLexer, an abstract class which specifies the external interface provided to flex C++ lexer objects, and yyFlexLexer, which defines a particular lexer class. If you want to create multiple lexer classes, you use the -P flag to rename each yyFlexLexer to some other xxFlexLexer. You then include <FlexLexer.h> in your other sources once per lexer class.

Apache 2.0

The following are used under the Apache 2.0 license: activemqcpp 3.1.2, ant 1.7.1, apache-activemq 5.3.2 fuse, apache-camel 2.2.0, axis-c 1.6, bsf 2.3.0, cglib 2.1.3, com-mons-beanutils 1.7, commons-collections 3.2, commons-codec 1.3, commons-digester 1.8, commons-fileupload 1.0, commons-lang 2.4, commons-logging 1.1.1, commons-pool 1.3, cxf 2.1, dozer 4.2.1, dwr 2.0.1, encache 2.0, ezmorph 0.8.1, groovy 1.6.1, gwt 2.0.0, gwt-log 2.5.0, jakarta-oro 2.0.6, jencks 2.0, jmxterm 1.0 alpha 4, json 0.9, lingo 1.3, log4j 1.2.15, piccolo 1.1, spring 2.5.6, tomcat 6.0.26, velocity 1.5, xerces 2.7.0.

To view the full license text see Apache 2.0.

BSD

The following is used under the BSD license:

• antlr 2.7.5H3Copyright © 2003-2006 Terrence Parr

• asm 1.5.3Copyright © 2000-2005 INRIA Fance Telecom

• base64coder 0Copyright © 2003-2010 Christian d’Heureuse, Inventec Informatick AG, Zurich, Switzerland; www.source-code.biz, www.inventec.ch/chdh

• dojo 0.4.1Copyright © 2005-2006 The Dojo Foundation. All rights reserved.

• net-snmp-openssl 5.1.0Portions of these libraries are copyright.Networks Associates Technology, Inc copyright noticeCopyright © 2001-2003 Network Associates Technology, Inc. All rights reserved.

- Cambridge Broadband Ltd.Portions of this code are copyright © 2001-2003 Cambridge Broadbank, Ltd. All rights reserved.

- Sun Microsystems, Inc. copyright noticeCopyright © 2003 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, USA. All rights reserved.

- Sparta, Inc. copyright noticeCopyright © 2003-2008, Sparta, Inc.

- Cisco/BUPTNIC copyright noticeCopyright 2004 Cisco, Inc. and Information Network, Center of Beijing University of Posts and Telecommunications. All rights reserved.

- Fabasoft R&D Software GmbH & Co KG copyright noticeCopyright Fabasoft R&D Software GmbH & Co KG, 2003; [email protected], author Bern-hard Penz

• pqxx 1.5.1 C++ API to the PostgreSQL database management systemCopyright © 2003 by Jeroen Vermeulen, Ray Dassen, Bart Samwel, Roger Leigh, Palle Gir-gensohn. All rights reserved.


• xstream 1.3.1Copyright © 2003-2006 Joe WalnesCopyright © 2006-2007, Xstream Committers

The software listed under the BSD license provides for the following:

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other mate-rials provided with the distribution.

Neither the name of the author, nor the names of other contributors may be used to endorse or promote products derived from this software without specific prior writ-ten permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CON-TRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUD-ING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DIS-CLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBU-TORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES)INCLUDING, BUT NOT LIM-ITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIA-BILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

dom4j 1.6.1

• dom4j 1.6.1Copyright © 2001 - 2005 MetaStuff Ltd. All rights reserved.

Redistribution and use of this software and associated documentation ("Software"), with or without modification, are permitted provided that the following conditions are met:

- Redistributions of source code must retain copyright statements and notices. Redistribu-tions must also contain a copy of this document.

- Redistributions in binary form must reproduce the above copyright notice, this list of condi-tions and the following disclaimer in the documentation and/or other materials provided with the distribution.

- The name "DOM4J" must not be used to endorse or promote products derived from this Software without prior written permission of MetaStuff, Ltd. For written permission, please contact [email protected].

- Products derived from this Software may not be called "DOM4J" nor may "DOM4J" appear in their names without prior written permission of MetaStuff, Ltd. DOM4J is a registered trademark of MetaStuff, Ltd.

- Due credit should be given to the DOM4J Project - http://www.dom4j.org

THIS SOFTWARE IS PROVIDED BY METASTUFF, LTD. AND CONTRIBUTORS ``AS IS''AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL METASTUFF, LTD. OR ITS CONTRIBUTORS BE LIABLE FOR ANY


DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUEN-TIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUD-ING

NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Copyright 2001-2005 (C) MetaStuff, Ltd. All Rights Reserved.

jdom 1.1.1

• jdom 1.1.1Copyright 2000-2004 Jason Hunter and Brett McLaughlin


- Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer.

- Redistributions in binary form must reproduce the above copyright notice, this list of condi-tions, and the disclaimer that follows these conditions in the documentation and/or other materials provided with the distribution.

- The name "JDOM" must not be used to endorse or promote products derived from this soft-ware without prior written permission. For written permission, please contact <request_AT_jdom_DOT_org>.

- Products derived from this software may not be called "JDOM", nor may "JDOM" appear in their name, without prior written permission from the JDOM Project Management <request_AT_jdom_DOT_org>.

In addition, we request (but do not require) that you include in the end-user docu-mentation provided with the redistribution and/or in the software itself an acknowledgement equivalent to the following:

"This product includes software developed by the JDOM Project (http://www.jdom.org/)."

Alternatively, the acknowledgment may be graphical using the logos available at http://www.jdom.org/images/logos.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRAN-TIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJ-ECT CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This software consists of voluntary contributions made by many individuals on behalf of the JDOM Project and was originally created by Jason Hunter <jhunter_AT_jdom_DOT_org> and Brett McLaughlin <brett_AT_jdom_DOT_org>. For more information on the JDOM Project, please see <http://www.jdom.org/>.


hsqldb 1,8.1.2

• hsqldb 1.8.1.2.Copyright © 2001-2010 The HSQL Development Group. All rights reserved.

For work developed by the HSQL Development Group:

Copyright (c) 2001-2010, The HSQL Development Group All rights reserved.


- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.


- Neither the name of the HSQL Development Group nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CON-TRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUD-ING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DIS-CLAIMED. IN NO EVENT SHALL HSQL DEVELOPMENT GROUP, HSQLDB.ORG, OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTER-RUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLI-GENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

For work originally developed by the Hypersonic SQL Group:

Copyright (c) 1995-2000 by the Hypersonic SQL Group. All rights reserved.




- Neither the name of the Hypersonic SQL Group nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior writ-ten permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CON-TRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUD-ING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DIS-CLAIMED. IN NO EVENT SHALL THE HYPERSONIC SQL GROUP, OR CON-TRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIM-ITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIA-


BILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This software consists of voluntary contributions made by many individuals on behalf of the

Hypersonic SQL Group.

SourceForge Logo

This page last updated 6 March 2010.

Java is a Trademark of Sun Microsystems, Inc. (under various licenses). Contents of this page are ©2001-2010 The hsql Development Group. All rights reserved under the terms of the applicable Licenses.

java_concurrent 1.3.4

• java_concurrent 1.3.4By Doug Lea. Public domain except for the Java Software technologies, which fall under the license excerpted below.

With respect to java_concurrent 1.3.4 (JavaSoftware technologies excerpted license)

The Java Software technologies are Copyright (c) 1994-2000 Sun Microsystems, Inc. All rights reserved. Sun hereby grants Doug Lea a non-exclusive, worldwide, non-transferable license to use, reproduce, create derivative works of, and distribute the Java Software and derivative works thereof in source and binary forms as part of a larger work, and to sublicense the right to use, reproduce and distribute the Java Software and Doug Lea's derivative works as the part of larger works through mul-tiple tiers of sublicensees provided that the following conditions are met:

- Neither the name of or trademarks of Sun may be used to endorse or promote products including or derived from the Java Software technology without specific prior written per-mission; and

- Redistributions of source or binary code must contain the above copyright notice, this notice and the following disclaimers:

This software is provided "AS IS," without a warranty of any kind. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED. SUN MICROSYSTEMS, INC. AND ITS LICENSORS SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED BY LICENSEE AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE OR ITS DERIVA-TIVES. IN NO EVENT WILL SUN MICROSYSTEMS, INC. OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR DIRECT, INDI-RECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF SUN MICROSYSTEMS, INC. HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. You acknowledge that Software is not designed, licensed or intended for use in the design, construction, operation or maintenance of any nuclear facility.

Where “Java Software technologies” means classes/java/util/ArrayList.java, and classes/java/util/HashMap.java.

LGPL 2.1

The following are used under the LGPL2.1 license:


• hibernate 3.2Copyright © 2006

• hibernate-annotations 3.3.0Copyright © 2009

• hibernate-entitymanager 3.4.0Copyright © 2008

• javassist 0Copyright 1999-2008 Shigeru Chiba

• jcommon 0.9.1Copyright © 2004

• jfreechart 0.9.16 a free chart library for the Java(tm) platformCopyright © 2000-2004 Object Refinery Limited and Contributors. All rights reserved.

• tinymice 3.2.7Copyright © 2003-2010 John Sorlin, Michael Keck, Andrew Tetlow. All rights reserved.

The software listed under the LGPL2.1 license provides for the following:

This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version.

This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FIT-NESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.

You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

MIT License

• mapserv 4.10.0 - TSCCopyright 1996-2005 Regents of the University of Minnesota

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to per-mit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Mozilla Public License 1.0

• saxon he9-2-1-2jCopyright © Michael Kay and others as listed in the documentation.

To view the full license text see Mozilla Public License 1.0.


Mozilla Public License 1.1

The following are used under the Mozilla Public License 1.1:

• itext 1.4.8Copyright © 2003-2006 Paulo Soares, Mark Hall, Bruno Lowagie, Mark Storer, and Xavier LeVourchrhino 1.6-R1Copyrights apply

To view the full license text see Mozilla Public License 1.1.

net-snmp-openssl 5.1.0

• CMU/UCD

Copyright © 1989, 1991, 1992 by Carnegie Mellon University,

• Derivative Work 1996, 1998-2000

Copyright 1996, 1998-2000 The Regents of the University of California

Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copy-right notice appears in all copies and that both that copyright notice and this per-mission notice appear in supporting documentation, and that the name of CMU and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written permission.

CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIA-BLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Open SSL

• openssl 0.9.8aCopyright © 1998-2008 The OpenSSL Project. All rights reserved.Copyright © 1995-1998 Eric Young ([email protected]). All rights reserved.



- Redistributions in binary form must reproduce the above copyright notice, this list of condi-tions and the following disclaimer in the documentation and/or other materials provided with the distribution. *

- All advertising materials mentioning features or use of this software must display the fol-lowing acknowledgment:

"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

- The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or pro-mote products derived from this software without prior written permission. For written permission, please contact [email protected].


- Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.

- Redistributions of any form whatsoever must retain the following acknowledgment:

"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTI-TUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLI-GENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

====================================================================

This product includes cryptographic software written by Eric Young ([email protected]). This product includes software written by Tim Hudson ([email protected]).

Original SSLeay License

-----------------------

Copyright (C) 1995-1998 Eric Young ([email protected]). All rights reserved.

This package is an SSL implementation written by Eric Young ([email protected]). The implementation was written so as to conform with Netscape’s SSL.

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson ([email protected]).

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) pro-vided with the package.


- Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.


- All advertising materials mentioning features or use of this software must display the fol-lowing acknowledgement:

"This product includes cryptographic software written by Eric Young ([email protected])"

The word 'cryptographic' can be left out if the routines from the library being used


are not cryptographic related.

- If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement:

"This product includes software written by Tim Hudson ([email protected])"

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PAR-TICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The licence and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution licence [including the GNU Public Licence.]

Open Symphony License

The following is used under the OpenSymphony license:

• ognl 2.6.7 Copyright © 1997 - 2003 Drew Davidson and Luke Blanchard. All rights reserved.

The software listed under the OpenSymphony license provides for the following:

The OpenSymphony Software License, Version 1.1. (this license is derived and fully compatible with the Apache Software License - see http://www.apache.org/LICENSE.txt). Copyright (c) 2001-2004 The OpenSymphony Group. All rights reserved.




- The end-user documentation included with the redistribution, if any, must include the fol-lowing acknowledgment:

"This product includes software developed by the OpenSymphony Group(http://www.opensymphony.com/)."

Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.

- The names "OpenSymphony" and "The OpenSymphony Group" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].


- Products derived from this software may not be called "OpenSymphony" or "OGNL", nor may "OpenSymphony" or "OGNL" appear in their name, without prior written permission of the OpenSymphony Group.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRAN-TIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDA-TION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCI-DENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTER-RUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLI-GENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

proxool 0.8.3

• proxool 0.8.3Copyright © 2002-2003 Proxool. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, is permitted provided that the following conditions are met:



- All advertising materials mentioning features or use of this software must display the fol-lowing acknowledgment:

"This product includes software developed by the Proxool Project(http://proxool.sourceforge.net/)."

- The name "Proxool" must not be used to endorse or promote products derived from this software without prior written permission.For written permission, please contact [email protected].

- Products derived from this software may not be called "Proxool" nor may "Proxool" appear in their names without prior written permission of the Proxool Project.

- Redistributions of any form whatsoever must retain the following acknowledgment:

"This product includes software developed by the Proxool Project (http://proxool.sourceforge.net/)."

THIS SOFTWARE IS PROVIDED BY THE PROXOOL PROJECT ̀ `AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PROXOOL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTI-TUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLI-GENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.


Ruby 1.8.5

• ruby 1.8.5Ruby is copyrighted free software by Yukihiro Matsumoto <[email protected]>.

You can redistribute it and/or modify it under either the terms of the GPL (see COPYING.txt file), or the conditions below:

• You may make and give away verbatim copies of the source form of the software without restriction, provided that you duplicate all of the original copyright notices and associated disclaimers.

• You may modify your copy of the software in any way, provided that you do at least ONE of the following:

- place your modifications in the Public Domain or otherwise make them Freely Available, such as by posting said modifications to Usenet or an equivalent medium, or by allowing the author to include your modifications in the software.

- use the modified software only within your corporation or organization.

- rename any non-standard executables so the names do not conflict with standard executa-bles, which must also be provided.

- make other distribution arrangements with the author.

• You may distribute the software in object code or executable form, provided that you do at least ONE of the following:

- distribute the executables and library files of the software, together with instructions (in the manual page or equivalent) on where to get the original distribution.

- accompany the distribution with the machine-readable source of the software.

- give non-standard executables non-standard names, with instructions on where to get the original software distribution.

- make other distribution arrangements with the author.

• You may modify and include the part of the software into any other software (possibly com-mercial). But some files in the distribution are not written by the author, so that they are not under this terms.

They are gc.c(partly), utils.c(partly), regex.[ch], st.[ch] and some files under the ./missing directory. See each file for the copying condition.

• The scripts and library files supplied as input to or produced as output from the software do not automatically fall under the copyright of the software, but belong to whomever gener-ated them, and may be sold commercially, and may be aggregated with this software.

THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Sun Microsystems, Inc. BCLA

• java 1.6.0_16 Copyright © 2009 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved.

To view the full license text see Sun Microsystem, Inc BCLA.


Apache 2.0 (full text)

Apache License

Version 2.0, January 2004

http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License"

shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

"Licensor"

shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

"Legal Entity"

shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your")

shall mean an individual or Legal Entity exercising permissions granted by this License.

"Source" form

shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

"Object" form

shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

"Work"

shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

"Derivative Works"

shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications rep-resent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.


"Contribution"

shall mean any work of authorship, including the original version of the Work and any modifica-tions or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "sub-mitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licen-sor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Con-tribution."

"Contributor"

shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contribu-tor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevoca-ble copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You insti-tute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or con-tributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

1. You must give any other recipients of the Work or Derivative Works a copy of this License; and

2. You must cause any modified files to carry prominent notices stating that You changed the files; and

3. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

4. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such


Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work oth-erwise complies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intention-ally submitted for inclusion in the Work by You to the Licensor shall be under the terms and con-ditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, ser-vice marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITH-OUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MER-CHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associ-ated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negli-gence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, includ-ing any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

Sun Microsystems, Inc. Binary Code License Agreement (full text)

Sun Microsystems, Inc. Binary Code License Agreement for the JAVA SE DEVELOPMENT KIT (JDK), VERSION 6

SUN MICROSYSTEMS, INC. ("SUN") IS WILLING TO LICENSE THE SOFTWARE IDENTIFIED BELOW TO YOU ONLY UPON THE CONDITION THAT YOU ACCEPT ALL OF THE TERMS CONTAINED IN THIS BINARY CODE LICENSE AGREEMENT AND SUPPLEMENTAL LICENSE TERMS (COLLECTIVELY "AGREEMENT"). PLEASE READ THE AGREEMENT CAREFULLY. BY USING THE SOFTWARE YOU ACKNOWLEDGE THAT YOU HAVE READ THE TERMS AND AGREE TO THEM. IF YOU ARE AGREEING TO THESE TERMS ON BEHALF OF A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT YOU HAVE THE LEGAL AUTHORITY TO BIND THE LEGAL ENTITY TO THESE TERMS. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT WISH TO BE BOUND BY THE TERMS, THEN


YOU MUST NOT USE THE SOFTWARE ON THIS SITE OR ANY OTHER MEDIA ON WHICH THE SOFTWARE IS CONTAINED.

1. DEFINITIONS. "Software" means the identified above in binary form, any other machine read-able materials (including, but not limited to, libraries, source files, header files, and data files), any updates or error corrections provided by Sun, and any user manuals, programming guides and other documentation provided to you by Sun under this Agreement. "General Purpose Desktop Computers and Servers" means computers, including desktop and laptop computers, or servers, used for general computing functions under end user control (such as but not specifically limited to e-mail, general purpose Internet browsing, and office suite productivity tools). The use of Soft-ware in systems and solutions that provide dedicated functionality (other than as mentioned above) or designed for use in embedded or function-specific software applications, for example but not limited to: Software embedded in or bundled with industrial control systems, wireless mobile telephones, wireless handheld devices, netbooks, kiosks, TV/STB, Blu-ray Disc devices, telematics and network control switching equipment, printers and storage management systems, and other related systems are excluded from this definition and not licensed under this Agree-ment. "Programs" means Java technology applets and applications intended to run on the Java Platform Standard Edition (Java SE) platform on Java-enabled General Purpose Desktop Comput-ers and Servers.

2. LICENSE TO USE. Subject to the terms and conditions of this Agreement, including, but not limited to the Java Technology Restrictions of the Supplemental License Terms, Sun grants you a non-exclusive, non-transferable, limited license without license fees to reproduce and use inter-nally Software complete and unmodified for the sole purpose of running Programs. Additional licenses for developers and/or publishers are granted in the Supplemental License Terms.

3. RESTRICTIONS. Software is confidential and copyrighted. Title to Software and all associated intellectual property rights is retained by Sun and/or its licensors. Unless enforcement is prohib-ited by applicable law, you may not modify, decompile, or reverse engineer Software. You acknowledge that Licensed Software is not designed or intended for use in the design, construc-tion, operation or maintenance of any nuclear facility. Sun Microsystems, Inc. disclaims any express or implied warranty of fitness for such uses. No right, title or interest in or to any trade-mark, service mark, logo or trade name of Sun or its licensors is granted under this Agreement. Additional restrictions for developers and/or publishers licenses are set forth in the Supplemen-tal License Terms.

4. LIMITED WARRANTY. Sun warrants to you that for a period of ninety (90) days from the date of purchase, as evidenced by a copy of the receipt, the media on which Software is furnished (if any) will be free of defects in materials and workmanship under normal use. Except for the fore-going, Software is provided "AS IS". Your exclusive remedy and Sun's entire liability under this limited warranty will be at Sun's option to replace Software media or refund the fee paid for Soft-ware. Any implied warranties on the Software are limited to 90 days. Some states do not allow limitations on duration of an implied warranty, so the above may not apply to you. This limited warranty gives you specific legal rights. You may have others, which vary from state to state.

5. DISCLAIMER OF WARRANTY. UNLESS SPECIFIED IN THIS AGREEMENT, ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT THESE DIS-CLAIMERS ARE HELD TO BE LEGALLY INVALID.

6. LIMITATION OF LIABILITY. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR


RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. In no event will Sun's liability to you, whether in contract, tort (including negligence), or otherwise, exceed the amount paid by you for Software under this Agreement. The foregoing limitations will apply even if the above stated war-ranty fails of its essential purpose. Some states do not allow the exclusion of incidental or conse-quential damages, so some of the terms above may not be applicable to you.

7. TERMINATION. This Agreement is effective until terminated. You may terminate this Agree-ment at any time by destroying all copies of Software. This Agreement will terminate immedi-ately without notice from Sun if you fail to comply with any provision of this Agreement. Either party may terminate this Agreement immediately should any Software become, or in either party's opinion be likely to become, the subject of a claim of infringement of any intellectual prop-erty right. Upon Termination, you must destroy all copies of Software.

8. EXPORT REGULATIONS. All Software and technical data delivered under this Agreement are subject to US export control laws and may be subject to export or import regulations in other countries. You agree to comply strictly with all such laws and regulations and acknowledge that you have the responsibility to obtain such licenses to export, re-export, or import as may be required after delivery to you.

9. TRADEMARKS AND LOGOS. You acknowledge and agree as between you and Sun that Sun owns the SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET trademarks and all SUN, SOLARIS,

JAVA, JINI, FORTE, and iPLANET-related trademarks, service marks, logos and other brand des-ignations ("Sun Marks"), and you agree to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www.sun.com/policies/trademarks. Any use you make of the Sun Marks inures to Sun's benefit.

10. U.S. GOVERNMENT RESTRICTED RIGHTS. If Software is being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), then the Government's rights in Software and accompanying documentation will be only as set forth in this Agreement; this is in accordance with 48 CFR 227.7201 through 227.7202-4 (for Department of Defense (DOD) acquisitions) and with 48 CFR 2.101 and 12.212 (for non-DOD acquisitions).

11. GOVERNING LAW. Any action related to this Agreement will be governed by California law and controlling U.S. federal law. No choice of law rules of any jurisdiction

will apply.

12. SEVERABILITY. If any provision of this Agreement is held to be unenforceable, this Agree-ment will remain in effect with the provision omitted, unless omission would frustrate the intent of the parties, in which case this Agreement will immediately terminate.

13. INTEGRATION. This Agreement is the entire agreement between you and Sun relating to its subject matter. It supersedes all prior or contemporaneous oral or written communications, pro-posals, representations and warranties and prevails over any conflicting or additional terms of any quote, order, acknowledgment, or other communication between the parties relating to its subject matter during the term of this Agreement. No modification of this Agreement will be binding, unless in writing and signed by an authorized representative of each party.

SUPPLEMENTAL LICENSE TERMS

These Supplemental License Terms add to or modify the terms of the Binary Code License Agree-ment. Capitalized terms not defined in these Supplemental Terms shall have the same meanings ascribed to them in the Binary Code License Agreement. These Supplemental Terms shall super-


sede any inconsistent or conflicting terms in the Binary Code License Agreement, or in any license contained within the Software.

A. Software Internal Use and Development License Grant. Subject to the terms and conditions of this Agreement and restrictions and exceptions set forth in the Software "README" file incorpo-rated herein by reference, including, but not limited to the Java Technology Restrictions of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable, limited license without fees to reproduce internally and use internally the Software complete and unmodified for the pur-pose of designing, developing, and testing your Programs.

B. License to Distribute Software. Subject to the terms and conditions of this Agreement and restrictions and exceptions set forth in the Software README file, including, but not limited to the Java Technology Restrictions of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable, limited license without fees to reproduce and distribute the Software, provided that (i) you distribute the Software complete and unmodified and only bundled as part of, and for the sole purpose of running, your Programs, (ii) the Programs add significant and primary func-tionality to the Software, (iii) you do not distribute additional software intended to replace any component(s) of the Software, (iv) you do not remove or alter any proprietary legends or notices contained in the Software, (v) you only distribute the Software subject to a license agreement that protects Sun's interests consistent with the terms contained in this Agreement, and (vi) you agree to defend and indemnify Sun and its licensors from and against any damages, costs, liabilities, settlement amounts and/or expenses (including attorneys' fees) incurred in connection with any claim, lawsuit or action by any third party that arises or results from the use or distribution of any and all Programs and/or Software.

C. License to Distribute Redistributables. Subject to the terms and conditions of this Agreement and restrictions and exceptions set forth in the Software README file, including but not limited to the Java Technology Restrictions of these Supplemental Terms, Sun grants you a non-exclusive,

non-transferable, limited license without fees to reproduce and distribute those files specifically identified as redistributable in the Software "README" file ("Redistributables") provided that: (i) you distribute the Redistributables complete and unmodified, and only bundled as part of Pro-grams, (ii) the Programs add significant and primary functionality to the Redistributables, (iii) you do not distribute additional software intended to supersede any component(s) of the Redis-tributables (unless otherwise specified in the applicable README file), (iv) you do not

remove or alter any proprietary legends or notices contained in or on the Redistributables, (v) you only distribute the Redistributables pursuant to a license agreement that protects Sun's interests consistent with the terms contained in the Agreement, (vi) you agree to defend and indemnify Sun and its licensors from and against any damages, costs, liabilities, settlement amounts and/or

expenses (including attorneys' fees) incurred in connection with any claim, lawsuit or action by any third party that arises or results from the use or distribution of any and all Programs and/or Software.

D. Java Technology Restrictions. You may not create, modify, or change the behavior of, or autho-rize your licensees to create, modify, or change the behavior of, classes, interfaces, or subpackages that are in any way identified as "java", "javax", "sun" or similar convention as specified by Sun in any naming convention designation.

E. Distribution by Publishers. This section pertains to your distribution of the Software with your printed book or magazine (as those terms are commonly used in the industry) relating to Java technology ("Publication"). Subject to and conditioned upon your compliance with the restrictions and obligations contained in the Agreement, in addition to the license granted in Paragraph 1 above, Sun hereby grants to you a non-exclusive, nontransferable limited right to reproduce com-plete and unmodified copies of the Software on electronic media (the "Media") for the sole pur-pose of inclusion and distribution with your Publication(s), subject to the following terms: (i) You may not distribute the Software on a stand-alone basis; it must be distributed with your Publica-


tion(s); (ii) You are responsible for downloading the Software from the applicable Sun web site; (iii) You must refer to the Software as JavaTM SE Development Kit 6; (iv) The Software must be reproduced in its entirety and without any modification whatsoever (including, without limita-tion, the Binary Code License and Supplemental License Terms accompanying the Software and proprietary rights notices contained in the Software); (v) The Media label shall include the follow-ing information: Copyright 2006, Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Sun, Sun Microsystems, the Sun logo, Solaris, Java, the Java Coffee Cup logo, J2SE, and all trademarks and logos based on Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. This information must be placed on the Media label in such a manner as to only apply to the Sun Software; (vi) You must clearly identify the Software as Sun's product on the Media holder or Media label, and you may not state or imply that Sun is responsible for any third-party software contained on the Media; (vii) You may not include any third party software on the Media which is intended to be a replacement or substitute for the Software; (viii) You shall indemnify Sun for all damages arising from your failure to com-ply with the requirements of this Agreement. In addition, you shall defend, at your expense, any and all claims brought against Sun by third parties, and shall pay all damages awarded by a court of competent jurisdiction, or such settlement amount negotiated by you, arising out of or in con-nection with your use, reproduction or distribution of the Software and/or the Publication. Your obligation to provide indemnification under this section shall arise provided that Sun: (a) pro-vides you prompt notice of the claim; (b) gives you sole control of the defense and settlement of the claim; (c) provides you, at your expense, with all available information, assistance and author-ity to defend; and (d) has not compromised or settled such claim without your prior written con-sent; and (ix) You shall provide Sun with a written notice for each Publication; such notice shall include the following information: (1) title of Publication, (2) author(s), (3) date of Publication, and (4) ISBN or ISSN numbers. Such notice shall be sent to Sun Microsystems, Inc., 4150 Network

Circle, M/S USCA12-110, Santa Clara, California 95054, U.S.A, Attention: Contracts Administra-tion.

F. Source Code. Software may contain source code that, unless expressly licensed for other pur-poses, is provided solely for reference purposes pursuant to the terms of this Agreement. Source code may not be redistributed unless expressly provided for in this Agreement.

G. Third Party Code. Additional copyright notices and license terms applicable to portions of the Software are set forth in the THIRDPARTYLICENSEREADME.txt file. In addition to any terms and conditions of any third party opensource/freeware license identified in the THIRDPARTYLI-CENSEREADME.txt file, the disclaimer of warranty and limitation of liability provisions in para-graphs 5 and 6 of the Binary Code License Agreement shall apply to all Software in this distribution.

H. Termination for Infringement. Either party may terminate this Agreement immediately should any Software become, or in either party's opinion be likely to become, the subject of a claim of infringement of any intellectual property right.

I. Installation and Auto-Update. The Software's installation and auto-update processes transmit a limited amount of data to Sun (or its service provider) about those specific processes to help Sun understand and optimize them. Sun does not associate the data with personally identifiable infor-mation. You can find more information about the data Sun collects at http://java.com/data/.

For inquiries please contact: Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A.

Mozilla Public License 1.0 (full text)

MOZILLA PUBLIC LICENSE

Version 1.0


1. Definitions.

1.1. ``Contributor'' means each entity that creates or contributes to the creation of Modifica-tions.

1.2. ``Contributor Version'' means the combination of the Original Code, prior Modifications used by a Contributor, and the Modifications made by that particular Contributor.

1.3. ``Covered Code'' means the Original Code or Modifications or the combination of the Original Code and Modifications, in each case including portions thereof.

1.4. `Èlectronic Distribution Mechanism'' means a mechanism generally accepted in the soft-ware development community for the electronic transfer of data.

1.5. `Èxecutable'' means Covered Code in any form other than Source Code.

1.6. `Ìnitial Developer'' means the individual or entity identified as the Initial Developer in the Source Code notice required by Exhibit A.

1.7. ``Larger Work'' means a work which combines Covered Code or portions thereof with code not governed by the terms of this License.

1.8. ``License'' means this document.

1.9. ``Modifications'' means any addition to or deletion from the substance or structure of either the Original Code or any previous Modifications. When Covered Code is released as a series of files, a Modification is:

A. Any addition to or deletion from the contents of a file containing Original Code or previ-ous Modifications.

B. Any new file that contains any part of the Original Code or previous Modifications.

1.10. `Òriginal Code'' means Source Code of computer software code which is described in the Source Code notice required by Exhibit A as Original Code, and which, at the time of its release under this License is not already Covered Code governed by this License.

1.11. ``Source Code'' means the preferred form of the Covered Code for making modifications to it, including all modules it contains, plus any associated interface definition files, scripts used to control compilation and installation of an Executable, or a list of source code differential com-parisons against either the Original Code or another well known, available Covered Code of the Contributor's choice. The Source Code can be in a compressed or archival form, provided the appropriate decompression or de-archiving software is widely available for no charge.

1.12. ``You'' means an individual or a legal entity exercising rights under, and complying with all of the terms of, this License or a future version of this License issued under Section 6.1. For legal entities, ``You'' includes any entity which controls, is controlled by, or is under common con-trol with You. For purposes of this definition, ``control'' means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) owner-ship of fifty percent (50%) or more of the outstanding shares or beneficial ownership of such entity.

2. Source Code License.

2.1. The Initial Developer Grant.

The Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive license, subject to third party intellectual property claims:

(a) to use, reproduce, modify, display, perform, sublicense and distribute the Original Code (or portions thereof) with or without Modifications, or as part of a Larger Work; and

(b) under patents now or hereafter owned or controlled by Initial Developer, to make, have made, use and sell (`Ùtilize'') the Original Code (or portions thereof), but solely to the extent that any such patent is reasonably necessary to enable You to Utilize the Original Code (or portions thereof) and not to any greater extent that may be necessary to Utilize further Modifications or combinations.

2.2. Contributor Grant.


Each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license, subject to third party intellectual property claims:

(a) to use, reproduce, modify, display, perform, sublicense and distribute the Modifications created by such Contributor (or portions thereof) either on an unmodified basis, with other Modi-fications, as Covered Code or as part of a Larger Work; and

(b) under patents now or hereafter owned or controlled by Contributor, to Utilize the Con-tributor Version (or portions thereof), but solely to the extent that any such patent is reasonably necessary to enable You to Utilize the Contributor Version (or portions thereof), and not to any greater extent that may be necessary to Utilize further Modifications or combinations.

3. Distribution Obligations.

3.1. Application of License.

The Modifications which You create or to which You contribute are governed by the terms of this License, including without limitation Section 2.2. The Source Code version of Covered Code may be distributed only under the terms of this License or a future version of this License released under Section 6.1, and You must include a copy of this License with every copy of the Source Code You distribute. You may not offer or impose any terms on any Source Code version that alters or restricts the applicable version of this License or the recipients' rights hereunder. How-ever, You may include an additional document offering the additional rights described in Section 3.5.

3.2. Availability of Source Code.

Any Modification which You create or to which You contribute must be made available in Source Code form under the terms of this License either on the same media as an Executable ver-sion or via an accepted Electronic Distribution Mechanism to anyone to whom you made an Exe-cutable version available; and if made available via Electronic Distribution Mechanism, must remain available for at least twelve (12) months after the date it initially became available, or at least six (6) months after a subsequent version of that particular Modification has been made available to such recipients. You are responsible for ensuring that the Source Code version remains available even if the Electronic Distribution Mechanism is maintained by a third party.

3.3. Description of Modifications.

You must cause all Covered Code to which you contribute to contain a file documenting the changes You made to create that Covered Code and the date of any change. You must include a prominent statement that the Modification is derived, directly or indirectly, from Original Code provided by the Initial Developer and including the name of the Initial Developer in (a) the Source Code, and (b) in any notice in an Executable version or related documentation in which You describe the origin or ownership of the Covered Code.

3.4. Intellectual Property Matters

(a) Third Party Claims.

If You have knowledge that a party claims an intellectual property right in particular func-tionality or code (or its utilization under this License), you must include a text file with the source code distribution titled ``LEGAL'' which describes the claim and the party making the claim in sufficient detail that a recipient will know whom to contact. If you obtain such knowledge after You make Your Modification available as described in Section 3.2, You shall promptly modify the LEGAL file in all copies You make available thereafter and shall take other steps (such as notify-ing appropriate mailing lists or newsgroups) reasonably calculated to inform those who received the Covered Code that new knowledge has been obtained.

(b) Contributor APIs.

If Your Modification is an application programming interface and You own or control pat-ents which are reasonably necessary to implement that API, you must also include this informa-tion in the LEGAL file.

3.5. Required Notices.

You must duplicate the notice in Exhibit A in each file of the Source Code, and this License in any documentation for the Source Code, where You describe recipients' rights relating to Covered Code. If You created one or more Modification(s), You may add your name as a Contributor to the


notice described in Exhibit A. If it is not possible to put such notice in a particular Source Code file due to its structure, then you must include such notice in a location (such as a relevant directory file) where a user would be likely to look for such a notice. You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Cov-ered Code. However, You may do so only on Your own behalf, and not on behalf of the Initial Developer or any Contributor. You must make it absolutely clear than any such warranty, sup-port, indemnity or liability obligation is offered by You alone, and You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of warranty, support, indemnity or liability terms You offer.

3.6. Distribution of Executable Versions.

You may distribute Covered Code in Executable form only if the requirements of Section 3.1-3.5 have been met for that Covered Code, and if You include a notice stating that the Source Code version of the Covered Code is available under the terms of this License, including a description of how and where You have fulfilled the obligations of Section 3.2. The notice must be conspicu-ously included in any notice in an Executable version, related documentation or collateral in which You describe recipients' rights relating to the Covered Code. You may distribute the Exe-cutable version of Covered Code under a license of Your choice, which may contain terms differ-ent from this License, provided that You are in compliance with the terms of this License and that the license for the Executable version does not attempt to limit or alter the recipient's rights in the Source Code version from the rights set forth in this License. If You distribute the Executable ver-sion under a different license You must make it absolutely clear that any terms which differ from this License are offered by You alone, not by the Initial Developer or any Contributor. You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of any such terms You offer.

3.7. Larger Works.

You may create a Larger Work by combining Covered Code with other code not governed by the terms of this License and distribute the Larger Work as a single product. In such a case, You must make sure the requirements of this License are fulfilled for the Covered Code.

4. Inability to Comply Due to Statute or Regulation.

If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Code due to statute or regulation then You must: (a) comply with the terms of this License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be included in the LEGAL file described in Section 3.4 and must be included with all distributions of the Source Code. Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it.

5. Application of this License.

This License applies to code to which the Initial Developer has attached the notice in Exhibit A, and to related Covered Code.

6. Versions of the License.

6.1. New Versions.

Netscape Communications Corporation (``Netscape'') may publish revised and/or new ver-sions of the License from time to time. Each version will be given a distinguishing version num-ber.

6.2. Effect of New Versions.

Once Covered Code has been published under a particular version of the License, You may always continue to use it under the terms of that version. You may also choose to use such Cov-ered Code under the terms of any subsequent version of the License published by Netscape. No one other than Netscape has the right to modify the terms applicable to Covered Code created under this License.

6.3. Derivative Works.

If you create or use a modified version of this License (which you may only do in order to apply it to code which is not already Covered Code governed by this License), you must (a) rename Your license so that the phrases ``Mozilla'', ``MOZILLAPL'', ``MOZPL'', ``Netscape'', ``NPL'' or any confusingly similar phrase do not appear anywhere in your license and (b) other-


wise make it clear that your version of the license contains terms which differ from the Mozilla Public License and Netscape Public License. (Filling in the name of the Initial Developer, Original Code or Contributor in the notice described in Exhibit A shall not of themselves be deemed to be modifications of this License.)

7. DISCLAIMER OF WARRANTY.

COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN ``AS IS'' BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF DEFECTS, MER-CHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INI-TIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECES-SARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.

8. TERMINATION.

This License and the rights granted hereunder will terminate automatically if You fail to com-ply with terms herein and fail to cure such breach within 30 days of becoming aware of the breach. All sublicenses to the Covered Code which are properly granted shall survive any termi-nation of this License. Provisions which, by their nature, must remain in effect beyond the termi-nation of this License shall survive.

9. LIMITATION OF LIABILITY.

UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE INITIAL DEVEL-OPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO YOU OR ANY OTHER PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHAR-ACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMI-TATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THAT EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.

10. U.S. GOVERNMENT END USERS.

The Covered Code is a ``commercial item,'' as that term is defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of ``commercial computer software'' and ``commercial computer software documenta-tion,'' as such terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquire Cov-ered Code with only those rights set forth herein.

11. MISCELLANEOUS.

This License represents the complete agreement concerning subject matter hereof. If any provi-sion of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. This License shall be governed by California law provisions (except to the extent applicable law, if any, provides otherwise), excluding its conflict-of-law pro-visions. With respect to disputes in which at least one party is a citizen of, or an entity chartered or registered to do business in, the United States of America: (a) unless otherwise agreed in writing, all disputes relating to this License (excepting any dispute relating to intellectual property rights) shall be subject to final and binding arbitration, with the losing party paying all costs of arbitra-tion; (b) any arbitration relating to this Agreement shall be held in Santa Clara County, California, under the auspices of JAMS/EndDispute; and (c) any litigation relating to this Agreement shall be subject to the jurisdiction of the Federal Courts of the Northern District of California, with venue lying in Santa Clara County, California, with the losing party responsible for costs, including


without limitation, court costs and reasonable attorneys fees and expenses. The application of the United Nations Convention on Contracts for the International Sale of Goods is expressly excluded. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not apply to this License.

12. RESPONSIBILITY FOR CLAIMS.

Except in cases where another Contributor has failed to comply with Section 3.4, You are responsible for damages arising, directly or indirectly, out of Your utilization of rights under this License, based on the number of copies of Covered Code you made available, the revenues you received from utilizing such rights, and other relevant factors. You agree to work with affected parties to distribute responsibility on an equitable basis.

Mozilla Public License 1.1 (full text)

Mozilla Public License Version 1.1

1. Definitions.

1.0.1. "Commercial Use"

means distribution or otherwise making the Covered Code available to a third party.

1.1. "Contributor"

means each entity that creates or contributes to the creation of Modifications.

1.2. "Contributor Version"

means the combination of the Original Code, prior Modifications used by a Contributor, and the Modifications made by that particular Contributor.

1.3. "Covered Code"

means the Original Code or Modifications or the combination of the Original Code and Modifica-tions, in each case including portions thereof.

1.4. "Electronic Distribution Mechanism"

means a mechanism generally accepted in the software development community for the elec-tronic transfer of data.

1.5. "Executable"

means Covered Code in any form other than Source Code.

1.6. "Initial Developer"

means the individual or entity identified as the Initial Developer in the Source Code notice required by Exhibit A.

1.7. "Larger Work"

means a work which combines Covered Code or portions thereof with code not governed by the terms of this License.

1.8. "License"

means this document.

1.8.1. "Licensable"

means having the right to grant, to the maximum extent possible, whether at the time of the initial grant or subsequently acquired, any and all of the rights conveyed herein.

1.9. "Modifications"

means any addition to or deletion from the substance or structure of either the Original Code or any previous Modifications. When Covered Code is released as a series of files, a Modification is:

1. Any addition to or deletion from the contents of a file containing Original Code or previous Modifications.

2. Any new file that contains any part of the Original Code or previous Modifications.

1.10. "Original Code"


means Source Code of computer software code which is described in the Source Code notice required by Exhibit A as Original Code, and which, at the time of its release under this License is not already Covered Code governed by this License.

1.10.1. "Patent Claims"

means any patent claim(s), now owned or hereafter acquired, including without limitation, method, process, and apparatus claims, in any patent Licensable by grantor.

1.11. "Source Code"

means the preferred form of the Covered Code for making modifications to it, including all mod-ules it contains, plus any associated interface definition files, scripts used to control compilation and installation of an Executable, or source code differential comparisons against either the Origi-nal Code or another well known, available Covered Code of the Contributor's choice. The Source Code can be in a compressed or archival form, provided the appropriate decompression or de-archiving software is widely available for no charge.

1.12. "You" (or "Your")

means an individual or a legal entity exercising rights under, and complying with all of the terms of, this License or a future version of this License issued under Section 6.1. For legal entities, "You" includes any entity which controls, is controlled by, or is under common control with You. For purposes of this definition, "control" means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial ownership of such entity.

2. Source Code License.

2.1. The Initial Developer Grant.

The Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive license, subject to third party intellectual property claims:

1. under intellectual property rights (other than patent or trademark) Licensable by Initial Developer to use, reproduce, modify, display, perform, sublicense and distribute the Original Code (or portions thereof) with or without Modifications, and/or as part of a Larger Work; and

2. under Patents Claims infringed by the making, using or selling of Original Code, to make, have made, use, practice, sell, and offer for sale, and/or otherwise dispose of the Original Code (or portions thereof).

3. the licenses granted in this Section 2.1 (a) and (b) are effective on the date Initial Developer first distributes Original Code under the terms of this License.

4. Notwithstanding Section 2.1 (b) above, no patent license is granted: 1) for code that You delete from the Original Code; 2) separate from the Original Code; or 3) for infringements caused by: i) the modification of the Original Code or ii) the combination of the Original Code with other soft-ware or devices.

2.2. Contributor Grant.

Subject to third party intellectual property claims, each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license

1. under intellectual property rights (other than patent or trademark) Licensable by Contributor, to use, reproduce, modify, display, perform, sublicense and distribute the Modifications created by such Contributor (or portions thereof) either on an unmodified basis, with other Modifications, as Covered Code and/or as part of a Larger Work; and

2. under Patent Claims infringed by the making, using, or selling of Modifications made by that Contributor either alone and/or in combination with its Contributor Version (or portions of such combination), to make, use, sell, offer for sale, have made, and/or otherwise dispose of: 1) Modifi-cations made by that Contributor (or portions thereof); and 2) the combination of Modifications made by that Contributor with its Contributor Version (or portions of such combination).

3. the licenses granted in Sections 2.2 (a) and 2.2 (b) are effective on the date Contributor first makes Commercial Use of the Covered Code.

4. Notwithstanding Section 2.2 (b) above, no patent license is granted: 1) for any code that Con-tributor has deleted from the Contributor Version; 2) separate from the Contributor Version; 3) for


infringements caused by: i) third party modifications of Contributor Version or ii) the combina-tion of Modifications made by that Contributor with other software (except as part of the Contrib-utor Version) or other devices; or 4) under Patent Claims infringed by Covered Code in the absence of Modifications made by that Contributor.

3. Distribution Obligations.

3.1. Application of License.

The Modifications which You create or to which You contribute are governed by the terms of this License, including without limitation Section 2.2. The Source Code version of Covered Code may be distributed only under the terms of this License or a future version of this License released under Section 6.1, and You must include a copy of this License with every copy of the Source Code You distribute. You may not offer or impose any terms on any Source Code version that alters or restricts the applicable version of this License or the recipients' rights hereunder. How-ever, You may include an additional document offering the additional rights described in Section 3.5.

3.2. Availability of Source Code.

Any Modification which You create or to which You contribute must be made available in Source Code form under the terms of this License either on the same media as an Executable version or via an accepted Electronic Distribution Mechanism to anyone to whom you made an Executable version available; and if made available via Electronic Distribution Mechanism, must remain available for at least twelve (12) months after the date it initially became available, or at least six (6) months after a subsequent version of that particular Modification has been made available to such recipients. You are responsible for ensuring that the Source Code version remains available even if the Electronic Distribution Mechanism is maintained by a third party.

3.3. Description of Modifications.

You must cause all Covered Code to which You contribute to contain a file documenting the changes You made to create that Covered Code and the date of any change. You must include a prominent statement that the Modification is derived, directly or indirectly, from Original Code provided by the Initial Developer and including the name of the Initial Developer in (a) the Source Code, and (b) in any notice in an Executable version or related documentation in which You describe the origin or ownership of the Covered Code.

3.4. Intellectual Property Matters

(a) Third Party Claims

If Contributor has knowledge that a license under a third party's intellectual property rights is required to exercise the rights granted by such Contributor under Sections 2.1 or 2.2, Contributor must include a text file with the Source Code distribution titled "LEGAL" which describes the claim and the party making the claim in sufficient detail that a recipient will know whom to con-tact. If Contributor obtains such knowledge after the Modification is made available as described in Section 3.2, Contributor shall promptly modify the LEGAL file in all copies Contributor makes available thereafter and shall take other steps (such as notifying appropriate mailing lists or news-groups) reasonably calculated to inform those who received the Covered Code that new knowl-edge has been obtained.

(b) Contributor APIs

If Contributor's Modifications include an application programming interface and Contributor has knowledge of patent licenses which are reasonably necessary to implement that API, Contributor must also include this information in the legal file.

(c) Representations.

Contributor represents that, except as disclosed pursuant to Section 3.4 (a) above, Contributor believes that Contributor's Modifications are Contributor's original creation(s) and/or Contribu-tor has sufficient rights to grant the rights conveyed by this License.

3.5. Required Notices.

You must duplicate the notice in Exhibit A in each file of the Source Code. If it is not possible to put such notice in a particular Source Code file due to its structure, then You must include such notice in a location (such as a relevant directory) where a user would be likely to look for such a notice. If You created one or more Modification(s) You may add your name as a Contributor to


the notice described in Exhibit A. You must also duplicate this License in any documentation for the Source Code where You describe recipients' rights or ownership rights relating to Covered Code. You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Code. However, You may do so only on Your own behalf, and not on behalf of the Initial Developer or any Contributor. You must make it abso-lutely clear than any such warranty, support, indemnity or liability obligation is offered by You alone, and You hereby agree to indemnify the Initial Developer and every Contributor for any lia-bility incurred by the Initial Developer or such Contributor as a result of warranty, support, indemnity or liability terms You offer.

3.6. Distribution of Executable Versions.

You may distribute Covered Code in Executable form only if the requirements of Sections 3.1, 3.2, 3.3, 3.4 and 3.5 have been met for that Covered Code, and if You include a notice stating that the Source Code version of the Covered Code is available under the terms of this License, including a description of how and where You have fulfilled the obligations of Section 3.2. The notice must be conspicuously included in any notice in an Executable version, related documentation or collat-eral in which You describe recipients' rights relating to the Covered Code. You may distribute the Executable version of Covered Code or ownership rights under a license of Your choice, which may contain terms different from this License, provided that You are in compliance with the terms of this License and that the license for the Executable version does not attempt to limit or alter the recipient's rights in the Source Code version from the rights set forth in this License. If You distribute the Executable version under a different license You must make it absolutely clear that any terms which differ from this License are offered by You alone, not by the Initial Devel-oper or any Contributor. You hereby agree to indemnify the Initial Developer and every Contrib-utor for any liability incurred by the Initial Developer or such Contributor as a result of any such terms You offer.

3.7. Larger Works.

You may create a Larger Work by combining Covered Code with other code not governed by the terms of this License and distribute the Larger Work as a single product. In such a case, You must make sure the requirements of this License are fulfilled for the Covered Code.

4. Inability to Comply Due to Statute or Regulation.

If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Code due to statute, judicial order, or regulation then You must: (a) comply with the terms of this License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be included in the legal file described in Section 3.4 and must be included with all distributions of the Source Code. Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it.

5. Application of this License.

This License applies to code to which the Initial Developer has attached the notice in Exhibit A and to related Covered Code.

6. Versions of the License.

6.1. New Versions

Netscape Communications Corporation ("Netscape") may publish revised and/or new versions of the License from time to time. Each version will be given a distinguishing version number.

6.2. Effect of New Versions

Once Covered Code has been published under a particular version of the License, You may always continue to use it under the terms of that version. You may also choose to use such Cov-ered Code under the terms of any subsequent version of the License published by Netscape. No one other than Netscape has the right to modify the terms applicable to Covered Code created under this License.

6.3. Derivative Works

If You create or use a modified version of this License (which you may only do in order to apply it to code which is not already Covered Code governed by this License), You must (a) rename Your license so that the phrases "Mozilla", "MOZILLAPL", "MOZPL", "Netscape", "MPL", "NPL" or any confusingly similar phrase do not appear in your license (except to note that your license differs


from this License) and (b) otherwise make it clear that Your version of the license contains terms which differ from the Mozilla Public License and Netscape Public License. (Filling in the name of the Initial Developer, Original Code or Contributor in the notice described in Exhibit A shall not of themselves be deemed to be modifications of this License.)

7. Disclaimer of warranty

Covered code is provided under this license on an "as is" basis, without warranty of any kind, either expressed or implied, including, without limitation, warranties that the covered code is free of defects, merchantable, fit for a particular purpose or non-infringing. The entire risk as to the quality and performance of the covered code is with you. Should any covered code prove defec-tive in any respect, you (not the initial developer or any other contributor) assume the cost of any necessary servicing, repair or correction. This disclaimer of warranty constitutes an essential part of this license. No use of any covered code is authorized hereunder except under this disclaimer.

8. Termination

8.1. This License and the rights granted hereunder will terminate automatically if You fail to com-ply with terms herein and fail to cure such breach within 30 days of becoming aware of the breach. All sublicenses to the Covered Code which are properly granted shall survive any termi-nation of this License. Provisions which, by their nature, must remain in effect beyond the termi-nation of this License shall survive.

8.2. If You initiate litigation by asserting a patent infringement claim (excluding declatory judg-ment actions) against Initial Developer or a Contributor (the Initial Developer or Contributor against whom You file such action is referred to as "Participant") alleging that:

1. such Participant's Contributor Version directly or indirectly infringes any patent, then any and all rights granted by such Participant to You under Sections 2.1 and/or 2.2 of this License shall, upon 60 days notice from Participant terminate prospectively, unless if within 60 days after receipt of notice You either: (i) agree in writing to pay Participant a mutually agreeable reasonable royalty for Your past and future use of Modifications made by such Participant, or (ii) withdraw Your litigation claim with respect to the Contributor Version against such Participant. If within 60 days of notice, a reasonable royalty and payment arrangement are not mutually agreed upon in writing by the parties or the litigation claim is not withdrawn, the rights granted by Participant to You under Sections 2.1 and/or 2.2 automatically terminate at the expiration of the 60 day notice period specified above.

2. any software, hardware, or device, other than such Participant's Contributor Version, directly or indirectly infringes any patent, then any rights granted to You by such Participant under Sec-tions 2.1(b) and 2.2(b) are revoked effective as of the date You first made, used, sold, distributed, or had made, Modifications made by that Participant.

8.3. If You assert a patent infringement claim against Participant alleging that such Participant's Contributor Version directly or indirectly infringes any patent where such claim is resolved (such as by license or settlement) prior to the initiation of patent infringement litigation, then the rea-sonable value of the licenses granted by such Participant under Sections 2.1 or 2.2 shall be taken into account in determining the amount or value of any payment or license.

8.4. In the event of termination under Sections 8.1 or 8.2 above, all end user license agreements (excluding distributors and resellers) which have been validly granted by You or any distributor hereunder prior to termination shall survive termination.

9. Limitation of liability

Under no circumstances and under no legal theory, whether tort (including negligence), contract, or otherwise, shall you, the initial developer, any other contributor, or any distributor of covered code, or any supplier of any of such parties, be liable to any person for any indirect, special, inci-dental, or consequential damages of any character including, without limitation, damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses, even if such party shall have been informed of the possibility of such damages. This limitation of liability shall not apply to liability for death or personal injury resulting from such party's negligence to the extent applicable law prohibits such limitation. Some jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so this exclusion and limitation may not apply to you.

10. U.S. government end users


The Covered Code is a "commercial item," as that term is defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer software" and "commercial computer software documenta-tion," as such terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquire Cov-ered Code with only those rights set forth herein.

11. Miscellaneous

This License represents the complete agreement concerning subject matter hereof. If any provi-sion of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. This License shall be governed by California law provisions (except to the extent applicable law, if any, provides otherwise), excluding its conflict-of-law pro-visions. With respect to disputes in which at least one party is a citizen of, or an entity chartered or registered to do business in the United States of America, any litigation relating to this License shall be subject to the jurisdiction of the Federal Courts of the Northern District of California, with venue lying in Santa Clara County, California, with the losing party responsible for costs, includ-ing without limitation, court costs and reasonable attorneys' fees and expenses. The application of the United Nations Convention on Contracts for the International Sale of Goods is expressly excluded. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not apply to this License.

12. Responsibility for claims

As between Initial Developer and the Contributors, each party is responsible for claims and dam-ages arising, directly or indirectly, out of its utilization of rights under this License and You agree to work with Initial Developer and Contributors to distribute such responsibility on an equitable basis. Nothing herein is intended or shall be deemed to constitute any admission of liability.

13. Multiple-licensed code

Initial Developer may designate portions of the Covered Code as "Multiple-Licensed". "Multiple-Licensed" means that the Initial Developer permits you to utilize portions of the Covered Code under Your choice of the MPL or the alternative licenses, if any, specified by the Initial Developer in the file described in Exhibit A.

reliatel - tone software · 2019. 10. 7. · chapter 1 introduction 3 installing stepar note: if...

Documents