# Installation Guide

# Upgrading Oracle Communications Services Gatekeeper

This chapter describes upgrading Oracle Communications Services Gatekeeper 4.0/4.1 to Oracle Communications Services Gatekeeper 4.1.1

## Introduction

An Oracle Communications Services Gatekeeper 4.0/4.1 installation can be upgraded to Oracle Communications Services Gatekeeper 4.1.1 without shutting down the entire cluster or domain, which leads to no service interruption for applications using Oracle Communications Services Gatekeeper. The process is known as a Rolling Upgrade and is a WebLogic Server feature.

The process is based on a rolling scheme, where each server in the domain, one at the time, is stopped, upgraded to the new version, and then started. This process upgrades the WebLogic Server and the Oracle Communications Services Gatekeeper Core services, but leaves all communication services as before the upgrade.

When all servers have been upgraded, the communication services in use need to be upgraded. This is done using in-production redeployment, which is a WebLogic Server feature that enables the communication services to be upgraded without any traffic interruption.

It is strongly recommended that any configuration data be backed up prior to the upgrade.

## Limitations

The following limitations applies for the upgrade:

- The patch XUE6 must have been applied to the Oracle Communications Services Gatekeeper 4.0 installation.
- Do not make configuration changes during the upgrade process until all the servers in the cluster have been upgraded. This is especially true for new configuration options. Servers will silently ignore settings that are not understood, and the local configuration file may not be updated properly. Using new configuration options may remove the capability of un-installing a maintenance upgrade in a rolling fashion.
- For a minor release, during the rolling upgrade, there must be two entirely separate installation directories. That is, the location of the old installation and the location of the new installation must be two different directories.
- After running the database migration scripts, new SLAs cannot be added on any server still running version 4.0.

(Running database migration scripts is not necessary between 4.1 to 4.1.1.)

- Servers on older versions should not be restarted during the upgrade process.
- The Service Enabler for Parlay X 2.1/Extended Web Services/SMPP must be redeployed, see Upgrade Communication Services and Interceptors.
- The Service Enabler for Parlay X 2.1/Extended Web Services/SMPP must be redeployed, see Upgrade Communication Services and Interceptors.
- The Service Enablers for SIP Communication Services can not use registered notifications after an upgrade, see Upgrade Communication Services and Interceptors.

## Task Overview

The upgrade process is divided into a set of sub-steps, see below:

Step 1: Upgrade the Servers

Step 2: Upgrade the Communication Services

Step 3: Configure New Features

Step 4: Post Upgrade Procedure

### Step 1: Upgrade the Servers

Below is a description of the upgrade process for the servers. All steps must be performed on all servers, unless stated otherwise. The first server to upgrade must be the Administration Server.

1. Prepare the server to be upgraded. See Prepare to Upgrade.
2. Stop the Administration server, see Stop Server.
3. Upgrade the Administration server to the new version, see Upgrade Server to New Version.
4. Migrate the database, see Migrating the Database. This step should only be performed once.

This step is not necessary if you are moving from 4.1 to 4.1.1.

5. Verify that the $PATH and $CLASSPATH environment variables point to the upgraded environment. Clean the shell environment and setup the environment variables according to the instruction in Upgrade Server to New Version if necessary.
6. Start the Administration server.
7. Repeat the following steps on each managed server:

1. Stop the managed server, see Stop Server.
2. Upgrade the managed server to the new version, see Upgrade Server to New Version.
3. Verify that the $PATH and $CLASSPATH environment variables point to the upgraded environment. Clean the shell environment and setup the environment variables according to the instruction in Upgrade Server to New Version if necessary.
4. Start the managed server.

### Step 2: Upgrade the Communication Services

When all servers have been upgraded, the Communication Services must be upgraded, see Upgrade Communication Services and Interceptors.

If the new SIP-type Communication Services are to be used, the co-located Oracle Converged Application Server must be used.

### Step 3: Configure New Features

Oracle Communications Services Gatekeeper 4.1 has a set of new features that must be manually installed and configured when upgrading. Note that it is only necessary to perform these steps if you are using this new functionality.

This step is not necessary if you are upgrading from 4.1 to 4.1.1.

- Using New Features in an Upgraded Environment

- Upgrading SIP Connectivity
- Using RESTFul Service Facades
- Using SOA Service Facades

### Step 4: Post Upgrade Procedure

