Configuring the SPA932 Contents Introduction Document ID: 109117

Configuring the SPA932
Document ID: 109117
IntroductionHow do I configure the SPA932?Related Information
This article is one in a series to assist in the setup, troubleshooting, and maintenance of Cisco Small Business
products (formerly Linksys Business Series).
Q. How do I configure the SPA932?
The SPA932 is a 32−button attendant console for the SPA962. Each SPA932 unit provides 32 programmable
speed−dial or direct station select (DSS) buttons, Each lighted button indicates line status (idle, ringing, busy,
or null) using a busy lamp field (BLF). Incoming calls can be immediately transferred to the proper location
by pushing a button assigned to the extension on the SPA932. Two SPA932 units can be attached to a single
SPA962 to monitor a total of 64 separate lines.
Step 1:
Connect to the administration web server for the SPA962 to which the SPA932 is connected.
To use the SPA962 with an SPA932, it must be running Release 5.1.12 or later.
Step 2:
Click Admin/Advanced on the web administrator server page.
Step 3:
Click the SPA932 tab. If you do not see the SPA932 tab, check your firmware version, and
upgrade as necessary.
Step 4:
Select yes from the Unit 1 Enable pull−down selection list. Click the SPA932 tab. If you do
not see the SPA932 tab, check your firmware version, and upgrade as necessary.
If you have installed two SPA932 units, also select yes from the Unit 2 Enable pull−down
selection list.
Step 5:
Make sure that no is selected on the Test Mode Enable selection list. This option, which is
useful for testing the SPA932, is disabled by default. You cannot complete the software
configuration for the SPA932 if this option is enabled.
Step 6:
Complete the configuration required for whichever SIP proxy servers that you selected. You
need the following information to complete the SPA932 configuration:
♦ Server IP address (or hostname if supported)
♦ ?Phone and/or extension or user identifier
Step 7:
For each extension or user that you want to monitor using the SPA932, enter the
configuration script in
the appropriate field for each key.
Note: You can identify the user or extension number in the space provided next to each key
proceeding. This will help ensure that you enter the correct information in each field.
The configuration script is composed of the following keywords, followed by an equal sign
and separated by semicolons (;):
♦ fnc−defines which of the following functions are enabled for the specified key
(separate more than one function with a plus sign (+):
− blf−busy lamp field function used for monitoring line activity
− sd−speed dial function
− cp−call pickup (if supported by the SIP proxy server)
♦ ?sub−Use this keyword to identify the phones to be monitored.
♦ ?usr −Use this keyword to identify the specific users or extensions to be monitored.
♦ ?nme−(optional) Use this field with the SPA9000 to identify any alias that has been
assigned to the extension in the Linksys IP phone configuration.
♦ ?vid−(optional) Use this field to identify the SPA962 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 SPA962.
Note: You only need to use the vid= keyword in the first entry assigned to each SPA962
Subsequent keys will use the same extension.
Broadsoft Syntax
The following is an example entry for a Broadsoft server:
fnc=enabled_functions;[email protected];[email protected]
Replace the variables (in italics), as follows:
• enabled_functions with cp for call pickup, sd for speed dial, and blf for busy lamp field; separate
multiple functions in any order with a plus sign (+)
• ?blf_list_uri with the URI assigned to the BLF monitoring list on the Broadsoft server.
• ?broadsoft with the IP address or hostname of the Broadsoft server.
• ?dn with the number associated with the user account on the Monitored Users list.
For example, the following enables speed dialing and BLF monitoring for the user account reception, with a
BLF monitoring list URI of marketing, on a Broadsoft server with the IP address
fnc=sd+blf;[email protected];[email protected]
Note: The nme keyword is not used because the Broadsoft server automatically uses the assigned user
account name.
Step 8:
Repeat Step 6 for each extension or user that you are monitoring using the SPA932.
Step 9:
Click Submit All Changes at the bottom of the page.
Related Information
• Technical Support &Documentation − Cisco Systems
Updated: Dec 12, 2008
Document ID: 109117