Cisco SRP521W-K9-G1 Administration Guide - Page 113

Using a Mini-Certificate, Encrypted Master Salt 16B or 128b

Page 113 highlights

Configuring Voice Configuring Dial Plans 6 • Encrypted Master Salt (16B or 128b) Using a Mini-Certificate The Master Key and Master Salt are encrypted with the public key from the called party mini-certificate. The Master Key and Master Salt are used by both ends for deriving session keys to encrypt subsequent RTP packets. The called party then responds with a Callee Final message (which is an empty message). The Mini-Certificate (MC) contains the following information: • User Name (32B) • User ID or Phone Number (16B) • Expiration Date (12B) • Public Key (512b or 64B) • Signature (1024b or 512B) The MC has a 512-bit public key used for establishing secure calls. The administrator must provision each subscriber of the secure call service with an MC and the corresponding 512-bit private key. The MC is signed with a 1024-bit private key of the service provider, which acts as the Certificate Authority (CA) of the MC. The 1024-bit public key of the CA signing the MC must also be provisioned for each subscriber. The CA public key is used to verify the MC received from the other end. If the MC is invalid, the call will not switch to secure mode. The MC and the 1024-bit CA public key are concatenated and base64 encoded into the single parameter Mini Certificate. The 512-bit private key is base64 encoded into the SRTP Private Key parameter, which should be kept secret, like a password. (Mini Certificate and SRTP Private Key are configured in the Line pages (1-4). Because the secure call establishment relies on exchange of information embedded in message bodies of SIP INFO requests/responses, the service provider must ensure that the network infrastructure allows the SIP INFO messages to pass through with the message body unmodified. Cisco SRP500 Series Services Ready Platforms Administration Guide (SRP520 Models) 113

  • 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
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229

Configuring Voice
Configuring Dial Plans
Cisco SRP500 Series Services Ready Platforms Administration Guide (SRP520 Models)
113
6
Encrypted Master Salt (16B or 128b)
Using a Mini-Certificate
The Master Key and Master Salt are encrypted with the public key from the called
party mini-certificate. The Master Key and Master Salt are used by both ends for
deriving session keys to encrypt subsequent RTP packets. The called party then
responds with a Callee Final message (which is an empty message).
The Mini-Certificate (MC) contains the following information:
User Name (32B)
User ID or Phone Number (16B)
Expiration Date (12B)
Public Key (512b or 64B)
Signature (1024b or 512B)
The MC has a 512-bit public key used for establishing secure calls. The
administrator must provision each subscriber of the secure call service with an
MC and the corresponding 512-bit private key. The MC is signed with a 1024-bit
private key of the service provider, which acts as the Certificate Authority (CA) of
the MC. The 1024-bit public key of the CA signing the MC must also be
provisioned for each subscriber.
The CA public key is used to verify the MC received from the other end. If the MC
is invalid, the call will not switch to secure mode. The MC and the 1024-bit CA
public key are concatenated and base64 encoded into the single parameter Mini
Certificate. The 512-bit private key is base64 encoded into the SRTP Private Key
parameter, which should be kept secret, like a password. (Mini Certificate and
SRTP Private Key are configured in the Line pages (1-4).
Because the secure call establishment relies on exchange of information
embedded in message bodies of SIP INFO requests/responses, the service
provider must ensure that the network infrastructure allows the SIP INFO
messages to pass through with the message body unmodified.