 |
|
 |
 |
Diameter Common/Util Package Installation |
 |
Steps for installation |
| |
Step 1: Prerequisites |
| |
Hardware Requirements |
| |
A current Linux desktop class machine
with network access should be enough. |
| |
Libraries Requirements |
| |
- libamps (AMPS library)
- libxml2 (XML Libraray)
- libdiameter (Diameter Base Stack library) |
| |
Note: We assume that all these above libraries
available on your system before proceeding
to the further steps. |
| |
Step 2: Get Source Code |
| |
In order to download the source code of
Diameter App Common, you need to have the
subversion installed on the system to be
used. Download the Diameter App Common source
code from its svn repository:
mkdir diameterstack |
| |
svn co https://diameterstack.svn.sourceforge.net/svnroot/diameterstack
diameterstack |
| |
Step 3: Compile and Install |
| |
1. To compile the source
code of Diameter App Common library enter
to the diameterstack/appcommon directory.. |
| |
cd diameterstack/appcommon |
| |
2. Execute the script
autogen.sh to generate makefiles from autotools.
In Linux, if the script is in your current
working directory, following command may
be used for executing the script: |
| |
./autogen.sh --prefix=/usr –datarootdir=/etc
For debugging with gdb, following command
may be used:
./autogen.sh --prefix=/usr --enable-debug=yes
For release compilation, following command
may be used:
./autogen.sh --prefix=/usr --enable-debug=no
--enable-opt=8 |
| |
Note: If –prefix are not given then
Diameter App Common library will install
to default directories. Default directorie
for installation of library is /usr/local/lib. |
| |
3. Compile the Diameter
App Common library by using the command:
make |
| |
4. Install the compiled
Diameter App Common library by using the
command:
make install |
| |
Not: if you use different directories
for installation rather than default directories
then you should add your path for library
file to environment variable LD_LIBRARY_PATH. |
|
 |
Diameter Stack Installation |
 |
Guide for compilation
and installation of Diameter Stack. |
 |
Steps for installation |
| |
Step 1: Prerequisites |
| |
Hardware Requirements |
| |
A current Linux desktop class machine
with network access should be enough. |
| |
Libraries Requirements |
| |
- libamps (AMPS library)
- libxml2 (XML Libraray) |
| |
Note: We assume that all these above libraries
available on your system before proceeding
to the further steps. |
| |
Step 2: Get Source Code |
| |
In order to download the source code of
Diameter Stack, you need to have the subversion
installed on the system to be used. Download
the Diameter Stack source code from its
svn repository:
mkdir diameterstack
svn co https://diameterstack.svn.sourceforge.net/svnroot/diameterstack
diameterstack |
| |
Step 3: Compile and Install |
| |
1. To compile the source
code of Diameter Stack enter to the diameterstack/baseprotocol
directory.. |
| |
cd diameterstack/baseprotocol |
| |
2. Execute the script
autogen.sh to generate makefiles from autotools.
In Linux, if the script is in your current
working directory, following command may
be used for executing the script: |
| |
./autogen.sh --prefix=/usr –datarootdir=/etc
For debugging with gdb, following command
may be used:
./autogen.sh --prefix=/usr --enable-debug=yes
For release compilation, following command
may be used:
./autogen.sh --prefix=/usr --enable-debug=no
--enable-opt=8 |
| |
Note: If –prefix are not given then
Diameter Stack will install to default directories.
Default directorie for installation of library
is /usr/local/lib. |
| |
3. Compile the Diameter
Stack by using the command:
make |
| |
4. Install the compiled
Diameter Stack by using the command:
make install |
| |
Not: if you use different directories
for installation rather than default directories
then you should add your path for library
file to environment variable LD_LIBRARY_PATH. |
|
 |
Home Subscriber Server Installation |
 |
Guide for compilation
and installation of Home Subscriber Server(HSS). |
 |
