Avaya Communication Manager
Avaya Communication ManagerAvaya IP DECT Installation,Administration, and Maintenance16-601625Issue 1August 2006
2006 Avaya Inc.All Rights Reserved.NoticeWhile reasonable efforts were made to ensure that the information in thisdocument was complete and accurate at the time of printing, Avaya Inc. canassume no liability for any errors. Changes and corrections to the informationin this document may be incorporated in future releases.For full support information, please see the complete document,Avaya Support Notices for Software Documentation, document number03-600758.To locate this document on our Web site, simply go tohttp://www.avaya.com/support and search for the document number inthe search box.Documentation disclaimerAvaya Inc. is not responsible for any modifications, additions, or deletions tothe original published version of this documentation unless such modifications,additions, or deletions were performed by Avaya. Customer and/or End Useragree to indemnify and hold harmless Avaya, Avaya's agents, servants andemployees against all claims, lawsuits, demands and judgments arising out of,or in connection with, subsequent modifications, additions or deletions to thisdocumentation to the extent made by the Customer or End User.Link disclaimerAvaya Inc. is not responsible for the contents or reliability of any linked Websites referenced elsewhere within this documentation, and Avaya does notnecessarily endorse the products, services, or information described or offeredwithin them. We cannot guarantee that these links will work all of the time andwe have no control over the availability of the linked pages.WarrantyAvaya Inc. provides a limited warranty on this product. Refer to your salesagreement to establish the terms of the limited warranty. In addition, Avaya’sstandard warranty language, as well as information regarding support for thisproduct, while under warranty, is available through the following Web site:http://www.avaya.com/support.CopyrightExcept where expressly stated otherwise, the Product is protected by copyrightand other laws respecting proprietary rights. Unauthorized reproduction,transfer, and or use can be a criminal, as well as a civil, offense under theapplicable law.Avaya supportAvaya provides a telephone number for you to use to report problems or to askquestions about your product. The support telephone numberis 1-800-242-2121 in the United States. For additional support telephonenumbers, see the Avaya Web site: http://www.avaya.com/support.
ContentsChapter 1: Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Abbreviations and Definitions . . . . . . . . . . . . . . . . . . . . . . . .References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .779Chapter 2: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . .11About the Avaya IP DECT Solution . . . . . . . . . . . . . . . . . . . . . . . . . .11About the IP DECT base stations . . . . . . . . . . . . . . . . . . . . . . . . . . .12Avaya DECT Mobility Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . .13IP signalling and media stream . . . . . . . . . . . . . . . . . . . . . . . . . . . .14IP DECT base station Synchronisation. . . . . . . . . . . . . . . . . . . . . . . .17IP DECT base station channel capacity . . . . . . . . . . . . . . . . . . . . . . .20About the Handsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20About Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21System Capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Chapter 3: Installation and Configuration . . . . . . . . . . . . . . . . .23Avaya IP DECT system start up. . . . . . . . . .Startup of the IP DECT base stations . . . .Booting Overview . . . . . . . . . . . . .Startup of Avaya IP DECT Mobility Manager .ADMM in IP DECT base station mode . .ADMM in Host-Mode . . . . . . . . . . . .Installing the ADMM software . . . . . . .Configure Start Parameter . . . . . . . .To maintain the running ADMM on PC . .Booter . . . . . . . . . . . . . . . . . . . . .Booter versions . . . . . . . . . . . . . .DHCP client. . . . . . . . . . . . . . . . .DHCP REQUEST . . . . . . . . . . . . . .DHCP OFFER. . . . . . . . . . . . . . . .Retries . . . . . . . . . . . . . . . . . . .TFTP client . . . . . . . . . . . . . . . . .Application . . . . . . . . . . . . . . . . . . .Booter update . . . . . . . . . . . . . . .Mandatory options . . . . . . . . . . . . .Optional options . . . . . . . . . . . . . .IP DECT base station LED Status. . . . . . .State graph of the start up phases . . . . . .23232424242425252626262627272828282929303132Issue 1 August 20063
ContentsStatic local configuration of the IP DECT base station . . . . . . . . . . . . . . .33802.1Q Support . . . . . . . . . . . . . . . . . . . . . . .Avaya DECT Mobility Manager Requirements . . . . .ADMM running on an IP DECT base station . . . .ADMM running on a Linux Server . . . . . . . . .Principles and Parameter . . . . . . . . . . . . . . . .Why not VLAN ID 0 . . . . . . . . . . . . . . . . . . .VLAN and the Boot Phase of a IP DECT base station .DHCP . . . . . . . . . . . . . . . . . . . . . . . . .Local configuration of the IP DECT base stations.353535363636363637Configuring the Avaya DECT Mobility Manager . . . . .Service Login procedure . . . . . . . . . . . . . . .Licensing . . . . . . . . . . . . . . . . . . . . . . . .Definition of the License IP DECT base stationsGet and add the License Key and PARK numberSystem . . . . . . . . . . . . . . . . . . . . . . . . .System settings . . . . . . . . . . . . . . . . . .Rebooting the ADMM . . . . . . . . . . . . . . .User Account. . . . . . . . . . . . . . . . . . . .Time zones . . . . . . . . . . . . . . . . . . . . .SNMP . . . . . . . . . . . . . . . . . . . . . . . .Backup . . . . . . . . . . . . . . . . . . . . . . .IP Regions . . . . . . . . . . . . . . . . . . . . . . .IP DECT base station Configuration . . . . . . . . .DECT configuration . . . . . . . . . . . . . . . .States of an IP DECT base station . . . . . . . .IP Trunks . . . . . . . . . . . . . . . . . . . . . . . .Configuration of IP DECT handsets . . . . . . . . .System Features . . . . . . . . . . . . . . . . . . . .Voice Mail . . . . . . . . . . . . . . . . . . . . .Media Server System Features . . . . . . . . . .Digit Treatment . . . . . . . . . . . . . . . . . .Corporate Directory . . . . . . . . . . . . . . . .TFTP based Corporate Directory . . . . . . . . .WML . . . . . . . . . . . . . . . . . . . . . . . 5Chapter 4: Avaya Communication Manager . . . . . . . . . . . . . . . .67Usage and Important Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67ACM system administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .674 Avaya IP DECT Installation, Administration, and Maintenance.
ContentsChapter 5: Functional description . . . . . . . . . . . . . . . . . . . . .73Registration of Avaya 3701 and Avaya 3711 . . . . . . . . . . . . . . . . . . . . .73WML . . . . . . . . . . . . . . . . . .Pre-configured URL . . . . . . . .User Input of URLs . . . . . . . .Corporate Directory . . . . . . . .LDAP based Corporate Directory .TFTP based Corporate Directory .737374747475Message Waiting Indication for the 20DT HandsetAvaya system . . . . . . . . . . . . . . . . . .Avaya DECT Mobility Manager . . . . . . . . .Message sequence chart . . . . . . . . . . . .Configuration . . . . . . . . . . . . . . . . . .7676777878Chapter 6: Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . .79Booter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Checking the IP DECT base station Booter Version . . . . . . . . . . . . . .Manual Update of the IP DECT base station Booter . . . . . . . . . . . . . . .797980Static local configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Checking the local configuration . . . . . . . . . . . . . . . . . . . . . . . . .Removing the local configuration . . . . . . . . . . . . . . . . . . . . . . . .808081Avaya 3701 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Checking the Avaya 3701 Firmware Version. . . . . . . . . . . . . . . . . . .Upgrading the Avaya 3701 Firmware . . . . . . . . . . . . . . . . . . . . . . .818182Avaya 3711 maintenance and diagnosticAvaya 3711 Auto Call Test Mode . . .Avaya 3711 Auto Answer Test Mode .Avaya 3711 Site Survey Mode . . . .Avaya 3711 Master Reset . . . . . . .Change the Avaya 3711 Security PIN.858586878788Avaya 3711 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Checking the Avaya 3711 Firmware Version. . . . . . . . . . . . . . . . . . .Upgrading the Avaya 3711 Firmware . . . . . . . . . . . . . . . . . . . . . . .888889Site Survey Measurement Equipment . . . . . . . . . . . . . . . . . . . . . . . .92Diagnostic . . . . . . . . .Syslog . . . . . . . . .Telnet user shell . . . .Login . . . . . . . .Command overview9393949595.Issue 1 August 20065
ContentsIP DECT base station console commands .ADMM console commands . . . . . . . . .SNMP . . . . . . . . . . . . . . . . . . . . . . .DECT Monitor of the Avaya IP DECT System .96979798Appendix A: Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . .103Supported Codecs and Codec negotiation . . . . . . . . . . . . . . . . . . . . .103MIB-II . . . . . . . . .system (1) . . . .interfaces (2) . . .at (3) . . . . . . .ip (4) . . . . . . .icmp (5) . . . . . .tcp (6) . . . . . . .udp (7) . . . . . .egp (8) . . . . . .cmot (9) . . . . . .transmission (10)snmp (11) . . . . .104104105108108113115117118118118119WML Tags and Attributes supported . . . . . . . . . . . . . . . . . . . . . . . . .121Detailed overview:Avaya IP Phones and the ADMM/Avaya 3711. . . . . . . . . . . . . . . . . . . .122Protocols and Ports used by Avaya IP DECT System. . . . . . . . . . . . . . . .125.6 Avaya IP DECT Installation, Administration, and Maintenance.
Chapter 1: OverviewPurposeThis document describes the installation and administration of the Avaya IP DECT solutionusing Avaya DECT Mobility Manager version 1.x.x.Abbreviations and DefinitionsAbbreviationsACAuthentication CodeACMAvaya Communication ManagerADMMAvaya IP DECT Mobility ManagerADPCMAdaptive Differential Pulse Code ModulationCMCommunication ManagerDECTDigital Enhanced CordlessTelecommunicationDHCPDynamic Host Configuration ProtocolDSPDigital Signal ProcessorGAPGeneric Access ProfileIPEIInternational Portable Equipment IdentityIP Base StationIP DECT Base StationHTTPHyper Text Transfer ProtocolMSSFMedia Server System FeaturesOMMOpen Mobility Manager (same as ADMM)PARKPortable Access Rights KeyPPPortable Part (same as IP DECT handset)RFPRadio Fixed Part (same as IP Base Station)RTCPReal Time Control ProtocolIssue 1 August 20067
OverviewRTPReal Time ProtocolTFTPTrivial File Transfer ProtocolVLANVirtual Local Area NetworkDefinitionsDECTDigital Enhanced Cordless Telecommunication The standard (ETS 300 175) essentially specifies theair interface, known as the radio interface. Voice anddata can both be transmitted via this interface. Its key technical characteristics are:- Frequency range: approx. 1,880 – 1,900 GHz(approx. 20 MHz bandwidth)- 10 carrier frequencies (1,728 MHz spacing) with 12time slots each *)- Doubling the number of time slots (to 24) using theTDMA process- Net data rate per channel of 32 kbit/s (for voicetransmission using ADPCM)- Voice coding using the ADPCM method- Maximum transmission power of 10 mWGAPGeneric Access Profile GAP is the abbreviation for Generic Access Profile The GAP standard (ETS 300 444) is based on thesame technology as DECT, but is limited to the mostimportant basic features. This standard was created inorder to allow telephones of different vendors to beused on any type of DECT system. It thus representsthe smallest common denominator of allmanufacturer-specific variants of the DECT standard. An important limitation in the GAP standard is thatexternal handover is not possible. For this reasonconnection handover is used, which is supported byGAP terminals. The operation of GAP-capable telephones iscomparable to that of analogue terminals. For example,features can be called up via ‘*’ and ‘#’ procedures.HandoverHandoverA handover is similar to roaming, but occurs during anongoing call. A handover normally takes place ”in thebackground,” without disrupting the call (seamless handover).8 Avaya IP DECT Installation, Administration, and Maintenance
PurposeIPEIInternational Portable Equipment Identity 13-digit identification code for telephones Example: 00019 0592015 3 (the final digit is thechecksum). The code is represented in decimal form. This code is globally unique.PARKPortable Access Rights KeyAccess code for the handset. This code determines whether atelephone can access a particular DECT system. Used forunique selection of the system at enrolment.HandoverDECT base station networkingWhile in motion, the telephone performs ongoingmeasurements to determine which base station is bestreceived. The one that can be best received is defined as theactive base station. To prevent the telephone from rapidlyswitching back and forth between two base stations that canbe almost equally well received, certain threshold values arein effect. (similar to a Schmitt trigger circuit )References1. The TFTP Protocol (Revision 2), RFC 1350, July 19922. Avaya – Open Mobility configuration settings; KI CTB0062593. Product Requirements and System Architecture; Integrating DeTeWe IP DECT wireless intoAvaya Multi Vantage Solution utilising an IP infrastructure4. Product Requirements and System Architecture; Integrating DeTeWe IP DECT wireless intoAvaya IP Office utilising an IP infrastructure5. RFC 1156, Management Information Base for Network Management of TCP/IP-basedinternets, May 19906. RFC 1213, Management Information Base for Network Management of TCP/IP-basedinternets: MIB-II, March 19917. RFC 1450, Management Information Base for version 2 of the Simple NetworkManagement Protocol (SNMPv2), April 19938. http://www.simpleweb.org/ietf/mibs/index.html?sel IETF9. Avaya 3711 User Guide10. Avaya 3701 User Guide11. Avaya IP Telephone LAN Administrators GuideIssue 1 August 20069
Overview10 Avaya IP DECT Installation, Administration, and Maintenance
Chapter 2: IntroductionAbout the Avaya IP DECT SolutionThe DECT over IP system comprises the following components : IP DECT Base Stations distributed over an IP network and offering DECT as a wirelessinterface. ACM Media Server/Media Gateway as telephony system platforms DECT telephone: Avaya 3701 and Avaya 3711 wireless phones Avaya DECT Mobility Manager (ADMM): management interface for IP DECT Solution,which runs on either one of the IP DECT Base stations or on a dedicated LINUX serverThe following pictures give a graphical overview of the architecture of the Avaya IP DECTsolution:Media ServerMedia GatewayWeb Browser foradministration purposesIP DECT BaseStations256 max.The Media Server, Media Gateway, ADMM and the IP DECT base stations communicatethrough the IP infrastructure. The IP DECT base stations and the IP DECT handsetscommunicate over air, where the DECT GAP protocol is used or DECT GAP with proprietaryenhancements.Issue 1 August 200611
IntroductionAbout the IP DECT base stationsAll IP DECT base stations have the same hardware and software capabilities.One of the IP DECT base stations within an IP DECT installation may be chosen to operate notin the IP DECT base station only mode but in the Avaya DECT Mobility Manager (ADMM)mode. During installation, you will set one of the IP DECT base stations to ADMM mode, or youwill use a dedicated LINUX server running as an ADMM. The others are in the IP DECT basestation only mode.IP DECT base station only mode:Within that mode, the IP DECT base station converts IP protocol to DECT protocol and thentransmits the traffic to and from the Handsets over a DECT timeslot. On air the IP DECT basestation has 12 time slots, eight can have associated DSP resources for media streams, theremaining four time slots are used for example for control signalling between IP DECT basestations and the Handsets or for bearer handover.Groups of IP DECT base stations have to be built which are named Cluster. Within a Cluster IPDECT base stations are synchronised to enable a seamless hand over when a user crossesfrom one IP DECT base station’s zone of coverage to another. For synchronisation it is notnecessary for an IP DECT base station to communicate directly with all other IP DECT basestations in the system. Each IP DECT base station only needs to be able to communicate withthe next IP DECT base station in the chain. But it is preferable for an IP DECT base station tosee more than one IP DECT base station to guarantee synchronisation in the event that one ofthe IP DECT base stations fails.The four control signalling channels are also used to carry bearer signals that signal theHandset to start the hand over process. If the radio signal of another IP DECT base station isstronger than that of the current IP DECT base station, then the Handset starts the hand overprocess to the IP DECT base station that has the stronger signal as the user moves around thesite.Avaya IP DECT Mobility Manager (ADMM) mode:In this mode, an IP DECT base station functions as a regular IP DECT base station. Additionallyit is responsible for H.323 signalling between the IP DECT system and the telephony or mediaserver. Further on it takes management part of the IP-DECT solution. You designate an IPDECT base station as the ADMM by assigning an IP address to the IP DECT base station in theDHCP scope (see Mandatory options on page 29) or by setting the data via OM Configurator(see Static local configuration of the IP DECT base station on page 33). After an IP DECT basestation is designated as the ADMM, it starts the extra services on board (for example, t
Avaya Communication Manager Avaya IP DECT Installation, Administration, and Maintenance 16-601625 Issue 1 . This document describes the installation and administration of the Avaya IP DECT solution using Avaya DECT Mobility Manager version 1.x.x. . important basic features. This standard was created in
Avaya Avaya Aura Session Manager 7.0.0.0.700007 Avaya Aura System Manager 7.0.0.0.16266 Avaya Aura Communication Manager 7.0-441 Build 0.22477 Avaya Session Border Controller for Enterprise 7.-21-6602 Avaya G430 Media Gateway 37.19. Avaya 96x0 Phone (SIP) 2_6_14_5 Avaya 9608 Phone (SIP) 7.0.0 R39 Avaya 96x0 Phone (H.323) 3.230A
Avaya 4610SW IP Telephone (SIP) Avaya 4620SW IP Telephones (SIP) SIP version 2.2.2 Avaya 9620 IP Telephones (H.323) Avaya one-X Deskphone Edition 1.5 Avaya 9620 IP Telephones (SIP) Avaya 9630 IP Telephones (SIP) Avaya one-X Deskphone Edition SIP 2.0.3 Avaya one-X Desktop Edition (SIP) 2.1 Service Pack 2 Avaya 6408D Digital Telephone - Avaya .
Avaya IP Office solution A vaya IP Office 500 V2 Embedded Voicemail Avaya Web RTC Gateway Avaya one -X Portal Avaya IP Office Manager Avaya IP Office Analogue PHONE 8 Avaya IP Office VCM64/PRID U Avaya IP Office DIG DCPx16 V2 10.0.0.1.0 build 53 10.0.0.1.0 build 53 10.0.0.1.0 bui ld 3
Avaya S8300 Server with Avaya G700 Media Gateway Avaya Communication Manger 4.0 (R014x.00.0.730.5) Avaya 9650 IP Telephone Avaya one-X Deskphone Edition 1.5 (H.323) Avaya 9640G IP Telephone Avaya one-X Deskphone Edition 1.5 (H.323) Avaya 9640 IP Telephone
from Avaya to install and configure Avaya components. Configure the CTI Link on the Avaya CM A CTI Link (also known as a T-Link) between the Avaya Communication Manager and AES is required for communication of events via TSAPI. The Avaya CM can be configured via the Avaya Site Administration tool (GEDI) or through a telnet session.
Avaya PARTNER Advanced Communications System Avaya MERLIN MAGIX Avaya IP Office Avaya S8100 Media Server on Avaya G600 Media Gateway or CMC1 Gateway Avaya S8300 Media Server and an Avaya G700 Media Gateway Market Segment Small to Mid Stand Alone or Small of Large 2-48 stations Small/mid standalone Target 20-80 station size
avaya ip office Video Softphone aCm ip Softphone avaya ip agent avaya one-x Communicator avaya Communicator 2.1 avaya Communicator for microsoft lync 6.4.0.2 avaya one-x agent avaya aura agent desktop e169 media Station i2050 softphone Flare experience H175 Video phone 2 linK o
These Application Notes will outline a solution for using SIP as a trunk protocol between Avaya Aura Session Manager, Avaya Aura Communication Manager 5.2.1 and Avaya IP Office. As shown in Figure 1, the Avaya 96xx IP Telephone (H.323) and 2420 Digital Telephone are