When all servers have been upgraded, two new singleton services must be added and new CDR, EDR, and alarm definitions must added.

Follow the steps below to perform the post-upgrade procedures:

1. Add the singleton services BudgetEnforcementProxy and GeoStorageProxy. Starting in the Administration console in the Domain Structure pane:

1. Choose Environment Clusters<Network Tier cluster>. Choose the Singleton Services tab.
2. Click New, and enter the following:

In the Name field, enter `BudgetEnforcementProxy`

In the Class Name field, enter `com.bea.wlcp.wlng.core.budget.BudgetEnforcementSingletonService`

3. Click Finish.

Note: | If you are upgrading from 4.1 to 4.1.1, you do not need to complete d or e.

4. Click New, and enter the following:

In the Name field, enter `GeoStorageProxy`

In the Class Name field, enter `com.bea.wlcp.wlng.geostorage.GeoStorageSingletonService`

5. Click Finish.

2. To update the CDR, EDR and Alarm information for the new and updated services, use the EDR Configuration page in the Administration Console. See Reference: New EDR, CDR, and Alarm definitions for a list of new and changed EDRs, CDRs, and Alarms.

## Prepare to Upgrade

Using the Administration console, delete the `BudgetEnforcementProxy` singleton service. Starting in the Domain Structure pane, choose Environment Clusters<Network Tier cluster>. Choose the Singleton Services tab. Check the check-box `BudgetEnforcementProxy` and click Delete.

## Migrating the Database

Some aspects of the way Oracle Communications Services Gatekeeper stores information in the database have changed with this release. You must run a set of migration scripts to upgrade your current data to Service Gatekeeper 4.0 formats.

This step is not necessary for upgrades from 4.1 to 4.1.1.

These scripts are located in the `migration.zip` file, which is found in `<$BEA_HOME for OCSG 4.1>/wlserver_10.3/common/templates/scripts/`

Note: | The database scripts for MySQL (migrate_mysql.txt) and Oracle Database (migrate_oracle.txt) must be updated. Change from: `UPDATE wlng_slas set sla_scope = 'sp_node' where sla_type='service_provider';` to: `UPDATE wlng_slas set sla_scope = 'sp' where sla_type='service_provider_node';`

#### Database Migration

To run the script:

1. Create a `migration` directory under the `scripts` directory.
2. Unzip the`migration.zip` file into the `migration` directory.
3. Make sure the environment variables JAVA_HOME and ORACLE_HOME (for ORACLE DB) or MYSQL_HOME (for MySQL) are set properly.
4. Run the script with the required parameters, as follows (replace CAPS with appropriate values):

    db_migration.sh <DB TYPE [oracle | mysql]> <DB HOST> <DB NAME | ORACLE SERVICE NAME> <DB USERID> <PASSWORD>

## Stop Server

Stop the server gracefully so all in-flight requests are processed before the shutdown start.

For information on how to stop a server using the administration console, see section Shutdown servers in a cluster in the Administration Console Online Help at http://download.oracle.com/docs/cd/E12840_01/wls/docs103/ConsoleHelp/core/index.html.

For information about using the Graceful Shutdown command, see shutdown in WebLogic Scripting Tool at http://download.oracle.com/docs/cd/E12840_01/wls/docs103/config_scripting/index.html.

You must shut the server down before starting to upgrade it.

## Upgrade Server to New Version

Follow the steps below to upgrade the server:

1. Install Oracle Communications Services Gatekeeper 4.1.1, see Installing Oracle Communications Services Gatekeeper.

Install it under a directory different from the $BEA_HOME directory used for your previous Oracle Communications Services Gatekeeper, whether it is 4.0 or 4.1. Do not configure the domain. The domain configuration used in your previous Oracle Communications Services Gatekeeper installation will be used.

2. Setup necessary environment variables.

On Windows: run the script `$BEA_HOME_411\wlserver_10.3\server\bin\setWLSEnv.cmd`

On UNIX: source the script `$BEA_HOME_411/wlserver_10.3/server/bin/setWLSEnv.sh`

`$BEA_HOME_411` refers to the `$BEA_HOME` directory for Oracle Communications Services Gatekeeper 4.1.1

3. Change directory to `$BEA_HOME_411/wlserver_10.3/common/templates/scripts/upgrade` and execute the target dist in the ant script. The ant script takes the following arguments:

-Ddomain40.home, the $DOMAIN_HOME directory used in your previous Oracle Communications Services Gatekeeper installation, either 4.0 or 4.1.

-Dbea40.home, the $BEA_HOME directory used in your previous Oracle Communications Services Gatekeeper installation, either 4.0 or 4.1.

-Dbea41.home, the $BEA_HOME directory used in your new Oracle Communications Services Gatekeeper 4.1.1 installation.

-Dwlsold.home, the $WLS_HOME directory used in your previous Oracle Communications Services Gatekeeper installation, either 4.0 or 4.1.

-Dwlsnew.home, the $WLS_HOME directory used in your new Oracle Communications Services Gatekeeper 4.1.1 installation.

-Docsg.home, the $OCSG_HOME directory used in your new Oracle Communications Services Gatekeeper 4.1.1 installation.

-Dserver.name, the server name.

Example: (for 4.0 to 4.1/4.1.1):

ant dist -Ddomain40.home=/usr/local/ocsg-install/user_projects/domains/ocsg-domain
-Dbea40.home=/usr/local/ocsg40-install -Dbea41.home=/usr/local/ocsg41-install
-Dwlsold.home=/usr/local/ocsg40-install/wlserver_10.3
-Dwlsnew.home=/usr/local/ocsg41-install/wlserver_10.3
-Docsg.home=/usr/local/ocsg41-install/ocsg_4.1
-Dserver.name=AdminServer

Example: (for 4.1.0 to /4.1.1):

ant dist -Ddomain40.home=/usr/local/ocsg-install/user_projects/domains/ocsg-domain
-Dbea40.home=/usr/local/ocsg410-install -Dbea41.home=/usr/local/ocsg411-install
-Dwlsold.home= /usr/local/ocsg410-install/wlserver_10.3
-Dwlsnew.home=/usr/local/ocsg411-install/wlserver_10.3
-Docsg.home=/usr/local/ocsg411-install/ocsg_4.1
-Dserver.name=AdminServer

If the default installation directories were used, only these arguments need to be defined: Ddomain40.home, -Dbea40.home, -Dbea41.home, Dserver.name.

4. If the co-located Oracle Converged Applications Server is to be used for SIP connectivity, follow the instructions in Upgrading SIP Connectivity. This should be done only on the Administration Server.

This step is not necessary for upgrade from 4.1 to 4.1.1.

5. If the RESTful Service Facades are to be used, follow the instructions in Using RESTFul Service Facades. This should be done only on the Administration Server.

This step is not necessary for upgrade from 4.1 to 4.1.1.

6. Set access privileges on the files. Change permission to read/write/execute on all files in `$DOMAIN_HOME/bin`.
7. The upgrade script assumes that the JDK was installed in `$BEA_HOME_41/jdk160_05` (SUN) or `$BEA_HOME_41/jrockit_160_05` (JRockit). Verify that the JDK you are using is installed in the appropriate directory. If the generic UNIX installer is used, the JDK is not provided so this must be installed. If generic installer was used to install Oracle Communications Services Gatekeeper, make sure to set the JAVA_HOME, defined in `$DOMAIN_HOME/bin/setDomainEnv.sh` to the right path in the file system.

## Upgrade Communication Services and Interceptors

Note: | The infrastructure for the RESTful Service Facades needs to be deployed before upgrading the Communications Services. See Using RESTFul Service Facades.

When the upgraded Oracle Communications Services Gatekeeper domain has been started, each Communication Service needs to be upgraded. This is done using the hitless upgrade procedure.

Refer to Hitless Upgrade Using Production Redeployment in Oracle Communications Services Gatekeeper System Administrator’s Guide for directions on how to perform a hitless upgrade.

The EAR names for each communication service and the JAR names for the network protocol plug-in are found under the heading “Properties for <Communication service>” in the section of Oracle Communications Services Gatekeeper System Administrator’s Guide which describes the appropriate Communication Service. There are a new set of Communication Services provided with Oracle Communications Services Gatekeeper:

- Parlay X 2.1 Payment/Diameter
- Native SMPP
- Native MM7

These must be deployed manually, as they are not deployed automatically during an upgrade. Refer to the individual sections for each of these Communication Services in Oracle Communications Services Gatekeeper System Administrator’s Guide for information on which EARs to deploy.