Steps for installation |
| |
Step 1: Prerequisites |
| |
Hardware Requirements |
| |
A current Linux desktop class machine
with network access should be enough. |
| |
Libraries Requirements |
| |
- libamps (AMPS library)
- libxml2 (XML Libraray)
- libdiameter (Diameter Base Stack library)
- libdiamappcommon (Diameter application
common library) |
| |
Note: We assume that all these above libraries
available on your system before proceeding
to the further steps. |
| |
Step 2: Get Source Code |
| |
In order to download the source code of
Home Subscriber Server, you need to have
the subversion installed on the system to
be used. Download the Home Subscriber Server
source code from its svn repository:
mkdir imshss
svn co https://imshss.svn.sourceforge.net/svnroot/imshss
imshss |
| |
Step 3: Compile and Install |
| |
1. To compile the source
code of Home Subscriber Server enter to
the imshss directory..
cd imshss |
| |
2. Execute the script
autogen.sh to generate makefiles from autotools.
In Linux, if the script is in your current
working directory, following command may
be used for executing the script: |
| |
./autogen.sh --prefix=/usr –datarootdir=/etc
For debugging with gdb, following command
may be used:
./autogen.sh --prefix=/usr --datarootdir=/etc
--enable-debug=yes
For release compilation, following command
may be used:
./autogen.sh --prefix=/usr --datarootdir=/etc
--enable-debug=no --enable-opt=8 |
| |
Note: If –prefix and –datarootdir
are not given then HSS will install to default
directories. Default directories for installation
are /usr/local/bin for binary files , /usr/local/lib
for libraries and /usr/local/hss for configuration
files. |
| |
3. Compile the Home Subscriber
Server by using the command:
make |
| |
4. Install the compiled
Home Subscriber Server by using the command:
make install |
| |
Not: if you use different directories
for installation rather than default directories
then you should add you binary file path
to environment variable PATH and libraries
file to environment variable LD_LIBRARY_PATH. |
| |
Step 4: Configure and Start HSS |
| |
The configuration file hss_config.xml
is used to provide the configuration options
for running the HSS application. The default
path for installation of this configuration
file is /usr/local/share/hss
The name of application installed for executing
the HSS is 'hss'. In Linux the default path
for its installation is /usr/local/bin.
Use the following command for starting the
HSS.
$ hss |
|
 |
Online Charging System Installation |
 |
Guide for compilation
and installation of Online Charging Server(OCS). |
 |
Steps for installation |
| |
Step 1: Prerequisites |
| |
Hardware Requirements |
| |
A current Linux desktop class machine
with network access should be enough. |
| |
Libraries Requirements |
| |
- libamps (AMPS library)
- libxml2 (XML Libraray)
- libdiameter (Diameter Base Stack library)
- libdiamappcommon (Diameter application
common library) |
| |
Note: We assume that all these above libraries
available on your system before proceeding
to the further steps. |
| |
Step 2: Get Source Code |
| |
In order to download the source code of
Online Charging Server, you need to have
the subversion installed on the system to
be used. Download the Online Charging Server,
source code from its svn repository:
mkdir imsocs
svn co https://imsocs.svn.sourceforge.net/svnroot/imsocs
imsocs |
| |
Step 3: Compile and Install |
| |
1. To compile the source
code of Online Charging Server enter to
the imsocs directory..
cd imsocs |
| |
2. Execute the script
autogen.sh to generate makefiles from autotools.
In Linux, if the script is in your current
working directory, following command may
be used for executing the script: |
| |
./autogen.sh --prefix=/usr –datarootdir=/etc
For debugging with gdb, following command
may be used:
./autogen.sh --prefix=/usr --datarootdir=/etc
--enable-debug=yes
For release compilation, following command
may be used:
./autogen.sh --prefix=/usr --datarootdir=/etc
--enable-debug=no --enable-opt=8 |
| |
Note: If –prefix and –datarootdir
are not given then OCS will install to default
directories. Default directories for installation
are /usr/local/bin for binary files , /usr/local/lib
for libraries and /usr/local/onlinecharging
for configuration files. |
| |
3. Compile the Online
Charging Server by using the command:
make |
| |
4. Install the compiled
Online Charging Server by using the command:
make install |
| |
Not: if you use different directories
for installation rather than default directories
then you should add you binary file path
to environment variable PATH and libraries
file to environment variable LD_LIBRARY_PATH. |
| |
Step 4: Configure and Start OCS |
| |
The configuration file ocs_config.xml
is used to provide the configuration options
for running the OCS application. The default
path for installation of this configuration
file is /usr/local/share/onlinecharging
The name of application installed for executing
the OCS is 'onlinecharging'. In Linux the
default path for its installation is /usr/local/bin.
Use the following command for starting the
OCS.
$ onlinecharging |
|
 |
