Linksys WIP310 SPA500 Series and WIP310 IP Phone Administration Guide - Page 122

SIP Initial INVITE and MWI Challenge, SIP Over TLS, Configuring Security, Quality

Page 122 highlights

Configuring Security, Quality, and Network Features Setting Security Features 5 SIP Initial INVITE and MWI Challenge SIP INVITE (initial) and MWI message in a session can be challenged by the endpoint. The purpose of this challenge is to restrict the SIP servers that are permitted to interact with the devices on the service provider network, which significantly increases the security of the VoIP network by preventing malicious attacks against the device. To configure SIP INVITE challenge: STEP 1 Log in to the web administration interface. STEP 2 Click Admin Login and advanced. STEP 3 Click Ext , then scroll to the SIP Settings section. STEP 4 In the Auth INVITE field, choose yes. STEP 5 Click Submit All Changes. SIP Over TLS Transport layer security (TLS) is a standard protocol for securing and authenticating communications over the Internet. SIP Over TLS eliminates the possibility of malicious activity by encrypting the SIP messages by the SIP proxy of the service provider and the end user. SIP Over TLS relies on the widely-deployed and standardized Transport Layer Security (TLS) protocol. Note that SIP Over TLS encrypts only the signaling messages and not the media. A separate secure protocol such as Secure Real-Time Transport Protocol (SRTP) (see below) can be used to encrypt voice packets. The TLS protocol has two layers: • TLS Record Protocol -- layered on top of a reliable transport protocol, such as SIP or TCH, it ensures that the connection is private by using symmetric data encryption and it ensures that the connection is reliable. • TLS Handshake Protocol -- allows authentication between the server and client and the negotiation of an encryption algorithm and cryptographic keys before the application protocol transmits or receives any data. TLS is application protocol-independent. Higher-level protocols such as SIP can layer on top of the TLS protocol transparently. Cisco SPA 500 Series and WIP310 IP Phone Administration Guide 111

  • 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
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300

Configuring Security, Quality, and Network Features
Setting Security Features
Cisco SPA 500 Series and WIP310 IP Phone Administration Guide
111
5
SIP Initial INVITE and MWI Challenge
SIP INVITE (initial) and MWI message in a session can be challenged by the
endpoint. The purpose of this challenge is to restrict the SIP servers that are
permitted to interact with the devices on the service provider network, which
significantly increases the security of the VoIP network by preventing malicious
attacks against the device.
To configure SIP INVITE challenge:
STEP 1
Log in to the web administration interface.
STEP
2
Click
Admin Login
and
advanced
.
STEP
3
Click
Ext
<number>, then scroll to the
SIP Settings
section.
STEP
4
In the Auth INVITE field, choose
yes
.
STEP
5
Click
Submit All Changes
.
SIP Over TLS
Transport layer security (TLS) is a standard protocol for securing and
authenticating communications over the Internet.
SIP Over TLS eliminates the possibility of malicious activity by encrypting the SIP
messages by the SIP proxy of the service provider and the end user. SIP Over TLS
relies on the widely-deployed and standardized Transport Layer Security (TLS)
protocol. Note that SIP Over TLS encrypts only the signaling messages and not
the media. A separate secure protocol such as Secure Real-Time Transport
Protocol (SRTP) (see below) can be used to encrypt voice packets.
The TLS protocol has two layers:
TLS Record Protocol -- layered on top of a reliable transport protocol, such
as SIP or TCH, it ensures that the connection is private by using symmetric
data encryption and it ensures that the connection is reliable.
TLS Handshake Protocol -- allows authentication between the server and
client and the negotiation of an encryption algorithm and cryptographic
keys before the application protocol transmits or receives any data.
TLS is application protocol-independent. Higher-level protocols such as SIP can
layer on top of the TLS protocol transparently.