The Service Enablers for the SIP plug-ins have been updated to work with a co-located Oracle Converged Application Server. These must be redeployed, and cannot be upgraded using the hitless upgrade procedure. In order for the new SIP-type plug-ins to be functional, the steps involving upgrading the SIP Connectivity must be performed. Any subscriptions for notifications that have been registered by an application must be unregistered prior to the upgrade and then re-registered after the upgrade since there are incompatible changes to the store. Exceptions will be thrown if old data is accessed after the upgrade.

The Service Enabler for Parlay X 2.1/Extended Web Services Binary SMS/SMPP does not support to be hitlessly upgraded from the version that was a part of Oracle Communications Services Network Gatekeeper 4.0 to the version included in Oracle Communications Services Network Gatekeeper 4.0. The 4.0 version must be undeployed before the servers are upgraded and then the new version is deployed after the servers are upgraded.

The Service interceptors have also been updated. Deploy:

- interceptor.ear
- cdr_to_diameter.ear

in the same manner as the Communication Services. The Service Interceptors are located in the directory `$OCSG_HOME/applications`, where `$OCSG_HOME` is the installation directory for Oracle Communications Services Gatekeeper 4.1.

## Using New Features in an Upgraded Environment

A set of new features and components were added in Oracle Communications Services Gatekeeper 4.1. This section describes how to leverage these features.

### Upgrading SIP Connectivity

Oracle Communications Services Gatekeeper used WebLogic SIP server to connect to the SIP network. A standalone SIP Server installation was used.

Oracle Communications Services Gatekeeper 4.1 has Oracle Converged Application Server co-located with the Network Tier server.

Follow the instructions below to use Converged Application Server for SIP Communication Services.

Note: | Make sure that the modifications are done only on the Administration server and it is shut down while doing edits to config.xml.

1. Edit the configuration file $DOMAIN_HOME/config/config.xml. Use Listing 10-1 as an example when adding SIP-specific settings. One <server> entry is needed per Network Tier Server.
2. Edit the configuration file $DOMAIN_HOME/config/config.xml. Add the SIP custom resource definitions stated in Listing 10-2 after the Network Tier custom resource definition. The parts that must be updated are presented in bold. Correlate the server names, defined in <target> with the server names defined in $DOMAIN_HOME/config/custom/datatier.xml.
3. Restart the server after the configuration file has been updated.
Listing 10-1 Example config.xml with SIP definitions

    <server>

        <name>WLNG_NT1</name>

        <max-message-size>20000000</max-message-size>

        <log>

          <name>WLNG_NT1</name>

          <log-file-severity>Info</log-file-severity>

          <memory-buffer-severity>Info</memory-buffer-severity>

        </log>

        <machine>NT1</machine>

        <listen-port>8001</listen-port>

        <cluster>WLNG_NT_Cluster</cluster>

        <web-server>

          <name>WLNG_NT1</name>

          <web-server-log>

            <logging-enabled>false</logging-enabled>

          </web-server-log>

        </web-server>

        <listen-address>host-nt1.bea.com</listen-address>

        <network-access-point>

          <name>sipchannel</name>

          <protocol>sip</protocol>

          <listen-port>5060</listen-port>

          <public-port>5060</public-port>

          <http-enabled-for-this-protocol>false</http-enabled-for-this-protocol>

          <tunneling-enabled>false</tunneling-enabled>

          <outbound-enabled>true</outbound-enabled>

          <enabled>true</enabled>

          <two-way-ssl-enabled>false</two-way-ssl-enabled>

          <client-certificate-enforced>false</client-certificate-enforced>

        </network-access-point>

        <network-access-point>

          <name>sips</name>

          <protocol>sips</protocol>

          <listen-port>5061</listen-port>

          <public-port>5061</public-port>

          <http-enabled-for-this-protocol>false</http-enabled-for-this-protocol>

          <tunneling-enabled>false</tunneling-enabled>

          <outbound-enabled>true</outbound-enabled>

          <enabled>true</enabled>

          <two-way-ssl-enabled>false</two-way-ssl-enabled>

          <client-certificate-enforced>false</client-certificate-enforced>

        </network-access-point>

        <jta-migratable-target>

          <name>WLNG_NT1</name>

          <user-preferred-server>WLNG_NT1</user-preferred-server>

          <cluster>WLNG_NT_Cluster</cluster>

        </jta-migratable-target>

        <managed-server-independence-enabled>false</managed-server-independence-enabled>

      </server>

    <server>

        <name>WLNG_NT2</name>

        <max-message-size>20000000</max-message-size>

        <log>

          <log-file-severity>Info</log-file-severity>

          <memory-buffer-severity>Info</memory-buffer-severity>

        </log>

        <machine>NT2</machine>

        <listen-port>8001</listen-port>

        <cluster>WLNG_NT_Cluster</cluster>

        <web-server>

          <web-server-log>

            <logging-enabled>false</logging-enabled>

          </web-server-log>

        </web-server>

        <listen-address>host-nt2.bea.com</listen-address>

        <network-access-point>

          <name>sipchannel</name>

          <protocol>sip</protocol>

         <listen-port>5070</listen-port>

          <public-port>5070</public-port>

         <http-enabled-for-this-protocol>false</http-enabled-for-this-protocol>

          <tunneling-enabled>false</tunneling-enabled>

          <outbound-enabled>true</outbound-enabled>

          <enabled>true</enabled>

          <two-way-ssl-enabled>false</two-way-ssl-enabled>

          <client-certificate-enforced>false</client-certificate-enforced>

        </network-access-point>

        <network-access-point>

         <name>sips</name>

          <protocol>sips</protocol>

          <listen-port>5071</listen-port>

          <public-port>5071</public-port>

         <http-enabled-for-this-protocol>false</http-enabled-for-this-protocol>

          <tunneling-enabled>false</tunneling-enabled>

          <outbound-enabled>true</outbound-enabled>

          <enabled>true</enabled>

          <two-way-ssl-enabled>false</two-way-ssl-enabled>

          <client-certificate-enforced>false</client-certificate-enforced>

        </network-access-point>

        <jta-migratable-target>

          <user-preferred-server>WLNG_NT2</user-preferred-server>

          <cluster>WLNG_NT_Cluster</cluster>

        </jta-migratable-target>

        <managed-server-independence-enabled>false</managed-server-independence-enabled>

      </server>

