Cisco SPA901-UK Provisioning Guide - Page 36

Encrypting a File with the SPC, Generic

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

Creating Provisioning Scripts Encrypting a File with the SPC 2 Preencrypting configuration profiles offline with symmetric key encryption allows the use of HTTP for resyncing profiles. The provisioning server uses HTTPS to handle initial provisioning of IP Telephony devices after deployment. This feature reduces the load on the HTTPS server in large scale deployments. The final file name does not need to follow a specific format, but it is conventional to end the name with the .cfg extension to indicate that it is a configuration profile. Encrypting a File with the SPC The SPC can generate different types of configuration files by using different types of encryption. • Generic, non-targeted CFG file, without an explicit key • Targeted (--target option), also encrypts the CFG file without an explicit key, but uses the MAC address of the target IP Telephony device, and only that device can decode it • Explicit key-based encryption of the CFG file. Generic A generic, non-targeted CFG file is accepted as valid by any IP Telephony device that resyncs to it. The following command generates a basic CFG file: spc spa962.txt spa962.cfg This example compiles the plain-text spa962.txt file into the binary spa962.cfg file understood by the SPA962. The --scramble option performs encryption that does not require the explicit transmission of a key to the target device. It requires one randomizing argument. For example, spc --scramble SomeSecretPhrase spa962.txt spa962.cfg The resulting encrypted spa962.cfg is accepted as valid by any IP Telephony device that resyncs to it. Cisco Small Business IP Telephony Devices Provisioning Guide 35

  • 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
Encrypting a File with the SPC
Cisco Small Business IP Telephony Devices Provisioning Guide
35
2
Preencrypting configuration profiles offline with symmetric key encryption allows
the use of HTTP for resyncing profiles. The provisioning server uses HTTPS to
handle initial provisioning of IP Telephony devices after deployment. This feature
reduces the load on the HTTPS server in large scale deployments.
The final file name does not need to follow a specific format, but it is conventional
to end the name with the .cfg extension to indicate that it is a configuration profile.
Encrypting a File with the SPC
The SPC can generate different types of configuration files by using different
types of encryption.
•
Generic, non-targeted CFG file, without an explicit key
•
Targeted (
--target
option), also encrypts the CFG file without an explicit key,
but uses the MAC address of the target IP Telephony device, and only that
device can decode it
•
Explicit key-based encryption of the CFG file.
Generic
A generic, non-targeted CFG file is accepted as valid by any IP Telephony device
that resyncs to it. The following command generates a basic CFG file:
spc spa962.txt spa962.cfg
This example compiles the plain-text spa962.txt file into the binary spa962.cfg file
understood by the SPA962. The
--scramble
option
performs encryption that does
not require the explicit transmission of a key to the target device. It requires one
randomizing argument. For example,
spc --scramble SomeSecretPhrase spa962.txt spa962.cfg
The resulting encrypted spa962.cfg is accepted as valid by any IP Telephony
device that resyncs to it.