Instruction Manual
Table Of Contents
- Preface
- Introducing Linksys IP Phones
- Getting Started
- Managing Linksys IP Phones
- Using the 900 Series LCD Display
- Localization
- Changing the Display Background (SPA942/962)
- Using the SPA932 (Sidecar) with the SPA962
- Configuring the Web Service
- RSS Newsfeeds (SPA962)
- Call Appearances and Extensions
- Line Key LEDs
- Using Call Features
- Selecting the Audio I/O Device and Line
- Making Calls
- Answering and Ending Calls
- Hold and Resume
- Call Waiting
- Speed Dialing
- Three-Way Conferencing
- Attended Call Transfer
- Blind Call Transfer
- Call Back
- Message Waiting Indication (MWI)
- Accessing Voicemail
- Muting Calls
- Shared Call Appearances
- Personal Directory
- Caller and Called Name Matching
- Dialing Assistance
- Supplementary Services
- Call Logs
- Audio Volume Adjustment
- Managing Ring Tones
- Configuring a Dial Plan
- System Administration
- Troubleshooting FAQ
- SPA900 Series LCD Command Reference
- Entering Names and Numbers into the Directory
- Entering Directory Names, Numbers and Ring Default
- 2 Speed Dial
- 3 Call History
- 4 Ring Tone
- 5 Preferences
- 6 Call Forward
- 7 Time/Date
- 8 Voice Mail
- 9 Network
- 9.1 DCHP
- 9.2 Current IP Address
- 9.3 Host Name
- 9.4 Domain
- 9.5 Current NetMask
- 9.6 Current Gateway
- 9.7 Enable Web Server
- 9.8 Non DHCP IP Address
- 9.9 Non DHCP Subnet Mask
- 9.10 Non DHCP Default Route
- 9.11 Non DHCP DNS 1
- 9.12 Non DHCP DNS 2
- 9.13 Non DHCP NTP Server 1
- 9.14 Non DHCP NTP Server 2
- 9.15 Multicast Address
- 9.16 Enable VLAN
- 9.17 VLAN ID
- 9.18 CDP
- 10 Product Info
- 11 Status
- 12 Reboot
- 13 Restart
- 14 Factory Reset
- 15 Custom Reset
- 16 Set Password
- 17 Set LCD Contrast
- 18 CallPark Status
- 19 Language (SPA922, 942, and 962)
- 20 GUI Properties (SPA962)
- 21 Web Service (SPA962)
- Linksys IP Phone Field Reference
- Acronyms
- Glossary
2-15
Linksys IP Phone Administrator Guide
Firmware Version 5.1
Chapter 2 Getting Started
Provisioning
Reboot URL
The Reboot URL lets you reboot the Linksys IP phone.
Note The Linksys IP phone reboots only when it is idle.
The Reboot URL is http://spa-ip-addr/admin/reboot.
Provisioning
This section describes the provisioning functionality of the Linksys IP phone. This section includes the
following topics:
• Provisioning Capabilities, page 2-15
• Configuration Profile, page 2-15
For detailed information about provisioning the Linksys IP phone, refer to the Linksys SPA Provisioning
Guide.
Provisioning Capabilities
The Linksys IP phone provides for secure provisioning and remote upgrade. Provisioning is achieved
through configuration profiles transferred to the device via TFTP, HTTP, or HTTPS.
The Linksys IP phone can be configured to automatically resync its internal configuration state to a
remote profile periodically and on power up. The automatic resyncs are controlled by configuring the
desired profile URL into the device.
The Linksys IP phone accepts profiles in XML format, or alternatively in a proprietary binary format,
which is generated by a profile compiler tool, SIP Profile Compiler (SPC), available from Linksys. The
Linksys IP phone supports up to 256-bit symmetric key encryption of profiles. For the initial transfer of
the profile encryption key (initial provisioning stage), the Linksys IP phone can receive a profile from
an encrypted channel (HTTPS with client authentication), or it can resync to a binary profile generated
by the Linksys-supplied profile compiler. In the latter case, the profile compiler can encrypt the profile
specifically for the target Linksys IP phone, without requiring an explicit key exchange.
Remote firmware upgrade is achieved via TFTP or HTTP (firmware upgrades using HTTPS are not
supported). Remote upgrades are controlled by configuring the desired firmware image URL into the
Linksys IP phone via a remote profile resync.
For further information about remote provisioning refer to the LVS SPA Provisioning Guide.
Configuration Profile
The Linksys IP phone configuration profile can be either an XML file or a binary file with a proprietary
format.
The XML file consists of a series of elements (one per configuration parameter), encapsulated within
the element tags <flat-profile> … </flat-profile>. The encapsulated elements specify values for
individual parameters. The following is an example of a valid XML profile:
<flat-profile>
<Admin_Passwd>some secret</Admin_Passwd>
<Upgrade_Enable>Yes</Upgrade_Enable>