Offline Charging System Installation |
 |
Steps for installation |
| |
Step 1: Prerequisites |
| |
Hardware Requirements |
| |
A current Linux desktop class machine
with network access should be enough. |
| |
Libraries Requirements |
| |
- libamps (AMPS library)
- libxml2 (XML Libraray)
- libdiameter (Diameter Base Stack library)
- libdiamappcommon (Diameter application
common library) |
| |
Note: We assume that all these above libraries
available on your system before proceeding
to the further steps. |
| |
Step 2: Get Source Code |
| |
In order to download the source code of
Offline Charging Server, you need to have
the subversion installed on the system to
be used. Download the Offline Charging Server,
source code from its svn repository:
mkdir imscdf
svn co https://imscdf.svn.sourceforge.net/svnroot/imscdf
imscdf |
| |
Step 3: Compile and Install |
| |
1. To compile the source
code of Offline Charging Server enter to
the imscdf directory..
cd imscdf |
| |
2. Execute the script
autogen.sh to generate makefiles from autotools.
In Linux, if the script is in your current
working directory, following command may
be used for executing the script: |
| |
./autogen.sh --prefix=/usr –datarootdir=/etc
For debugging with gdb, following command
may be used:
./autogen.sh --prefix=/usr --datarootdir=/etc
--enable-debug=yes
For release compilation, following command
may be used:
./autogen.sh --prefix=/usr --datarootdir=/etc
--enable-debug=no --enable-opt=8 |
| |
Note: If –prefix and –datarootdir
are not given then CDF will install to default
directories. Default directories for installation
are /usr/local/bin for binary files , /usr/local/lib
for libraries and /usr/local/offlinecharging
for configuration files. |
| |
3. Compile the Offline
Charging Server by using the command:
make |
| |
4. Install the compiled
Offline Charging Server by using the command:
make install |
| |
Not: if you use different directories
for installation rather than default directories
then you should add you binary file path
to environment variable PATH and libraries
file to environment variable LD_LIBRARY_PATH. |
| |
Step 4: Configure and Start CDF |
| |
The configuration file offcs_config.xml
is used to provide the configuration options
for running the CDF application. The default
path for installation of this configuration
file is /usr/local/share/offlinecharging
The name of application installed for executing
the CDF is 'offlinecharging'. In Linux the
default path for its installation is /usr/local/bin.
Use the following command for starting the
CDF.
$ offlinecharging |
|
 |
Media Server Installation |
| |
Quick Install
Following is a quick overview of the steps
required to be accomplished for compiling
and installing the Media Server from its
source. If you are new to use this procedure,
skip over to Step 1 for a detailed description
of all these requirements.
mkdir imsmrf
svn co https://imsmrf.svn.sourceforge.net/svnroot/imsmrf
imsmrf
cd imsmrf/sourcecode
./autogen.sh --prefix=/usr --datarootdir=/etc
--enable-debug=no --enable-opt=8 --enable-snmp=yes
--enable-ms-trace=yes –enable-media-trace=yes
make
make instal |
 |
