Cisco SPA525G Administration Guide - Page 182

Configuring the SPA932 Attendant Console, SPA932 Parameter Notes

Page 182 highlights

9 Configuring the SPA932 Attendant Console Setting Up the SPA932 Attendant Console • sub-Use this keyword to identify the phones to be monitored). Its value and syntax is stationName@$PROXY, where system variable $PROXY contains the proxy server IP and port (e.g. 192.168.8.101:6060). NOTE: Unit/key LEDs will not light without the "sub" keyword. • usr or ext-Use one of these keywords to identify the specific users or extensions to be monitored. Its value and syntax is extensionNumber@$PROXY, where system variable $PROXY contains the proxy server IP and port (e.g. 192.168.8.101:6060). • nme (optional)- Use this field with the SPA9000 to identify any alias that has been assigned to the extension in the SPA9X2 phone configuration.The nme parameter indicates the extension name, which in this case is the same as the station name. • vid (optional)- All LEDs on the SPA932 use phone extensions that they are assigned to. By default, LEDs on the SPA932 are assigned to the first configured extension on the connected phone. You can optionally assign LEDs to any other phone extensions using vid=keyword. Use this field to identify the phone extension to use with the monitored list specified by the sub= keyword, when more than one BLF monitored list is configured on the SIP proxy server. The possible values are 1 to 6, corresponding to each of the six extensions available on the phone. Only use the vid= keyword in the first entry assigned to each phone extension. Subsequent keys will use the same extension. See "SPA932 Parameter Notes" section on page 183. 180 Cisco SPA and Wireless IP Phone Administration Guide

  • 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

Configuring the SPA932 Attendant Console
Setting Up the SPA932 Attendant Console
180
Cisco SPA and Wireless IP Phone Administration Guide
9
sub—Use this keyword to identify the phones to be monitored). Its value and
syntax is stationName@$PROXY, where system variable $PROXY contains the
proxy server IP and port (e.g. 192.168.8.101:6060).
usr or ext—Use one of these keywords to identify the specific users or
extensions to be monitored. Its value and syntax is extensionNumber@$PROXY,
where system variable $PROXY contains the proxy server IP and port (e.g.
192.168.8.101:6060).
nme (optional)— Use this field with the SPA9000 to identify any alias that has
been assigned to the extension in the SPA9X2 phone configuration.The nme
parameter indicates the extension name, which in this case is the same as the
station name.
vid (optional)— All LEDs on the SPA932 use phone extensions that they are
assigned to. By default, LEDs on the SPA932 are assigned to the first
configured extension on the connected phone. You can optionally assign LEDs
to any other phone extensions using vid=keyword. Use this field to identify the
phone extension to use with the monitored list specified by the sub= keyword,
when more than one BLF monitored list is configured on the SIP proxy server.
The possible values are 1 to 6, corresponding to each of the six extensions
available on the phone. Only use the vid= keyword in the first entry assigned to
each phone extension. Subsequent keys will use the same extension. See
“SPA932 Parameter Notes” section on page 183
.
NOTE:
Unit/key LEDs will not light without the
“sub” keyword.