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

Configuration File Compression, File Encryption, block chaining mode.

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

Creating Provisioning Scripts Open Format Configuration File 2 Configuration File Compression Optionally, the XML configuration profile can be compressed to reduce the network load on the provisioning server. The supported compression method is the gzip deflate algorithm (RFC1951). The gzip utility and a compression library that implements the same algorithm (zlib) are readily available from Internet sites. To identify when compression is applied, the IP Telephony Device expects the compressed file to contain a gzip compatible header, as generated by invoking the gzip utility on the original XML file. For example, if profile.xml is a valid profile, the file profile.xml.gz is also accepted. This example can be generated with either of the following commands: # first invocation, replaces original file with compressed file: gzip profile.xml # second invocation, leaves original file in place, produces new compressed file: cat profile.xml | gzip > profile.xml.gz The IP Telephony Device inspects the downloaded file header to determine the format of the file. The choice of file name is not significant and any convention that is convenient for the service provider can be used. File Encryption An XML configuration profile can be encrypted using symmetric key encryption, whether or not it is already compressed. The supported encryption algorithm is the American Encryption Standard (AES), using 256-bit keys, applied in cipher block chaining mode. NOTE Compression must precede encryption for the IP Telephony Device to recognize a compressed and encrypted XML profile. First generate the XML, then compress with gzip, and finally encrypt. The OpenSSL encryption tool, available for download from various Internet sites, can be used to perform the encryption. Note that support for 256-bit AES encryption may require recompilation of the tool (so as to enable the AES code). The firmware has been tested against version openssl-0.9.7c. Cisco Small Business IP Telephony Devices Provisioning Guide 36

  • 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
Creating Provisioning Scripts
Open Format Configuration File
Cisco Small Business IP Telephony Devices Provisioning Guide
36
2
Configuration File Compression
Optionally, the XML configuration profile can be compressed to reduce the
network load on the provisioning server. The supported compression method is
the gzip deflate algorithm (RFC1951). The gzip utility and a compression library
that implements the same algorithm (zlib) are readily available from Internet sites.
To identify when compression is applied, the IP Telephony Device expects the
compressed file to contain a gzip compatible header, as generated by invoking the
gzip utility on the original XML file.
For example, if profile.xml is a valid profile, the file profile.xml.gz is also accepted.
This example can be generated with either of the following commands:
# first invocation, replaces original file with compressed file:
gzip profile.xml
# second invocation, leaves original file in place, produces new compressed
file:
cat profile.xml | gzip > profile.xml.gz
The IP Telephony Device inspects the downloaded file header to determine the
format of the file. The choice of file name is not significant and any convention that
is convenient for the service provider can be used.
File Encryption
An XML configuration profile can be encrypted using symmetric key encryption,
whether or not it is already compressed. The supported encryption algorithm is
the American Encryption Standard (AES), using 256-bit keys, applied in cipher
block chaining mode.
NOTE
Compression must precede encryption for the IP Telephony Device to recognize a
compressed and encrypted XML profile. First generate the XML, then compress
with gzip, and finally encrypt.
The OpenSSL encryption tool, available for download from various Internet sites,
can be used to perform the encryption. Note that support for 256-bit AES
encryption may require recompilation of the tool (so as to enable the AES code).
The firmware has been tested against version openssl-0.9.7c.