Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 .
Document status: Standard Document version: 01.02 Document date: 15 June 2007 Copyright © 2004-2007, Nortel Networks All Rights Reserved. Sourced in Canada The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specified in this document.
Revision history June 2007 Standard 01.02. This document is up-issued to reflect a change in the revision history. May 2007 Standard 01.01. This document is issued to support Nortel Communication Server 1000 Release 5.0. This document contains information previously contained in the following legacy document, now retired: WLAN IP Telephony Installation and Configuration (553-3001-304). August 2005 Standard 4.00. This document is up-issued to support Nortel Communication Server 1000 Release 4.5.
Revision history Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 01.02 Standard Release 5.0 15 June 2007 Copyright © 2004-2007, Nortel Networks .
Contents New in this release 13 Feature description 13 Other changes 13 Multicast 14 Zones for wireless handsets 14 Open and use the Admin menu on the handset 14 Admin menu options for the WLAN Handset 6120/6140 14 Download the software 14 Feature programming for the WLAN Handset 6120/6140 14 Test the wireless handsets 14 Run Site Survey for the WLAN Handset 6120/6140 14 Diagnostics mode 14 Push-to-talk 14 Wireless handset status messages 15 How to get help 17 Getting help from the Nortel Web site 1
Contents Components 26 Language 27 Licenses 27 Wi-Fi Multimedia 27 Wired Equivalent Privacy 28 Wi-Fi Protected Access 28 Wi-Fi Protected Access2 28 Virtual Private Network 28 Push-to-talk feature 28 Text-messaging feature 28 Loud noise environments 29 WLAN IP Telephony Manager 2245 29 WLAN Application Gateway 2246 30 Access Points 30 Handset switchover 31 Handset switchover 31 Loss of signal 31 Planning 33 Challenges of integrating voice applications 33 High overhead of 802.
Contents 7 Communication Server 1000 Telephony Manager 54 Zones 54 Other network design considerations 55 Access Point interference 56 SSID options and limitations 57 Layer 3 implementation 58 WLAN IP Telephony Manager 2245 planning 59 Installation requirements 59 Capacities 59 WLAN IP Telephony Manager 2245 groups 60 Gateway and timing function 64 Roaming and handover 64 Multicast 65 Placement guidelines for the WLAN IP Telephony Manager 2245 65 WLAN Application Gateway 2246 planning 73 WLAN IP Telephony M
Contents TFTP Server location in a NAT environment 89 WLAN Application Gateway 2246 in a NAT environment CS 1000 features 90 IP Phone 2004 features 91 89 Installation Required materials 93 Supplied equipment 94 Preinstallation checklist 94 WLAN IP Telephony Manager 2245 installation tasks About the front panel 94 Wall-mount 95 Rack-mount 96 LAN connection 97 Power connection 97 WLAN Application Gateway 2246 installation 97 93 94 WLAN IP Telephony Manager 2245 configuration 99 Introduction 99 Functi
Contents 9 Update software on the WLAN Application Gateway 2246 115 Update software on a wireless handset 115 Software update (version 97.
Contents Continuing configuration through Telnet 160 Connecting through Telnet 160 Configuring the Telephone Line 161 Deleting a handset 162 Searching for a handset 162 Feature programming 163 Setting or changing a password 164 System status 164 Network status 165 Software versions 166 Telephone line status 167 Certification testing 167 WLAN Application Gateway 2246 certification 167 Wireless handset certification 167 Software 168 Software updates 168 TFTP software updates Systems 170 Planning Worksheet
Contents 11 Timing information 199 Diagnostic Tools 200 Run Site Survey for the WLAN Handset 2210/2211/2212 200 Run Site Survey for the WLAN Handset 6120/6140 201 Diagnostics Mode 204 Syslog Mode 207 Data capture 213 Questions 213 Data checklist 213 Site-data required for the capture analysis 214 Syslog capture configuration 215 Signaling Server log capture 216 General data capture 217 Capture assert error messages with the Configuration Cradle 218 Network speech levels 219 Reference documents 220 Appendix
Contents Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure 21 22 23 24 25 26 27 28 Procedure 29 Procedure 30 Procedure 31 Searching for a handset 162 Programming a feature 163 Setting or changing a password 164 Viewing system status 165 Certifying wireless handsets on an existing system 168 Transferring the software using FTP 169 Loading software updates 170 Using the serial port as the Application Server communication link 172 Using the CLI to capture a Signaling Server
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.0. Feature description Support is provided for the WLAN Handset 6120/6140 through the addition of the Nortel WLAN Handset 6100 Series Administration Tool Software.
New in this release Multicast The WLAN Handset 6140 uses IP multicast addresses. Zones for wireless handsets The WLAN Handset 6120/6140 is added to the designated wireless handset types. Open and use the Admin menu on the handset The procedures for opening and using the Admin menu on the WLAN Handset 6120/6140 and how to make an alphanumeric string entry are added.
Other changes Wireless handset status messages The new messages are: • Error! • Server Unavailable. Restarting... Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 01.02 Standard Release 5.0 15 June 2007 Copyright © 2004-2007, Nortel Networks .
New in this release Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 01.02 Standard Release 5.0 15 June 2007 Copyright © 2004-2007, Nortel Networks .
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 www.nortel.com/erc Getting help through a Nortel distributor or reseller If you purchased a service contract for your Nortel product from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller. Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 01.02 Standard Release 5.0 15 June 2007 Copyright © 2004-2007, Nortel Networks .
Overview This chapter contains information about the following topics: • "Subject" (page 19) • "Applicable systems" (page 20) • "Conventions" (page 21) • "Related information" (page 21) • "Declaration of conformity" (page 22) • "Shielded cable" (page 22) • "Wireless telephone network description" (page 22) • "Call Server" (page 24) • "DHCP Server" (page 25) • "TFTP Server" (page 25) • "Firewall" (page 25) • "WLAN Handset 2210/2211/2212 and WLAN Handset 6120/6140" (page 25) • "WL
Overview • Nortel WLAN Handset 2211 • Nortel WLAN Handset 2212 • Nortel WLAN Handset 6120 • Nortel WLAN Handset 6140 Note about legacy products and releases This NTP contains information about systems, components, and features that are compatible with Nortel Communication Server 1000 Release 5.0 software. For more information about legacy products and releases, click the Technical Documentation link under Support & Training on the Nortel home page: www.nortel.
Resources 21 Conventions In this document, the following systems are referred to generically as system: • Communication Server 1000M (CS 1000M) • Communication Server 1000E (CS 1000E) The following systems are referred to generically as large systems: • Communication Server 1000M Half Group (CS 1000M HG) • Communication Server 1000M Single Group (CS 1000M SG) • Communication Server 1000M Multi Group (CS 1000M MG) Resources This section lists information sources that relate to this document.
Overview Declaration of conformity The WLAN IP Telephony Manager 2245 and WLAN Application Gateway 2246 have been found to comply with the following: • FCC Part 15 Class A - Radiate and Conducted Emissions requirements • CISPR 22 Class A - Radiate and Conducted Emissions requirements • ICES 003 Class A - Radiate and Conducted Emissions requirements • EN 55022 Class A - Radiated and Conducted Emissions requirements • EN 55024 Immunity Requirements • EN 61000-3-2 Harmonic Current Emissions •
Wireless telephone network description • Trivial File Transfer Protocol (TFTP) server • Firewall • 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 23 Figure 1 "Typical wireless telephone network configuration" (page 24) shows a typical wireless telephone network configuration.
Overview 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 5.0 software. Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 01.02 Standard Release 5.0 15 June 2007 Copyright © 2004-2007, Nortel Networks .
WLAN Handset 2210/2211/2212 and WLAN Handset 6120/6140 25 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.
Overview 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. Just like wired telephones, the wireless handsets receive calls directly, receive transferred calls, transfer calls to other extensions, and make outside and long-distance calls (subject to corporate restrictions).
WLAN Handset 2210/2211/2212 and WLAN Handset 6120/6140 27 • 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 Charger—required hardware (USB cable not included) • USB Cable for the Nortel WLAN Handset 6100 Series Dual Slot Handset Charger ATTE
Overview 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.
WLAN IP Telephony Manager 2245 29 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.
Overview Telephony Manager 2245 model numbers and capacities" (page 30). If greater capacity is required, multiple units can be used in a master-slave arrangement.
Handset switchover 31 affect the coverage area and capacity of the wireless system. Typically, the requirements for use of handsets are similar to that of other wireless data devices. The APs must be either SVP-compliant or WMM-compliant to support QoS. For a list of supported APs, see Appendix "Compatible Access Points" (page 223). Handset switchover When 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.
Overview Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 01.02 Standard Release 5.0 15 June 2007 Copyright © 2004-2007, Nortel Networks .
Planning This chapter contains information about the following topics: • "Challenges of integrating voice applications" (page 33) • "DHCP server planning" (page 36) • "TFTP Server planning" (page 38) • "Syslog Server planning" (page 40) • "Access point planning" (page 40) • "Network planning" (page 46) • "Network recommendation" (page 46) • "Network management" (page 47) • "Zones" (page 54) • "Other network design considerations" (page 55) • "WLAN IP Telephony Manager 2245 planning"
Planning • 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.11 has a very high amount of overhead associated with transmitting a packet. To compare an 802.3 network with an 802.11 network, the difference in overhead for transmitting line-rate minimum frame sizes compared to the line-rate maximum frame sizes on an 802.
Challenges of integrating voice applications 35 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. All of these mechanisms present challenges to the engineering of voice networks. Dynamic adjustments work well for guaranteeing minimum coverage and connectivity of devices, particularly data devices. Voice requires more planned engineering.
Planning 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. Without a way to give preferential transmission opportunities to voice devices, supporting voice applications is a tremendous challenge on 802.11 WLANs.
DHCP server planning 37 handset performs a DNS lookup of the name SLNKSVP2, if Options 6 (DNS Server) and 15 (Domain Name) are configured. • DHCP Option 152. If an optional WLAN Application Gateway 2246 is used in the system, its IP address can be specified with this option. Each wireless handset effectively uses two IP addresses in the wireless subnet: one for the physical wireless handset and a second alias IP address that is used on the WLAN IP Telephony Manager 2245.
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 39 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. How well a server works with the handsets can vary between code versions on the handset. You can configure handsets to not contact the TFTP server upon boot up, by configuring 255.255.255.
Planning Nortel has tested the following TFTP servers. They are listed in order of preference. • Nortel TFTP server (ONMS application) • 3COM TFTP • PumpkinTFTP Syslog Server planning A Syslog Server listens for incoming syslog messages on UDP port 514 and then processes the messages according to local administrative procedures. Usually the syslog messages are logged for subsequent review by the system operator.
Access point planning 41 A site survey is critical to designing and implementing a wireless LAN. The site survey is used to determine the number of APs needed to support the wireless handset users and to determine the best placement of the APs. Different AP vendors provide different tools to do this. Site survey To conduct a site survey, set up an AP at a particular location.
Planning the Site Survey mode displays signals only from APs on the same Extended Service Set ID (ESSID), check for signals from APs using all ESSIDs to avoid channel overlap. Figure 3 Frequencies used by b radio • Wireless handset range—Wireless LAN coverage must be available wherever wireless handsets are used. Although the typical range for a wireless handset is comparable to that of a laptop computer utilizing a wireless LAN PC Card, the range can not be exactly the same.
Access point planning 43 — 15% of the available bandwidth per call for 1 Mbs operation. Note: These requirements mean that areas with a high-use density must receive RF coverage at the highest data rate of operation. • LAN bandwidth—Estimate anticipated peak call volume to ensure that enough bandwidth is available to handle the network traffic generated by all the wireless handsets. Handsets require approximately 150 kbps of bandwidth per call.
Planning cases, a room originally built for a specific purpose, such as a radiology lab, can be converted into something completely different, such as a conference room. The blueprint can also show areas proposed for future building expansion. • Mark possible wireless handset usage locations on the blueprint and refer to the marked blueprint during the physical walk-through and inventory.
Access point 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 46). Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 01.02 Standard Release 5.0 15 June 2007 Copyright © 2004-2007, Nortel Networks .
Planning 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.
Network management 47 — 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.255 eq 68 set security acl ip SpectraLink permit cos 6 udp 0.0.0.0 255.255.255.255 0.0.0.0 255.255.255.
Planning 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.
Network management 49 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.
Planning 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.
Network management 51 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 52). For troubleshooting purposes, you can view a path trace to the signaling server or any other IP address.
Planning 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. With RTCP-XR, you can right-click on the set in the IPSM Convergence or tabular view and retrieve detailed real-time set statistics, such as local and remote latency and jitter.
Network management 53 Call tracking is another feature that is not specifically related to QoS monitoring or fault monitoring, but that is important to solution manageability.
Planning 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 54).
Other network design considerations 55 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.
Planning 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. For example, if a large number of laptops exist in a campus and if 802.
Other network design considerations 57 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. The transmit power is fixed at 50 mW, which establishes the radius of the cell. Now the effects of cell size, based on the other fixed parameters, can be compared. If the deployed cells have a radius of anywhere from 33 ft to 75 ft, the call capacity per square foot is essentially the same.
Planning Layer 3 implementation Where possible, simplify the number of subnets that are used for client devices. Even in a Distributed Campus architecture, you can have a few central subnets for clients. As a general rule, Nortel recommends that wired or wireless IP phones be placed in a separate VLAN (subnet) from data devices. This placement can be accomplished by providing one VLAN (subnet) for all WLAN telephony devices, as shown in Figure 9 "Single telephony VLAN implementation" (page 58).
WLAN IP Telephony Manager 2245 planning 59 industry. So to mitigate risks, you can use a firewall to block all but the ports needed for IP Telephony. This practice becomes complex and costly when multiplied by a number of subnets. A more cost-effective alternative to implementing a firewall is to assign private addresses to the handsets and let the WLAN IP Telephony Manager 2245 network address translation (NAT) capabilities serve as a form of secure firewall to the telephony LAN (T-LAN).
Planning In any subnet where wireless handsets are used, each subnet must have one or more WLAN IP Telephony Managers 2245. A WLAN IP Telephony Manager 2245 group on a subnet consists of one or more WLAN IP Telephony Managers 2245 and their associated wireless handsets. Only one master WLAN IP Telephony Manager 2245 can be on a subnet.
WLAN IP Telephony Manager 2245 planning 61 Table 4 "Multiple WLAN IP Telephony Manager 2245-80 capacities" (page 61) lists the call capacities for WLAN IP Telephony Manager 2245-80 groups. Table 5 "Multiple WLAN IP Telephony Manager 2245-10 and 2245-20 capacities" (page 62) lists the handset capacities for WLAN IP Telephony Manager 2245-10 and 2245-20 groups.
Planning Table 5 Multiple WLAN IP Telephony Manager 2245-10 and 2245-20 capacities Number of WLAN IP Telephony Managers 2245 Number of handsets WLAN IP Telephony Manager 2245-10 Number of handsets WLAN IP Telephony Manager 2245-20 1 10 20 2 20 40 3 30 not applicable 4 40 not applicable For example, if there are two subnets for handsets in a campus and some handsets are directed to one subnet and some to the other, there are two Call Admission Control domains operating independently.
WLAN IP Telephony Manager 2245 planning 63 The handsets encapsulate their voice payloads in SVP for QoS. The handsets further synchronize communications, so that the handsets are able to avoid collisions with each other more effectively than the usual 802.11 collision avoidance mechanisms. Each handset maintains a list of up to four APs as potential candidates for roaming.
Planning To gain this type of predictability, engineer the maximum calls per AP based on 1 Mb/2 Mb rate selections in the handsets, configure that number as the call limit on the WLAN IP Telephony Manager 2245, and then configure the actual rate of the handsets (on the WLAN IP Telephony Manager 2245) to Automatic. That way, the WLAN is engineered for the worst case, but in optimal conditions, more throughput is left over for other devices to use, because the handsets use higher data rates.
Placement guidelines for the WLAN IP Telephony Manager 2245 65 returns. If the wireless handset is configured to use ESSID of the new WLAN, it automatically discovers the ESSID of the APs operating in broadcast mode. Table 6 "Roaming and handover capabilities summary" (page 65) summarizes the capabilities.
Planning Before adding the WLAN IP Telephony Manager 2245 to the network: • Ensure that the APs used in the network are Voice Interoperability for Enterprise Wireless (VIEW) certified. For more information, go to www.spectralink.com/consumer/partners/view_certification.jsp. • Ensure that the handsets are running Nortel Phase II software (97.070 or greater).
Placement guidelines for the WLAN IP Telephony Manager 2245 67 To achieve excellent voice quality, Nortel recommends using G711 CODEC with the following configuration: • End-to-end delay < = 150 ms (one way) • Packet loss < = 0.5% • The maximum jitter buffer for the handsets set as low as possible. For more information, see Converging the Data Network with VoIP Fundamentals (NN43001-260).
Planning • 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 69). • For an example of an end-to-end delay for a LAN to a Public Switched Telephone Network (PSTN), see Figure 14 "Example 3: End-to-end delay and packet loss for a LAN to a PSTN" (page 70). Figure 12 Example 1: End-to-end delay and packet loss for a LAN Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 01.
Placement guidelines for the WLAN IP Telephony Manager 2245 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 01.02 Standard Release 5.0 15 June 2007 Copyright © 2004-2007, Nortel Networks .
Planning 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 71) and Procedure 1 "Measuring jitter, delay and packet loss" (page 71).
Placement guidelines for the WLAN IP Telephony Manager 2245 71 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.
Planning —End— 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 72) and Figure 17 "Part 2: Example of analysis of a packet stream captured between segment A and B" (page 73). Figure 16 Part 1: Example of analysis of a packet stream captured between segment A and B Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 01.02 Standard Release 5.
WLAN Application Gateway 2246 planning 73 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.
Planning 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) • easy access to the front panel, which is used for cabling • for the WLAN Application Telephony Gateway 2246, a maximum distance of 32
Planning worksheets 75 Record the static IP address assignments and store them in a safe place. 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.
Planning WINS Server IP address Workgroup name Syslog Server IP address First alias IP address Last alias IP address Copy and complete the worksheet from Table 8 "Wireless handset planning worksheet" (page 76) to maintain a configuration record for the handsets. Table 8 Wireless handset planning worksheet Line * MAC Address * User Name Dialin g 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.
System information This chapter contains information about the following topics: • "Bandwidth management" (page 77) • "Codecs" (page 79) • "Jitter buffer" (page 80) • "RLR and SLR" (page 80) • "RTCP" (page 80) • "Gain adjustment" (page 81) • "Programmable rings and tones" (page 81) • "Virtual Office" (page 81) • "Branch Office" (page 81) • "Survivable Remote Gateway" (page 82) • "External Applications Server" (page 83) • "End-to-end QoS" (page 83) • "NAT" (page 83) • "CS 1000
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 master 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 master WLAN IP Telephony Manager 2245.
Codecs 79 OR PRT IPDN 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 the master of a WLAN IP Telephony Manager 2245 group, and subsequently registered with the LTPS and Call Server.
System information 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.723.
Branch Office 81 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 9 "IP Phone 2004 and handset Local mode license display (MG 1000B only)" (page 82).
NAT 83 Note 2: No patch is required for SRG 1.0 based on BCM 3.7 or SRG50 systems 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.
System information NAT Traversal feature The NAT Traversal feature is used where the IP Phone (this includes the handsets) is located on the private side of the NAT router, while the rest of the Server resides on the public side. 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.
NAT Figure 18 VPN design over a Layer 2 network Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 01.02 Standard Release 5.0 15 June 2007 Copyright © 2004-2007, 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 85), Figure 19 "VPN design over a Layer 3 network" (page 86), Figure 20 "Not recommended VoWLAN design" (page 87), and Figure 21 "Network configuration 3 with Full DHCP Server" (page 89), the clouds can represent a corporate intranet or the public Internet.
NAT 87 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. Therefore, Nortel recommends that you do not use the network design shown in Figure 20 "Not recommended VoWLAN design" (page 87) as a design for the VPN feature.
System information 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. WLAN IP Telephony Manager 2245 in a NAT environment The IP Telephony Manager 2245 must be in constant communication with the handsets to ensure handset functionality.
NAT 89 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 89).
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 89). 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 91 IP Phone 2004 features Table 12 "IP Phone 2004 features" (page 91) provides information about the IP Phone 2004 features for the handsets.
System information 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 01.02 Standard Release 5.0 15 June 2007 Copyright © 2004-2007, Nortel Networks .
Installation This chapter contains information about the following topics: • "Required materials" (page 93) • "Preinstallation checklist" (page 94) • "WLAN IP Telephony Manager 2245 installation tasks" (page 94) • "WLAN Application Gateway 2246 installation" (page 97) 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 95 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 97 4 Repeat steps 1-3 for each additional WLAN IP Telephony Manager 2245. The mounting plate is designed to provide 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.
Installation Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 01.02 Standard Release 5.0 15 June 2007 Copyright © 2004-2007, Nortel Networks .
WLAN IP Telephony Manager 2245 configuration This chapter contains information about the following topics: • "Introduction" (page 99) • "Configuration tasks" (page 101) • "Connect to the WLAN IP Telephony Manager 2245" (page 101) • "Configure the network" (page 103) • "Configure the WLAN IP Telephony Manager 2245" (page 106) • "Change the password" (page 108) 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 Each WLAN IP Telephony Manager 2245 is configured with an IP address with which all of the wireless handsets communicate. In addition, each WLAN IP Telephony Manager 2245 is configured with a pool of IP addresses. When a wireless handset registers with a WLAN IP Telephony Manager 2245, the wireless handset is assigned one of the IP addresses from the pool.
Connect to the WLAN IP Telephony Manager 2245 101 the entire WLAN IP Telephony Manager 2245 group fails. All active calls are lost and no future calls can be placed until the master WLAN IP Telephony Manager 2245 is replaced (either by installing a spare or by reconfiguring one of the slaves to be a master).
WLAN IP Telephony Manager 2245 configuration Procedure 5 Connecting to the WLAN IP Telephony Manager 2245 through a serial port Step Action 1 Using a DB-9 female, null-modem cable, connect the WLAN IP Telephony Manager 2245 to the serial port of a terminal or PC.
Configure the network 103 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. Note: The login name and password are case-sensitive. The NetLink SVP-II System menu appears. The following menu choices are available: • System Status—view software code version, error messages, and status of operation.
WLAN IP Telephony Manager 2245 configuration Fore more information about the master WLAN IP Telephony Manager 2245, see "Master WLAN IP Telephony Manager 2245" (page 60). • Hostname:—optional field. Change the default hostname of this WLAN IP Telephony Manager 2245, if desired. Hostname is for identification purposes only. Note: Spaces cannot be entered in this field. • Subnet mask—the subnet mask of the subnet. • Default Gateway—the default gateway for the subnet.
Configure the network 105 • 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 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 106). —End— Changing the master IP address To change the IP address of the master WLAN IP Telephony Manager 2245, change it in the Network Configuration menu and reboot the system.
Configure the WLAN IP Telephony Manager 2245 107 — Enter DHCP. Ensure that the IP address of the master WLAN IP Telephony Manager 2245 is configured in the DHCP server and configure the other WLAN IP Telephony Managers 2245 to obtain the information from the DHCP server. — Enter DNS. Ensure that the IP address of the master WLAN IP Telephony Manager 2245 is configured in the DNS server and configure the other WLAN IP Telephony Managers 2245 to retrieve this information from the DNS server.
WLAN IP Telephony Manager 2245 configuration To ensure the system transmits voice packets efficiently and with minimal delay, you must configure the decimal value for voice packets higher than the value for data packets. The configurable classes are: — Administration—used for Telnet, TFTP and other administrative traffic. This class can have the lowest priority because it does not require voice quality. — WT (in call)—traffic requires voice quality.
Change the password 109 3 • first character must be a letter • other characters can be a letter or a number • dashes, spaces, and punctuation marks are not allowed (alphanumeric only) Select Set Password and press Enter. Alternatively, press the S key on the keyboard. Record the password and keep it in a safe place. —End— If you forget the password, use the steps in Procedure 9 "Changing a forgotten password" (page 109) to log on to the SVP server.
WLAN IP Telephony Manager 2245 configuration Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 01.02 Standard Release 5.0 15 June 2007 Copyright © 2004-2007, Nortel Networks .
Administration and maintenance This section contains information about the following topics: • "Adding a WLAN IP Telephony Manager 2245 to the system" (page 111) • "Replacing a WLAN IP Telephony Manager 2245" (page 112) • "Removing a WLAN IP Telephony Manager 2245 from the system" (page 113) • "Changing the master WLAN IP Telephony Manager 2245" (page 113) • "Viewing software version" (page 113) • "Updating software" (page 114) • "Wireless handset download messages" (page 117) Adding a WL
Administration and maintenance is checking in again and again, it can indicate a problem on the network, such as poor AP coverage for a user who is moving about. This information is useful when troubleshooting. Replacing a WLAN IP Telephony Manager 2245 Failed master WLAN IP Telephony Manager 2245 If the master WLAN IP Telephony Manager 2245 fails, no telephone calls can be made or received on that subnet.
View software version 113 —End— 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.
Administration and maintenance For the WLAN IP Telephony Manager 2245 To view the software versions for the WLAN IP Telephony Manager 2245, follow the steps in Procedure 11 "Viewing the software version" (page 114). Procedure 11 Viewing the software version Step Action 1 From the WLAN IP Telephony Manager 2245 NetLink SVP-II System screen, select System Status and press Enter. 2 On the System Status Menu screen, scroll down to Software Versions and press Enter.
Software updates 115 Update software on the WLAN IP Telephony Manager 2245 To update the software on the WLAN IP Telephony Manager 2245, reset it. When the WLAN IP Telephony Manager 2245 starts up, it compares its software version to the software version on the TFTP Server. The WLAN IP Telephony Manager 2245 downloads the software from the TFTP Server if the versions are different.
Administration and maintenance If the TFTP Server cannot be reached at the time the wireless handset is powered on, resets, or comes back into a WLAN service area, the wireless handset tries a few times to contact the TFTP Server, and then gives up and uses the existing software.
Wireless handset download messages 117 For more information, see WLAN Handsets Fundamentals (NN43001-505). Displays When the wireless handset is powered on, it displays a series of messages indicating that it is searching for new software, checking the versions, and downloading the software. During the download, a progress bar on the wireless handset display screen displays the progress of the download.
Administration and maintenance Download failure or recovery messages Table 14 "Failure and recovery messages" (page 118) lists the display messages for the wireless handset that indicate a failure or recovery situation during the software download process. Table 14 Failure and recovery messages Message Description Server Busy Wireless handset is attempting to download from a TFTP Server that is busy downloading other handsets and refusing additional downloads.
Troubleshooting This chapter contains information about the following topics: • "Troubleshooting the WLAN IP Telephony Manager 2245" (page 119) • "Troubleshooting the WLAN Application Gateway 2246" (page 122) • "Troubleshooting the handset" (page 122) • "Dropped calls" (page 124) • "Troubleshooting coverage issues" (page 144) • "Before calling Nortel Technical Support" (page 144) Troubleshooting the WLAN IP Telephony Manager 2245 Use the System Status Menu screen to obtain information about
Troubleshooting 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 120) lists the alarms and the actions required to eliminate the alarm.
Troubleshooting the WLAN IP Telephony Manager 2245 121 — drop—packets dropped due to insufficient memory — fifo—overrun occurred during reception — alignment—non-octet-aligned packets (number of bits not divisible by 8) — multicast—packets received with a broadcast or multicast destination address • TX—Ethernet statistics about the transmitted signal during System Uptime.
Troubleshooting 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. Double-check WLAN connections and interfaces to ensure that they are all configured as full-duplex.
Troubleshooting the handset • 123 At what location did the problem occur? Record this information and provide it to the system administrator or Nortel Technical Support. Access Point problems Most, but not all, wireless handset audio problems are related to AP range, positioning, and capacity. Performing a Site Survey as described in "Site survey" (page 41) can isolate the AP causing these types of problems.
Troubleshooting Duplex mismatch A duplex mismatch on the WLAN can cause the wireless handsets to not operate properly. Double-check WLAN connections and interfaces to ensure that they are all configured as full-duplex. No ring It is possible in certain situations for a voice mail message to be left on a wireless handset without the wireless handset ever ringing. This situation could occur when a wireless handset is out of range of an AP for even a few seconds.
Dropped calls 125 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 125) summarizes the status messages, in alphabetical order. Table 16 Wireless handset status messages Message Description Action 3 chirps Wireless handset is not able to communicate with the best AP, probably because that AP has no bandwidth available. None. This is only a warning.
Troubleshooting Message Description Action Auth Failed xxxxxxxxxxxx x...x = AP MAC address Handset authentication is refused by 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 Timeout xxxxxxxxxxxx x...x = AP MAC address Handset did not receive an authentication response from the AP; displays the MAC of the failing AP. Check the handset and AP security settings.
Dropped calls 127 Message Description Action 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. Bad Payload Type The VPN server is not accepting some of the parameters passed to it by the handset. One common instance is if two handsets try to use the Client IP.
Troubleshooting Message Description Battery Low Action The Battery Low message indicates that the battery pack can be changed while the call is still in progress. For the WLAN Handsets 2210/ 2211/2212 only, do not press Power Off/End Call. Place the call on Hold or Park, quickly remove the discharged battery and replace with a charged battery, power on the handset and press Power On/Start Call to resume the call in progress. For the WLAN Handsets 6120/ 6140 only, do not press End.
Dropped calls 129 Message Description Action Charge Complete The wireless handset is now fully charged. No action needed. Checking Code Wireless handset is contacting the TFTP Server to determine if it has a newer version of software that must be downloaded. None. This message usually only lasts for approximately one second. If message remains displayed, power off and contact Nortel Technical Support. Checking DHCP IP The wireless handset is retrieving DHCP information from the DHCP server.
Troubleshooting Message Description Action wireless handset stops trying. Reconfigure the DHCP server and power-cycle the wireless handset. DHCP Error 5 Failure during WEP Key rotation process (proprietary failure). DHCP Lease Exp yyy.yyy.yyy.yyy y...y = DHCP Server IP address DHCP is not responding to renewal attempts. At least one renewal succeeded.
Dropped calls 131 Message Description Action Erase Failed Download process failed to erase the memory in the wireless handset. Operation retries but can eventually report the error int. error: 0F. Power cycle the wireless handset. Erasing memory The wireless handset has determined that a download must occur and is erasing the current software from memory. None. When the progress bar fills the display line, the erase operation is complete. Note: Do not turn the handset off during this operation.
Troubleshooting Message Description Action Invalid ID Info The VPN server did not recognize this user. Make sure that the local ID (KEY ID) entered in the handset matches the key ID in the VPN server. For a Contivity VPN server, the local ID must match the username. Multiple SVP Svr yyy.yyy.yyy.yyy y...y = WLAN IP Telephony Manager 2245 IP address Handset received responses from multiple WLAN IP Telephony Managers 2245; displays the IP address of one responding WLAN IP Telephony Manager 2245.
Dropped calls 133 Message Description Action No Host IP (Addr) The wireless handset is configured for static IP (as opposed to use DHCP) and no valid host IP address (the wireless handset IP address) is entered. Enter a valid IP address in the configuration settings or change to use DHCP. No IP Address Invalid IP address. Check the IP address of the wireless handset and reconfigure if required. No Net Access Cannot authenticate or associate with AP. Verify the AP configuration.
Troubleshooting Message Description Action • Out of Range 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 SSID of the handset. • incorrect WEP settings Verify that all the WEP settings in the handset match those in the APs. • Incorrect Security settings Verify that all the Security setting in the AP. No Net Found xxxxxxxxxxxx yy x...
Dropped calls 135 Message Description Action No SVP Response yyy.yyy.yyy.yyy y...y = SVP Server IP address The handset has lost contact with the WLAN IP Telephony Manager 2245. This can be caused by bad radio reception or a problem with the WLAN IP Telephony Manager 2245. The handset keeps trying to fix the problem for 20 seconds, and the message can clear by itself. If it does not, the handset restarts. Report this problem to the system administrator if it keeps happening.
Troubleshooting Message Description Action No VPN Server The handset cannot find the VPN server. Check that the value of the VPN Server IP address configured through the administration menu or the Configuration Cradle match the address of the VPN server. Not Installed! A required software component is missing. Check that all required software files are on the TFTP Server, if over-the-air downloading is being used. If the error repeats, contact Nortel Technical Support.
Dropped calls 137 Message Description Action Server Unavailable. Restarting... (For the WLAN Handset 6120/6140 only) An error caused the handset to lose the call. It is trying to restart and return to standby mode. Occurs during Restart on Error mode. The handset is attempting to register with the PBX and resume normal operation. Error details may be available through the Syslog Server and by download with the Handset Administration Tool. SKT Open Failed Socket open fail.
Troubleshooting Message Description Action TFTP ERROR(x):yy A failure occurred during a TFTP software download. (x) = the file number that was being downloaded; yy = an error code describing the particular failure. Error code 01, 02 or 07—check the TFTP Server configuration. Possible error codes are: • 01 = TFTP Server did not find the requested file. • 02 = Access violation (reported from TFTP Server). • 07 = TFTP Server reported No such user error.
Dropped calls 139 Message Description Action Waiting Wireless handset has attempted some operation several times and failed. It is now waiting for a period of time before attempting that operation again. None. The wireless handset is waiting for a specified period of time before attempting that operation again. Watchdog Timeout The wireless handset failed to hear from the Call Server within the watchdog timeout interval. Verify the Call Server is operational and connected to the network.
Troubleshooting MANUFACTURER CODE: [NAME] MODEL: NT CODE: NT2K00GI COLOR CODE: 66 RLS CODE: 0 SER NUM: 7641C7 FWSW VERSION: 0602B59 .idu 62 2 I2004 TN: 062 0 00 02 V TN ID CODE: i2004 ISET MAC ADR: 00:90:7A:01:7E:47 ISET IP ADR: 192 .168 .010 .200 LTPS IP ADR: 047 .011 .214 .165 MANUFACTURER CODE: [NAME] MODEL: NT CODE: NTTQ5010 COLOR CODE: 66 RLS CODE: 7 SER NUM: 017E47 FWSW VERSION: 097.021 LD 32 STAT command The wireless handsets are shown REGISTERED in the standby and active modes.
Dropped calls 141 192.168.10.200 is an alias IP address assigned by the WLAN IP Telephony Manager 2245. TN HWID STATUS HOSTIP TERMIP PORT ______ _______________________________ ______ __________ ____________ _______ 0x600a 00000000000003000907a017e476607 REG 47.11.214.165 192.168.10.
Troubleshooting • last two digits—Release Code. The Release Codes are defined as follows: — IP Phone 2004 Phase 1—0 — IP Phone 2004 Phase 2—2 — WLAN Handset 2210—0x06 — WLAN Handset 2211—0x07 — WLAN Handset 2212—0x08 -> dsetShow TN IP Address Hardware ID TermType ---- --------------- ------------------ ---------6004 192.168.10.100 180060387641c76600 i2004 600A 192.168.10.
Dropped calls 143 isetShow, isetShowByTN, and isetShowByIP Similar to the dsetShow command, the wireless handset outputs its specific hardware ID (see dsetShow) and alias IP, not the physical IP address. The FW version has a different format . in this output. In the following example, the telephone with TN 062-02 is the WLAN Handset 2211. -> isetShow Set Information --------------IP Address Type RegType State Up Time Set-TN Regd-TN ---------- ---- ----- ---- ----- ----- ------192.168.10.
Troubleshooting -> usiLibTraceOn "192.168.10.200", 255, 255 value = 0 = 0x0 Determining alias IP addresses When diagnosing network problems, (for example, to ping the wireless handset), it is useful to know the mapping between the alias IP addresses as displayed by various Call Server commands and the physical IP address of the wireless handset. There is no single command that provides this information; however, the administrator can determine it in two ways: 1.
Before calling Nortel Technical Support • any error messages displayed on the handset display screen • content of the Syslog Server (if using) • log of the DHCP Server (if available), if using DHCP Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 01.02 Standard Release 5.0 15 June 2007 Copyright © 2004-2007, Nortel Networks .
Troubleshooting Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 01.02 Standard Release 5.0 15 June 2007 Copyright © 2004-2007, Nortel Networks .
Appendix A WLAN Application Gateway 2246 This appendix contains information about the following topics: • "Introduction" (page 147) • "Third-party applications" (page 150) • "Installation" (page 151) • "Configuration" (page 153) • "Continuing configuration through Telnet" (page 160) • "System status" (page 164) • "Certification testing" (page 167) • "Updating software" (page 168) • "Planning Worksheet for Handsets" (page 171) • "Free the serial port for administrative purposes" (page
Appendix A WLAN Application Gateway 2246 Model number Maximum number of users NTTQ65CA 256 NTTQ65DA 512 NTTQ65EA 1024 NTTQ65FA 10000 In Figure 23 "WLAN Application Gateway 2246 connections" (page 148), 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. Only one of these connections can be used at one time.
Introduction 149 Figure 24 Ethernet switch connections Front panel The WLAN Application Gateway 2246 models have similar front panel indicators. See Figure 25 "NTTQ65xx" (page 150). 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 01.02 Standard Release 5.0 15 June 2007 Copyright © 2004-2007, Nortel Networks .
Appendix A 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 150).
Installation 151 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 Cal
Appendix A WLAN Application Gateway 2246 Procedure 13 Installing the WLAN Application Gateway 2246 Step Action 1 Place the WLAN Application Gateway 2246 on a shelf or convenient location. Note: 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 • Bits per second: 9600 • Data bits: 8 • Parity: None • Stop bits: 1 • Flow control: None 153 Note: If using Windows 2000, Service Pack 2 must be installed 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.
Appendix A WLAN Application Gateway 2246 Administration console navigation Use the keys described in Table 18 "Administration console navigation" (page 154) to move around the Administration console screens. 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.
Configuration 4 155 Select the Feature Programming option to configure the function sequence that activates the application. See "Programming a feature" (page 163). —End— Configuring the OAI Box Follow the steps in Procedure 15 "Configure the system type from the OAI Box Configuration option" (page 155) to configure the system type. Procedure 15 Configure the system type from the OAI Box Configuration option Step Action 1 From the NetLink OAI System screen, select OAI Box Configuration.
Appendix A WLAN Application Gateway 2246 Procedure 16 Configuring the network Step Action 1 From the NetLink OAI System screen, select Network Configuration. 2 Enter the configuration information for the WLAN Application Gateway 2246, as provided by the network administrator. • Ethernet Address—this is the MAC address of the WLAN Application Gateway 2246. This address is set at the factory.
Configuration 157 also possible to access the WLAN Application Gateway 2246 using its hostname instead of the IP address. • Logging—can be configured to Syslog or NONE. • Log server—enter the IP address or hostname of the Syslog Server on the network if Syslog is configured. The WLAN Application Gateway 2246 writes Syslog format diagnostic messages to the Syslog Server. • SNTP server—can be configured as a hostname, IP address, or NONE. The SNTP server is a Simple Network Time server.
Appendix A WLAN Application Gateway 2246 —End— All components cycle through their usual diagnostic routine. Connecting to the Application Server Some applications can require a LAN connection between the Application Server and the WLAN Application Gateway 2246. If the applications do not require a LAN connection, use the RS-232 port connection. In some situations, a modem is connected to be used for remote administration of the WLAN Application Gateway 2246.
Configuration 159 The WLAN Application Gateway 2246 uses the following pins on the connector. Table 19 Pins on the connector Pin Function 1 Carrier Detect 2 Data OAI Receives 3 Data OAI Transmits 5 Ground 7 Ready to Send 8 Clear to Send Connect to the Application Server through the LAN The IP address must be configured for the WLAN Application Gateway 2246 to function on the LAN. Follow the application instructions to identify the WLAN Application Gateway 2246 to the application.
Appendix A WLAN Application Gateway 2246 Figure 28 WLAN Application Gateway 2246 connection to Application Server through a modem Continuing configuration through Telnet After the IP address for the WLAN Application Gateway 2246 is configured, the WLAN Application Gateway 2246 reset and connected to the LAN and the Application Server, Telnet can be used to continue the WLAN Application Gateway 2246 configuration.
Continuing configuration through Telnet 161 When the configuration procedure is complete, the NetLink OAI System screen adds a Feature Programming option. Also, the OAI Line Configuration option is replaced by a Telephone Line Configuration option. Configuring the Telephone Line Each handset that uses the application features must be configured with its line number and MAC address. The name and extension number of the handset user can be entered.
Appendix A WLAN Application Gateway 2246 4 Write the MAC address on the Wireless Handset Planning Worksheet. See "Planning Worksheet for Handsets" (page 171). 5 Repeat step 4, step 5, and step 6 for each wireless handset to be added or changed. 6 Press Esc to return to the NetLink OAI System screen. —End— Deleting a handset Follow the steps in Procedure 20 "Deleting a handset" (page 162) to delete a WLAN IP Telephony Manager.
Continuing configuration through Telnet 163 2 At the Telephone Line Configuration screen, select the field to use as the search key (MAC Address, Name, or Extension), 3 Press S to display a search screen dialog box. 4 Type an appropriate search string. 5 Press Enter. The success or failure of the search appears at the bottom of the screen. 6 Continue to change the search string for different search criteria or exit by pressing the Esc key.
Appendix A WLAN Application Gateway 2246 3 Type any label up to six characters. The label you type here appears on the handset telephone display screen next to the assigned number on the FCN menu. —End— Setting or changing a password You can configure a unique password for the WLAN Application Gateway 2246. The password restricts access to administrative functions of the device. WARNING Record the password and store it in a safe place.
System status 165 Procedure 24 Viewing system status Step Action 1 From the NetLink OAI System screen, select the System Status Menu option. 2 At the Systems Status Menu screen, select from the following options: • Application Active—Yes appears if the application is communicating correctly with the WLAN Application Gateway 2246. No appears if the application is not connected. This field is read-only and changes dynamically.
Appendix A WLAN Application Gateway 2246 • User Time Period—the length of time (in seconds) that statistics accumulate in the Userpkts column before resetting to zero. When troubleshooting a problem, use this setting to isolate statistics for a given time period (for example, one hour). This is the only field in this screen that can be changed by the user. The rest of the display is a table of Ethernet statistics.
Certification testing 167 components. This information helps determine if the most recent version of software is running, and assists Nortel Technical Support in troubleshooting software problems. Viewing software versions From the System Status Menu screen, select Software Versions. Telephone line status The Telephone Line Status screen displays which wireless handsets are communicating with the WLAN Application Gateway 2246.
Appendix A WLAN Application Gateway 2246 WLAN Application Gateway 2246 installation on existing system Follow the steps in Procedure 25 "Certifying wireless handsets on an existing system" (page 168) to certify the wireless handsets on an existing system. Procedure 25 Certifying wireless handsets on an existing system Step Action 1 Place a test call. 2 Test the features on each handset to ensure the system is working properly. 3 Test the application on each handset.
Software 169 Nortel periodically upgrades the fnctla.bin file, which is the only file downloaded. The other files are configuration files and their names are provided for information and backup purposes. Obtain software using FTP When using FTP, a host system is used to connect to a remote system. In this example, the host is the client and the server is the WLAN Application Gateway 2246. The put command means to copy the files from the host to the remote system.
Appendix A WLAN Application Gateway 2246 7 Navigate to the NetLink OAI System screen for the WLAN Application Gateway 2246 8 Select System Status. 9 Select Software Versions to verify that software versions for the WLAN Application Gateway 2246 are correct. 10 Reset the system through the OAI Box Configuration screen in order to restore Maintenance Lock to N. —End— Note: You can use a GUI FTP client instead of the described command line FTP procedure.
Planning Worksheet for Handsets The code downloads into the WLAN Application Gateway 2246. —End— Planning Worksheet for Handsets Copy and complete the worksheet in Table 21 "Handset Planning Worksheet" (page 171) to track parameters for each handset. Table 21 Handset Planning Worksheet OAI Port MAC Address User Name Dialing Ext.
Appendix A WLAN Application Gateway 2246 OAI Port MAC Address User Name Dialing Ext. IP Address (if static) 26 27 28 29 30 Free the serial port for administrative purposes If the serial port is being used as the primary communication link with the Application Server, you must enter the OAI command to free the serial port to allow it to be used for administrative purposes, such as changing the IP address of the WLAN Application Gateway 2246.
Appendix B 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 173) • "Product-specific configuration" (page 176) • "WLAN specific configuration" (page 177) • "General WLAN configuration" (page 183) • "DHCP server options" (page 184) • "DHCP options" (page 184) • "Quality of Service checklist for voice over WLAN
Appendix B Troubleshooting WLAN IP Telephony installations Figure 29 System Information table Figure 30 System History table Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 01.02 Standard Release 5.0 15 June 2007 Copyright © 2004-2007, Nortel Networks .
Site data-gathering tables 175 Figure 31 Customer Environment table 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. Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 01.02 Standard Release 5.
Appendix B Troubleshooting WLAN IP Telephony installations Figure 33 Attachments: Other Required table Product-specific configuration The following sections provide product-specific configuration information. Terminal proxy server Ensure that the system meets the following requirements: • CS1000 Release 3.0: include the patches identified in the current product bulletin 2210, 2211: firmware version 97.070 2245: load 174.027 • CS1000 Release 4.
WLAN specific configuration 177 Handsets For the WLAN Handsets 2210/2211/2212, configure the license code to 010 to download the Nortel UNIStim firmware. For the WLAN Handsets 6120/6140, configure the Telephony Protocol to 032. For firmware and documentation, go to www130.nortelnetworks.com. WLAN IP Telephony Manager 2245 If you have multiple WLAN IP Telephony Manager 2245s, you must split the alias IP address range to allocate a range to each 2245.
Appendix B Troubleshooting WLAN IP Telephony installations Nortel switches This section contains configuration information for Nortel switches. Nortel WLAN Security Switch The 2350, 2360, and 2380 model switches have the following requirements: • load 4.1.
WLAN specific configuration • 179 Enable Multicast Support on the WLAN Security Switch 2270 to enable use of the PTT feature for Nortel Handsets. With the following settings, you can use Multicast for some of the regular SVP server and PBX control traffic: Switch > General: Ethernet Multicast Support = Enabled: (2.2) Switch > General, Ports: click ports 1 edit on right hand side of the screen and configure Multicast Appliance Mode = Enabled. • Turn off Rogue AP Detection.
Appendix B Troubleshooting WLAN IP Telephony installations You must add B and C as members under mobility group configuration for switch A. You must add A and C as members under mobility group configuration for switch B. You must add A and B as members under mobility group configuration for switch C. The above recommendation is true in the case of VoDATA as well. WLAN Security Switch 2270 notes The following list contains important information about the WLAN Security Switch 2270 and pre-3.2.116.
WLAN specific configuration 181 ATTENTION 2.x code is not supported. Nortel recommends that sites upgrade to 3.2.116.21 code. Contact Nortel GNTS Technical support to obtain this code—do not download it from the Cisco Web site.
Appendix B Troubleshooting WLAN IP Telephony installations AP: 1230 2950 connected the APs 2950 connected to 2245 7 access-list 101 permit udp 172.23.0.016 eq 5200 172.23.0.
General WLAN configuration AP:1230 3650 connected to APs 183 6509 connected to 2245 7 policy-map trust -voice-2245 class voice-sig set ip dscp 40 class voice-bearer set ip dscp 46 8 int fastethernet 03 (the port that is connected with 2245) switchport access vlan xx switchport mode access mls qos trust cos mls qos cos 5 service-policy input trust-voice-2245 General WLAN configuration The following is a list of considerations for general WLAN configuration: • Multicast must be configured in any WLA
Appendix B Troubleshooting WLAN IP Telephony installations DHCP server options The DHCP server options known to work in almost every situation are 3, 7, 42, 66, 128, 151, and 152: • DHCP Option 3—the Default Gateway • DHCP Option 7—the Syslog Server • DHCP Option 42—the Time Server • DHCP Option 60—the Class Identifier • DHCP Option 66—the IP address of the TFTP Server • DHCP Option 151—the IP address of the WLAN IP Telephony Manager 2245 • DHCP Option 152—the IP address for the optional W
DHCP options 185 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Mask Code. 8 bits. Always set to 1. Length. 8 bits. Always set to 4. Mask. 32 bits. Subnet mask of the client. RFCs: [RFC 2132] DHCP Options. Updated by: RFC 3942. DHCP option 3: Length: 6+ bytes This option specifies a list of 32 bit IP addresses for routers on the client’s subnet. The routers SHOULD be listed in order of preference.
Appendix B Troubleshooting WLAN IP Telephony installations 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.
DHCP options 187 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.
Appendix B Troubleshooting WLAN IP Telephony installations 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.
DHCP options 189 This string can be NULL terminated although the NULL is not required for parsing. 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.
Appendix B Troubleshooting WLAN IP Telephony installations the relevant information out of this option and uses it to configure the primary and (optionally) secondary TPSs. Either this encapsulated 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 187).
Quality of Service checklist for voice over WLAN applications 191 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.
Appendix B Troubleshooting WLAN IP Telephony installations 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.
Quality of Service checklist for voice over WLAN applications 193 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. • Fix the transmit (TX) power setting and disable auto-power features.
Appendix B Troubleshooting WLAN IP Telephony installations • Use appropriate security mechanisms for the wireless telephones and the requirements of the environment: — 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.
Quality of Service checklist for voice over WLAN applications 195 — Enable the voice VLAN across the network between the AP, to the SVP, to the Signaling Server, to the Call Manager and all components in between. — Assign all devices in this VLAN to one subnet. – 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.
Appendix B Troubleshooting WLAN IP Telephony installations • EAP or MAC Reauthentication interval • TKIP MIC Failure Holdoff Time 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.
Troubleshooting 197 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.
Appendix B Troubleshooting WLAN IP Telephony installations Handset error messages Table 26 "Handset error messages" (page 198) 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.
Timing information 199 Short Error code Description Action 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. Forward the DHCP option 151 to the IP of the SVP server. Verify the settings on the AP. Verify that there is no 2.4 Ghz interference of any kind. SVP No SVP IP No static IP entered into the phone for the WLAN IP Telephony Manager 2245. Check for a valid IP in the phone.
Appendix B Troubleshooting WLAN IP Telephony installations 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. If none of these get a response from the WLAN IP Telephony Manager 2245, the handset attempts to find a different AP and repeats the above handshake sequence.
Diagnostic Tools 201 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, as follows: i:bbbbb sn ch bcn eeeeeeeeeee DGHI rrrrrrrrrrrrr+xxxx mmm G:gggg P:pppp Any Smry where i = index of selected AP (range: 0-3) bbbbb = last three octets of the ESSID for a disco
Appendix B Troubleshooting WLAN IP Telephony installations • current security configuration When Run Site Survey begins, it is in single SSID mode. Press the Any soft key to switch to all APs (regardless of SSID) mode; the Any soft key changes to MyID.
Diagnostic Tools 203 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. ab7b -28 02 ALPHA 2ae5 -48 06 WSMTES 2ae5 -56 11 voice Any Detl In detail mode, the display appears as follows. The left and right arrow keys move between AP indices.
Appendix B Troubleshooting WLAN IP Telephony installations ATTENTION Numbers racing across the handset display indicate that AP information is being obtained. A Waiting message indicates that the system is not configured properly and the handset cannot find any APs. Diagnostics Mode Diagnostics Mode evaluates the overall quality of the link between the handsets, AP, and the infrastructure equipment (call server, WLAN IP Telephony Manager 2245, and gateways).
Diagnostic Tools 205 TxRetryCount is the transmit retry count since power up. Diagnostics Screen 2 displays the following information: Jitter nnnnn LastRate nnnnn GatewayType mnemo where Jitter is the current delta from the desired jitter buffer depth, in microseconds. LastRate is the last successful transmit data rate. GatewayType is a mnemonic that indicates the gateway type.
Appendix B Troubleshooting WLAN IP Telephony installations mnem is a mnemonic that indicates why the handset did not hand off to this candidate: Unkn reason unknown Weak signal strength too weak Rate One or more basic rates not supported Full AP cannot handle bandwidth requirements AthT Authentication Timeout AthF Authentication Failure AscT Association Timeout AscF Association Failure SecT Security Timeout SecF Security Failure Cnfg Configuration error—AP is not configured correct
Diagnostic Tools 207 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. Note: If the Syslog Server address is blank (000.000.000.000 or 255.255.255.255) or the handset is using DHCP and no option 7 is received from the DHCP server, the handset does not send any syslog messages.
Appendix B Troubleshooting WLAN IP Telephony installations Syslog message Contents 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 dependent) Call Start Call type (telephony, OAI, PTT) AP MAC AP signal strength Call End AP MAC AP signal strength Nortel Communication Server 1000 WLAN IP Telephon
Diagnostic Tools Syslog message Contents Audio stats (AStat) AP MAC AP signal strength Payload size (in ms) Payloads sent Payloads received Payloads missed (not received) Payloads missed rate (over last 5 seconds) Payloads late Payloads late rate (over last 5 seconds) Average jitter Audio threshold (AThresh) exceeded (Sent if payloads missed rate or payloads late rate exceeds 2%, or if the average jitter is over 2 ms) AP MAC AP signal strength Payload size (in ms) Payloads sent Payloads received Paylo
Appendix B Troubleshooting WLAN IP Telephony installations Syslog message Contents Radio stats (NStat) AP MAC AP signal strength Directed packets sent Directed packets received Multicast packets sent Multicast packets received Broadcast packets sent Broadcast packets received TX dropped count TX drop rate (over last 5 seconds) TX retry count TX retry rate (over last 5 seconds) RX retry count RX retry rate (over last 5 seconds) Radio threshold (NThresh) exceeded (Sent if TX drop rate exceeds 2%, or
Diagnostic Tools Syslog message 211 Contents Broadcast packets sent Broadcast packets received TX dropped count TX drop rate (over last 5 seconds) TX retry count TX retry rate (over last 5 seconds) RX retry count RX retry rate (over last 5 seconds) VPN: Established IKE phase 1 SA, renew in xs VPN: Established IKE phase2 SA yy:yy, renew in xs (a phase1 message follows the phase 2 message, sent whenever a phase 1 or phase 2 security association completes) Expiration time and security association identifi
Appendix B Troubleshooting WLAN IP Telephony installations Reason code number Meaning 8 AUTH TIMEOUT 9 ASSOC TIMEOUT 10 FAILED AUTHENTICATION 11 FAILED ASSOCIATION 12 SOFT NEIGHBOR 13 NO SIG IMPROVEMENT 16 NO KEEPALIVE 17 LOST AUDIO 18 NO RESPONSE 19 NO PRIVACY 20 APP UNHAPPY 21 DISASSOCIATED 22 NO HANDOFF 23 HANDOFF 24 INITIAL ASSOC 25 LOST AP 26 TX FAILURES 27 CHANGING RATES 28 UNDEFINED 29 EAP START TIMEOUT 30 LEAP CHALLENGE TIMEOUT 31 EAP SUCCESS TIMEOUT
Data capture Reason code number Meaning 43 FAILED ACTION 44 DELTS 45 QOS REQUIRED 46 CHANGED LISTEN INTERVAL 213 Data capture Use the information presented in this section to begin capturing the correct data for analysis.
Appendix B Troubleshooting WLAN IP Telephony installations 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.
Data capture 215 • the TLAN and ELAN IPs for the Voice Gateway Media Cards (VGMC) • a network diagram For more information, see "Network diagram" (page 215).
Appendix B Troubleshooting WLAN IP Telephony installations 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 (SS).
Data capture 217 General data capture Before you run the show run-config or debug commands, enable text capturing on your Hyper terminal or Telnet application that you use to access the WLAN Security Switch 2270. 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.
Appendix B Troubleshooting WLAN IP Telephony installations 4 Start the wireless and wired sniffer captures. 5 Initiate a handset to handset regular call or Push-to-talk call. 6 Continue the voice conversation for 1 to 2 minutes. 7 End the call that you established in Step 5. 8 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.
Network speech levels 219 2 While the Config program is running, remove the battery pack and place the handset in the Configuration Cradle. 3 Open the File menu and select Get Assert Information. 4 Browse to the location to which you want to save the .asrt file. 5 Click Get Assert Data. The handset uploads the .asrt file to the location that you specified in Step 4. 6 Call Nortel Technical Support and make arrangements to e-mail the file and error message from the display.
Appendix B Troubleshooting WLAN IP Telephony installations Figure 35 Network speech levels Reference documents Table 30 "References" (page 220) lists reference documents and related-reading for this appendix. 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.
Reference documents 221 Source and type Title Revision Comments Nortel White Paper [QoE] Designing QoS-Enabled Networks for Voice & Data User Quality-of- Experience (QoE) (not applicable) (not applicable) Nortel Technical Solution Guide IP Telephony Client Deployment January 2006 Version 1.0 (not applicable) Nortel Technical Solution Guide Solutions Guide for VoWLAN January 2006 Version 1.
Appendix B Troubleshooting WLAN IP Telephony installations Source and type Title Revision Comments IEEE [802.11g] IEEE Std 802.11 Wireless LAN Medium Access Control and Physical Layer Specifications (not applicable) Further Higher Data Rate Extension in the 2.
Appendix C 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 01.02 Standard Release 5.
Index Symbols/Numerics 10 Mbs 73 50 ms 80 70 ms 80 802.1 pq 83 802.
Index 225 L Language 27 latency 80 Layer 2 port 83 Layer 2 QoS 83 Layer 2 switch port 83 Layer 3 port 83 locking the WLAN IP Telephony Manager 2245 115 loss plan 81 LTPS 111 M master WLAN IP Telephony Manager 2245 60, 60, 113 multicast addresses 65 Multicasting 65 N network segments 65 No ring 124 node 80 non-master WLAN IP Telephony Server 2245 60 Nortel WLAN Security Switch 178 Nortel WLAN Security Switch 2270 178 P remote endpoint 80 reset the WLAN IP Telephony Manager 2245 115, 115 RF basics 193 RL
Index W WLAN Wi-Fi Protected Access (WPA) 28 Wi-Fi Protected Access2 (WPA2) 28 Wired Equivalent Privacy (WEP) 28 configuration 183 WLAN applications 191 Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning NN43001-504 01.02 Standard Release 5.0 15 June 2007 Copyright © 2004-2007, Nortel Networks .
Nortel Communication Server 1000 WLAN IP Telephony Installation and Commissioning Copyright © 2004-2007, Nortel Networks All Rights Reserved. Publication: NN43001-504 Document status: Standard Document version: 01.02 Document date: 15 June 2007 To provide feedback or report a problem in the document, go to www.nortel.com/documentfeedback. Sourced in Canada The information in this document is subject to change without notice.
