Cisco CP-7942G Administration Guide - Page 28

Establishing and Identifying Protected Calls, Call Security Interactions and Restrictions

Page 28 highlights

Understanding Security Features for Cisco Unified IP Phones Chapter 1 An Overview of the Cisco Unified IP Phone Note There are interactions, restrictions, and limitations that affect the security level of the conference call depending on the security mode of the participant's phones and the availability of secure conference bridges. See Table 1-4 and Table 1-5 for information about these interactions. Establishing and Identifying Protected Calls A protected call is established when your phone, and the phone on the other end, is configured for protected calling. The other phone can be in the same Cisco IP network, or on a network outside the IP network. Protected calls can only be made between two phones. Conference calls and other multiple-line calls are not supported. A protected call is established using this process: 1. A user initiates the call from a protected phone (protected security mode). 2. The phone displays the icon (encrypted) on the phone screen. This icon indicates that the phone is configured for secure (encrypted) calls, but this does not mean that the other connected phone is also protected. 3. A security tone plays if the call is connected to another protected phone, indicating that both ends of the conversation are encrypted and protected. If the call is connected to a non-protected phone, then the secure tone is not played. Note Protected calling is supported for conversations between two phones. Some features, such as conference calling, shared lines, Extension Mobility, and Join Across Lines are not available when protected calling is configured. Call Security Interactions and Restrictions Cisco Unified Communications Manager checks the phone security status when conferences are established and changes the security indication for the conference or blocks the completion of the call to maintain integrity and also security in the system. Table 1-4 provides information about changes to call security levels when using Barge. Table 1-4 Call Security Interactions When Using Barge Initiator's Phone Security Level Feature Used Non-secure Barge Secure (encrypted) Barge Secure (authenticated) Barge Non-secure Barge Call Security Level Encrypted call Authenticated call Encrypted call Authenticated call Results of Action Call barged and identified as non-secure call Call barged and identified as authenticated call Call barged and identified as authenticated call Call barged and identified as non-secure call Table 1-5 provides information about changes to conference security levels depending on the initiator's phone security level, the security levels of participants, and the availability of secure conference bridges. 1-14 Cisco Unified IP Phone 7962G and 7942G Administration Guide for Cisco Unified Communications Manager 7.0 OL-15483-01

  • 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

1-14
Cisco Unified IP Phone 7962G and 7942G Administration Guide for Cisco Unified Communications Manager 7.0
OL-15483-01
Chapter 1
An Overview of the Cisco Unified IP Phone
Understanding Security Features for Cisco Unified IP Phones
Note
There are interactions, restrictions, and limitations that affect the security level of the conference call
depending on the security mode of the participant’s phones and the availability of secure conference
bridges. See
Table 1-4
and
Table 1-5
for information about these interactions.
Establishing and Identifying Protected Calls
A protected call is established when your phone, and the phone on the other end, is configured for
protected calling. The other phone can be in the same Cisco IP network, or on a network outside the IP
network. Protected calls can only be made between two phones. Conference calls and other multiple-line
calls are not supported.
A protected call is established using this process:
1.
A user initiates the call from a protected phone (protected security mode).
2.
The phone displays the
icon
(
encrypted) on the phone screen. This icon indicates that the phone
is configured for secure (encrypted) calls, but this does not mean that the other connected phone is
also protected.
3.
A security tone plays if the call is connected to another protected phone, indicating that both ends
of the conversation are encrypted and protected. If the call is connected to a non-protected phone,
then the secure tone is not played.
Note
Protected calling is supported for conversations between two phones. Some features, such as conference
calling, shared lines, Extension Mobility, and Join Across Lines are not available when protected calling
is configured.
Call Security Interactions and Restrictions
Cisco Unified Communications Manager checks the phone security status when conferences are
established and changes the security indication for the conference or blocks the completion of the call
to maintain integrity and also security in the system.
Table 1-4
provides information about changes to
call security levels when using Barge.
Table 1-5
provides information about changes to conference security levels depending on the initiator’s
phone security level, the security levels of participants, and the availability of secure conference bridges.
Table 1-4
Call Security Interactions When Using Barge
Initiator’s Phone
Security Level
Feature Used
Call Security Level
Results of Action
Non-secure
Barge
Encrypted call
Call barged and identified as non-secure call
Secure (encrypted)
Barge
Authenticated call
Call barged and identified as authenticated call
Secure
(authenticated)
Barge
Encrypted call
Call barged and identified as authenticated call
Non-secure
Barge
Authenticated call
Call barged and identified as non-secure call