5 About Installation and Removal
This chapter provides information about the installed components for the Oracle Communications Convergent Charging Controller application described in this guide. It also lists the files installed by the application that you can check for, to ensure that the application installed successfully.
UCAI Requirements
The signaling capacity requirements for the SS7 links to the originating network switch are dependent on the following parameters:
- BHCA for service
- Required normal network link load
- Average number of octets send and received per call
The bit rate capacity can be estimated as:
r=(x.b)/450
Where:
- x = the BCHA number
- b = number of octets per call (sent or received)
Example:
Assuming 100 octets per call (both sent and received), a service with 300000 BHCA would require 66.7 Kbits per second.
If 64Kbit s-1 links are used, and a link load of 60% is required, a link would support 38.4 Kbit s-1.
Therefore, 2 links would be required to support the load. For redundancy, an additional link is normally installed unless the link load figure takes account of this.
ISUP Signalling Link Set Dimensioning
Terminating Exchange Signaling
Since the terminating trunk signaling may need to establish and clear more than one call per call to the service, the terminating exchange signaling requirements are a multiple of the originating signaling requirements.
The average number of calls that must be established as a result of each incoming call determines the required multiple.
Example: If each service invocation requires a call to be established to an SRF and then routed to final destination, a multiplication factor of 2 would be applied to determine the terminating exchange signaling requirements.
Trunk dimensioning
The number of trunks that must be configured is totally dependent on the number of simultaneous calls UCAI must handle.
This is dependent on traffic forecasts and quality of service (QoS) data. If a service is expected to have x busy hour call attempts (BHCA), with each call lasting an average of y seconds, then the number of simultaneous calls C is:
c=(x.y)/3600
The number of VSSP trunks is the number of simultaneous calls divided by the number of speech channels in a trunk (E1=30, T1=24).
When QoS is taken into consideration, the number of trunks will be increased, to allow for the non-uniform profile of real service usage.
Example: A service requires 10000 BHCA and has an average call hold time of 2 minutes. The number of simultaneous calls is therefore 3334, which is 14 T1 trunks. To achieve the desired QoS requires a 30% over provisioning of capacity, which results in 19 T1 trunks.
Installation and Removal Overview
For information about the following requirements and tasks, see Installation Guide:
- Convergent Charging Controller system requirements
- Pre-installation tasks
- Installing and removing Convergent Charging Controller packages
Add vssp entry to SLEE.cfg
Configure UCAI to use the SLEE by adding an entry for the vssp process in SLEE.cfg.
Unless the setup of this installation of UCAI is unusual, the line should be:
INTERFACE=VSSP vssp.sh /IN/service_packages/VSSP/bin
EVENTFor more information about adding entries to SLEE.cfg, see SLEE Technical Guide.
Checking the Installation
Refer to these checklists to ensure that UCAI has installed correctly.
Checklist
Follow the steps in this checklist to ensure UCAI has been installed on a SLC machine correctly.
- Log in to SLC machine as root.
- Check the following directory structure exists with subdirectories:
/IN/service_packages/VSSP
- Check the directory contains subdirectories and that all are owned by:
acs_oper user (group oracle)
- Check the entries of following file:
/IN/service_packages/SLEE/etc/SLEE.cfg
SLEE startup entries for VSSP on a SLC:
INTERFACE=VSSP vssp.sh /IN/service_packages/VSSP/bin EVENT - Check that the processes listed in the process lists are running on the relevant machine. For a list of the processes which should be running, see Process list .