Installation, Administration and Maintenance
Aastra Telecom
Page: 26 (47)
3.3 Configuring
the
OpenMobility Manager
The OMM runs on a designated RFP within a SIP-DECT deployment. The
OMM is designated via DHCP options or statically declared via the OM
Configurator tool. All other RFPs in the deployment are configured to point
back to the OMM in the deployment.
The OMM can be configured via HTTP. The OMM acts as a HTTP server
which binds to port 80 by default. If executed in host mode the port can be
configured via the command line interface.
The configuration data will be either read from the internal flash memory or
from a local file. A local file is only used if specified on the command line on a
PC host.
The configuration file is a human readable ASCII file. Changing the
configuration file outside the OMM is not permitted.
The configuration file can be downloaded and uploaded via the web
interface.
The service access is restricted to one active session at a time and is
password protected.
The browser used for service access has to be at least Microsoft Internet
Explorer 6.0 or Mozilla Firefox 1.0 and must have frame support, JavaScript
and cookies enabled.
3.3.1
Service Login procedure
The OMM allows only one user at a time to configure the system. A user
must authenticate with a user name and a password. Both strings are
checked case sensitive.
Default login is “omm” and password is “omm”. Administrators should
change the admin password on the System page after accessing the OMM.
