Avaya 16-601433 IP Phone User Manual


 
Optimizing the Server
40 Avaya IP Telephone File Server Application Reference Guide
In addition, you can automatically FTP this backup file to another central FTP server – which
could be anonymous or secure – and still avoid the administrative overhead of individual FTP
user administration.
To use automatic archive:
1. In the MV_Manager, go to the Advanced settings page.
2. Set the Customer FTP Backup flag to enabled.
3. Enter the Backup Directory for the remote FTP server.
4. Enter the customer server FTP UserName.
5. Enter the customer server FTP Password.
Also ensure that the primary file server address is entered and enabled and/or a secondary file
server address is enabled. Then choose the backup interval required.
Note:
Note: It is not normally expected that the option outlined in this and the previous section
would be active simultaneously, but can be within the administration limits
currently set. If so, some backup activity will be ignored if offered to servers not
set up to receive it.
To set up an alternative backup to a network storage unit, link the Backup directory to a network
share file server or use another utility program to mirror the data.
Improving TFTP Reliability
TFTP can be problematic in busy networks. Two options are available to improve TFTP file
download to 4600 Series IP Telephones:
Set the Maximum Client limit (0 = unlimited) in the INI file (applies to all server modes), to
control the number of individual telephones accessing the server, by storing a list of
individual IP addresses. The server itself can handle hundreds of connections in parallel.
The telephone, however, must download several files to complete an upgrade and may be
blocked by others accessing the server. Setting a limit like 100 ensures that individual
phones get more access to the server.
Assign a Client Session time in seconds with 0 = unlimited. Setting a session time
reserves a time slot on a server for that duration to allow file downloads to be completed.
This parameter effectively triggers when the Maximum Client count limit is reached
because until that point, all new requests from unique IP addresses are accepted.