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
1-12
Linksys IP Phone Administrator Guide
Firmware Version 5.1
Chapter 1 Introducing Linksys IP Phones
Technology Background
SIP-NAT Interoperation
In the case of SIP, the addresses where messages/data should be sent to a Linksys IP phone system are
embedded in the SIP messages sent by the device. If the Linksys IP phone system is located behind a
NAT device, the private IP address assigned to it is not usable for communications with the SIP entities
outside the private network.
Note The ITSP might offer an outbound NAT-Aware proxy, which discovers the public IP address from the
remote endpoint and eliminates the need to modify the SIP message from the UAC.
The Linksys IP phone system must substitute the private IP address information with the proper external
IP address/port in the mapping chosen by the underlying NAT to communicate with a particular public
peer address/port. For this, the Linksys IP phone system must perform the following tasks:
• Discover the NAT mappings used to communicate with the peer.
This can be done with the help of an external device, such as a STUN server. A STUN server
responds to a special NAT-Mapping-Discovery request by sending back a message to the source IP
address/port of the request, where the message contains the source IP address/port of the original
request. The Linksys IP phone system can send this request when it first attempts to communicate
with a SIP entity over the Internet. It then stores the mapping discovery results returned by the
server.
• Communicate the NAT mapping information to the external SIP entities.
If the entity is a SIP Registrar, the information should be carried in the Contact header that
overwrites the private address/port information. If the entity is another SIP UA when establishing a
call, the information should be carried in the Contact header as well as in the SDP embedded in SIP
message bodies. The VIA header in outbound SIP requests might also need to be substituted with
the public address if the UAS relies on it to route back responses.
• Extend the discovered NAT mappings by sending keep-alive packets.
Because the mapping is alive only for a short period, the Linksys IP phone system continues to send
periodic keep-alive packets through the mapping to extend its validity as necessary.