Listing 10-2 Custom resource definitions for SIP to be edited in config.xml

    <custom-resource>

    <name>sipserver</name>

    <target>WLNG_NT_Cluster</target>

    <descriptor-file-name>custom/sipserver.xml</descriptor-file-name>

    <resource-class>com.bea.wcp.sip.management.descriptor.resource.SipServerResource</resource-class>

    <descriptor-bean-class>com.bea.wcp.sip.management.descriptor.beans.SipServerBean</descriptor-bean-class>

    </custom-resource>

    <custom-resource>

    <name>datatier</name>

    <target>WLNG_NT_Cluster</target>

    <descriptor-file-name>custom/datatier.xml</descriptor-file-name>

    <resource-class>com.bea.wcp.sip.management.descriptor.resource.DataTierResource</resource-class>

    <descriptor-bean-class>com.bea.wcp.sip.management.descriptor.beans.DataTierBean</descriptor-bean-class>

    </custom-resource>

    <custom-resource>

    <name>approuter</name>

    <target>AdminServer</target>

    <descriptor-file-name>custom/approuter.xml</descriptor-file-name>

    <resource-class>com.bea.wcp.sip.management.descriptor.resource.AppRouterResource</resource-class>

    <descriptor-bean-class>com.bea.wcp.sip.management.descriptor.beans.SipServerBean</descriptor-bean-class>

    </custom-resource>

### Using RESTFul Service Facades

RESTful Service Facades are new to Oracle Communications Services Gatekeeper 4.1.

Follow the instructions below to use the RESTful service Facades.

Note: | Make sure that the modifications are done only on the Administration server and it is shut down while doing edits to config.xml.

1. Add the settings specified in Listing 10-3 to $DOMAIN_HOME/config/config.xml. Correlate the server names, defined in <target>, with the actual server names.
2. Change the dd-model for all deployed applications from CustomRolesandPolicies to DDOnly. The following is required in the <app-deployment> sections of $DOMAIN_HOME/config.xml:
   `<security-dd-model>DDOnly</security-dd-model>`
3. Deploy the following files in all Access Tier servers:

- $BEA_HOME/wlserver_10.3/common/deployable-libraries/pubsub-1.0.war,
- $BEA_HOME/ocsg_4.1/applications/rest.jar

See Oracle WebLogic Server Deploying Applications to WebLogic Server at http://download.oracle.com/docs/cd/E12840_01/wls/docs103/deployment/ for a description of the different deployment options.

