AASTRA SIP-DECT (Release 2.1)- OM System Manual - Installation, Administration and Maintenance EN - Manual (Page 27)

SIP – DECT OM System Manual Release 2.1 4 Licensing
depl-1230/1.3 Page: 27 (196)
- messaging restricted to type “Info”, “Low”, “Normal” and “High” for all user (no
“Emergency” and “Locating Alert”), and
- no locating.
• up to two “normal” RFPs
- ◦ no messaging (except prio Info) and
- ◦ no locating.
On a small system it is prohibited to exceed the limits of license due configuration. Since
there is no activation or license file present, the software version is not checked. As the
system is not validated via RFPs and hence the latency timer does not play any role there
are no license violations possible at all.
When there are more than 2 RFPs configured while the PARK is changed only the first two
RFPs will stay in the configuration database. All other RFPs will be dropped silently.
4.4.2 Activated Built-in License (Medium System)
When the PARK is changed via the upload of an activation file, the OMM enters the activated
system state. In this state the OMM uses the following license features:
• up to 20 L-RFPs,
• messaging restricted to type “Info”, “Low”, “Normal” and “High” for all user (no
“Emergency” and “Locating Alert”), and
• no locating.
The OMM extracts the software version from the activation file and checks this against its
own software version. A lower software version within the activation file leads to a license
violation.
The OMM prevents a license violation due misconfiguration e.g. it is not possible to configure
a 21
st RFP in the system.
To obtain an activation file from the Aastra license server the MAC address of 3 RFPs must
be entered. These 3 validation RFPs are used to validate the activation.