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

URL Resolution, example, a profile subdirectory name might be supplied for each IP Telephony

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 72 highlights

Provisioning Tutorial Basic Resync 3 URL Resolution The profile URL can contain a provisioning server name instead of an explicit IP address. In this case, the IP Telephony Device performs a DNS lookup to resolve the name. A non-standard server port can be specified in the URL, using the standard syntax :port following the server name. Also, the configuration profile can be stored in a subdirectory of the server virtual root directory. Again, this is specified using standard URL notation. For example, the following is a valid Profile_Rule that requests the file spa962.cfg, in the server subdirectory /cisco/config, for the TFTP server running on host prov.telco.com, which listens for connection on port 6900. tftp://prov.telco.com:6900/cisco/config/spa962.cfg Again, macro expansion can be used anywhere in the URL. This can be convenient in organizing a directory of profiles on the server for the deployed devices. For example, a profile subdirectory name might be supplied for each IP Telephony Device in a dedicated general purpose parameter, with its value referred within a common profile rule via macro expansion. For example, GPP_B has the following definition: Dj6Lmp23Q The Profile_Rule has this value: tftp://prov.telco.com/cisco/$B/$MA.cfg Then, when resyncing, this IP Telephony Device (assuming a MAC address of 000e08012345) requests the profile at the following URL: tftp://prov.telco.com/cisco/Dj6Lmp23Q/000e08012345.cfg Cisco Small Business IP Telephony Devices Provisioning Guide 70

  • 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
70
3
URL Resolution
The profile URL can contain a provisioning server name instead of an explicit IP
address. In this case, the IP Telephony Device performs a DNS lookup to resolve
the name.
A non-standard server port can be specified in the URL, using the standard syntax
:port following the server name.
Also, the configuration profile can be stored in a subdirectory of the server virtual
root directory. Again, this is specified using standard URL notation.
For example, the following is a valid Profile_Rule that requests the file spa962.cfg,
in the server subdirectory /cisco/config, for the TFTP server running on host
prov.telco.com, which listens for connection on port 6900.
Again, macro expansion can be used anywhere in the URL. This can be convenient
in organizing a directory of profiles on the server for the deployed devices. For
example, a profile subdirectory name might be supplied for each IP Telephony
Device in a dedicated general purpose parameter, with its value referred within a
common profile rule via macro expansion.
For example, GPP_B has the following definition:
Dj6Lmp23Q
The Profile_Rule has this value:
Then, when resyncing, this IP Telephony Device (assuming a MAC address of
000e08012345) requests the profile at the following URL: