Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning Release: 5.5 Document Revision: 03.04 www.nortel.com NN43001-504 .
Nortel Communication Server 1000 Release: 5.5 Publication: NN43001-504 Document status: Standard Document release date: 23 September 2008 Copyright © 2004–2008 Nortel Networks All Rights Reserved. Sourced in Canada LEGAL NOTICE While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED.
. Contents New in this release 9 Feature description 9 Other changes 10 Revision history 10 How to get help Getting Getting Getting Getting help help help help 11 from the Nortel Web site 11 over the phone from a Nortel Solutions Center 11 from a specialist by using an Express Routing Code 12 through a Nortel distributor or reseller 12 Overview Subject 13 Resources 14 Declaration of conformity 14 Shielded cable 15 Wireless telephone network description 15 Call Server 17 DHCP Server 18 DHCP option
WLAN Application Gateway 2246 23 Access Points 23 Handset switchover 24 Loss of signal 24 Planning 25 Challenges of integrating voice applications 26 High overhead of 802.
Placement guidelines for the WLAN IP Telephony Manager 2245 59 WLAN Application Gateway 2246 planning 66 WLAN IP Telephony Manager 2245 and WLAN Application Gateway 2246 installation requirements 67 IP address planning 67 IP addressing with DHCP 68 Planning worksheets 68 System information 71 Bandwidth management 71 Zones 71 Zones for wireless handsets 72 Call blocking 73 Codecs 73 Jitter buffer 74 RLR and SLR 74 RTCP 74 Gain adjustment 75 Programmable rings and tones 75 In/Out of Service tones 75 Virt
Power connection 91 WLAN Application Gateway 2246 installation 91 WLAN IP Telephony Manager 2245 configuration 93 Introduction 93 Functional description 94 Configuration tasks 95 Connect to the WLAN IP Telephony Manager 2245 95 Serial port connection 96 Telnet connection 96 Configure the network 97 Save the configuration 99 Configure the WLAN IP Telephony Manager 2245 100 Change the password 102 Administration and maintenance 105 Adding a WLAN IP Telephony Manager 2245 to the system 105 Checking in
Configuration problems 118 Duplex mismatch 118 No ring 118 Far-end echo 118 Dropped calls 119 Wireless handset status messages 119 Using Call Server overlay commands 133 TPS CLI commands 136 Determining alias IP addresses 138 Troubleshooting coverage issues 139 Before calling Nortel Technical Support 139 WLAN Application Gateway 2246 Introduction 141 System overview 142 Front panel 143 Third-party applications 144 Nurse-call systems 145 Installation 145 Configuring the WLAN Application Gateway 2246 IP ad
Free the serial port for administrative purposes 165 Troubleshooting WLAN IP Telephony installations 167 Site data-gathering tables 167 Product-specific configuration 169 Terminal proxy server 169 Handsets 170 WLAN IP Telephony Manager 2245 170 Quality of Service 170 WLAN specific configuration 171 Nortel switches 171 Cisco access points and switches 171 General WLAN configuration 176 DHCP server options 177 DHCP options 178 DHCP support for handsets that emulate the IP Phone 2004 180 Format of the IP
. New in this release The following sections detail what is new in WLAN IP Telephony Installation and Commissioning (NN43001-504) for CS 1000 Release 5.5. Feature description The self healing software enhancement eliminates the need for manual intervention if a WLAN Telephony Manager 2245 fails. The wireless handsets are configured with the IP address of a designated WLAN Telephony Manager 2245.
New in this release Other changes Revision history September 2008 Standard 03.04. This document is up-issued to support CS 1000 Release 5.5. This document contains an update to technical content for WLAN IP Telephony Manager 2245. September 2008 Standard 03.03. This document is up-issued to support CS 1000 Release 5.5. This document contains an update to technical content. February 2008 Standard 03.02. This document is up-issued to support CS 1000 Release 5.5.
. How to get help This chapter explains how to get help for Nortel products and services. Getting help from the Nortel Web site The best way to get technical support for Nortel products is from the Nortel Technical Support Web site: www.nortel.com/support This site provides access to software, documentation, bulletins, and tools to address issues with Nortel products.
How to get help Getting help from a specialist by using an Express Routing Code To access some Nortel Technical Solutions Centers, you can use an Express Routing Code (ERC) to quickly route your call to a specialist in your Nortel product or service. To locate the current ERC for your product or service, go to: www.nortel.
. Overview This chapter contains information about the following topics: • • • • • • • • • • “Subject” (page 13) • • • • “WLAN IP Telephony Manager 2245” (page 22) “Resources” (page 14) “Declaration of conformity” (page 14) “Shielded cable” (page 15) “Wireless telephone network description” (page 15) “Call Server” (page 17) “DHCP Server” (page 18) “TFTP Server” (page 18) “Firewall” (page 18) “WLAN Handset 2210/2211/2212 and WLAN Handset 6120/6140” (page 18) “WLAN Application Gateway 2246” (page 2
Overview • • • Nortel WLAN Handset 2212 Nortel WLAN Handset 6120 Nortel WLAN Handset 6140 Resources This section lists information sources that relate to this document.
Wireless telephone network description • • 15 EN 61000-3-2 Harmonic Current Emissions EN 61000-3-3 Flicker Emissions WARNING Changes or modifications to this equipment not approved by Nortel can cause this equipment to not comply with part 15 of the FCC rules and void the user’s authority to operate this equipment. WARNING This equipment contains no user-serviceable parts inside. Refer servicing to qualified service personnel. ATTENTION FCC CFT 47 Part 15.
Overview • Nortel WLAN Handset 2210/2211/2212, and Nortel WLAN Handset 6120/6140 • • • Nortel WLAN IP Telephony Manager 2245 Nortel WLAN Application Gateway 2246 (optional) Access Point (AP)—one or more as required by the site Figure 1 "Typical wireless telephone network configuration" (page 17) shows a typical wireless telephone network configuration.
Call Server Figure 1 Typical wireless telephone network configuration Call Server The Call Server can be the Call Server of any Nortel Communication Server (CS) 1000 system running CS 1000 Release 4.5 or later software for WLAN Handset 6120/6140 and or Succession 3.0 or later for WLAN Handset 2210/2211/2212. Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 03.04 Standard 23 September 2008 Copyright © 2004–2008 Nortel Networks .
Overview DHCP Server The existing DHCP Server can be on either side of the firewall, according to the site administrator’s preference. The DHCP server is optional if the wireless handsets and WLAN IP Telephony Manager 2245 are statically configured.
WLAN Handset 2210/2211/2212 and WLAN Handset 6120/6140 19 Employees carry wireless handsets to make and receive calls as they move throughout the building. The handsets are used only on the premises; they are not cellular phones. The handsets communicate with the CS 1000 and with the WLAN IP Telephony Manager 2245.
Overview Components The WLAN Handset Series 2200 offers the following components for local configuration: • Nortel WLAN Handset 2200 Series Configuration Cradle Software—software only • Nortel WLAN Handset 2200 Series Configuration Cradle—required hardware (serial cable included) The WLAN Handset 6100 Series offers the following components for local configuration: • Nortel WLAN Handset 6100 Series Administration Tool Software—software only • Nortel WLAN Handset 6100 Series Dual Slot Handset Cha
WLAN Handset 2210/2211/2212 and WLAN Handset 6120/6140 21 When WMM is used, all voice traffic originating from the wireless handset is assigned the WMM Voice Access Category, making it the highest priority application. If the wireless network supports WMM, the handsets enable WMM support automatically; otherwise, SpectraLink Voice Prioritization (SVP) is used. Wired Equivalent Privacy The handsets support Wired Equivalent Privacy (WEP) as defined by the 802.11a, b, and g specification.
Overview Application Interface (OAI) messaging protocol. The WLAN Application Gateway 2246 forwards the messages to the WLAN IP Telephony Manager, which encapsulates the message for delivery to the handset. If text-messaging functions are programmed, the handset can receive text messages. While you access text messages, the handset is in messaging mode. Incoming calls ring with the second call-ringing sound. Loud noise environments The handsets are designed to provide optimal voice quality.
Access Points 23 Table 1 WLAN Telephony Manager 2245 model numbers and capacities NTTQ60BAE5 10 simultaneous users NTTQ60CAE5 20 simultaneous users NTTQ60AAE5 80 simultaneous users (standard) WLAN Application Gateway 2246 The WLAN Application Gateway 2246 is an optional device that enables third-party applications to communicate directly with up to 10 000 wireless handsets. The WLAN Application Gateway 2246 is connected to the LAN Ethernet switch through an RJ-45CAT5 cable.
Overview Handset switchover If a user on an active call is moving about, the call switches from AP to AP in the subnet. This changeover is transparent to the user. Loss of signal If a wireless handset is out of range of all APs, it waits 20 seconds for a signal to return. If a signal is not reacquired within 20 seconds, the wireless handset loses connection to the Call Server and any calls are dropped.
. Planning This chapter contains information about the following topics: • • • • • • • • • • • • • “Challenges of integrating voice applications” (page 26) • • “WLAN Application Gateway 2246 planning” (page 66) • • “IP address planning” (page 67) “DHCP server planning” (page 28) “TFTP Server planning” (page 30) “Syslog Server planning” (page 32) “Access point planning” (page 32) “Network planning” (page 39) “Network recommendation” (page 39) “Network management” (page 40) “Zones” (page 47) “Othe
Planning Challenges of integrating voice applications The integration of voice applications on any data network causes some challenges. WLANs create a number of problems for voice, above and beyond those inherent to most data networks, such as: • • • • high overhead of 802.11 rate scaling and variable capacity power adjustments and variable capacity Quality of Service (QoS) High overhead of 802.11 Unlike many other 802.n standards, 802.
Challenges of integrating voice applications 27 because handsets are roaming around and rate scaling up and down as necessary. Handsets are moving, and as they do, the engineering target of call capacity becomes a moving target. Power adjustments and variable capacity A WLAN has dynamic mechanisms in place for adjusting channels, adjusting power, and filling coverage holes, all in response to changes in the Radio Frequency (RF) environment.
Planning of time before starting transmission. Because of this simple mechanism, a nonvoice device is as equally as likely to be allowed to transmit as a voice device is. For example, if a data device does seize the medium, it can send a 1500-byte frame at the lowest data rate (if it is far away from the AP), and further delay voice frames. In addition, several data devices contending for the medium can each, in turn, send large frames before the voice device gained access to the medium.
DHCP server planning 29 Server 1 information using the same format as the IP Phone 2004. If the Server 2 information is also present in the option, it is ignored. • DHCP Option 151. This option contains the IP address of the WLAN IP Telephony Manager 2245. If Option 151 is not configured, the wireless handset performs a DNS lookup of the name SLNKSVP2, if Options 6 (DNS Server) and 15 (Domain Name) are configured. • DHCP Option 152.
Planning Figure 2 Sample DHCP reservation showing assigned parameters Another use for the DHCP server is to make code upgrades to the handset easier. To prevent handsets from checking for code upgrades, assign the value of 255.255.255.255 for the TFTP server address. A problem can arise for handset users who travel. For example, the company employing the handset solution is a retailer with many stores.
TFTP Server planning 31 At an installation, which uses both the WLAN Handsets 2210/2211/2212 and the WLAN Handsets 6120/6140, the software files for both handset series must be installed and available on the TFTP server for the site. Only one TFTP server is needed in the network, and it need not be colocated with the handsets or the WLAN IP Telephony Manager 2245. There is a client-dependent aspect to how the handsets function with the TFTP server.
Planning The TFTP Server can be located anywhere on the network if the wireless handsets have the subnet mask and default IP gateway configured correctly. However, the wireless handset expects a response within two seconds to any TFTP request. Therefore, the TFTP Server must not be located, for example, at the other end of a slow WAN link. If too many wireless handsets are attempting to download new software simultaneously, the downloads can slow down or return error messages.
Access point planning 33 It is essential to know where to install the APs to provide effective coverage for wireless handset use. It is necessary to verify that coverage is available where it is needed. The first step is to define exactly where the coverage is needed, which requires a site survey. Recommendation A site survey must be performed before installing a wireless LAN. A site survey is also recommended when an existing network structure is modified or when physical changes are made to a site.
Planning Access point requirement considerations for b radio Each site is unique in its AP requirements. Consider the following points when determining how many APs are needed and where to place them: • Minimum Radio Signal Strength—All APs in the coverage area must receive a signal strength better than -70dBm. Measurement is made in negative dBm, which measure the amount of signal loss due to distance. Therefore, stronger signals are those with smaller values.
Access point planning 35 • Number of wireless handsets per AP—Estimate the number of wireless handsets and the anticipated call volume per AP area to ensure that the maximum number of calls per AP is not exceeded. For the maximum number of calls per AP for each supported manufacturer, see “Compatible Access Points” (page 215). • The data rates at which the wireless handsets operate—Higher data rates (such as 11Mbs) can only be sustained while well within the range of the AP.
Planning • • Which locations are likely to generate the largest amount of traffic? Where is future network expansion most likely? Mobility requirements Assess the mobility requirements: • How many wireless handset users are in motion continually, such as in a warehouse or hospital? • How many users work from different fixed locations throughout the site? Physical site study Perform a study of the physical site: • Study blueprints of the proposed site.
Access point planning 37 RF transmission testing After the APs are installed and configured, measure the strength of the Radio Frequency (RF) transmissions. Signal strength testing ensures that all usage areas have adequate coverage. This can be performed in two ways. 1. Use the handsets to determine AP signal strength using the Site Survey mode. 2. Use two portable computers with wireless hardware operating on a point-to-point basis.
Planning Figure 4 Sample AP placement diagram for b radio Solving coverage issues To resolve coverage issues, add and relocate APs. Solving overlap issues To resolve overlap issues, reassign channels to the APs or relocate the APs. Like channels require 15–20dBm separation. See Figure 5 "b radio assignment" (page 39). Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 03.04 Standard 23 September 2008 Copyright © 2004–2008 Nortel Networks .
Network recommendation 39 Figure 5 b radio assignment For more information about overlap, see the AP vendor documentation. Network planning You must ensure that all connections and interfaces for the IP Telephony network are configured as full-duplex. Duplex mismatches anywhere on the WLAN can cause the wireless IP Telephony system not to function normally.
Planning packet format allowing the access points to prioritize legitimate handset traffic. — Necessary traffic for instance DHCP must be allowed, while all other traffic is denied. Sample Access Control List The following is a sample ACL for a voice VLAN named VLAN120. set security acl ip SpectraLink permit udp 0.0.0.0 255.255.255.255 eq 68 0.0.0.0 255.255.255.255 eq 67 set security acl ip SpectraLink permit udp 0.0.0.0 255.255.255.255 eq 67 0.0.0.0 255.255.255.
Network management 41 Assessment through a WLAN site survey Technical support for VoWLAN is contingent on customers performing a site survey of the WLAN. Currently, Nortel recommends the use of the Ekahau Site Survey tool to verify the network deployment, although other site survey tools are acceptable. The Ekahau product runs on a PC and uses a WLAN network interface card (NIC) to collect data for analysis. The output of the tool is a number of robust visualizations of the network.
Planning Both location-solution types use a form of triangulation to compute the location of the device. Depending on the power level of the AP, it can sometimes hear devices that it cannot transmit to. These factors combined create the following two scenarios: • It is difficult to calibrate network-based solutions by using a laptop running the site survey, because APs can sometimes hear clients that cannot hear the AP.
Network management 43 noticeable when a voice call traverses such a link. Vivinet Assessor is extremely useful for identifying the symptoms of issues and fixing such problem areas in the network long before the customer places the first call. Monitoring and reporting with Enterprise Network Monitoring System Enterprise Network Monitoring System (ENMS) 10.5 is a cross-portfolio management platform for fault management, network visualization, and troubleshooting.
Planning Figure 6 ENMS 10.5 IPSM overview After you click on a specific IP Phone, the panel in the lower right portion of the screen displays details automatically, such as the CS 1000 system, with which the IP Phone is registered. You can then right-click on the phone to show a data network path trace graphically, as shown in Figure 7 "ENMS 10.5 IPSM convergence view" (page 45). For troubleshooting purposes, you can view a path trace to the signaling server or any other IP address.
Network management 45 Figure 7 ENMS 10.5 IPSM convergence view ENMS can provide down to physical slot port connectivity for the wired network. This topology data is extremely useful when shown in the Converged View of a Path Trace. You can set the display to refresh periodically to display the latest information about IP address changes.
Planning Call tracking is another feature that is not specifically related to QoS monitoring or fault monitoring, but that is important to solution manageability.
Zones 47 The alert from Vivinet AppManager activates Vivinet Diagnostics, which traces the path of the call, collects diagnostic information, and can perform root cause analysis. You can save the results for further analysis and action. For an example, see Figure 8 "NetiQ Vivinet Diagnostics example" (page 47).
Planning Other network design considerations WLAN Handsets 2210/2211/2212 are 802.11b-only devices and the WLAN Handsets 6120/6140 are 802.11b, 802.11g and 802.11a devices, which creates challenging choices for network deployments.
Other network design considerations 49 GHz channels, which is detrimental to voice devices. As a general policy, for large amounts of data, use 802.11a for data and 802.11b for voice, but leave 802.11g disabled. Alternately, if there are few 802.11b/g data devices and the WLAN is to be used primarily for voice, consider enabling 802.11g support. The goal is to carefully control the number of data devices that share radio resources with voice devices.
Planning Because of the complexity of this topic and the simulation data that is required, it is not possible to discuss tuning all three variables or even two variables at a time. An example of a light to medium office environment (mostly cube space but some walls) is provided instead. Example The channel reuse factor for 802.11b networks is fixed at three (three nonoverlapping channels in the 2.4 GHz range), corresponding to channels 1, 6, and 11.
Other network design considerations 51 Nortel does not recommend a closed system for VoWLAN installations that use more than one SSID, including converged data and voice WLANs. The reason is that the SSID serves a valuable purpose in roaming. When it is hidden by not being included in the beacon, roaming devices must attempt to try all closed system APs. This result can dramatically impact device handoff times.
Planning units may be required in that single subnet to support the number of calls; however, fewer WLAN IP Telephony Manager 2245 units are needed than in an equivalent multisubnet deployment. A second advantage is that external security measures are easier and less costly to implement. It is common practice to put a telephony WLAN behind a firewall for security reasons. This is because security features on handsets, particularly authentication capabilities, tend to lag behind the industry.
WLAN IP Telephony Manager 2245 planning 53 ATTENTION When multiple WLAN IP Telephony Manager 2245 units are used, all the WLAN IP Telephony Manager 2245 units must use a uniform media type. Do not use full-duplex on some and half-duplex on others, or 10BaseT on some and 100BaseT on others. Capacities The WLAN IP Telephony Manager 2245 is available in three models: • WLAN IP Telephony Manager 2245-80: Serves 500 powered-on handsets (80 simultaneous calls).
Planning WLAN IP Telephony Manager 2245 failure After the initial registration, if a WLAN IP Telephony Manager 2245 units fails, the following occurs: 1. The wireless handset drops active calls. 2. The wireless handset then re-registers with another WLAN IP Telephony Manager 2245 units. 3. The wireless handset returns to the active state. The recovery period is approximately 60 seconds.
WLAN IP Telephony Manager 2245 planning 55 Table 3 Multiple WLAN IP Telephony Manager 2245-80 capacities (cont’d.
Planning and packet loss must still be maintained. The Layer 3 design guidelines for having clients and WLAN IP Telephony Manager 2245 in different subnets does not mean that the WLAN IP Telephony Manager 2245 clustercan also be separated by routers. All the WLAN IP Telephony Manager 2245 units in the cluster must still be collocated in the same subnet. WLAN handsets The WLAN Handsets 2210/2211/2212/6120/6140 support both G.711 and G.729 codecs, but only using a 30 ms packetization rate.
WLAN IP Telephony Manager 2245 planning 57 There is an alternative control on the WLAN IP Telephony Manager 2245 that affects call capacity across APs. This control allows the WLAN IP Telephony Manager 2245 to fix the data rates that handsets use. The options are Automatic and 1 Mb/2 Mb only. When you choose the latter, maximum call capacity drops by slightly more than half if G.711 is in use, or by slightly more than two-thirds if G.729 is in use.
Planning call without interruption while moving within a WLAN Extended Service Set (ESS) RF signal coverage area of a WLAN. This means that the wireless handset hands over the WLAN RF signal from AP to AP without interrupting the data stream. Access points on the same subnet The handset can perform handover and roaming across SVP-compliant APs that reside on the same subnet as the wireless handset and WLAN IP Telephony Manager 2245 group.
Placement guidelines for the WLAN IP Telephony Manager 2245 59 Routers are typically configured with filters to prevent multicast traffic from flowing outside of specific domains. The wireless LAN can be placed on a separate VLAN or subnet to reduce the effects of broadcast and multicast traffic from devices in other network segments.
Planning Strict timing requirements dictate that the WLAN IP Telephony Manager 2245 must be placed as close as possible to the handsets, ideally in the same subnet. End-to-end jitter, delay and packet loss budget is a general VoIP best practice: • End-to-end delay is the time it takes for voice to go from the microphone of the sending telephone to the earpiece of the receiving telephone.
Placement guidelines for the WLAN IP Telephony Manager 2245 61 Figure 11 Jitter removal for packets going to the AP The following figures describe end-to-end delay for differing topologies: • For an example of an end-to-end delay for a LAN, see Figure 12 "Example 1: End-to-end delay and packet loss for a LAN" (page 62). • For an example of an end-to-end delay for a WAN, see Figure 13 "Example 2: End-to-end delay and packet loss for a WAN" (page 62).
Planning Figure 12 Example 1: End-to-end delay and packet loss for a LAN Figure 13 Example 2: End-to-end delay and packet loss for a WAN Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 03.04 Standard 23 September 2008 Copyright © 2004–2008 Nortel Networks .
Placement guidelines for the WLAN IP Telephony Manager 2245 63 Figure 14 Example 3: End-to-end delay and packet loss for a LAN to a PSTN Use the following tools to measure jitter, delay and packet loss: • • • Ping (to estimate delay and packet loss) Netmeeting (to generate RTP traffic) Ethernet (to capture and analyze the RTP traffic) For more information, see Figure 15 "Measuring jitter, delay and packet loss" (page 64) and Procedure 1 “Measuring jitter, delay, and packet loss” (page 64).
Planning Figure 15 Measuring jitter, delay and packet loss Procedure 1 Measuring jitter, delay, and packet loss Step Action 1 Connect PC 2 to LAN segment C. 2 Obtain the IP address of PC 2. 3 Start Netmeeting. 4 Connect PC 1 to the LAN on segment B. 5 Ping PC 2 and note the length of the round-trip delay. 6 Start Ethernet and capture packets on the correct interface. 7 Configure a filter for RTP packets. 8 Start a Netmeeting session on PC 2.
Placement guidelines for the WLAN IP Telephony Manager 2245 For an example of packet stream analysis for jitter and packet loss, see Figure 16 "Part 1: Example of analysis of a packet stream captured between segment A and B" (page 65) and Figure 17 "Part 2: Example of analysis of a packet stream captured between segment A and B" (page 66).
Planning Figure 17 Part 2: Example of analysis of a packet stream captured between segment A and B Usually the WLAN IP Telephony Manager 2245 is placed in the same subnet as WLAN handsets. This was previously a rule, but it is now just a recommendation. The WLAN IP Telephony Manager 2245 sometimes must be placed in a different subnet from the handsets. However, the rules for delay, jitter, and packet loss still apply.
IP address planning 67 WLAN IP Telephony Manager 2245 and WLAN Application Gateway 2246 installation requirements Locate the WLAN IP Telephony Manager 2245 and optional WLAN Application Gateway 2246 in a space with: • sufficient backboard mounting space and proximity to the LAN access device (switched Ethernet switch), Call Server, and power source • • • rack-mount unit (if using) • for the WLAN IP Telephony Manager 2245, a maximum distance of 325 feet (100 meters) from the Ethernet switch easy acc
Planning IP addressing with DHCP A pool of alias IP addresses must be configured on the WLAN IP Telephony Manager 2245 for the use of the wireless handsets. The use of a 22-bit subnet mask provides IP addresses for approximately 500 wireless handsets (1024 nodes). Allocate a pool of an equal number of IP addresses on the DHCP server for the wireless handsets. For example: 142.223.204.1 to 142.223.205.254 are allocated on the DHCP Server for the use of the wireless handsets. 142.223.206.1 to 142.223.207.
Planning worksheets Table 6 WLAN IP Telephony Manager 2245 planning worksheet (cont’d.) First alias IP address Last alias IP address Copy and complete the worksheet from Table 7 "Wireless handset planning worksheet" (page 69) to maintain a configuration record for the handsets. Table 7 Wireless handset planning worksheet Line * MAC Address * User Name Dialing Ext. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 *—required only if using the optional WLAN Application Gateway 2246.
Planning Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 03.04 Standard 23 September 2008 Copyright © 2004–2008 Nortel Networks .
. System information This chapter contains information about the following topics: • • • • • • • • • • • • • • • “Bandwidth management” (page 71) “Codecs” (page 73) “Jitter buffer” (page 74) “RLR and SLR” (page 74) “RTCP” (page 74) “Gain adjustment” (page 75) “Programmable rings and tones” (page 75) “Virtual Office” (page 75) “Branch Office” (page 75) “Survivable Remote Gateway” (page 76) “External Applications Server” (page 77) “End-to-end QoS” (page 77) “NAT” (page 77) “CS 1000 features” (page 84)
System information It is good practice to create a Bandwidth Management Zone for each WLAN IP Telephony Manager 2245 group (one group per subnet) in LD 117. Use the CHG ZDES command to name the zone with the IP address of the WLAN IP Telephony Manager 2245. => NEW ZONE => CHG ZDES where W indicates WLAN IP Telephony Manager 2245 and nnn.nnn.nnn.nnn is the IP address of the WLAN IP Telephony Manager 2245.
Codecs 73 Alias IP address Using the DN of a wireless handset, support personnel can obtain the current or most recent alias IP address used by a wireless handset when it checked in with a WLAN IP Telephony Manager 2245 group, and subsequently registered with the LTPS and Call Server.
System information Manager 2245 repackages the voice data to the correct packet size. The jitter buffer is always configured to 70 ms, and any UNIStim messages that configure the jitter buffer are ignored. ATTENTION IMPORTANT! If the wireless handset is registered to the same LTPS as the IP Phones, configure only the subset of codecs supported by both the wireless handsets and the IP Phones. If it is necessary for the IP Phone to use a codec that is not supported on the wireless handsets, such as G.
Branch Office 75 Gain adjustment The handsets ignore any UNIStim messages that adjust the loss plan of the wireless handset. Programmable rings and tones The wireless handsets support alerting cadences but only a single alerting frequency. The wireless handsets have the same call progress tone capability as the existing IP Phones 2004. In/Out of Service tones When the handset completes registration with the Call Server, it plays the In Service tone.
System information For the MG 1000B, if a wireless handset is registered to the Small System Controller (SSC) in Local mode, the local-mode license information appears on the wireless handset on the second line of the display. Since the maximum number of display characters on the wireless handset is 19 characters, the local-mode license information about the wireless handset display is truncated. See Table 8 "IP Phone 2004 and handset Local mode license display (MG 1000B only)" (page 76).
NAT 77 For more information about SRG, see Main Office Configuration Guide for Survivable Remote Gateway 50 (NN43001-307), . External Applications Server The External Applications Server (XAS) applications are not available on the handsets. End-to-end QoS End-to-end QoS, such as DiffServ, and Layer 2 QoS, such as 802.1 Qp, are not supported on the wireless telephone system. Any UNIStim commands sent to the wireless handsets attempting to adjust Layer 2 or Layer 3 QoS parameters are ignored.
System information To ensure correct deployment of the wireless handsets in this type of network configuration, most, if not all, of the WLAN equipment must reside on the private side of the NAT router. Network configurations The WLAN Handset 2212 has a VPN feature that enables an IPsec tunnel to a Nortel VPN Router, which is the only IPsec platform supported today. This feature alters some of the usual design recommendations for the telephony components, such as the WLAN IP Telephony Manager 2245.
NAT 79 Figure 18 VPN design over a Layer 2 network Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 03.04 Standard 23 September 2008 Copyright © 2004–2008 Nortel Networks .
System information Figure 19 VPN design over a Layer 3 network ATTENTION If the WLAN IP Telephony Manager 2245 is not in the same subnet as the handsets, the handsets do not work. ATTENTION In Figure 18 "VPN design over a Layer 2 network" (page 79), Figure 19 "VPN design over a Layer 3 network" (page 80), Figure 20 "Not recommended VoWLAN design" (page 81), and Figure 21 "Network configuration 3 with Full DHCP Server" (page 83), the clouds can represent a corporate intranet or the public Internet.
NAT 81 Connect the private interface of the VPN Router to the trusted side of the network. Make sure that client DHCP traffic flows through the VPN Router. If a network path around the VPN Router exists for the handsets to get DHCP assignments, the routing requirements on the VPN Router become much more complicated. To support such a scenario, you must configure static routes on the public interface as well as inject those routes into the routing protocol on the private interface.
System information not count the number of calls controlled by the other WLAN IP Telephony Manager. This creates a blind spot for each device, and it is possible to oversubscribe an AP by up to 2:1. The best solution to this problem is to have the WLAN Handsets 2210/2211 handsets use the same WLAN IP Telephony Manager as the WLAN Handset 2212 (VPN). This WLAN IP Telephony Manager is on the other (remote) side of the VPN Router from the handsets, that is, over a routed hop.
NAT 83 Figure 21 Network configuration 3 with Full DHCP Server TFTP Server location in a NAT environment The TFTP Server can be located on the public side of the network. In this case, the NAT router (and Wireless Security Switch if deployed) can have to be configured to allow WLAN Handsets access to the TFTP Server (allow traffic through on the required ports). This scenario is represented in Figure 21 "Network configuration 3 with Full DHCP Server" (page 83).
System information The WLAN Application Gateway 2246 can be located on the public side of the network as long as traffic is allowed on the correct ports. This scenario is represented in Figure 21 "Network configuration 3 with Full DHCP Server" (page 83). Alternatively, the WLAN Application Gateway 2246 can be placed on the private side of the network. CS 1000 features Nearly all CS 1000 features are supported on the wireless telephone system and WLAN Handsets 22x1.
IP Phone 2004 features 85 Table 11 IP Phone 2004 features Feature Supported on the WLAN handsets Keypad Yes Navigation keys Yes Description Up—Volume Up button Down—Volume Down button Left button— Right button— 6 feature keys Yes 4 soft-labelled keys Yes Display Partially IP phone 2004: 5x24 display Handsets: 4x19 display Message Waiting Indicator Yes Small envelope icon in the top right of the handset LCD display Branch Office Yes Survivable Remote Gateway Yes Virtual Office Parti
System information Table 11 IP Phone 2004 features (cont’d.) Feature Supported on the WLAN handsets Password Admin No Description The handsets can be password-protected, but this is different from the IP Phone 2004 password protection mechanism. The IP Phone 2004 password protection is supported, in addition to the handset password protection. KEM No Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 03.
. Installation This chapter contains information about the following topics: • • • • “Required materials” (page 87) “Preinstallation checklist” (page 88) “WLAN IP Telephony Manager 2245 installation tasks” (page 88) “WLAN Application Gateway 2246 installation” (page 91) Required materials The following equipment must be provided by the customer: • power outlet(s)—must accept the provided AC adapter, one for the WLAN IP Telephony Manager 2245 and one for the WLAN Application Gateway 2246 (if used).
Installation Supplied equipment Each WLAN IP Telephony Manager 2245 and WLAN Application Gateway 2246 is shipped with one Class II AC adapter with 24V DC, 1A output. Preinstallation checklist Ensure that the following requirements are met prior to installation: • The location chosen for the WLAN IP Telephony Manager 2245 and WLAN Application Gateway 2246 is adequate and power is available. • • • APs are SVP-compatible and coverage is adequate.
WLAN IP Telephony Manager 2245 installation tasks 89 Figure 22 WLAN IP Telephony Manager 2245 front panel • RS-232 port—the male DB-9 connector (DTE). Provides an RS-232 connection to a terminal, terminal emulator, or modem for system administration.
Installation Procedure 2 Wall-mounting the WLAN IP Telephony Manager 2245 Step Action 1 Use a 18-inch drill bit to drill four pilot holes, on 1.84 by 12.1 inch centers (approximately equivalent to 1-1316 inch by 12-18 inch). 2 Insert the #8 x 34-inch screws in the pilot holes and tighten, leaving a 18 to 14-inch gap from the wall. 3 Slide the WLAN IP Telephony Manager 2245 over the screws until the WLAN IP Telephony Manager 2245 drops into place in the keyhole openings of the flange.
WLAN Application Gateway 2246 installation 91 the correct minimum spacing between units. When mounting multiple units, stack the units in the rack as closely as possible. --End-- LAN connection Use an RJ-45 cable to connect the NETWORK port on the WLAN IP Telephony Manager 2245 to the connecting port on the Ethernet switch. Power connection Follow the steps in Procedure 4 “Connecting the power” (page 91) to connect the power to the WLAN IP Telephony Manager 2245.
Installation Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 03.04 Standard 23 September 2008 Copyright © 2004–2008 Nortel Networks .
. WLAN IP Telephony Manager 2245 configuration This chapter contains information about the following topics: • • • • • • “Introduction” (page 93) “Configuration tasks” (page 95) “Connect to the WLAN IP Telephony Manager 2245” (page 95) “Configure the network” (page 97) “Configure the WLAN IP Telephony Manager 2245” (page 100) “Change the password” (page 102) Introduction The WLAN IP Telephony Manager 2245 acts as a proxy for the wireless handsets and provides several services for them.
WLAN IP Telephony Manager 2245 configuration If the WLAN Telephony Manager 2245 fails, the wireless handset drops active calls, then re-registers with another WLAN IP Telephony Manager 2245 in their list. The wireless handsets return to active state after this registration period. This failure does not affect other wireless handsets registered on the other WLAN IP Telephony Manager 2245 units.
Connect to the WLAN IP Telephony Manager 2245 95 IP packets (the packets use a nonstandard protocol number), there can be no Layer 3 routing in the path. Therefore, the wireless handsets and WLAN IP Telephony Manager 2245 units must be in the same logical subnet. • RTP packets between the wireless telephone and the WLAN IP Telephony Manager 2245 always contain 30 ms worth of voice, no matter what is configured on the Call Server.
WLAN IP Telephony Manager 2245 configuration Nortel recommends that you perform the complete initial configuration after the serial connection is made. Serial port connection Follow the steps in Procedure 5 “Connecting to the WLAN IP Telephony Manager 2245 through a serial port” (page 96) to connect to the WLAN IP Telephony Manager 2245 through a serial port.
Configure the network 97 Follow the steps in Procedure 6 “Connecting to the WLAN IP Telephony Manager 2245 through Telnet” (page 97) to connect to the WLAN IP Telephony Manager 2245 through Telnet. Procedure 6 Connecting to the WLAN IP Telephony Manager 2245 through Telnet Step Action 1 Run a Telnet session to the IP address of the WLAN IP Telephony Manager 2245. 2 Enter the login and the password. The login name and password are case-sensitive. The NetLink SVP-II System menu appears.
WLAN IP Telephony Manager 2245 configuration Configure the following Network Configuration screen fields with information provided by the network administrator: • IP Address:—enter the complete IP address for the WLAN IP Telephony Manager 2245, including digits and periods. • Hostname:—optional field. Change the default hostname of this WLAN IP Telephony Manager 2245, if desired. Hostname is for identification purposes only. Do not include spaces. • • • Subnet mask—the subnet mask of the subnet.
Configure the network 99 • Maintenance Lock—indicates whether the WLAN IP Telephony Manager 2245 is in Maintenance Lock mode. • Disable Telnet Service—indicates whether a Telnet session can access the WLAN IP Telephony Manager 2245. The available options are: — Y—prevents a Telnet session from accessing the WLAN IP Telephony Manager 2245. — N—allows a Telnet session to access the WLAN IP Telephony Manager 2245.
WLAN IP Telephony Manager 2245 configuration If the WLAN IP Telephony Manager 2245 is in Maintenance Lock, a prompt appears asking if the configuration is to be saved. 2 Enter Y. 3 Alternatively, select the Reset option found in the SVP-II Configuration screen. Press Esc. See “Configure the WLAN IP Telephony Manager 2245” (page 100).
Configure the WLAN IP Telephony Manager 2245 101 ATTENTION All alias addresses must be on the same subnet as the WLAN IP Telephony Manager 2245. The IP addresses cannot be duplicated on other subnets or WLAN IP Telephony Manager 2245 units. There is no limit to the number of IP addresses that can be assigned, but the capacity of each WLAN IP Telephony Manager 2245 is 500 wireless handsets. • Ethernet link—select auto-negotiate unless there is a need to specify the link speed.
WLAN IP Telephony Manager 2245 configuration • Reset—if this option is selected, a prompt appears to reset the WLAN IP Telephony Manager 2245 when you exit the SVP-II Configuration screen. • Reset all SVP servers—if this option is selected, all WLAN IP Telephony Manager 2245 units on the subnet are reset. ATTENTION Resetting the WLAN IP Telephony Manager 2245 terminates any calls in progress. Change the password Nortel recommends that the default password be changed.
Change the password Step Action 1 Connect your terminal to the RS-232 port using a null-modem cable. 2 To communicate with the gateway, open a terminal emulation program, such as HyperTerminal. 3 Power cycle the SVP server. 4 After the log on prompt appears, within 60 seconds, enter the log on: 103 maint 5 At the slnk > prompt, enter the password: admin A confirmation message appears to inform you that the password is changed to admin.
WLAN IP Telephony Manager 2245 configuration Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 03.04 Standard 23 September 2008 Copyright © 2004–2008 Nortel Networks .
. Administration and maintenance This section contains information about the following topics: • “Adding a WLAN IP Telephony Manager 2245 to the system” (page 105) • “Removing a WLAN IP Telephony Manager 2245 from the system” (page 106) • • • “View software version” (page 106) “Software updates” (page 107) “Wireless handset download messages” (page 110) Adding a WLAN IP Telephony Manager 2245 to the system When a WLAN IP Telephony Manager 2245 is added to the system, the change is seamless and
Administration and maintenance Removing a WLAN IP Telephony Manager 2245 from the system When a WLAN IP Telephony Manager 2245 is removed from the system, wireless handsets using the WLAN IP Telephony Manager 2245 are affected. If the removal of the WLAN IP Telephony Manager 2245 is intentional, lock and idle it before removing the WLAN IP Telephony Manager 2245. When a WLAN IP Telephony Manager 2245 is removed from the system, the removal is detected within two seconds.
Software updates 107 Ensure that the Functional Code version matches the latest version available from Nortel: www.nortel.com/support --End-- For the WLAN Application Gateway 2246 For information about viewing the software versions for the optional WLAN Application Gateway 2246, see Appendix A “Software versions” (page 160).
Administration and maintenance Lock the system Always lock the WLAN IP Telephony Manager 2245 in the SVP-II Configuration screen before updating the software. Locking the WLAN IP Telephony Manager 2245 prevents new calls from starting. Reset the WLAN IP Telephony Manager 2245 after the update is complete. ATTENTION All calls in progress are terminated when the WLAN IP Telephony Manager 2245 is reset.
Software updates 109 From the Signaling Server or Voice Gateway Media Card, use the oam> or IPL> isetGet command to display a list of all currently registered wireless handsets that are running the old firmware version. Use this command on all LTPS Signaling Servers or Voice Gateway Media Cards that have IP Phones and wireless handsets currently registered: oam> isetGet fwvsn== Software update (version 97.071) for the WLAN Handsets 2210/2211/2212 To download version 97.
Administration and maintenance ATTENTION IMPORTANT! While the wireless handset is updating the software, the NO SVC message displays, and the wireless handset must not be powered off. For approximately 10 seconds, the wireless handset cannot be powered off. A warning message appears during that time. If the warning message is not displayed, the wireless handset can be powered off without damage. When the update is complete, the wireless handset displays the extension number, and is ready for use.
Wireless handset download messages 111 Table 14 Failure and recovery messages (cont’d.) Message Description TFTP Error (x):yy A failure occurred during the TFTP download of one of the files. (x) = the file number that was being downloaded. yy = an error code describing the particular failure. Possible error codes are: • • • 01 = TFTP Server did not find the requested file. • 81 = File put into memory did not CRC. The wireless handset attempts to download the file again. • FF = Timeout error.
Administration and maintenance Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 03.04 Standard 23 September 2008 Copyright © 2004–2008 Nortel Networks .
. Troubleshooting This chapter contains information about the following topics: • • • • • • “Troubleshooting the WLAN IP Telephony Manager 2245” (page 113) “Troubleshooting the WLAN Application Gateway 2246” (page 116) “Troubleshooting the handset” (page 116) “Dropped calls” (page 119) “Troubleshooting coverage issues” (page 139) “Before calling Nortel Technical Support” (page 139) Troubleshooting the WLAN IP Telephony Manager 2245 Use the System Status Menu screen to obtain information about syste
Troubleshooting Error Status screen The Error Status screen displays any alarms that indicate some system malfunction. Some of these alarms are easily remedied. Others require a call to Nortel Technical Support. From the System Status Menu screen, select Error Status. The Error Status screen displays active alarms on the WLAN IP Telephony Manager 2245. Table 15 "WLAN IP Telephony Manager 2245 active alarms and actions" (page 114) lists the alarms and the actions required to eliminate the alarm.
Troubleshooting the WLAN IP Telephony Manager 2245 115 • Max (maximum) calls—number of calls that can be supported by the WLAN IP Telephony Manager 2245 (depends on network speed). • RX—Ethernet statistics about the received signal during System Uptime.
Troubleshooting Software Version Numbers screen The Software Version Numbers screen provides information about the software version currently running on the WLAN IP Telephony Manager 2245. This information helps to determine if the most recent software version is running. This information assists Nortel Technical Support in troubleshooting software problems. Speed or duplex mismatch A duplex mismatch on the WLAN can cause the WLAN IP Telephony Manager 2245 to not operate properly.
Troubleshooting the handset 117 Context When troubleshooting a problem with a wireless handset, it is important to determine the context of when and where the problem occurred.
Troubleshooting Configuration problems Certain problems are associated with improper configuration of either the WLAN IP Telephony 2245, the optional WLAN Application Gateway 2246, or the wireless handset. Configuration problems are generally corrected by changing the configuration on the WLAN IP Telephony 2245, the WLAN Application Gateway 2246, or the wireless handset. There can also be incorrect programming of the APs.
Dropped calls 119 Dropped calls If calls are dropping, use the Site Survey mode of the wireless handset in the area where the problem occurred to determine if there is inadequate AP coverage in that area. Wireless handset status messages Wireless handset status messages provide information about the handset communication with the AP and Call Server. Table 16 "Wireless handset status messages" (page 119) summarizes the status messages, in alphabetical order.
Troubleshooting Table 16 Wireless handset status messages (cont’d.) Message Description Action Assoc Timeout xxxxxxxxxxxx x...x = AP MAC address Handset did not receive an association response from the AP; displays the MAC of the failing AP. Check the handset and AP security settings. Ensure that the AP is configured per the Configuration Note. Try another AP. Auth Failed xxxxxxxxxxxx x...x = AP MAC address Handset authentication is refused by the AP; displays the MAC of the failing AP.
Dropped calls 121 Table 16 Wireless handset status messages (cont’d.) Message Description Action Bad Network IP The value of the Remote Network IP address entered in the handset through the menus or the Configuration Cradle is missing or invalid. Enter a valid remote network IP address. Bad Network Mask The value of the network mask for the Remote Network entered in the handset through the menus or the Configuration Cradle is missing or invalid. Enter a valid network mask.
Troubleshooting Table 16 Wireless handset status messages (cont’d.) Message Description Action (battery icon), Low Battery message, and beep Battery Low Low battery In call: the battery icon displays and a soft beep is heard when the user is on the wireless handset and the battery charge is low. User has approximately 15 to 30 minutes of battery life left. Battery Low The Battery Low message indicates that the battery pack can be changed while the call is still in progress.
Dropped calls 123 Table 16 Wireless handset status messages (cont’d.) Message Description Action Battery Failure The battery pack is not functioning. Replace the battery pack with a new or confirmed battery pack. Only the approved battery pack works. Battery Failed Battery pack is damaged or incompatible with the handset. Replace the battery pack with a new or confirmed battery pack. Only the approved battery pack works. Can’t renew DHCP yyy.yyy.yyy.yyy y...
Troubleshooting Table 16 Wireless handset status messages (cont’d.) Message Description Action DHCP Error (1-5) DHCP Error 1 The wireless handset cannot locate a DHCP server. It tries every 4 seconds until a server is located. DHCP Error 2 The wireless handset has not received a response from the DHCP server to a request for an IP address. It retries until a DHCP server is found. DHCP Error 3 The server refuses to lease the wireless handset an IP address. It keeps trying.
Dropped calls 125 Table 16 Wireless handset status messages (cont’d.) Message Description Action DL Not On Sector The handset software download files are incorrect or corrupted. Download new software from the Nortel site. See “Software updates” (page 107). DO NOT POWER OFF The wireless handset is in a critical section of the software update. None. Do not remove the battery or attempt to power off the phone while this message is displayed.
Troubleshooting Table 16 Wireless handset status messages (cont’d.) Message Description Action Flash Config Error Handset internal configuration is corrupt. Perform the Restore Defaults operation from the administrator menu and reprogram, or reprogram using the Configuration Cradle. Initializing The wireless handset is performing a power-on initialization. None. This is informational only. Internal Err. # # The wireless handset has detected a fault from which it cannot recover.
Dropped calls 127 Table 16 Wireless handset status messages (cont’d.) Message Description Action No DHCP Server Handset is unable to contact the DHCP server. Check that DHCP is operational and connected to the WLAN or use Static IP configuration in the handset. No ESSID (For the WLAN Handsets 2210/2211/ 2212 only.) Attempted to run the site survey application without an ESSID configured. Let the handset come completely up. Statically configure an ESSID in the Admin menu.
Troubleshooting Table 16 Wireless handset status messages (cont’d.) Message No Net Found Description Out of Range • Incorrect WEP settings • Incorrect Security settings Try getting closer to an AP. Check to see if other handsets are working within the same range of an AP. If so, check the ESSID of the handset. Verify that all the WEP settings in the handset match those in the APs. Verify that all the Security setting in the AP.
Dropped calls 129 Table 16 Wireless handset status messages (cont’d.) Message Description Action determine a more specific cause. No PBX Response The wireless handset tried to send a message to the Call Server and failed to get a response. Verify the Call Server is operational and connected to the network. No Proposal The handset and the VPN server cannot agree on a set of configuration parameters.
Troubleshooting Table 16 Wireless handset status messages (cont’d.) Message Description Action No SVP Server No DNS Entry The handset is unable to perform DNS lookup for the WLAN IP Telephony Manager 2245; server had no entry for SVP Server. The network administrator must verify that a proper IP address is entered for the SVP Server DHCP option. No SVP Server No DNS IP The handset is unable to perform a DNS lookup for the WLAN IP Telephony Manager 2245; no IP address for DNS server.
Dropped calls 131 Table 16 Wireless handset status messages (cont’d.) Message Description Action Restart Command The wireless handset received a restart command from the Call Server. None. The wireless handset automatically restarts in a few seconds. RTP Open Failed The handset is unable to open the requested RTP or RTCP socket. Reboot the handset. If the error repeats, contact Nortel Technical Support. Select License The correct protocol has not been selected from the license set.
Troubleshooting Table 16 Wireless handset status messages (cont’d.) Message Description Action SVP Service Rej. The WLAN IP Telephony Manager 2245 has rejected a request from the wireless handset. The wireless handset restarts and attempts to reregister with the WLAN IP Telephony Manager 2245, which usually fixes the problem. Report this to the administrator if it keeps happening. System Busy yyy.yyy.yyy.yyy y...
Dropped calls 133 Table 16 Wireless handset status messages (cont’d.) Message Description Action Unknown xx:yy:zz A phrase is missing from your phintl file. Download new software from the Nortel site. See “Software updates” (page 107). Updating Code Wireless handset is downloading new software into memory. The number icons at the bottom of the display indicate which file number is currently being downloaded. This message also displays a progress bar.
Troubleshooting LD 32 IDU command For the handsets, the IDU command outputs the following specific information: • • • Release code: Rls: 6 (2210), Rls: 7 (2211) or Rls: 8 (2212) • The IP address is the alias IP address of the wireless handset that is provided by the WLAN IP Telephony Manager 2245. The MAC address is the MAC address of the wireless handset. In other words, the MAC address and the IP address are not related.
Dropped calls 135 LD 32 STAT command The wireless handsets are shown REGISTERED in the standby and active modes. In the following example, 61 0 is an IP Phone 2004 and 62 2 is a WLAN Handset 2211 in the standby mode. .stat 61 0 IDLE REGISTERED 00 .stat 62 2 IDLE REGISTERED 00 LD 117 Inventory command In the inventory report, the wireless handsets have a specific release code and NT code, similar to the IDU command output. In the following example, 61 0 is an IP Phone 2004 and 62 2 is a WLAN Handset 2211.
Troubleshooting TPS CLI commands The following sections describe TPS command line interface (CLI) commands. dsetShow command In the dsetShow command output, the handsets have a specific Hardware ID. The alias IP address is output, not the physical wireless handset IP address. In the following example, the IP Phone 2004 has an IP address of 192.168.10.100 and the WLAN Handset 2211 has an alias IP address of 192.168.10.200.
Dropped calls 137 isetCount and isetGet Use the alias IP address of the handsets in the expression string of the isetCount and isetGet commands, not the physical IP address. The following is an example of the isetGet output for the WLAN Handset 2211. ->isetGet "IP == 192.168.10.200" IP Address Type RegType State Up Time Set-TN Regd-TN HWID FWVsn ---------- ----- ------- ----- ------- ------- ---------------- --------192.168.10.200 i2004 Regular online 0 00:12:00 062-02 062-02 3000907a017e476607 097.
Troubleshooting IP Address Type RegType State Up Time Set-TN Regd-TN ---------- ---- ----- ---- ----- ----- ------192.168.10.200 i2004 Regular online 0 02:03:22 062-02 062-02 HWID FWVsn UNIStimVsn SrcPort DstPort ----------------- ----- ------- ----- -----3000907a017e476607 097.021 2.
Before calling Nortel Technical Support 139 For more information, see WLAN Handsets Fundamentals (NN43001-505), . Troubleshooting coverage issues Coverage issues are best resolved by adding and relocating APs as required. Overlap issues can be resolved by reassigning channels to the APs or by relocating the APs. For more information, see “Troubleshooting WLAN IP Telephony installations” (page 167).
Troubleshooting Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 03.04 Standard 23 September 2008 Copyright © 2004–2008 Nortel Networks .
. Appendix WLAN Application Gateway 2246 This appendix contains information about the following topics: • • • • • • • • • • “Introduction” (page 141) “Third-party applications” (page 144) “Installation” (page 145) “Configuration” (page 147) “Continuing configuration through Telnet” (page 153) “System status” (page 158) “Certification testing” (page 161) “Software” (page 161) “Planning Worksheet for Handsets” (page 164) “Free the serial port for administrative purposes” (page 165) Introduction With
WLAN Application Gateway 2246 Table 17 Model numbers with maximum number of users (cont’d.) Model number Maximum number of users NTTQ65CA 256 NTTQ65DA 512 NTTQ65EA 1024 NTTQ65FA 10000 In Figure 23 "WLAN Application Gateway 2246 connections" (page 142), a WLAN Application Gateway 2246 is connected to the site LAN through an Ethernet switch. The connection to the Application Server can be accomplished by a direct connection (RS-232) or through the Ethernet connection.
Introduction 143 Figure 24 Ethernet switch connections Front panel The WLAN Application Gateway 2246 models have similar front panel indicators. See Figure 25 "NTTQ65xx" (page 144). The NTTQ65xx is available in scaled increments to support up to 10 000 users. Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 03.04 Standard 23 September 2008 Copyright © 2004–2008 Nortel Networks .
WLAN Application Gateway 2246 Figure 25 NTTQ65xx • Network Link LEDs — (L)NKOK—lit when there is a network connection, (for example, LINK OK). — (A)CT—lit if there is system activity. — (C)OL—lit if there are network collisions. — (E)RROR—lit when the system has detected an error. • Status LEDs—indicate system messages and status. See Figure 25 "NTTQ65xx" (page 144).
Installation 145 Manufacturing: • • relay alarms to handsets from malfunctioning equipment enable managers to monitor production output Call Centers: • • review queue statistics receive alarms when metrics exceed thresholds Nurse-call systems In the health care market, the following nurse-call system manufacturers have applications known to be compatible with the WLAN Application Gateway 2246: • • • • • • • • • Dukane Corporation Emergin WirelessOffice Globestar Indyme Corporation Jeron Nurse Call
WLAN Application Gateway 2246 Procedure 12 Installing the WLAN Application Gateway 2246 Step Action 1 Place the WLAN Application Gateway 2246 on a shelf or convenient location. ATTENTION The WLAN Application Gateway 2246 is physically connected to the Ethernet switch and can be placed in any convenient location within 325 ft (100 m) of the switch. It can also be rack-mounted.
Configuration • • • 147 Parity: None Stop bits: 1 Flow control: None ATTENTION If you use Windows 2000, you must install Service Pack 2 to enable the use of HyperTerminal™. 3 Reset the system. The following appears on the terminal display: 04830130 4 Type the following command using the terminal or PC keyboard: 0255CC [CTRL M] [CTRL J] The command does not display on the screen as it is typed. The Login prompt appears.
WLAN Application Gateway 2246 Table 18 Administration console navigation To perform this function Press Select function from menu Arrow keys to highlight the selection. Press Enter. Display menu associated with highlighted field Enter. The Enter key displays the options associated with an item or allows an entry to be typed into the field. Exit screen Esc. Press the Esc key to return to the previous screen. Move one line up Move one line down Corresponding arrow key.
Configuration 149 Configuring the OAI Box Follow the steps in Procedure 14 “Configure the system type from the OAI Box Configuration option” (page 149) to configure the system type. Procedure 14 Configure the system type from the OAI Box Configuration option Step Action 1 From the NetLink OAI System screen, select OAI Box Configuration. This option does not appear unless Use NetLink GW with mogX00 is configured to Yes, which is the default.
WLAN Application Gateway 2246 • Ethernet Address—this is the MAC address of the WLAN Application Gateway 2246. This address is set at the factory. • IP Address—enter the complete IP address for the WLAN Application Gateway 2246, including digits and periods. Do not use DHCP. The IP address can be changed after initial configuration. • Hostname—the default host name can be changed. This is the name of the WLAN Application Gateway 2246 to which connection is made.
Configuration 151 current date and time from the SNTP server and tags syslog messages with the date. • IGMP Enabled—configure as Yes or No. IGMP is Internet Group Routing Protocol. IGMP Enabled allows the WLAN Application Gateway 2246 to join multicast groups. Enable this option if the network switch connected to the WLAN Application Gateway 2246 requires IGMP for multicast traffic to be forwarded.
WLAN Application Gateway 2246 Connect to the Application Server through an RS-232 port Some applications or systems can require an RS-232 connection between the Application Server and the WLAN Application Gateway 2246. If the applications have the ability to communicate messages over TCP/IP, and do not require a serial connection, the RS-232 cabling is not required. In that case, the LAN connection (port 5456) through the Ethernet switch can be used for the applications.
Continuing configuration through Telnet 153 Figure 27 WLAN Application Gateway 2246 connection to Application Server through the LAN Connect to Application Server through a modem Connect the modem to the Gateway serial port using a cable that conforms to RS-232 standards for DTE-to-DCE connections. See Figure 28 "WLAN Application Gateway 2246 connection to Application Server through a modem" (page 153).
WLAN Application Gateway 2246 The Telnet method of connection is used for routine maintenance of the system for both local and remote administration, depending on the network. Follow the steps in Procedure 17 “Connecting to a WLAN Application Gateway 2246 through Telnet” (page 154) to connect to a WLAN Application Gateway 2246 through Telnet.
Continuing configuration through Telnet 155 Procedure 18 Configuring a telephone line Step Action 1 From the NetLink OAI System screen, select Telephone Line Configuration and press Enter. 2 At the Telephone Line Configuration screen, use the arrow keys to navigate to the Name and Extension fields. 3 Enter the associated data for the wireless handsets. • MAC Address—the MAC address is printed on the sticker underneath the battery on the handset.
WLAN Application Gateway 2246 The Telephone Line Configuration screen displays. 2 Use the arrow keys to highlight the line to be deleted. 3 Press D to delete the handset information. 4 Press Y to accept changes. 5 Press Esc to return to the NetLink OAI System screen. --End-- Searching for a handset While in the Telephone Line Configuration or the Telephone Line Status screens, a search hot key is available.
Continuing configuration through Telnet 157 Feature programming The application function is accessed in the handset by pressing the FCN button plus a second button. The button used to access the application feature from the wireless handset is configured through the Feature Programming option. FCN 1-6 are hard-coded. If the application function is programmed to use FCN 1-6, the hard-coded function is overridden. Nortel recommends using 7, 8, or 9 for the application function.
WLAN Application Gateway 2246 Procedure 22 Setting or changing a password Step Action 1 From the NetLink OAI System screen, select Change Password and press Enter. The Change Password screen displays. An asterisk (*) indicates an item that is not applicable. 2 Enter the default password: admin 3 Follow the prompts to configure a new password. --End-- System status Use the steps in Procedure 23 “Viewing system status” (page 158) to view the status of the system.
System status 159 Application Gateway 2246. See “Telephone line status” (page 160). --End-- Network status The WLAN Application Gateway 2246 is connected to the Ethernet network, referred to as the LAN. The information about this connection displayed on the Network Status screen. The following information appears at the top of the screen: • Ethernet Address—MAC address of the WLAN Application Gateway 2246 (hexadecimal).
WLAN Application Gateway 2246 • Collisions—the number of times the Ethernet controller attempts to send a packet, but another device on the network transmitted at the same time, corrupting the transmission. • Collision Drops—the number of packets the Ethernet controller discards, because there were over sixteen collisions. After sixteen collisions, the Ethernet controller hardware discards the current packet and attempts to send the next packet in its buffer.
Software 161 The WLAN Application Gateway 2246 displays up to 16 telephone lines at one time. Move to the next group of 16 lines by using the arrow keys. Certification testing The following sections provide information about certification testing. WLAN Application Gateway 2246 certification After the WLAN Application Gateway 2246 is properly connected to the Application Server, LED 1 blinks.
WLAN Application Gateway 2246 Software updates After obtaining the software updates from Nortel, they must be transferred to the appropriate location in the LAN. This enables the corresponding system components to access and update their software. The FTP (File Transfer Protocol) method of transfer is used. In the WLAN Application Gateway 2246, the flash file system has the following files: Table 20 Software files File name Description config.bin OAI box configuration fnctla.
Software 163 FTP OR FTP . 3 Log on using the default administrator logon and password: admin admin 4 At the FTP prompt, type binary. 5 At the FTP prompt, rename and transfer the functional code file to the client server or WLAN Application Gateway 2246. put mog700.bin fnctla.bin where MOG700.bin is the downloaded file. fnctla.bin is the new name of the file. 6 After the file transfer is complete, use the Quit command to quit FTP.
WLAN Application Gateway 2246 Procedure 26 Loading software updates Step Action 1 Install a TFTP Server on a LAN-connected system. 2 Consult the server vendor’s documentation for information about TFTP. 3 After obtaining the software update from Nortel, load the software in a location that is accessible by the TFTP program. 4 To configure the host and start the download, from the NetLink OAI System screen, select the TFTP Server Download Configuration option.
Free the serial port for administrative purposes 165 Table 21 Handset Planning Worksheet (cont’d.) OAI Port MAC Address User Name Dialing Ext.
WLAN Application Gateway 2246 Step Action 1 Disconnect the terminal or PC from the serial port on the WLAN Application Gateway 2246. 2 Reconnect the communication cable between the WLAN Application Gateway 2246 and the Application Server. 3 Reset the system. --End-- Normal communication between the Application Server and WLAN Application Gateway 2246 commences. Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 03.
. Appendix Troubleshooting WLAN IP Telephony installations This appendix contains information required for troubleshooting and diagnosing of a WLAN IP Telephony installation, including the following topics: • • • • • • • “Site data-gathering tables” (page 167) • • • • • • “Troubleshooting” (page 189) • • “Network speech levels” (page 212) “Product-specific configuration” (page 169) “WLAN specific configuration” (page 171) “General WLAN configuration” (page 176) “DHCP server options” (page 177)
Troubleshooting WLAN IP Telephony installations Figure 29 System Information table Figure 30 System History table Figure 31 Customer Environment table Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 03.04 Standard 23 September 2008 Copyright © 2004–2008 Nortel Networks .
Product-specific configuration 169 Figure 32 Attachments: IP Sniffer Trace Captures table ATTENTION Take the wired traces at the mirrored port, to which the 2245 connects, on the Data Switch. Take the Wireless traces at the Access Points (AP), which are associated with the Wireless Telephony Sets (WTS), on the channels that are used. Figure 33 Attachments: Other Required table Product-specific configuration The following sections provide product-specific configuration information.
Troubleshooting WLAN IP Telephony installations 2210, 2211: firmware version 97.070 2245: load 174.027 • CS1000 Release 4.0: include the patches identified in the current product bulletin 2210, 2211, 2212: firmware version 97.070 2245: load 174.027 • CS1000 Release 4.5: include the patches identified in the current product bulletin 2210, 2211, 2212: firmware version 97.070 2245: load 174.027 • BCM 3.6: requires cumulative patch #3 2210, 2211: firmware version 97.070 • BCM 3.
WLAN specific configuration 171 DSCP tags determine packet priorities for QoS. Nortel recommends the following settings: WT (In call)—46 (default 4) WT (Standby)—40 (default 0) RTP—46 (default 4) PBX—40 (default 0) Inter-SVP2—0 (default) Other networks may use different settings—adjust as needed to match the network.
Troubleshooting WLAN IP Telephony installations Configure the following settings: • • • • dtim-interval 3 protocol 119 enabled less than 10 ms voice latency voice WMM enabled For more information, see the Cisco Aironet 1200 Series User Guide, . Nortel WLAN Security Switch 2270 and the Cisco 4400 Series WLAN Controller Alpha The 2270 and 4400 infrastructure has the following requirements: • • Turn off aggressive load balancing. • Configure 802.
WLAN specific configuration 173 • Verify that the AP session timeout is at least 1800 seconds. Nortel recommends that you configure the AP session timeout to 65 534 seconds. • Verify the following setting: 2230 AP DTIM = 3 • If there are multiple WLAN Security Switch 2270s installed, which are intended to participate in a single RF mobility group, the following criteria must be met: — The RF mobility group name must be same on all 2270s that belong to the RF mobility group.
Troubleshooting WLAN IP Telephony installations SILVER QoS to voice SSID. This is only a best-effort recommendation. If the voice traffic drops as a result, move back to GOLD QoS for voice. • The PTT feature does not work in 2.0 code if the WLAN Security Switch 2270 is configured in L2-LWAPP mode. This issue is resolved in the 2.2.x code. • There is a client-handoff feature in the advanced options in the command line interface (CLI) for release 3.0.107.0. For more information, go to www.cisco.com.
WLAN specific configuration 175 Table 22 1230 connected with 2950 and 2245 connected with 2950 (cont’d.) AP: 1230 2950 connected the APs 2950 connected to 2245 3 int fastethernet 0.
Troubleshooting WLAN IP Telephony installations Table 23 1230 connected with 3560 and 2245 connected with 6509 (cont’d.) AP:1230 3650 connected to APs 6509 connected to 2245 3 int fastethernet 0.240 encapsulation dot1Q 240 service-policy input wireless-SVPVoIP interface fastethernet 01 priority-queue out mls qos trust cos class-map match-all voice-sig match access-group 100 4 (for return path) dot11 priority-map avvid access-list 100 permit udp 172.23.0.016 eq 5000 172.23.0.
DHCP server options 177 • The signal Strength must be -70dB or greater to provide sufficient voice quality and proper operation. Note that -60dB or better is required for 11 MB data rate. • Wireless bridges are not permitted because they contribute to bottleneck delays. • The transmission power must be the same on all APs and match the power setting on the handsets. • AP bandwidth usage must be limited to 65 to 80% maximum for handset usage.
Troubleshooting WLAN IP Telephony installations DHCP options This section provides the IEEE definitions of the DHCP options. The term SHOULD, as used in this section, is to be interpreted as described in [RFC2119]. DHCP option 1: Subnet Mask. Length: 6 bytes This option specifies the client’s subnet mask. If both the Subnet Mask and the router option are specified in a DHCP reply, this option MUST be first.
DHCP options 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 IP address Code. 8 bits. Always set to 7. Length. 8 bits. 4+ in multiples of 4. IP address. 32 bits. One or more IPv4 addresses. RFCs: [RFC 2132] DHCP Options. Updated by: RFC 3942. DHCP option 15: 3+ bytes This option specifies the domain name that client should use when resolving hostnames via DNS. 00 01 02 03 04 05 06 07 Code 08 09 10 11 12 13 14 15 Length 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Domain name Code. 8 bits.
Troubleshooting WLAN IP Telephony installations DHCP support for handsets that emulate the IP Phone 2004 DHCP support in the IP Phone 2004 terminal requires a Class Identifier option with each DHCP Discovery and Request message. Additionally, the IP Phone 2004 checks for either a Vendor Specific option message with a specific, unique to Nortel IP Phone 2004 encapsulated subtype, or a site-specific DHCP option.
DHCP options 181 Format of the IP Phone 2004 Terminal DHCP Encapsulated Vendor Specific option The following definition describes the Nortel IP Phone 2004 specific, Encapsulated Vendor Specific option. This option must be encapsulated in a DHCP Vendor Specific option (Refer to RFC 1541 and RFC 1533) and returned by the DHCP server as part of each DHCP OFFER and ACK message for the IP Phone 2004 to accept these messages as valid.
Troubleshooting WLAN IP Telephony installations Notes: 1. aaa and rrr are ASCII-encoded decimal numbers with a range of 0 to 255. They identify the Action Code and Retry Count, respectively, for the associated TPS server. Internally, to the IP Phone 2004, they are stored as one octet (0x00..0xFF). These fields must be no longer than three digits. 2. The first server is always considered the primary, and the second server always considered secondary. 3.
DHCP options 183 option or a similarly encoded site-specific option must be present. Configure the DHCP server to send one or the other—but not both. WinNT implementations must use the Site Specific option. For more information, see “DHCP support for handsets that emulate the IP Phone 2004” (page 180). The format of the Terminal DHCP Site Specific option field is: Type, Length, Data.
Troubleshooting WLAN IP Telephony installations Notes: 3. If only one server is required, terminate the primary TPS sequence immediately with (.) instead of (;). Example: Norteli2004- A,iii.jjj.kkk.lll:ppppp,aaa,rrr 4. The valid options are one server or two servers (0, 3, or other numbers are not allowed). 5. The Action code values are: • 0 - reserved • • • 1 - UNIStim Hello (currently only this value is a valid choice) 2 to 254 - reserved 255 - reserved 6.
Quality of Service checklist for voice over WLAN applications 3. Enable SVP in the APs. SVP must be enabled in all APs that carry voice traffic. Not all AP vendors use SVP terminology. Cisco 350,1100, and 1200 series APs, for instance, refer to SVP compatibility as Protocol 119 support. The SpectraLink Web site provides AP settings used in SVP compatibility testing. To download the AP configuration manuals, go to www.spectralink.com. 4.
Troubleshooting WLAN IP Telephony installations RF basics and AP configuration The following points include the characteristics of a good RF environment that uses access point parameters for Nortel wireless telephone voice communications. Only channels 1, 6, and 11 are used. • • • Disable auto-channel select features and use fixed channels. • Configure areas where wireless telephone users can congregate with special care: Fix the transmit (TX) power setting and disable auto-power features.
Quality of Service checklist for voice over WLAN applications 187 — Nortel WLAN IP Telephony telephones support WEP, WPA-PSK, or WPA2-PSK. — Nortel recommends that you always use Open Authentication because it is more secure. — You can use a No WEP temporary SSID during troubleshooting so that you can gather wireless data with visibility into the SpectraLink Radio Protocol (SRP) data structures. After troubleshooting is complete, disable this temporary SSID.
Troubleshooting WLAN IP Telephony installations – Ideally, there is no routing between any network devices used for voice communication. – If routing is necessary, keep it in the back-end, between the SVP and PBX Call Server. Keep routing short and quick. There are other access point parameters necessary for the proper operation of voice communications. Often, these are not adjustable.
Troubleshooting 189 Troubleshooting Ensure that the WLAN IP Telephony and PBX product mix lines up with the compatibility matrix in the current Product Bulletin. If the site does not conform, it is not classified as a supported installation. Diagnosis flows The following sections provide information about the troubleshooting process for different types of issues. Call or signalling-related issues Signaling issues are not normally a result of an issue with the IP data network.
Troubleshooting WLAN IP Telephony installations Voice-quality issues The transport, or IP data network, are the most likely causes of voice-quality issues. In some circumstances, product issues (such as echo or Digital Signal Processor (DSP) errors) can cause problems with voice quality. The data network does not introduce echo into a conversation, but it can enhance existing echo. In a converged environment, voice competes with data traffic for bandwidth and processor time.
Handset error messages 191 Handset error messages Table 26 "Handset error messages" (page 191) shows error messages that appear on the liquid crystal diode (LCD) display of the wireless handsets. Table 26 Handset error messages Short Error code Description Action Assert Assert Errors The phone detects possible network errors and cannot recover without configuration modification. Verify the AP settings: data rates and fragmentation threshold.
Troubleshooting WLAN IP Telephony installations Table 26 Handset error messages (cont’d.) Short Error code Description Action PBX No PBX The phone is not communicating with the PBX. Check the cross connects, bridge clips, punch downs on demarcation block, amphenol tail. and PBX (see if the extension is built correctly). SVP No SVP Response The phone cannot communicate with the WLAN IP Telephony Manager 2245. Configure the Ethernet switch port and SVP to 100/full.
Diagnostic Tools 193 Table 27 Timing WLAN IP Telephony Manager 2245 to the AP Handset to the WLAN IP Telephony Manager 2245 Delay ≤ 100 ms Delay ≤ 100 ms Jitter ≤ 1 ms Jitter ≤ 30 ms Packet loss ≤ 2% Packet loss ≤ 2% The handset sends a handshake to the WLAN IP Telephony Manager 2245 every 30 seconds. If no response is received from the WLAN IP Telephony Manager 2245, the handset tries four more times, for a total of five attempts.
Troubleshooting WLAN IP Telephony installations 111111 -22 33 444 111111 -22 33 444 111111 -22 33 444 111111 -22 33 444 MyID Detl where 111111 = last three octets of the ESSID for the discovered AP 22 = signal strength of the specified AP 33 = channel number of the specified AP 4444 = DTIM interval configured for the specified AP MyID = soft key to toggle between single and any ESSID mode Detl = soft key to toggle between summary and detail screens Press the Detl soft key to view the details
Diagnostic Tools 195 P:pppp = pair-wise key security Any = soft key to toggle between single and multiple ESSID mode Smry = soft key to return to summary display Run Site Survey for the WLAN Handset 6120/6140 Site Survey is used to evaluate the facility coverage before certifying that an installation is complete. It can also be used at any time to evaluate coverage by testing signal strength, to gain information about an AP, and to scan an area to look for all APs, regardless of SSID.
Troubleshooting WLAN IP Telephony installations second has a signal strength of –48dBm, and is configured on channel 6 with a beacon interval of 200 ms. The third has a signal strength of –56dBm and is configured on channel 11 with a beacon interval of 100 ms. ab7bc8 -28 02 100 2ae578 -48 06 200 2ae596 -56 11 100 Any Detl When you select Any SSID mode, the summary display contains the first six characters of the APs SSID instead of the beacon interval, as shown in the following example.
Diagnostic Tools 197 rrrrr = rates supported—basic rates have a b following the rate + = more rates supported than displayed xxxx = WMM or UPSD if supported mmmm = security mode G:gggg = group key security P:pppp = pair-wise key security Any/MyID = soft key to toggle between single and multiple SSID mode Detl/Smry = soft key to toggle between the multiple AP display (summary) and the single AP display (detail) ATTENTION Numbers racing across the handset display indicate that AP information is being obtaine
Troubleshooting WLAN IP Telephony installations Diagnostics Screen 1 displays the following information: MissedRcvCnt nnnnn MissedXmtCnt nnnnn RxRetryCount nnnnn TxRetryCount nnnnn where MissedRcvCnt is the missed receive packet count since power up. MissedXmtCnt is the missed transmit packet count since power up. RxRetryCount is the receive retry count since power up. TxRetryCount is the transmit retry count since power up.
Diagnostic Tools 199 2 : mmmm ch - ss mnem 3 : mmmm ch - ss mnem where C is the AP currently in use. 1, 2, and 3 are the candidate APs. mmmm is the hexadecimal number comprised of the last two octets of the AP MAC address. ch is the channel number that the AP is configured on. ss is the signal strength for the AP in dBm. aid is the Association ID of the currently associated AP.
Troubleshooting WLAN IP Telephony installations Diagnostics Screen 5 displays the following information: Sec-ErrCount nnnnn LstSecErrSeq nnnnn where Sec-ErrCount is the security error count since power up. LstSecErrSeq is the MAC frame sequence number with the last security error. Syslog Mode A Syslog Server must be present on the network so that the handset can send log messages and have them saved. The Syslog Server IP address can be configured using DHCP or statically configured.
Diagnostic Tools 201 Table 28 Syslog message contents Syslog message Contents Failed Handoff (sent whenever the handset decided to hand off, but failed trying) Failed AP MAC Failed AP signal strength Current AP MAC Current AP signal strength Failure reason Successful Handoff New AP MAC New AP signal strength Old AP MAC Old AP signal strength Reason for handoff Other candidate APS: • • • Security Error MAC Signal strength Reason not used AP MAC AP signal strength Security mode Error details (mode dep
Troubleshooting WLAN IP Telephony installations Table 28 Syslog message contents (cont’d.
Diagnostic Tools 203 Table 28 Syslog message contents (cont’d.
Troubleshooting WLAN IP Telephony installations Table 28 Syslog message contents (cont’d.
Diagnostic Tools 205 Table 29 Syslog reason codes (cont’d.
Troubleshooting WLAN IP Telephony installations Table 29 Syslog reason codes (cont’d.) Reason code number Meaning 44 DELTS 45 QOS REQUIRED 46 CHANGED LISTEN INTERVAL Data capture Use the information presented in this section to begin capturing the correct data for analysis.
Data capture 207 Figure 34 DHCP scope Notes: 1. Before you begin the data capture, disable any encryption protocols so that the data can be analyzed. If this is not possible, you must supply the encryption keys. 2. Time sync the wired and wireless IP sniffer traces (to the second if possible) and note whatever difference is present. This is crucial for the captures to be analyzed as a whole event. 3. Include the Nortel case number and the capture date in the name of each file. 4.
Troubleshooting WLAN IP Telephony installations • • the TLAN and ELAN IPs for the Voice Gateway Media Cards (VGMC) • • a site survey • • • • • • • the encryption protocol a network diagram For more information, see “Network diagram” (page 208).
Data capture Configure the handset: • • Admin Menu > Diagnostics > Diagnostics mode on Admin Menu > Diagnostics > Syslog mode > full If a Syslog Server is not available, use a public domain Syslog—for more information, see the KIWI Syslog Daemon available from www.kiwisyslog.com. Signaling Server log capture Use the CLI to obtain a log capture from the Signaling Server. Procedure 28 Using the CLI to capture a Signaling Server log Step Action 1 Open a telnet session to the Signaling Server.
Troubleshooting WLAN IP Telephony installations Multiple times is better—copy and paste the following commands on the WLAN Security Switch 2270 CLI, rather than typing them individually. The screen begins scrolling with output as soon as you type the commands. • • • show run-config (from all WLAN Security Switch 2270s) show tech support show msglog The wired sniffer must sniff the Gig port of the WLAN Security Switch 2270. No capture filter is required; get everything.
Capture assert error messages with the Configuration Cradle 8 211 End debug; copy and paste the following commands on the CLI: debug disable-all show debug 9 Stop the wired and wireless captures. 10 Zip the captures and send them to Nortel. --End-- Scan for interference. MetaGeek Wi-Spy 2.4GHz Spectrum Analyzer is one low-cost option. For more information, go to www.metageek.net.
Troubleshooting WLAN IP Telephony installations 6 Call Nortel Technical Support and make arrangements to e-mail the file and error message from the display. --End-- Network speech levels Figure 35 "Network speech levels" (page 212) shows the network speech levels for digital sets—end-to-end performance. Figure 35 Network speech levels Reference documents Table 30 "References" (page 213) lists reference documents and related-reading for this appendix.
Reference documents 213 Table 30 References Source and type Title Revision Comments Nortel Product Bulletin WLAN Handset 2210/2211 January 2006 Up-issue Nortel NTP 553-3001-304 Standard 4.
Troubleshooting WLAN IP Telephony installations Table 30 References (cont’d.) Source and type Title Revision Comments SpectraLink White Paper NetLink Wireless Telephone WLAN Compatibility List PN: 72-9000-00-W See the current version at the SpectraLink Web site. NetLink Wireless Telephone WLAN Compatibility List IEEE [802.11] IEEE Std 802.11 Wireless LAN Medium Access Control and Physical Layer Specifications (not applicable) (not applicable) IEEE [802.11b] IEEE Std 802.
. Appendix Compatible Access Points The Nortel Voice over Wireless LAN solution is supported on VIEW-certified Access Points (APs). For a list of certified APs, go to the SpectraLink Web site www.spectralink. com. On the home page, select RESOURCES > Wi-Fi COMPATIBILITY. The SpectraLink Web site also contains configuration notes for the compatible APs. Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 03.
Compatible Access Points Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 03.04 Standard 23 September 2008 Copyright © 2004–2008 Nortel Networks .
. Index 10 Mbs 66 50 ms 74 70 ms 74 802.1 pq 77 802.
locking the WLAN IP Telephony Manager 2245 108 loss plan 75 LTPS 105 M multicast addresses 58 Multicasting 58 N network segments 59 No ring 118 node 74 Nortel WLAN Security Switch 171 Nortel WLAN Security Switch 2270 172 P packet loss 74 Planning worksheets 68 prevent new calls from starting 108 priority 77 Programmable rings and tones 75 Push-to-talk (PTT) 21, 58 Q Wi-Fi Protected Access (WPA) 21 Wi-Fi Protected Access2 (WPA2) 21 Wired Equivalent Privacy (WEP) 21 Send Loudness Rating (SLR) 74 sit
Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning Copyright © 2004–2008 Nortel Networks All Rights Reserved. Release: 5.5 Publication: NN43001-504 Document status: Standard Document revision: 03.04 Document release date: 23 September 2008 To provide feedback or to report a problem in this document, go to www.nortel.com/documentfeedback. www.nortel.
