Cisco SPA901-UK Provisioning Guide - Page 45

URL Syntax, If server is missing, then the tftp server specified through DHCP option 66 is

Get Cisco SPA901-UK - Small Business Pro PDF manuals and user guides
UPC - 745883570751
View all Cisco SPA901-UK manuals
Add to My Manuals
Save this manual to your list of manuals

Page 45 highlights

Creating Provisioning Scripts Proprietary Plain-Text Configuration File 2 URL Syntax Standard URL syntax is used to specify how to retrieve configuration files and firmware loads in Profile_Rule* and Upgrade_Rule parameters, respectively. The syntax is as follows: [ scheme:// ] [ server [:port]] filepath Where scheme is one of the following values: • tftp • http • https If scheme is omitted, tftp is assumed. The server can be a DNS-recognized host name or a numeric IP address. The port is the destination UDP or TCP port number. The filepath must begin with the root directory (/); it must be an absolute path. If server is missing, then the tftp server specified through DHCP (option 66) is used. If port is missing, then the standard port for the specified scheme is used (tftp uses UDP port 69, http uses TCP port 80, https uses TCP port 443). A filepath must be present. It need not necessarily refer to a static file, but can indicate dynamic content obtained through CGI. Macro expansion applies within URLs. The following are examples of valid URLs: /$MA.cfg /cisco/spa021025.bin 192.168.1.130/profiles/init.cfg tftp://prov.call.com/cpe/cisco$MA.cfg http://neptune.speak.net:8080/prov/$D/$E.cfg https://secure.me.com/profile?Linksys Cisco Small Business IP Telephony Devices Provisioning Guide 44

  • 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
Creating Provisioning Scripts
Proprietary Plain-Text Configuration File
Cisco Small Business IP Telephony Devices Provisioning Guide
44
2
URL Syntax
Standard URL syntax is used to specify how to retrieve configuration files and
firmware loads in Profile_Rule* and Upgrade_Rule parameters, respectively. The
syntax is as follows:
[ scheme:// ] [ server [:port]] filepath
Where scheme is one of the following values:
•
tftp
•
http
•
https
If scheme is omitted, tftp is assumed. The server can be a DNS-recognized host
name or a numeric IP address. The port is the destination UDP or TCP port number.
The filepath must begin with the root directory (/); it must be an absolute path.
If server is missing, then the tftp server specified through DHCP (option 66) is
used.
If port is missing, then the standard port for the specified scheme is used (tftp
uses UDP port 69, http uses TCP port 80, https uses TCP port 443).
A filepath must be present. It need not necessarily refer to a static file, but can
indicate dynamic content obtained through CGI.
Macro expansion applies within URLs. The following are examples of valid URLs:
/$MA.cfg
/cisco/spa021025.bin
192.168.1.130/profiles/init.cfg