Avaya Communication Manager IP DECT Installation, Administration And Maintenance Manual
  1. Manuals
  2. Brands
  3. Avaya Manuals
  4. Software
  5. Communication Manager IP DECT
  6. Installation, administration and maintenance manual
Avaya Communication Manager IP DECT Installation, Administration And Maintenance Manual

Avaya Communication Manager IP DECT Installation, Administration And Maintenance Manual

With communication manager
Hide thumbs
Table of Contents

Advertisement

Quick Links

Avaya Communication Manager
Avaya IP DECT Installation,
Administration, and Maintenance
16-601625
Issue 1
August 2006

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Communication Manager IP DECT and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Avaya Communication Manager IP DECT

Summary of Contents for Avaya Communication Manager IP DECT

  • Page 1 Avaya Communication Manager Avaya IP DECT Installation, Administration, and Maintenance 16-601625 Issue 1 August 2006...
  • Page 2 Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone...

  • Page 3: Table Of Contents

    Chapter 3: Installation and Configuration ....Avaya IP DECT system start up......
  • Page 4 Local configuration of the IP DECT base stations....Configuring the Avaya DECT Mobility Manager ....
  • Page 5 Message Waiting Indication for the 20DT Handset ....Avaya system ........
  • Page 6 SNMP ........DECT Monitor of the Avaya IP DECT System ....

  • Page 7: Chapter 1: Overview

    Chapter 1: Overview Purpose This document describes the installation and administration of the Avaya IP DECT solution using Avaya DECT Mobility Manager version 1.x.x. Abbreviations and Definitions Abbreviations Authentication Code Avaya Communication Manager ADMM Avaya IP DECT Mobility Manager ADPCM...
  • Page 8 ‘*’ and ‘#’ procedures. Handover Handover A handover is similar to roaming, but occurs during an ongoing call. A handover normally takes place ”in the background,” without disrupting the call (seamless handover). 8 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 9: References

    References 1. The TFTP Protocol (Revision 2), RFC 1350, July 1992 2. Avaya – Open Mobility configuration settings; KI CTB006259 3. Product Requirements and System Architecture; Integrating DeTeWe IP DECT wireless into Avaya Multi Vantage Solution utilising an IP infrastructure 4.
  • Page 10 Overview 10 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 11: Chapter 2: Introduction

    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 server The following pictures give a graphical overview of the architecture of the Avaya IP DECT solution: Media Server...

  • Page 12: About The Ip Dect Base Stations

    One of the IP DECT base stations within an IP DECT installation may be chosen to operate not in 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 you will use a dedicated LINUX server running as an ADMM.

  • Page 13: Avaya Dect Mobility Manager

    ● - Corporate Directory (LDAP or TFTP based) - WML browser The Avaya DECT Mobility Manager (ADMM) may run on one of the IP DECT base station or on a dedicated Linux Server. Issue 1 August 2006...

  • Page 14: Ip Signalling And Media Stream

    IP DECT base station.The following figure illustrates this scenario. IP-Phone Media Server Media Gateway Primary Base Station ADMM Signalling (IP DECT Base Station in ADMM mode) Base Station Control RTP/RTCP 14 Avaya IP DECT Installation, Administration, and Maintenance...
  • Page 15 IP signalling and media stream To establish a call between two DECT handsets the same IP streams must be established like in the scenario before, except the IP phone is not involved. The following figure illustrates this scenario. Media Server Media Gateway ADMM (IP DECT Base Station...
  • Page 16 LAN to direct the voice to the secondary IP DECT base station, as shown in the following figure. IP-Phone Media Server Media Gateway Secondary Base Primary Base Station Station ADMM (IP DECT Base Station in ADMM mode) Signalling Base Station Control RTP/RTCP 16 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 17: Ip Dect Base Station Synchronisation

    IP DECT base station Synchronisation As the DECT set user moves into the next IP DECT base station zone of coverage, the DECT set detects that the IP DECT base station has a better signal strength. Again, the media stream from the IP phone cannot move to the secondary IP DECT base station, so the primary IP DECT base station uses the LAN to direct the voice to the new secondary IP DECT base station.
  • Page 18 If a IP DECT base station loses the synchronisation the IP DECT base station does not accept new calls ("Busy-Bit"). There is a delay of max. 3 minutes until the active calls on this IP DECT base station are finished. Then it tries to get synchronised again. 18 Avaya IP DECT Installation, Administration, and Maintenance...
  • Page 19 IP DECT base station Synchronisation An IP DECT installation is more reliable if a IP DECT base station can receive the signal from more than only one IP DECT base station, because the other signals are also used for synchronisation. Unreliable Installation R 101 R 102...

  • Page 20: Ip Dect Base Station Channel Capacity

    About the Handsets There are two models of Handsets: the Avaya 3711 and the Avaya 3701. A detailed description of the two phones an their local features is available with Avaya 3711 User Guide and Avaya 3701 User Guide. Also Avaya Kirk DECT phones (WT9620 and DT20) and standard 3 party DECT GAP phones function on the IP DECT solution.

  • Page 21: About Licensing

    About Licensing About Licensing The ADMM needs to be enabled with a license key, which depends on the MAC address of some IP DECT base stations in the DECT system. The license key needs to be entered / administered via the ADMM web administration interface. There are a sets of licenses with additional upgrade licenses .

  • Page 22: System Capacities

    IP DECT base stations are administered than licensed the DECT system will block the voice streams. System Capacities There is only one Avaya DECT Mobility Manager (ADMM) in the system. The capacities are depending on the platform, the ADMM is running on. ADMM running on a IP DECT base station: up to 256 IP DECT base stations can be controlled ●...

  • Page 23: Chapter 3: Installation And Configuration

    IP DECT base stations, IP DECT handsets and ACM Media Server ● a Redhat Enterprise 4.0 ES Linux Server, if it is decided not to run the Avaya DECT ● Mobility Manager on a IP DECT base station a TFTP Server ●...

  • Page 24: Booting Overview

    In this case the ADMM Software has to be installed on PC running with Linux Red Hat. The essential network settings the ADMM is working with are depending on the configuration of the PC Kernel. 24 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 25: Installing The Admm Software

    Avaya IP DECT system start up Once started, the ADMM is running permanently while not stopped and when ever the PC is running. In case of fatal errors or PC reboot, the OM recovers automatically. CAUTION: Be sure that the versions of the ADMM and the IP DECT base station software CAUTION: within your IP DECT installation are the same.

  • Page 26: To Maintain The Running Admm On Pc

    Booter Booter versions This documentation referring to IP DECT for Avaya is written for the Booter SW 3.2.x. But note, in test installations there may be some different versions of the booter SW in use: Booter version 2.1.y ●...

  • Page 27: Dhcp Request

    Avaya IP DECT system start up TFTP server mandatory ● Public Option 224: "OpenMobility” mandatory ● Public Option 225: VLAN ID optional ● Note: If local configuration via OM Configurator is set, these information will be read Note: from internal flash memory instead.

  • Page 28: Retries

    Public Option 228: Syslog server port optional ● DHCP Option 6: Domain Name Server optional ● DHCP Option 15: Domain Name optional ● DHCP Option 42: Network Time Protocol Server optional ● 28 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 29: Booter Update

    Avaya IP DECT system start up Note: If local configuration via OM Configurator is set, these information will be read Note: from internal flash memory instead. Booter update Automatic booter update Each application SW comes with the latest released booter SW. The application SW will update the booter automatically as long as the major release number of the booter SW has not changed, e.g booter SW 2.1.2 will not be automatically updated by booter SW 3.x.y, but booter...

  • Page 30: Optional Options

    The code for this option is 42. Its minimum length is 4, and the length MUST be a multiple of 4. Code Address 1 Address 2 +-----+-----+-----+-----+-----+-----+-----+-----+-- 42 | a1 | a2 | a3 | a4 | a1 | a2 | ... +-----+-----+-----+-----+-----+-----+-----+-----+-- 30 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 31: Ip Dect Base Station Led Status

    Avaya IP DECT system start up IP DECT base station LED Status The following diagram shows the led status of the IP DECT base station according to the different states during start-up. State LED state Remarks Booter RED on Wait for link up...

  • Page 32: State Graph Of The Start Up Phases

    2 seconds Application on / 50ms off Failure, i.e. connection to OMM lost Synchronize DECT LED green Application Failure, i.e. connection to OMM lost Up & running Change of the local configuration 32 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 33: Static Local Configuration Of The Ip Dect Base Station

    IP DECT base station. The parameters configurable via the OM Configurator comply with the DHCP option, please see section Avaya IP DECT system start up on page 23 for details. If local static configuration has been done, DHCP is not used anymore.
  • Page 34 Static local configuration on page 80. It is also be possible to reset all data at the IP DECT base station, please see section Removing the local configuration on page 81. 34 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 35: 802.1Q Support

    VLAN and the Boot Phase of a IP DECT base station on page 36). Avaya DECT Mobility Manager Requirements ADMM running on an IP DECT base station If the ADMM is running on an IP DECT base station the VLAN ID configured for the IP DECT base station is used for the ADMM.

  • Page 36: Admm Running On A Linux Server

    DHCP scopes are required (This procedure applies regardless of the Ethernet switch being used): The following scenario with arbitrary VLAN IDs details the steps a IP DECT base station would go through in a typical dual-VLAN implementation. 36 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 37: Local Configuration Of The Ip Dect Base Stations

    Configuring the Avaya DECT Mobility Manager Step A. DHCP scope within the naive VLAN: 1. IP DECT base station boots up and obtains an address on the native VLAN. 2. The data VLAN DHCP Public option 225 directs the IP DECT base station to go to voice VLAN.

  • Page 38: Service Login Procedure

    Administration of IP Regions, ● Administration of the attached IP DECT base stations, ● Administration of IP Trunks, ● Administration of the IP DECT handsets, ● Configuration of the System Features and ● 38 Avaya IP DECT Installation, Administration, and Maintenance...
  • Page 39 Configuring the Avaya DECT Mobility Manager Administration of the License options. ● If no user action takes place the ADMM logs out the user after 5 minutes. To logout from the system click at ‘Logout’. Note: If the browser is closed without logging out first the service access will be blocked Note: for 5 minutes for other clients.

  • Page 40: Licensing

    The License IP DECT base stations have to be defined in that manner as described in About Licensing on page 21. Press New button and add the MAC addresses of the License IP DECT base stations: 40 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 41: Get And Add The License Key And Park Number

    Configuring the Avaya DECT Mobility Manager If that has been done please wait for the green mark as shown by the next picture. Get and add the License Key and PARK number The second step is to go to the DeTeWe Website and enter the serial number generated by the first step along with a TAN from you documentation.

  • Page 42: System

    If the ADMM is running on an IP DECT base station and SNTP is not used, date and time can be configured at the ADMM. This has to be done to provide date and time to the Avaya 3711. The time zone, which is shown on this Web page, has been configured at the IP region section of the Web service.
  • Page 43 Configuring the Avaya DECT Mobility Manager The date and time will be provided by the ADMM to the Avaya 3711 if the Avaya 3711 initiates a DECT location registration. This will be done in the following cases: Subscribing at the ADMM ●...

  • Page 44: Rebooting The Admm

    ‘Reboot’. There is also the option to reset the configuration. User Account Initially the Avaya IP DECT Mobility Manager service is accessible via a build-in user account only. After initial installation or after removing the configuration file the user account is set to the user ‘craft’...

  • Page 45: Time Zones

    Configuring the Avaya DECT Mobility Manager Time zones The local time and date displayed on Avaya 3711 DECT handset devices depend on the IP region the handsets are located in. Each IP region is configured to a certain time zone (see also Backup on page 48).

  • Page 46: Snmp

    It does not indicate the running time of the operating system which does not correspond to the operational IP DECT base station state. This value does not make a statement about the DECT network. 46 Avaya IP DECT Installation, Administration, and Maintenance...
  • Page 47 Configuring the Avaya DECT Mobility Manager The SNMP agent responds to SNMPv1 and SNMPv2c read requests for the standard MIB-II objects. The MIB-II contains 11 object groups, which are described in MIB-II on page 104. The agent supports both SNMPv1 and SNMPv2c traps. It sends a 'coldStart' trap when it first starts up, and an enterprise-specific trap 'nsNotifyShutdown' when it stops.

  • Page 48: Backup

    (host where the browser application is executed) as well as to restore an older configuration. The configuration file is a checksum protected, compressed and readable file. Restoring a previously saved configuration will lead to a reset of the ADMM to take effect. 48 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 49: Ip Regions

    An IP Region is used to define a relation between a IP DECT base station and the IP Trunks which have to be used to communicate with the Avaya communication server. At least one region has to be administered before an IP DECT base station or IP trunk can be added.

  • Page 50: Ip Dect Base Station Configuration

    There are conditions where this is not possible, for instance with IP DECT base stations at remote locations. In this case the IP DECT base stations shall be grouped to different clusters. The Avaya DECT Mobility Manager will not try to synchronise IP DECT base stations over cluster borders.

  • Page 51: Dect Configuration

    Configuring the Avaya DECT Mobility Manager One IP DECT base station per cluster can be configured as master. The master is displayed in bold font. Each IP DECT base station is identified by its ethernet address (6 byte hex format, colon separated).

  • Page 52: States Of An Ip Dect Base Station

    For any IP DECT base station with activated DECT functionality this phase should last only for a few seconds after starting up the IP DECT base station. If this state lasts longer this may indicate an hardware failure. 52 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 53: Ip Trunks

    The IP address column displays the current IP address of an IP DECT base station. IP Trunks An IP Trunk defines a communication relation between an ADMM and an Avaya communication server for H.323 signaling. IP Trunks can be added to the system by pressing the ‘New’ button. A popup window appears providing the configuration of a new Trunk.
  • Page 54 Trunk. An IP Trunk could be deleted by pressing the trash can icon . A similar popup window asks for confirmation showing the current configuration of this IP Trunk. 54 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 55: Configuration Of Ip Dect Handsets

    Configuring the Avaya DECT Mobility Manager Configuration of IP DECT handsets At the IP DECT handsets web page all configured DECT handsets are sorted by their number. To keep the list concise, the complete list is split up into sub-lists containing up to 100 handsets.
  • Page 56 Installation and Configuration The type of the phone will be automatically detected in case of the Avaya 3701 and Avaya 3711. If the type of a phone can not be detected the type will be set to WT9620 automatically. If the type (WT9620, 20DT, GAP) of the phone is configured before subscription and the type can not be detected then the configured type will be used.
  • Page 57 Configuring the Avaya DECT Mobility Manager If the user wants to find a certain handset then the search function can be used. A click on the ‘Search’ button provides the following pop-up window. The user can enter the handsets’s number or IPEI. At least one parameter has to be set.
  • Page 58 The search function can also be used to get to the right sub-list in one step. To force an update of date/time, voice mail number or the (de)activation of MSSF items immediately at the Avaya 3711 press the ‘Update’ button. 58 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 59: System Features

    Configuring the Avaya DECT Mobility Manager System Features Voice Mail The Voice Mail number can be administered on ADMM which will be common for all subscribed DECT users. In case the Voice Mail number should be different for the DECT users it should be left blank on ADMM and have it set on the DECT sets.

  • Page 60: Media Server System Features

    To mute the telephone during the execution of some system feature set the corresponding mute flag. The menu items appear on the telephone display in the user selected language. By changing the language the menu items will be updated. 60 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 61: Digit Treatment

    Configuring the Avaya DECT Mobility Manager Digit Treatment The Digit Treatment replaces, deletes or inserts digits for numbers received by the LDAP based Corporate Directory or WML. This functions is region dependent. The digits are treated in two steps: At first all invalid characters like space or hyphens are removed from the number (e.g.
  • Page 62 In case of "none” the feature is inactive and no item for the corporate directory is displayed in the telephone menu. LDAP based Corporate Directory The fields for TFTP based Corporate Directory can be edited, if the Corporate Directory Type =LDAP is set: 62 Avaya IP DECT Installation, Administration, and Maintenance...
  • Page 63 Please note: SSL (default port 689) is not supported Root Directory ● The search base has to be edited (e.g. "ou=people,o=avaya.com” or "o=detewe group”). User Name and User Password ● User name or password may be filled, if requested by the LDAP Server. Otherwise an anonymous bind takes place.

  • Page 64: Tftp Based Corporate Directory

    Path and file; sequence of up to 127 characters, default: "nasystem/dir_list" The entries in the file look like: "John Smith,01983 562335", without ", and entries are separated by '\n'. The first element is the name and the second is the telephone number. 64 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 65: Wml

    Configuring the Avaya DECT Mobility Manager Update Interval (mandatory) ● The Corporate Directory is updated within the time interval (hours) by reading the lists automatically from the TFTP server. If zero is typed, no update will be done. Update (Button on top) ●...
  • Page 66 Installation and Configuration 66 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 67: Chapter 4: Avaya Communication Manager

    Multiple Locations feature set is limited and depending on the configuration of the ACM and IP DECT system. The Avaya 3711 user should use the ADMM’s AVAYA Menu for activating/deactivating ACM features if the station’s COS has the Console Permission turned off (set to `n`).
  • Page 68 Dial Access? y Busy Threshold: 255 Night Service: Queue Length: 0 Service Type: tie Auth Code? n Member Assignment Method: manual display trunk-group 100 Page 2 of 21 Group Type: isdn TRUNK PARAMETERS 68 Avaya IP DECT Installation, Administration, and Maintenance...
  • Page 69 ACM system administration Codeset to Send Display: 0 Codeset to Send National IEs: 6 Charge Advice: none Supplementary Service Protocol: a Digit Handling (in/out): overlap/enbloc Digit Treatment: insertion Digits: QSIG Value-Added? n Digital Loss Group: 18 Incoming Calling Number - Delete: Insert: Format: Disconnect Supervision - In? y...
  • Page 70 3: T00190 4: T00191 The DECT station administration should be XMOBILE Type and the Configuration set ● should be blank. The Avaya 37x1 DECT sets support ICON Message Waiting Type and 16x2 Length of Display: display station 4006001 Page 1 of 3...
  • Page 71 ACM system administration STATION Headset? n Speaker? n Mounting: d Floor: Cord Length: 0 Building: Set Color: ABBREVIATED DIALING List1: List2: List3: HOT LINE DESTINATION Abbreviated Dialing List Number (From above 1, 2 or 3): Dial Code: Line Appearance: call-appr Issue 1 August 2006...
  • Page 72 Avaya Communication Manager 72 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 73: Chapter 5: Functional Description

    ● If the registration was successful the name and the number occurs. WML is only available for the Avaya 3711. You can access a WML site with few key strokes: 1. Long press of the "Menu” soft key 2. Select WML Portal.

  • Page 74: User Input Of Urls

    Now you can navigate within the WML pages if the URL is a valid link to a WML server. Corporate Directory The corporate directory is only available for the Avaya 3711. You can access the Corporate Directory with few key strokes: 1.

  • Page 75: Tftp Based Corporate Directory

    Searches are enabled by: 1. Long press of the "Menu” soft key 2. Select Directory. 3. Press OK. (Or use the key as mentioned above.) 4. Enter a partly qualified string of that name, you are looking for. 5. Press OK. 6.

  • Page 76: Message Waiting Indication For The 20Dt Handset

    The idea for the Message Waiting Indication feature for 20DT handsets is to map the Avaya systems message indication to a call indication from the voice mail to generate a call log entry, so the user can retrieve this message by calling the voice mail entry.

  • Page 77: Avaya Dect Mobility Manager

    Avaya system switches off the message indication state. An entry in the call log can not be removed by the Avaya DECT Mobility Manager. This may confuse the user in certain situations like the voice mail was already retrieved if using another phone.

  • Page 78: Message Sequence Chart

    MWI OFF Set MWI state Configuration The following administration must be done in the Avaya DECT Mobility Manager for the Message Waiting Indication feature (please refer also to IP Trunks on page 53): Terminal type of 20DT telephone handset ●...

  • Page 79: Chapter 6: Maintenance

    Chapter 6: Maintenance Booter Booter update may be handled via DHCP Option 254 "UPDATE” (see Booter update page 29) automatically. In any case you may have direct control to booter SW, if you use a telnet user session. Checking the IP DECT base station Booter Version You can display the version information of the IP DECT base station booter using the telnet interface of an IP DECT base station.

  • Page 80: Manual Update Of The Ip Dect Base Station Booter

    2. Enter login: root and password: avaya12 3. Enter "local_db” The display will show the local configuration settings of the IP DECT base station. > local_db use_local_cfg=1 ip=172.30.111.234 subnet=255.255.0.0 siaddr=172.30.206.20 boot_file=/omm_avaya.tftp ommip=172.30.111.234 > 80 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 81: Removing The Local Configuration

    1. Short press the "Menu” soft key 2. Enter the following key sequence: R***76# 3. Select Version Number 4. Press OK. The display will show the software and the hardware level of the Avaya 3701 Issue 1 August 2006...

  • Page 82: Upgrading The Avaya 3701 Firmware

    Maintenance Upgrading the Avaya 3701 Firmware The Avaya 3701 download adapter has to be used to upgrade the Avaya 3701 firmware. Please observe the instruction for use which comes with your adapter. Connect the download adapter directly to a serial port on your PC and connect the plug-in power supply unit to the download adapter.
  • Page 83 Avaya 3701 Firmware Select the COM port to which you have connected the download adapter. Issue 1 August 2006...
  • Page 84 Maintenance Specify whether or not the update procedure should be logged. 84 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 85: Avaya 3711 Maintenance And Diagnostic

    Avaya 3711 Auto Call Test Mode You can put the Avaya 3711 in the "auto call test mode” with few keystrokes. In this mode the phone will call a specified number cyclically. You can use this feature to generate traffic for test purposes.

  • Page 86: Avaya 3711 Auto Answer Test Mode

    To stop the test, switch the phone off and on again. Avaya 3711 Auto Answer Test Mode You can put the Avaya 3711 in the "auto answer test mode” with few keystrokes. In this mode the phone will answer incoming calls automatically. You can use this feature together this phones in the "auto call test mode”...

  • Page 87: Avaya 3711 Site Survey Mode

    Avaya 3711 Site Survey Mode You can put the Avaya 3711 in the "site survey mode” with few keystrokes. In this mode the phone will display the IP DECT base stations and the actual field strength of the receiving signal in dBM.

  • Page 88: Change The Avaya 3711 Security Pin

    1. Short press the "Menu” soft key 2. Enter the following key sequence: R***76# 3. Select Version Number 4. Press OK. The display will show the software and the hardware level of the Avaya 3711 88 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 89: Upgrading The Avaya 3711 Firmware

    Avaya 3711 Firmware Upgrading the Avaya 3711 Firmware Connect Avaya 3711 to your PC’s serial interface via an specific download cable and start the installer program from your PC. Issue 1 August 2006...
  • Page 90 Maintenance If the Avaya 3711 is connected, the following mask appears: 90 Avaya IP DECT Installation, Administration, and Maintenance...
  • Page 91 Avaya 3711 Firmware If the connected Avaya 3711 is identified by the Installer, the Avaya 3711 is switched off Issue 1 August 2006...

  • Page 92: Site Survey Measurement Equipment

    One measuring base station with its own power supply ● One stand and mains adapter/battery for the base stations ● One reference telephone with special software ● Battery chargers, if necessary ● Spectrum analyser ● 92 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 93: Diagnostic

    DECT frequency range (approx. 1.9 GHz) Diagnostic Syslog The Avaya DECT Mobility Manager and the IP DECT base stations are capable of propagating syslog messages conforming to RFC 3164. This feature together with the IP address of a host collecting these messages can be configured.

  • Page 94: Telnet User Shell

    Each IP DECT base station (ADMM included) offers a lot of command within the telnet shell. Most of them are useful for diagnostic and may help experts, to resolve failures. Some commands can harm the system operation. 94 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 95: Login

    Open telnet session to the IP DECT base station ● Username is ‘iprfp’ ● Password is ‘crftpw’ ● Welcome to IP RFP OpenMobility Avaya Version x.y.z Fr Apr 29 12:34:06 CEST 2005 Release (BUILD 0) 172.30.111.232 login: iprfp Password: Welcome to the system usershell! 172.030.111.232 >...

  • Page 96: Ip Dect Base Station Console Commands

    - leave the IP-RFP console Please note the "spy” command, which enables you to increase the level of syslog messages. This should be only used by the support organization because it can harm the system operation. 96 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 97: Admm Console Commands

    Diagnostic ADMM console commands If you type "ommconsole” and you have opened the session on the ADMM IP DECT base station you are able to use the following ADMM related commands: Please note the "spy” command, which enables you to increase the level of syslog messages especially for subsystems of the ADMM.

  • Page 98: Dect Monitor Of The Avaya Ip Dect System

    DECT Monitor of the Avaya IP DECT System For a better error detection in the Avaya IP DECT system the DECT Monitor can be used. The DECT Monitor is an MS Windows based stand alone program. It provides the possibility to give a real time overview of the current IP DECT base station and telephone states in the Avaya IP DECT system.
  • Page 99 Diagnostic When all links have been established, the DECT data of the system are automatically read out and entered in the tables "RFP-Table" and "PP-Table". This procedure is called "Config Request". Next, the defined trace options (Event Mask) are sent to the ADMM. The options which are sent to the ADMM are always those which were active the last time the program was exited.
  • Page 100 Selecting the IP DECT base stations with the right mouse button the user can change visibility views and can even force a resynchronization of an IP DECT base station. 100 Avaya IP DECT Installation, Administration, and Maintenance...
  • Page 101 Diagnostic There are several optional child windows selectable. They are all listed below and give some more information about the Avaya IP DECT systems. Mostly they are statistics and for internal use only. Issue 1 August 2006...
  • Page 102 Maintenance 102 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 103: Appendix A: Appendix

    Supported Codecs and Codec negotiation Appendix A: Appendix Supported Codecs and Codec negotiation Like the CM the ADMM support silence suppression for G.711A and G.711MU, what isn't standard conform, but the ADMM doesn't support this feature for G.279 or G.729A. Here the G.729B/G.729AB codecs should be used to decrease the bandwidth.

  • Page 104: Mib-Ii

    MIB-II IP-Office IP DECT Standard G.729A SS G.729B (X)=> G.729AB (SID-Frames) (SID-Frames) G.729B SS G.729AB X(SID-Frames) X(SID-Frames) G.729AB SS G.723.1 5.3 G.723.1 5.3 SS X G.723.1 6.3 G.723.1 6.3 SS X X(SID-Frames) X(SID-Frames) MIB-II The following chapters describe the 11 object groups published in and 6.

  • Page 105: Interfaces (2)

    MIB-II sysName (5) An administratively-assigned name for this managed node. By convention, this is the node's fully-qualified domain name. sysLocation (6) The physical location of this node (e.g., "telephone closet, 3rd floor"). sysServices (7) A value which indicates the set of services that this entity potentially offers. The value is a sum. This sum initially takes the value zero, Then, for each layer, L, in the range 1 through 7, that this node performs transactions for, 2 raised to (L - 1) is added to the sum.
  • Page 106 -- generic SLIP ultra(29) -- ULTRA technologies ds3(30) -- T-3 sip(31) -- SMDS frame-relay(32) ifMtu (4) The size of the largest IP datagram which can be sent/received on the interface, specified in octets. 106 Avaya IP DECT Installation, Administration, and Maintenance...
  • Page 107 MIB-II ifSpeed (5) An estimate of the interface's current bandwidth in bits per second. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal bandwidth. ifPhysAddress (6) The interface's address at the protocol layer immediately "below"...
  • Page 108 IP gateways forward datagrams; Hosts do not (except those Source-Routed via the host). gateway(1) -- entity forwards datagrams host(2) -- entity does NOT forward datagrams 108 Avaya IP DECT Installation, Administration, and Maintenance...
  • Page 109 MIB-II ipDefaultTTL (2) The default value inserted into the Time-To-Live field of the IP header of datagrams originated at this entity, whenever a TTL value is not supplied by the transport layer protocol. ipInReceives (3) The total number of input datagrams received from interfaces, including those received in error. ipInHdrErrors (4) The number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors...
  • Page 110 The value of the least-significant bit in the IP broadcast address used for sending datagrams on the (logical) interface associated with the IP address of this entry. For example, when the Internet standard all-ones broadcast address is used, the value will be 1. 110 Avaya IP DECT Installation, Administration, and Maintenance...
  • Page 111 MIB-II ipAdEntReasmMaxSize (5) The size of the largest IP datagram which this entity can re-assemble from incoming IP fragmented datagrams received on this interface. ipRouteTable (21) The IP Route Table contains an entry for each route presently known to this entity. Note that the action to be taken in response to a request to read a non-existent entry, is specific to the network management protocol being used.
  • Page 112 An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1. 112 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 113: Icmp (5)

    MIB-II ipRouteInfo (13) A reference to MIB definitions specific to the particular routing protocol which is responsible for this route, as determined by the value specified in the route's ipRouteProto value. If this information is not present, its value should be set to the OBJECT IDENTIFIER { 0 0 }, which is a syntactically valid object identifier, and any conformant implementation of ASN.1 and BER must be able to generate and recognise this value.
  • Page 114 ICMP layer such as the inability of IP to route the resultant datagram. In some implementations there may be no types of error which contribute to this counter's value. icmpOutDestUnreachs (16) The number of ICMP Destination Unreachable messages sent. 114 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 115: Tcp (6)

    MIB-II icmpOutTimeExcds (17) The number of ICMP Time Exceeded messages sent. icmpOutParmProbs (18) The number of ICMP Parameter Problem messages sent. icmpOutSrcQuenchs (19) The number of ICMP Source Quench messages sent. icmpOutRedirects (20) The number of ICMP Redirect messages sent. icmpOutEchos (21) The number of ICMP Echo (request) messages sent.
  • Page 116 Information about a particular current TCP connection. An object of this type is transient, in that it ceases to exist when (or soon after) the connection makes the transition to the CLOSED state. 116 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 117: Udp (7)

    MIB-II tcpConnState (1) The state of this TCP connection. closed(1) listen(2) synSent(3) synReceived(4) established(5) finWait1(6) finWait2(7) closeWait(8) lastAck(9) closing(10) timeWait(11) tcpConnLocalAddress (2) The local IP address for this TCP connection. tcpConnLocalPort (3) The local port number for this TCP connection. tcpConnRemAddress (4) The remote IP address for this TCP connection.

  • Page 118: Egp (8)

    "type" is the symbolic value used for the media in the ifType column of the ifTable object, and "number" is the actual integer value corresponding to the symbol. No object defined in this group today. 118 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 119: Snmp (11)

    MIB-II snmp (11) Implementation of the snmp group is mandatory for all systems which support an SNMP protocol entity. Some of the objects defined below will be zero-valued in those SNMP implementations that are optimised to support only those functions specific to either a management agent or a management client.
  • Page 120 "ErrorStatus" component is "readOnly." snmpOutGenErrs (24) The total number valid SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the "ErrorStatus" component is "genErr." 120 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 121: Wml Tags And Attributes Supported

    ● Click to dial applications are supported using the <a>, <anchor>, <onevent> and <do> tags as detailed in Appendix C "Creating Web sites for the 4610 and 4620 IP Telephones” of the "Avaya IP Telephone LAN Administrators Guide” (Reference 11)

  • Page 122: Detailed Overview: Avaya Ip Phones And The Admm/Avaya 3711

    Appendix Detailed overview: Avaya IP Phones and the ADMM/Avaya 3711 Full details concerning the use of WML can be found in the "4600 Avaya IP Phone LAN Administrators Guide” (Reference 11) Attribute Supported by the Supported by 4610/4620 ADMM/Avaya 3711 <a>...
  • Page 123 Detailed overview: Avaya IP Phones and the ADMM/Avaya 3711 Attribute Supported by the Supported by 4610/4620 ADMM/Avaya 3711 <head> <i> <img> align height hspace localsrc vspace width <input> emptyok format maxlength name size tabindex title type value <meta> <noop> <onevent>...
  • Page 124 <refresh> <select> ivalue multiple name tabindex title value <setvar> name value <small> <strong> <table> <td> <template> onenterbackward onenterforward ontimer <timer> name value <tr> <u> <wml> {Universal xml:lang Attributes} class 3 of 3 124 Avaya IP DECT Installation, Administration, and Maintenance...

  • Page 125: Protocols And Ports Used By Avaya Ip Dect System

    Protocols and Ports used by Avaya IP DECT System Protocols and Ports used by Avaya IP DECT System Protocol IP DECT base station send IP DECT base station receive ADMM send ADMM receive Comments SRC port DST port SRC port...
  • Page 126 SNMP (Traps) > 64000 application DECTnetMonitor 8106 client port client port 8106 application RSXport (debug 38477 client port client port 38477 application tool) Additional protocols ICMP 2 of 2 126 Avaya IP DECT Installation, Administration, and Maintenance...
  • Page 127 Performance figures and data quoted in this document are typical, and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments to the detailed specifications at its discretion.
  • Page 128 Appendix 128 Avaya IP DECT Installation, Administration, and Maintenance...

This manual is also suitable for:

Ip dect

Table of Contents