Table of Contents
Advertisement
Provisioning Tutorial
Basic Resync
STEP 1
STEP 2
STEP 3
STEP 4
STEP 5
Cisco Small Business IP Telephony Devices Provisioning Guide
HTTP GET Resync
HTTP provides a more reliable resync mechanism than TFTP because HTTP
establishes a TCP connection and TFTP uses UDP that is less reliable. In addition,
HTTP servers offer improved filtering and logging features compared to TFTP
servers.
On the client side, using HTTP (with the GET method) simply means changing
TFTP to HTTP in the URL defined in the Profile_Rule parameter.
On the server side, the service provider must install and configure the HTTP
server. The IP Telephony Device does not require any special configuration setting
on the server to be able to resync using HTTP. If a standard web browser can
retrieve a profile from a particular server using HTTP, the IP Telephony Device
should be able to do so as well.
Exercise
Install an HTTP server on the local PC or other accessible host. (The open source
Apache server can be downloaded from the Internet.)
Copy the basic.txt configuration profile from the earlier exercises onto the virtual
root directory of the installed server.
Verify proper server installation (and file access of basic.txt) by accessing the
profile using a standard web browser.
Modify the Profile_Rule of the test IP Telephony Device to point to the HTTP server
in place of the TFTP server, so as to download its profile periodically.
For example, assuming the HTTP server is at 192. 1 68. 1 .300, enter the following
value:
http://192.168.1.200/basic.txt
Observe the syslog messages sent by the IP Telephony Device.
The periodic resyncs should now be obtaining the profile from the HTTP server.
Also, the server should be logging each request if connection logging is enabled in
the server configuration.
3
69
Advertisement
Table of Contents