Note: | If your installation uses multiple AT clusters, only one AT cluster can host RESTful facades. See the ”Deployment Model for Communications Services” chapter, the “Deployment of SOAP and RESTful Facades on Multiple AT Clusters” section in the System Administrator’s Guide for more information.

Listing 10-3 RESTful Service Facade definitions

    <jms-server>

    <name>JMSServer-AT1</name>

    <target>WLNG_AT1</target>

    </jms-server>

    <jms-server>

    <name>JMSServer-AT2</name>

    <target>WLNG_AT2</target>

    </jms-server>

    <jms-system-resource>

    <name>WLNG_ATJMSResource</name>

    <target>WLNG_AT_Cluster</target>

    <descriptor-file-name>jms/wlng_at-jms.xml</descriptor-file-name>

    </jms-system-resource>

### Using SOA Service Facades

SOA Service Facades are new to Oracle Communications Services Gatekeeper 4.1. For information on how to install the SOA Service Facades, see Installation of SOA Facades.

## Reference: New EDR, CDR, and Alarm definitions

Oracle Communications Services Gatekeeper 4.1 has introduced a set of new and changed EDR, CDR, and alarm definitions.

Refer to each of the following sections for a list of the changes:

- EDRs
- CDRs
- Alarms

The list contains IDs of the entries. Use the EDR configuration file `wlng-edr.xml`, and copy the definitions into the EDR Configuration page in the Administration console.

The EDR configuration file is located in the directory `config/custom` in the JAR file`$BEA_HOME_41/wlserver_10.3/common/templates/domains/ocsg-domain.jar`

### EDRs

Below is a list of changed and new EDRs. Copy the EDR definitions, not just the ID. These changes reflect 4.1 unless they are specifically marked 4.1.1.

Table 10-1 New or changed EDRs
Container service/Communication Service | EDR ID
--- | ---
Parlay X 2.1 Presence/SIP | Changed: edr id="2000"
| Changed: edr id="2001"
| Changed: edr id="2002"
| Changed: edr id="2003"
| Changed: edr id="2004"
| Changed: edr id="2005"
| Changed: edr id="2006"
| Changed: edr id="2007"
| Changed: edr id="2008"
| Changed: edr id="2009"
| Added: edr id="2010"
| Added: edr id="2011"
| Added: edr id="2012"
| Added: edr id="2013"
| Added: edr id="2014"
| Added: edr id="2015"
Binary SMS/SMPP and Parlay X 2.1 Short Messaging/SMPP | Added: edr id="7201"
| Added: edr id="7202"
| Added: edr id="7203"
| Added: edr id="7204"
| Added: edr id="7205"
| Added: edr id="7301"
| Added: edr id="7302"
| Added: edr id="7303"
| Added: edr id="7304"
| Added: edr id="7305"
| Added: edr id="7306"
| Added: edr id="7307"
Parlay X 2.1 Call Notification/SIP | Changed: edr id="8014"
| Changed: edr id="8015"
| Changed: edr id="8016"
| Changed: edr id="8017"
| Changed: edr id="8018"
| Changed: edr id="8019"
| Changed: edr id="8020"
| Changed: edr id="8021"
Parlay X 2.1 Third Party Call /SIP and INAP | Changed: edr id="8024"
Parlay X 2.1 Third Party Call /SIP | Added: edr id="8028"
| Added: edr id="8029"
Parlay X 2.1 Terminal Location | Added: edr id="9020"
| Added: edr id="9021"
| Added: edr id="9022"
Parlay X 3.0 Call Notification/Parlay | Added: edr id="11020"
| Added: edr id="11020"
| Added: edr id="11021"
| Added: edr id="11022"
| Added: edr id="11030"
| Added: edr id="11031"
| Added: edr id="11032"
| Added: edr id="11033"
| Added: edr id="11034"
| Added: edr id="11035"
| Added: edr id="11036"
WAP Push/PAP | Changed: edr id="14002"
| Added: edr id="14003"
Native MM7 | Added: edr id="401000"
| Added: edr id="401001"
| Added: edr id="401004"
| Added: edr id="401002"
| Added: edr id="401005"
| Added: edr id="401003"
| Added: edr id="401006"
| Added: edr id="401007"
Native SMPP | Added: edr id="400000"
| Added: edr id="400001"
| Added: edr id="400002"
| Added: edr id="400003"
| Added: edr id="400004"
| Added: edr id="400005"
| Added: edr id="400006"
| Added: edr id="400007"
| Added: edr id="400008"
| Added: edr id="400009"
| Added: edr id="400010"
| Added: edr id="400011"
| Added: edr id="400020"
| Added: edr id="400021"
| Added: edr id="400022"
| Added: edr id="400023"
| Added: edr id="400024"
| Added: edr id="400025"
| Added: edr id="400026"
| Added: edr id="400027"
| Added: edr id="400028"
| Added: edr id="400029"
| Added: edr id="400030"
| Added: edr id="400031"
| Added: edr id="400100"
| Added edr id=”400101”
| Added 4.1.1 edr id=”400102”
| Added 4.1.1 edr id=”400103”
| Added: edr id="400110"
| Added: edr id="400111"
| Added: edr id="400112"
Parlay X 2.1 Payment/Diameter | Added: edr id="15001"
| Added: edr id="15001"
| Added: edr id="15002"
| Added: edr id="15003"
| Added: edr id="15004"
| Added: edr id="15005"
| Added: edr id="15006"
| Added: edr id="15007"
| Added: edr id="15001"
Credit Control Interceptor | Added: edr id="16001"
| Added: edr id="16002"

