Linksys SPA921 Cisco Small Business IP Telephony Devices Provisioning Guide - Page 73

Step 1, Step 2, Step 3, Step 4, Step 5

Get Linksys SPA921 - Cisco - IP Phone PDF manuals and user guides
UPC - 745883570799
View all Linksys SPA921 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 73 highlights

Provisioning Tutorial Basic Resync 3 HTTP GET Resync HTTP provides a more reliable resync mechanism than TFTP because HTTP establishes a TCP connection and TFTP uses UDP, which 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 STEP 1 Install an HTTP server on the local PC or other accessible host. The open source Apache server can be downloaded from the Internet. STEP 2 Copy the basic.txt configuration profile from the earlier exercises onto the virtual root directory of the installed server. STEP 3 Verify proper server installation (and file access of basic.txt) by accessing the profile using a standard web browser. STEP 4 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.168.1.300, enter the following value: http://192.168.1.200/basic.txt STEP 5 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. Cisco Small Business IP Telephony Devices Provisioning Guide 71

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
Provisioning Tutorial
Basic Resync
Cisco Small Business IP Telephony Devices Provisioning Guide
71
3
HTTP GET Resync
HTTP provides a more reliable resync mechanism than TFTP because HTTP
establishes a TCP connection and TFTP uses UDP, which 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
STEP 1
Install an HTTP server on the local PC or other accessible host.
The open source Apache server can be downloaded from the Internet.
STEP 2
Copy the basic.txt configuration profile from the earlier exercises onto the virtual
root
directory of the installed server.
STEP 3
Verify proper server installation (and file access of basic.txt) by accessing the
profile using a standard web browser.
STEP 4
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.168.1.300, enter the following
value:
STEP 5
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.