Cisco SPA901-UK Provisioning Guide - Page 76

Profile Formats, Profile Compression

Page 76 highlights

Provisioning Tutorial Profile Formats 3 Profile Formats This section demonstrates the generation of configuration profiles. To explain the functionality in this section, TFTP from a local PC is used as the resync method, although HTTP or HTTPS can be used for testing as well, if it is convenient. This section includes the following topics: • Profile Compression, page 75 • Profile Encryption, page 76 • Partitioned Profiles, page 77 • Parameter Name Aliases, page 78 • Proprietary Profile Format, page 79 Profile Compression A configuration profile in XML format can become quite large if all parameters are individually specified by the profile. To reduce the load on the provisioning server, the IP Telephony Device supports compression of the XML file, by using the deflate compression format supported by the gzip utility (RFC 1951). Exercise STEP 1 Install gzip on the local PC. STEP 2 Compress the basic.txt profile from earlier exercises, by invoking gzip from the command line: gzip basic.txt This generates the deflated file basic.txt.gz. STEP 3 Save the deflated file in the TFTP server virtual root directory. STEP 4 Modify the Profile_Rule on the test device to resync to the deflated file in place of the original XML file, as in the following example: tftp://192.168.1.200/basic.txt.gz STEP 5 Click Submit All Changes. STEP 6 Observe the syslog trace from the IP Telephony Device. Cisco Small Business IP Telephony Devices Provisioning Guide 75

  • 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

Provisioning Tutorial
Profile Formats
Cisco Small Business IP Telephony Devices Provisioning Guide
75
3
Profile Formats
This section demonstrates the generation of configuration profiles. To explain the
functionality in this section, TFTP from a local PC is used as the resync method,
although HTTP or HTTPS can be used for testing as well, if it is convenient. This
section includes the following topics:
Profile Compression, page 75
Profile Encryption, page 76
Partitioned Profiles, page 77
Parameter Name Aliases, page 78
Proprietary Profile Format, page 79
Profile Compression
A configuration profile in XML format can become quite large if all parameters are
individually specified by the profile. To reduce the load on the provisioning server,
the IP Telephony Device supports compression of the XML file, by using the
deflate compression format supported by the gzip utility (RFC 1951).
Exercise
STEP 1
Install gzip on the local PC.
STEP 2
Compress the basic.txt profile from earlier exercises, by invoking gzip from the
command line:
gzip basic.txt
This generates the deflated file basic.txt.gz.
STEP
3
Save the deflated file in the TFTP server virtual root directory.
STEP 4
Modify the Profile_Rule on the test device to resync to the deflated file in place of
the original XML file, as in the following example:
STEP
5
Click
Submit All Changes
.
STEP
6
Observe the syslog trace from the IP Telephony Device.