### CDRs

Below is a list of changed and new CDR definitions.

Locate the CDR definition for the new CDR based on the method name and the package name in the EDR definition file. For new CDRs, copy the whole entry. If it is an existing and changed CDR, edit the listing. Example:

`<cdr>`

`<filter>`

`<method>`

`<name>void callConnected</name>`

`<class>com.bea.wlcp.wlng.plugin.tpc.sip.south.SipContextMapper</class>`

`<position>after</position>`

`</method>`

`</filter>`

`</cdr>`

Table 10-2 Changed or new CDRs
Communication Service | CDR Definition
--- | ---
Parlay X 2.1Presence/SIP | void notifyBusy New: com.bea.wlcp.wlng.plugin.callnotification.sip.south.CallNotificationPluginImpl Old: com.bea.wlcp.wlng.plugin.callnotification.sip.CallNotificationPlugin
| void notifyCalledNumber New: com.bea.wlcp.wlng.plugin.callnotification.sip.south.CallNotificationPluginImpl Old: com.bea.wlcp.wlng.plugin.callnotification.sip.CallNotificationPlugin
| void notifyNoAnswer New: com.bea.wlcp.wlng.plugin.callnotification.sip.south.CallNotificationPluginImpl Old: com.bea.wlcp.wlng.plugin.callnotification.sip.CallNotificationPlugin
| void notifyNotReachable New: com.bea.wlcp.wlng.plugin.callnotification.sip.south.CallNotificationPluginImpl Old: com.bea.wlcp.wlng.plugin.callnotification.sip.CallNotificationPlugin
| Action handleBusy New: com.bea.wlcp.wlng.plugin.callnotification.sip.south.CallDirectionPluginImpl Old: com.bea.wlcp.wlng.plugin.callnotification.sip.CallDirectionPlugin
| Action handleCalledNumber New: com.bea.wlcp.wlng.plugin.callnotification.sip.south.CallDirectionPluginImpl Old: com.bea.wlcp.wlng.plugin.callnotification.sip.CallDirectionPlugin
| Action handleNoAnswer New: com.bea.wlcp.wlng.plugin.callnotification.sip.south.CallDirectionPluginImpl
| Action handleNotReachable New: com.bea.wlcp.wlng.plugin.callnotification.sip.south.CallDirectionPluginImpl Old: com.bea.wlcp.wlng.plugin.callnotification.sip.CallDirectionPlugin
Parlay X 2.1/SIP | New entry: void callConnected com.bea.wlcp.wlng.plugin.tpc.sip.south.SipContextMapper
| New entry: void callReleased com.bea.wlcp.wlng.plugin.tpc.sip.south.SipContextMapper
Parlay X 3.0 Third Party Call/Parlay | New entry: void callEnded com.bea.wlcp.wlng.plugin.tpc.parlay.south.callback.AppMultiPartyCallPluginSouth
Native SMPP | New entry: void receiveSubmitSmResponse com.bea.wlcp.wlng.plugin.legacy.smpp.north.UpstreamSmppAgentImpl
| New entry: void receiveSubmitSmMultiResponsei com.bea.wlcp.wlng.plugin.legacy.smpp.north.UpstreamSmppAgentImpl
| New entry: void sendDeliverSmResp com.bea.wlcp.wlng.plugin.legacy.smpp.southbind.SmppPluginSouthImpl
Parlay X 2.1 Payment/Diameter | New entry: ChargeAmountResponse chargeAmount com.bea.wlcp.wlng.plugin.payment.diameter.north.AmountChargingPluginNorth
| New entry: RefundAmountResponse refundAmount com.bea.wlcp.wlng.plugin.payment.diameter.north.AmountChargingPluginNorth
| New entry: ChargeSplitAmountResponse chargeSplitAmount com.bea.wlcp.wlng.plugin.payment.diameter.north.AmountChargingPluginNorth
| New entry: ReserveAmountResponse reserveAmount com.bea.wlcp.wlng.plugin.payment.diameter.north.ReserveAmountChargingPluginNorth
| New entry: ReserveAdditionalAmountResponse reserveAdditionalAmount com.bea.wlcp.wlng.plugin.payment.diameter.north.ReserveAmountChargingPluginNorth
| New entry: ChargeReservationResponse chargeReservation com.bea.wlcp.wlng.plugin.payment.diameter.north.ReserveAmountChargingPluginNorth
| New entry: ReleaseReservationResponse releaseReservation com.bea.wlcp.wlng.plugin.payment.diameter.north.ReserveAmountChargingPluginNorth