Steps for installation |
| |
Step 1: Prerequisites |
| |
Hardware Requirements |
| |
A current Linux desktop class machine
with network access should be enough. |
| |
Libraries Requirements |
| |
- Hardware Requirements
- A current Linux desktop class machine
with network access should be enough.
- Software Requirements
- ibsndfile: Library for Reading and Writing
Sound Files
- libutil: UTIL Library
- libamps: AMPS (Asynchronous Middleware
for Protocol Servers) Library
- libsipstack: SIP Stack Library
- libsdpparser: SDP Parsing Library
- libdnsresolver: DNS Resolver Library
- glib2: Glib Library
- libxml2: Library providing XML and HTML
support |
| |
Note: We assume that all these above libraries
available on your system before proceeding
to the further steps. |
| |
Step 2: Get Source Code |
| |
In order to download the source code of
Media Server, you need to have the subversion
installed on the system to be used. Download
the Media Server source code from its svn
repository:
mkdir imsmrf
svn co https://imsmrf.svn.sourceforge.net/svnroot/imsmrf
imsmrf |
| |
Step 3: Compile and Install |
| |
1. To compile the source
code of Media Server go to the sourcecode
folder.
cd imsmrf/sourcecode |
| |
2. Execute the script
autogen.sh to generate makefiles from autotools.
In Linux, if the script is in your current
working directory, following command may
be used for executing the script: |
| |
./autogen.sh --prefix=/usr –datarootdir=/etc
For debugging with gdb, following command
may be used:
./autogen.sh --prefix=/usr --datarootdir=/etc
--enable-debug=yes --enable-snmp=yes --enable-ms-trace=yes
–enable-media-trace=yes
For release compilation, following command
may be used:
./autogen.sh --prefix=/usr --datarootdir=/etc
--enable-debug=no --enable-opt=8 --enable-snmp=yes
--enable-ms-trace=yes –enable-media-trace=yes |
| |
3. If you want to change
the configuration options for Media Server,
you can give those options, while executing
the autogen.sh script or use the configure
command at this moment. For more information
about the available options in the configure
command, execute the command:
./configure --help |
| |
4. Compile the Media
Server by using the command:
make |
| |
5. Install the compiled
Media Server by using the command:
make install |
| |
Step 4: Configure and Start Media
Server |
| |
The configuration file config.xml is used
to provide the configuration options for
running the Media Server application. The
default path for installation of this configuration
file is /etc/ms-{version}.
The name of application installed for executing
the Media Server is 'ms'. In Linux the default
path for its installation is /usr/local/bin.
Use the following command for starting the
Media Server:
ms
Now the Media Server is ready to listen
the requests and respond accordingly. |
|
 |
Operation, Administration, Maintenance & Provisioning (OAM&P) System Installation |
 |
Overview |
| |
OAMP system consists of four core modules
1. WebManager
2. TrapServer
3. SNMPManager
4. OAMPServiceClient
5. Network Analyzer
1-WebManager
This is major module responsible for running
core SNMP and trap services along with web
based OAMP client application. It also contains
the OAMP web service which is accessed by
desktop application client i.e. Network
Analyzer. WebManager also publishes a JMS
queue for the clients e.g. Network Analyzer
to get instant notifications for received
traps etc.
2-Trap Server
Trap Server is a J2se based server module
capable of receiving all sorts of traps,
notifications and inform messages from registered
SNMP agents. WebManager contains a web service
built on top of this server module, which
make it possible to open its north bound
interface for clients e.g. Network Analyzer.
3-SNMP Manager
SNMP Manager is a J2SE based SNMP server
module responsible for interfacing with
agents to perform low level SNMP operations,
that include agent registration to SNMP
server, performing get/set requests on agents
etc. SNMP manager is also deployed with
WebManager and its northbound is open for
clients via OAMP web service.
4-OAMPServiceClient
TrapServiceClient is the JAX-RPC client
written for OAMP JAX-WS web service. This
client module is used by Network Analyzer
to communicate with Trap Server, registered
SNMP agents and to perform SNMP get/set
operations.
5-Network Analyzer
Network Analyzer is a J2SE based desktop
application client. It provides features
of a standard NMS e.g. SNMP GET/SET requests,
Trap Viewer, remote management of trap &
SNMP server etc.
|
 |
