Product Guide - A5000 R5.4 – Aastra X series
BPS0121AENAA01
Page 66/74
5.5.4.3 Optimising and checking memory space capacities
From R5.3, it is possible to display information about Compact Flash capacities and occupation. It is
also possible to optimise the capacities of certain memory spaces according to customers' needs.
The overall total of the directories has a maximum capacity that may not be exceeded. It corresponds
to the size of the Compact Flash minus a hundred MB of emergency space, reserved for the operating
system. The values entered in each directory while adapting the memory spaces also have a
maximum.
For most of the adjustable values, it is not possible to define a value below the disk space currently
used by the function using this directory.
Four exceptions do exist though, for which a maximum size below the current size may be indicated.
These functions are: trace, export debug, export backup and export ticket. In these cases, the
directory will be cleaned by deleting the oldest crashes, traces, backups or tickets.
Behaviour beyond the defined limitations
The MMC used to define space allocation only centralises the information, since all the functions do
not handle limit approach in the same way.
The behaviours are as follows:
•
Export Debug / Traces / Dump IP /Export backup / Export ticket: the oldest files are deleted.
•
Directory: no locking. SNMP traps and Warning messages are sent to the logbook.
•
IVR / Announcements / TFTP / Pictures: Loading of new scripts (or announcements) not
allowed
•
IVB: the message currently being left is completed; the next ones are not authorised.
•
FTP: the message currently being left is completed; the next ones are not authorised.
•
TMA: TMA checks the size after the file is uploaded and deletes it if the limit is exceeded.