HTTP Redirect feature
HTTP redirection allows you to configure and use multiple servers to download files to IP phones
without the need to configure different values of HTTPSRVR (or TLSSRVR) for different groups of
phones.
You do not any special configuration on the phone. The phone responds automatically to HTTP
redirection requests from the HTTP server.
Using this feature you can:
• Spread the load across multiple servers. This feature allows local file servers to be used to
avoid bottlenecks caused by low bandwidth WAN links to remote locations.
• Use this capability for firmware upgrades, backup or restore and agent greeting download.
The feature supports the following HTTP Redirection response codes:
• 301 (Moved Permanently)
• 302 (Found)
• 303 (See Other)
• 307 (Moved Temporarily)
To be able to use this feature, you must configure the central file server to support HTTP
Redirection to an appropriate alternate server. See the
website for more information and
examples on configuring HTTP Redirection on IIS7 server.
Related links
on page 90
Backup and restore processing
IP deskphones support the HTTP client to back up and restore the user-specific data. The
deskphones support HTTP over TLS (HTTPS) for backup or restore. For backup, the deskphone
creates a file with all user-specific data if a backup file location is specified in system parameter
BRURI. The file is sent to the server by an HTTP PUT message, with appropriate success or a
failure confirmation.
Note:
IP phone H.323 v6.6.2 and later do not support HTTPS with MV_IPTEL or IIS 6. It is
recommended to upgrade to the current version of an HTTPS server that supports TLS 1.2.
The phone stores the authentication credentials and the realm in non-volatile memory that is not
overwritten if new phone software is downloaded. The default value of the credentials and the
realm is set to null at manufacture and at any other time that user-specific data is removed from
the deskphone.
For restore, the initiating process must supply only the backup file name. The file is requested
from the server by an HTTP GET message. If successful, the file is returned to the initiating
process. Otherwise a failure message is returned.
Administering your phone
May 2018
Installing and Administering Avaya J169/J179 IP Phone H.323
92