AudioCodes Media Pack MP-11x, Руководство пользователя

Страница: 398 / 650

User's Manual 398 Document #: LTRT-65432
MP-11x & MP-124
•
Upon receipt of an SNMP request from the provisioning server.
•
Upon receipt of a special SIP NOTIFY message from the provisioning server. The
NOTIFY message includes an Event header with the AudioCodes proprietary
value, "check-sync;reboot=false", as shown in the example below:
NOTIFY sip:<user>@<dsthost> SIP/2.0
To: sip:<user>@<dsthost>
From: sip:sipsak@<srchost>
CSeq: 10 NOTIFY
Call-ID: 1234@<srchost>
Event: check-sync;reboot=false
To enable this feature through the Web interface:
a. Open the Advanced Parameters page ( Configuration tab > VoIP menu >
SIP Definitions > Advanced Parameters ).
b. Under the Misc Parameters group, set the 'SIP Remote Reset' parameter to
Enable .
c. Click Submit .
33.2.4 Access Authentication with HTTP Server
You can configure the device to authenticate itself with the HTTP/S server. The device
authenticates itself by providing the HTTP/S server with its authentication username and
password. You can configure one of the following HTTP authentication schemes:

Basic Access Authentication: The device provides its username and password to
the HTTP server. The username and password is configured in the URL that you
define for downloading the file:
•
ini file:
AutoCmpFileUrl = 'https://<username>:<password>@<IP address
or domain name>/<file name>'

Digest Access Authentication: The authentication username and password is
negotiated between the device and HTTP/S server, using digest MD5 cryptographic
hashing. This method is safer than basic access authentication. The digest
authentication username and password are configured using the
AUPDDigestUsername and AUPDDigestPassword parameters, respectively.
33.2.5 Querying Provisioning Server for Updated Files
Each time the Automatic Update feature is triggered, for each file and its configured URL
the device does the following:
1. If you have configured the device to authenticate itself to the HTTP/S server for secure
access, the device sends the access authentication username and password to the
HTTP/S server (for more information, see ''Access Authentication with HTTP Server''
on page 398). If authentication succeeds, Step 2 occurs.
2. The device establishes an HTTP/S connection with the URL host (provisioning
server). If the connection is HTTPS, the device verifies the certificate of the
provisioning server, and presents its own certificate if requested by the server.
3. The device queries the provisioning server for the requested file by sending an HTTP
Get request. This request contains the HTTP User-Agent Header, which identifies the
device to the provisioning server. By default, the header includes the device's model
name, MAC address, and currently installed software and configuration versions.
Based on its own dynamic applications for logic decision making, the provisioning
server uses this information to check if it has relevant files available for the device and
determines which files must be downloaded (working in conjunction with the HTTP If-
Modified-Since header, described further on in this section).