Quick Install |
| |
WebManager
Check out the latest ManagerApp NetBeans
project from SVN.
To build the application, simply use NetBeans
Build operation.
WebManager is dependent on various third
party libraries and following NetBeans
Project modules which should be
in class path of the current project.
In case “Resolve Reference Problem”
error is popped up from NetBeans then
adjust the libraries path in the project
properties which should be [Project Folder]/lib/[Library
Name] and checkout
following projects from SVN. Also adjust
the project properties to add these projects
in classpath if not so already.
1. SNMPManager
2. TrapServer
By default building WebManager project
module will build SNMPManager and TrapServer
projects. However if any source code changes
are performed on other projects, those
project should be built using NetBeans
standard build operation and then WebManager
project should be rebuild to reflect the
latest changes.
Before deployment following actions should
be considered as pre-requisite:
MYSQL DATABASE SETUP
• Install latest MySQL
distribution from MySQL along with latest
distribution of MySQL GUI Tools.
• Get the latest OAMP MySQL dump
from SVN.
• Use MySQL Administrator application
to create the schema named OAMP and then
restore the downloaded dump file.
APACHE TOMCAT SETUP
• Usually NetBeans ships with built-in
apache tomcat distribution, however if
it isn’t available you’ll
have to download (Apache Tomcat) and register
the server in NetBeans. Please refer to
NetBeans.org for more details on registering
external Tomcat server with the IDE. Server
registration is not only used to deploy
the application but also to build the
application without errors.
• After installing tomcat following
action must be performed to enable application
security:
• Open [CATALINA_HOME]/conf/Server.xml
and add comment out current realm. Then
copy and paste the following realm in
the server.xml.
<Realm className="org.apache.catalina.realm.JDBCRealm"
debug="99"
driverName="com.mysql.jdbc.Driver"
connectionURL="jdbc:mysql://localhost:3306/oamp?
user=root&password=rootroot"
userTable="tbl_users"
userNameCol="username"
userCredCol="password"
userRoleTable="tbl_user_roles"
roleNameCol="role_name"
/>
Note: Change the database connection
settings according to your own MySQL installation.
OPENJMS SETUP
Download and install OpenJMS and add a
topic named TrapsTopic using OpenJMS admin
application client. This topic is published
from OAMP web service and Network Analyzer
listens to this topic to get Trap notifications
and details instantly. For more information
on this visit OpenJMS Official Web Site.
WEBMANAGER CONFIGURATIONS SETTINGS
• Modify the file in sources:
[Project Folder]\src\java\org\ict\oamp\config\appconfig.xml
and change the settings to your own MySQL
installation settings.
After performing all above tasks, rebuild
the project once again. If you want to
deploy the application using NetBeans
then just simply right click on the project
node and click deploy. If all goes well
then application will be available on
[tomcat host URL:port /webmanager]. In
case some errors were encountered then
check Tomcat logs for details.
TRAP Server
Trap server project deploys as part of
the WebManager (ManagerApp project).
To build the application though please
reset the libraries path from the project
properties.
SNMP Manager
Like Trap Server project SNMP Manager
project also deploys with WebManager and
to build the project from NetBeans reset
the libraries path from Project Properties
menu option.
Note: for both projects lib directory
in project folders contain all the required
third party library jars.
Network Analyzer
To build
the project, checkout the latest AdvoSSNetworkAnalyzer
NetBeans project from SVN.
This project depends on various third
party library jars contained in lib folder
of the project home directory. Also this
project is dependent on OAMPServiceClient
project. It is advisable to checkout OAMPServiceClient
NetBeans project when working for Network
Analyzer application.
Network Analyzer is a desktop application
so no deployment is required. Just click
the NetBeans standard Run command to run
the project.
When client is running, click Tools>Settings
from menu bar. A dialog box will appear
in which provide the WebManager HTTP URL
according to your own installation. Leave
the service name unchanged.
|
 |
Steps for installation |
| |
a). Agent Installation |
| |
b). Manager Installation |
| |
Step 2: Get Source Code |
| |
|
| |
Step 3: Compile and Install |
| |
|
| |
Step 4: Configure and Start Media
Server |
| |
|
|
|
|
 |
|
 |
|