SpectraLink NetLink Wireless Telephones Best Practices White Paper Wireless Telephone manual Tftp

Page 10

White Paper

3.0Network Infrastructure Considerations

3.1Physical Connections

3.2Assigning IP Addresses

3.3Software Updates Using

TFTP

The NetLink Wireless Telephone infrastructure components should connect to the facility’s local area network (LAN) using Ethernet switches, as opposed to Ethernet hubs, to provide adequate bandwidth and limit traffic collisions.

Ethernet switches should be configured to negotiate the connection requirements automatically. NetLink Telephony Gateways require 10Base-T, half-duplex transmission and the NetLink SVP Server utilizes 10/100Base-T, half or full-duplex transmissions and can be set to automatically negotiate or be configured to a specific transmission configuration.

Network wiring is an important component of any Ethernet based system and is subject to local and state building code specifications. Category 5, 4-pair 10/100Base-T Ethernet cabling should be used for NetLink Wireless Telephone infrastructure equipment.

NetLink Wireless Telephones operate as LAN client devices and therefore require IP addresses to work with the network. IP addresses can be assigned statically through the configuration menus on the handsets, or dynamically using standard DHCP protocol. For dynamic IP addressing, a DHCP server must be available.

NetLink Telephony Gateways and NetLink SVP Servers also require IP addresses and support either static or DHCP address assignment. When utilizing multiple NetLink SVP Servers with an IP telephony server, the master NetLink SVP server must be assigned a static IP address. When operating with an IP telephony server, the NetLink SVP Server also requires a range of IP addresses that covers the total number of Wireless Telephones supported by that NetLink SVP server. When a NetLink Wireless Telephone registers with the telephony server, one of the IP address within this range is used to communicate between the NetLink SVP Server and the telephony server. This IP address is used by the IP telephony server as an alias for the NetLink Wireless Telephone, 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 NetLink SVP Servers are used for added capacity, an exclusive range of IP addresses equivalent to the number of total users each NetLink SVP Server can support is required per NetLink SVP Server.

All NetLink components can be field-upgraded with new software to add features or capabilities and bug fixes. NetLink Wireless Telephones utilize a TFTP client to automatically download new code when available. NetLink Telephony Gateways have an integrated TFTP server to support Wireless Telephone and OAI Gateway software upgrades. For installations that do not use NetLink Telephony

Page 9

Page 9 Page 11
Image 10
Page 9 Page 11
Contents Deploying NetLink Wireless Telephones Wireless LAN Layout Considerations White Paper IntroductionWhite Paper Non-interfering, Overlapping 802.11b Channel Coverage Provides consistent coverage Access Point Bandwidth Considerations White Paper Telephone Usage Users Supported per Access Point White Paper Network Infrastructure Considerations TftpWhite Paper White Paper Quality of Service Data transmission rate of 2 Mb/s White Paper Security Security ConcernsUtilizing VLANs White Paper Deploying NetLink Wireless Telephones with a VPN White Paper NetLink Wireless Telephones and Subnets Conclusion Subnets and IP Telephony Server Interfaces
Top Page Image Contents