User guide

Dialogic

DSI Development Package for Linux - Release Notes Release 6.5.1

2.3 Diameter License Server Operation

Operation of licensing for the Dialogic

DSI Diameter Stack is slightly

different from other Dialogic

DSI Protocols in that is uses a License Server

which must be running prior to starting the Diameter Stack. This section

details operation of the license server:

First ensure that a valid run-time license is placed in a well know location

(outside the Development Package tree so that it is not overwritten when the

Development Package is updated). For example use /opt/DSI-LICENSES.

Before running gctload, startup the license server using the following

command:

/opt/DSI/LIC/lmgrd –local –c /opt/DSI-LICENSES

Now startup gctload in the normal way.

In order to add or change license files, after stopping gctload, it is necessary

to shutdown the license server. This is achieved using the following

command:

/opt/DSI/LIC/lmutil lmdown –c /opt/DSI-LICENSES

The user will be presented with a list of running license servers on the local

machine. The license server serving the “dialogic” vendor should be selected.

When starting the DMR binary it is necessary to specify the path to the run

time license on the command line using the –Lp option. The following is an

example of the appropriate system.txt syntax:

FORK_PROCESS dmr –Lp/opt/DSI-LICENSES

Note: Whilst the Dialogic

DSI Diameter Stack is the only licensed procotol

that requires a License Server, in the event that other Dialogic

DSI Protocol

Stacks are running (and using the ‘dialogic’ vendor key), these protocols will

also be licensed using the License Server whenever the license files are

located in the folder managed by the License Server.

2.4 DTU/DTR Java Example Diameter Applications

The DSI Diameter Stack is supported by two new example applications

written in Java:

DTU – Example Application for sending Diameter Update Location Requests.

DTR – Example Application for responding to Diameter Update Location

Requests using Update Location Answers.

Example configuration files are contained in the UPD/RUN directory.

The Java source code for the examples is contained in the UPD/SRC directory.

The existing makeall.sh shell script has been updated to build the applications

and the resultant Java jar files will be placed in the UPD/BIN directory.

Pre-built versions of the jar files are located in the JAVA directory.