Alcatel Voice over WLAN (R1.1.1) Design Manual

Alcatel Voice over WLAN (R1.1.1) Design Manual

Omnipcx enterprise – mobile ip touch
Table of Contents

Advertisement

Quick Links

Design Guide for the Alcatel OmniPCX Enterprise – Mobile IP Touch
Pre-Sales Communication
Voice over WLAN (R1.1.1) Design Guide
June 2005
ESD/ Central Pre Sales / DF/ JM
1/34
June 2005 – Ed 01
All rights reserved © 2004, Alcatel

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Voice over WLAN (R1.1.1) and is the answer not in the manual?

Questions and answers

Summary of Contents for Alcatel Voice over WLAN (R1.1.1)

  • Page 1 Design Guide for the Alcatel OmniPCX Enterprise – Mobile IP Touch Pre-Sales Communication Voice over WLAN (R1.1.1) Design Guide June 2005 ESD/ Central Pre Sales / DF/ JM 1/34 June 2005 – Ed 01 All rights reserved © 2004, Alcatel...
  • Page 2: Table Of Contents

    Design Guide for the Alcatel OmniPCX Enterprise – Mobile IP Touch Introduction & Objectives .....................4 1.1. Operational Components .....................4 1.1.1. OmniPCX Enterprise Applications Specific Elements ..........4 1.1.2. VoWLAN Infrastructure (SVP Server)................4 1.1.3. WLAN Infrastructure (Provided by Alcatel NIBU) ............5 1.1.4.
  • Page 3 Design Guide for the Alcatel OmniPCX Enterprise – Mobile IP Touch 3.2. Predictive Environment Solution Options (Responding to RFx) ........24 3.2.1. Manual Calculation of Predictive Coverage ............24 3.2.2. Predictive Tool Coverage Planning ...............25 Environment Verification & Validation .................25 4.1. Compliance with (R 1.1.1 Offer)..................25 4.1.1.
  • Page 4: Introduction & Objectives

    (such as financial considerations, deployment constraints, and business process limitations). Alcatel’s MIPT VoWLAN product offering is a multi-stage solution aimed at meeting customer demand for converged voice and data wireless environments based on 802.11 technologies. The R1.1.1 version of the MIPT suite is the result of leveraging existing OmniPCX Enterprise features with OEM products available in the Alcatel portfolio from Aruba, SpectraLink and others.
  • Page 5: Wlan Infrastructure (Provided By Alcatel Nibu)

    Design Guide for the Alcatel OmniPCX Enterprise – Mobile IP Touch 1.1.3. WLAN Infrastructure (Provided by Alcatel NIBU) OmniAccess 4304: Used to support a maximum of 4 AP. Equipped with eight 10/100 Ethernet ports (802.3af capable). Two different models providing either one 1000base-T...
  • Page 6: Server Elements (Dhcp, Tftp, Management)

    Alcatel openly recognizes the challenges faced by customers with existing 802.11 network implementations. For this reason, Alcatel also seeks to support Mobile IP Touch - Voice over Wireless Local Area Network solutions on a variety of approved third-party infrastructure architectures. Infrastructure vendors such as Aruba, Cisco (former Airespace product suite), Colubris and D-Link can possibly be used in lieu of Alcatel’s...
  • Page 7: Tftp Server

    TFTP Server requirements beyond standard TFTP protocol specifications to support MIPT terminals. It is possible to combine TFTP Server and DHCP Serer functions on a single external platform. Alcatel has validated the following TFTP Server platforms for use with MIPT solutions. Validated TFTP Server software platforms.
  • Page 8: Mobile Ip Touch Terminals

    1.1.5. Mobile IP Touch Terminals Alcatel makes two MIPT models available, one each for office and industrial use. The performance of these two handsets is very similar but their designs and options are focused for use in specific environments. Both of these terminals are products of an OEM partnership between Alcatel and Spectralink.
  • Page 9 Design Guide for the Alcatel OmniPCX Enterprise – Mobile IP Touch Swivel Clip for MIPT 300: Offering easy removal of battery, interchangeable clips for simple attachment to clothing. Charging Stands: The MIPT 300 and MIPT 600 each have an option for a model specific Charging Stand.
  • Page 10 Design Guide for the Alcatel OmniPCX Enterprise – Mobile IP Touch Configuration cradle: One MIPT set configuration at a time One slot per MIPT set type. MIPT set configuration via Windows-PC (RS-232 serial interface to PC). Direct upload or download from/to the MIPT set flash memory.
  • Page 11: Operational Modes And Considerations

    Being as no two customer network environments are exactly the same, it is critical for technology such as VoWLAN to possess a great degree of flexibility. Alcatel’s MIPT solution is not exempt from this requirement. The following section highlights some MIPT architectural adaptabilities.
  • Page 12: Appliance/Overlay Mode

    In Appliance Mode operation, Access Points are not directly attached to Alcatel OmniAccess Wireless Switches. In this type of operational mode, the Alcatel OmniAccess Wireless Switch acts only as an Access Point Controller and does not directly host AP via local 10/100 ports.
  • Page 13: Quality Of Service

    Design Guide for the Alcatel OmniPCX Enterprise – Mobile IP Touch Figure 2 OmniSwitch 6600-P24 (supporting IEEE 802.3af) Since the Access Points can not benefit from the Inline Power capabilities of the OmniAccess Wireless Switch, the Ethernet switch must be capable of supplying sufficient and standard format power (full 15W limit of IEEE 802.3af.) In the event that this can not be achieve, several options are available:...
  • Page 14: Security

    Security is always a sensitive topic to discuss, and opinions on how best to provide for it vary greatly from one engineer to the next. With this in mind, Alcatel is constantly developing the list of security options available within the MIPT VoWLAN solution offer to satisfy as many different opinions as possible.
  • Page 15: Authentication & Encryption

    Since all MIPT terminals must be manually configured with an SSID, the decision to enable or disable SSID broadcast is of little consequence to Alcatel MIPT terminals. There is no impact to ease of use or functionality presented by the state of SSID broadcast. Alcatel recommends that customers maintain their current or desired security policies governing this topic.
  • Page 16: Isolation Practices

    3.1. Pre Sale Data Collection In order to prepare an Alcatel VoWLAN solution, several pieces of documentation must be sourced from the customer. The accuracy of a final system proposal is directly related, in most cases, to the amount and quality of information collected prior to initiating design formulation.
  • Page 17: Logical Diagram

    Design Guide for the Alcatel OmniPCX Enterprise – Mobile IP Touch can be housed, to the type of physical connectors needed on the fiber patch cords to connect them to the network. To meet this requirement, the physical diagram must contain as much detail as possible.
  • Page 18: Floor Level Maps/Diagrams

    Design Guide for the Alcatel OmniPCX Enterprise – Mobile IP Touch Figure 5 IP Addressing Plan This call-flow diagram shows the logical paths for Voice and Data at Wireless and Wired level. Figure 6 Logical paths for Voice and Data 3.1.3.
  • Page 19: Customer Specific Application & Design Considerations

    3.1.4. Customer Specific Application & Design Considerations Due to the fact that Alcatel’s MIPT VoWLAN solution is being offered in a multi-stage fashion with evolving capabilities, it is important for the design engineer to compare expected customer usage patterns against current MIPT release restrictions before proposing an Alcatel MIPT VoWLAN solution.
  • Page 20: Mipt Offer Restrictions (R1.1.1)

    Design Guide for the Alcatel OmniPCX Enterprise – Mobile IP Touch 3.1.4.2. MIPT Offer Restrictions (R1.1.1) Before proposing an Alcatel MIPT VoWLAN solution, we must ensure that the customer environment can host the desired technology. This means ensuring the following: •...
  • Page 21 Alcatel’s MIPT VoWLAN R1.1.1 solution offers no support for voice compression. Only G.711 (without VAD) encoding is available. Alcatel offers no support for G.723 or G.729 on MIPT terminals at this time. This restriction applies to all MIPT call flows, even in inter-IP Domain communications where negotiated sessions will default to the higher bandwidth G.711 coding.
  • Page 22: Converged Wireless Environments

    Design Guide for the Alcatel OmniPCX Enterprise – Mobile IP Touch 3.1.4.3. Converged Wireless Environments One of the most significant reasons that businesses look to use wireless LAN technology to support voice is the desire to have a single infrastructure for both voice and data services. While this may at first sound like a very simple thing to implement, it often is far more complex to design than most customers originally anticipate.
  • Page 23 Customers seeking this type of solution can unify the infrastructure elements by using Alcatel’s OmniAccess product suite for both Wi-Fi formats. Alcatel’s OmniAccess 70 Access Point can be effectively leveraged to construct networks for both 2.4 GHz (802.11b/g) and 5 GHz (802.11a) networks simultaneously. For more detailed product information, visit http://www.alcatel.com/enterprise/en.
  • Page 24: Predictive Environment Solution Options (Responding To Rfx)

    Design Guide for the Alcatel OmniPCX Enterprise – Mobile IP Touch 3.2. Predictive Environment Solution Options (Responding to RFx) When answering an RFP or RFI, normally, there is little possibility of scheduling a Site Survey for various reasons: Building under construction or not yet built, short delay to answer the RFP, fair competition clause, etc.
  • Page 25: Predictive Tool Coverage Planning

    802.11 data clients with typical power and sensitivity specifications. It is for this reason that the use of predictive planning tools is not currently recommended by Alcatel. Even in the case of Alcatel's predictive planning tool, the unique operational characteristics of MIPT handsets can not be taken into full consideration, resulting in often flawed and under-engineered proposals.
  • Page 26: Exceptional Deal Handling

    Alcatel’s OmniAccess platform family can be used to support data as well as voice. For solutions that propose both voice and data coverage, it is important to distinguish between the needs of the voice and data elements.
  • Page 27: Design Examples

    Design Guide for the Alcatel OmniPCX Enterprise – Mobile IP Touch generated or roughly every 18 months. Some customers may be able to happily use VoWLAN technology in a static environment for many years without a renewed survey, others may find that continuous evolution of network demands require a validation every six months.
  • Page 28: Configuration For Up To 16 Ap (No Redundancy)

    Design Guide for the Alcatel OmniPCX Enterprise – Mobile IP Touch 5.2. Configuration for up to 16 AP (No redundancy) This configuration example depicts a model for up to 16 AP without a customer need for WLAN controller redundancy. Figure 12 Configuration for up to 16 AP (no redundancy)
  • Page 29: Configuration For Up To 16 Ap (With Redundancy)

    Unfortunately, the quotation process for the MIPT VoWLAN R1.1.1 solution is not as automated within ACTIS as many of Alcatel’s other voice technologies. For this reason, engineers are strongly encouraged to complete the framework of the target VoWLAN design prior to beginning the ACTIS process.
  • Page 30: References

    Access Points capable of supporting IEEE 802.11a as well as IEEE 802.11b/g. Alcatel also recommends that a measurable portion of Access Points deployed within the framework of most solutions be capable of supporting external antenna connection. The nominal increases in cost that these options may bring to a solution should be viewed as very inexpensive insurance against unforeseen future needs.
  • Page 31: Annex

    The correct placement for these Access Points The Site Survey tool is mainly used by Alcatel Professional Services and Business Partners. A site Survey is required every time it is needed to perform a quotation for VoWLAN implementation. a VoIP audit is also necessary.
  • Page 32: Call Handling

    Design Guide for the Alcatel OmniPCX Enterprise – Mobile IP Touch 8.2. Call Handling ESD/ Central Pre Sales / DF/ JM 32/34 June 2005 – Ed 01...
  • Page 33: Ip Flows

    Design Guide for the Alcatel OmniPCX Enterprise – Mobile IP Touch 8.3. IP Flows ESD/ Central Pre Sales / DF/ JM 33/34 June 2005 – Ed 01...
  • Page 34: Mipt Gatekeeper Ip Address In Dhcp Mode

    Design Guide for the Alcatel OmniPCX Enterprise – Mobile IP Touch 8.4. MIPT Gatekeeper IP address in DHCP mode ESD/ Central Pre Sales / DF/ JM 34/34 June 2005 – Ed 01...

Table of Contents