Technical data

118

Web interface

You can use the Dialogic

Diva

web interface, accessible at port 10005, to gain access to Dialogic

Diva

Media

Board and system configuration, management interfaces of the Diva Media Boards and drivers, generate

statistics and reports, invoke troubleshooting procedures, create/view trace files and view/control the status of

the hardware.

To access the Diva web interface you need a web browser with Java Script support. For instance, to access the

Diva web interface at local host, type in the address window of you browser: http://127.0.0.1:10005.

The Dialogic

Diva

HTTP server is controlled by the internet daemon and is running only during the time a

request from the user is processed. This allows for saving system resources.

WEB server configuration

The Dialogic® Diva® HTTP server (diva_httpd) is started via xinetd.

The product installation procedure will modify /etc/services and add the "diva-cfg" entry to this file. Finally, the

installation procedure will inform the internet daemon (if any running) about changes in the configuration file.

Before you can access the Diva HTTP server you need to set a password in the

/usr/lib/opendiva/divas/httpd/login/login file. The valid password should contain not less than seven characters

and being accessible only by "root".

If you generally want to disable the Diva HTTP server, you can execute cd /usr/lib/opendiva/divas && sh

./cfg_util.sh 4 and the configuration procedure will remove the "diva- cfg" entry from the /etc/services file

and inform the internet daemon about changes in the configuration file.

You can use stunnel http://www.stunnel.org Universal SSL tunnel to allow secure access to the Dialogic

Diva

WEB server.

Note: The stunnel is designed to work as SSL encryption wrapper between remote clients and local (xinetd-

startable) or remove servers. The concept is to have non-SSL aware daemons running on your system. You can

easily set them up to communicate with clients over secure SSL channels.

To access the Diva HTTP server at a different port, you need to change the port number associated with the

"diva- cfg" entry in the /etc/services file and restart the internet daemon.