### Alarms

Below is a list of changed and new alarms. Copy the new alarm definitions, not just the ID.

Table 10-3 New or changed alarms
Container service/Communication Service | Alarm ID
--- | ---
Container service | Added: alarm id="102826"
| Added: alarm id="102827"
| Removed: alarm id="103825"
| Changed: alarm id="102827"
| Added: alarm id="102828"
| Removed: alarm id="103826"
| Added: alarm id="102829
| Added: alarm id="102830"
| Added: alarm id="102831"
| Added alarm id="102832"
| Added: alarm id="102833"
| Added: alarm id="102834"
| Added: alarm id="102835"
| Added: alarm id="102836"
| Added: alarm id="102837"
| Added: alarm id="102838"
| Added: alarm id="102839"
| Added: alarm id="102840"
| Added: alarm id="102841"
| Added: alarm id="102842"
| Added: alarm id="102841"
| Added: alarm id="103827"
| Added: alarm id="103833"
Parlay X 2.1 Short Messaging/SMPP | Changed: alarm id="110602"
| Changed: alarm id="110616"
Parlay X 2.1 Presence/SIP | Removed: alarm id="110900"
| Changed: alarm id="110901"
| Changed: alarm id="110902"
| Changed: alarm id="110904"
| Removed: alarm id="110906"
| Changed: alarm id="110907"
| Changed: alarm id="110908"
| Changed: alarm id="110909"
| Changed: alarm id="110910"
| Changed: alarm id="110918"
| Changed: alarm id="110922"
| Removed: alarm id="110923"
| Removed: alarm id="110924"
Parlay X 2.1 Payment/Diameter | Added: alarm id="114201"
| Added: alarm id="114201"
| Added: alarm id="114202"
Container Service | Added: alarm id="111007"
SOAP to SOAP Communication Services | Added: alarm id="125101"
| Added: alarm id="125102"
CdrToDiameter | Added alarm id="113400
| Added: alarm id="113401"
| Added: alarm id="113402"
| Added: alarm id="113403"
| Added: alarm id="113404"
| Added: alarm id="113405"
| Added: alarm id="113406"
Credit Control Service Interceptor | Added: alarm id="113500"
| Added: alarm id="113501"
| Added: alarm id="113502"
| Added: alarm id="113503"
| Added alarm id="113504"
Geo-redundancy Container Service | Added: alarm id="113601"
| Added: alarm id="113602"
| Added alarm id="113701"
| Added: alarm id="113702"
Native MM7 | Added: alarm id="401050"
| Added: alarm id="401051"
| Added: alarm id="401052"
| Added: alarm id="401053"
Native SMPP | Added: alarm id="400104"
| Added: alarm id="400105"
| Added: alarm id="400106"
| Added: alarm id="400107"
| Added: alarm id="400110"
| Added: alarm id="400111"
| Added: alarm id="400112"
| Added: alarm id="400113"
| Added: alarm id="400114"