Polycom H340 - Manual (Page 16)

16
© 2010 Polycom, Inc. All rights reserved. POLYCOM ® , the Polycom “Triangles” logo and the names and marks associated with Polycom’s products are trademarks and/or service marks of Polycom, Inc.
and are registered and/or common law marks in the United States and various other countries. All other trademarks are property of their respective owners. No portion hereof may be reproduced or
transmitted in any form or by any means for any purpose other than the recipient’s personal use without the express written permission of Polycom
Deploying SpectraLink e340, h340 and i640 Wireless Telephones BEST PRACTICES GUIDE
October 2010
3.2 Assigning IP Addresses
SpectraLink handsets operate as LAN client devices and therefore require IP addresses to operate in the network. IP
addresses can be assigned statically through the configuration menus on the handsets or dynamically using standard
DHCP protocol. The Handset Administration Tool (HAT) can be used to quickly load and change administration options
in the handsets, including static IP addresses. For dynamic IP addressing, a DHCP server is required.
Telephony Gateways and SVP Servers also require IP addresses that can be obtained by either static or DHCP
address assignment. It is always recommended to configure production infrastructure components with static IP
addresses to ensure consistent system access. When using one or more SVP Server(s), (see Section 4.1.3) the
Registration SVP Server must be assigned a static IP address. The Registration SVP Server is identified by DHCP
option 151 to the wireless telephones.
When operating with an IP telephony server (IP PBX), other than Avaya or Cisco, the SVP Server also requires a range
of IP addresses that cover the total number of wireless telephones supported by that SVP Server. That range of IP
addresses is known as First Alias IP Address/Last Alias IP Address in the SVP Server configuration menu. It is
important to note that for redundancy purposes it may be necessary to assign more IP addresses to an SVP’s Alias IP
range than what the SVP Server would normally support. Each SVP Server supports up to 500 handsets registered, but
this can be limited by the total number of Alias IP addresses configured in the SVP Server.
When a handset is using SVP and registers with the telephony server, one of the IP (Alias) addresses within this range
is used to communicate between the SVP Server and the telephony server. This IP address is used by the SVP Server
as an alias to communicate with the telephony server on the wireless telephone’s behalf, but will not be equivalent to
the handset’s IP address that was either statically assigned or obtained from the DHCP server. The range of alias IP
addresses must not be used within any DHCP range or cover the IP address used by any other device. In the case
where multiple SVP Servers are used for added capacity or redundancy, an exclusive range of IP addresses equivalent
to the number of total users each SVP Server supports is required per SVP Server. All alias IP addresses must be
within the same IP subnet as the IP address of the SVP Server they are assigned to.
3.3 Software Updates Using TFTP
All SpectraLink infrastructure components are field-upgradeable in terms of new software features and bug fixes.
SpectraLink handsets utilize a TFTP client to automatically download new code when available. Deployments using
Telephony Gateways to connect to a traditional PBX have an integrated TFTP server to support Wireless Telephone
and OAI Gateway software upgrades. While, the integrated TFTP server can be used to deliver software to the
e340/h340/i640 handsets, the Telephony Gateway cannot hold both handset type (e340/h340/i640 and 8020/8030)
software files due to memory allocation. A network TFTP server will simultaneously update multiple handsets, while
the Telephony Gateway can only update handsets one at a time. Therefore, in larger systems and newer deployments,
a separate TFTP server should be used rather than using the Telephony Gateway’s TFTP server capability. For
deployments with multiple Telephony Gateways it is recommended to utilize an external TFTP server to centralize the
management and delivery of software.
The SVP Server also requires a TFTP server for software updates. The Telephony Gateway cannot be used as a TFTP
server for the SVP Server code. Telephony Gateways receive software updates only through manual FTP updates. The
OAI Gateways can receive software updates via FTP as well but if software recovery becomes necessary the OAI will
utilize a TFTP server. The latest s oftware versions are available from Polycom’s web site.