Aastra OpenCom 100 series, Руководство по монтажу и пусконаладке

Страница: 28 / 256

Update Notes
26
Update Notes
If you are already operating an OpenCom 100 communications system with an older
version of the software, the following notes will help you update to the release 10.
The release 10 is published at the same time for all members of the OpenCom 100 /
Aastra 800 product family. If you are operating multiple communications systems, for
example, on TC system networking, updating all communications systems at the
same time is a good idea to ensure optimal compatibility.
Update Licence
In contrast to earlier versions of the software for the OpenCom 100 communications
system you need an authorisation key for operating the release 10 software.
The update authorisation key is always valid for a specific software version (main
version and first sub-version, for example, “10.0”). You can use the update authori-
sation key you receive for updates up to this version. If you have, for example, pur-
chased an authorisation key for operating the release 10.3, alongside older versions,
you can also operate release 10.3, release 10.3.1, release 10.3.2, etc. When updating to
a higher version (in the example: release 10.4) you have to purchase an update
licence.
Note
If you do not enter the authorisation key, you can only conduct internal calls. In addi-
tion, an outgoing and an incoming external call is possible.
A licence for operating the software is included when you purchase a new
OpenCom 100 communications system. The licence for a newly purchased communi-
cations system authorises you to generate an authorisation key for newer versions of
the software within a time-frame determined by the licence. Please note that the pro-
duction date of the communications system is considered by the licence server for
generating these kinds of authorisation keys.
If you are operating an earlier version of the software and the update deadline deter-
mined by the licence has passed, you have to purchase an update licence.