Aastra NeXspan S Installation And Maintenance Manual
  1. Manuals
  2. Brands
  3. Aastra Manuals
  4. PBX
  5. NeXspan S
  6. Installation and maintenance manual
Aastra NeXspan S Installation And Maintenance Manual

Aastra NeXspan S Installation And Maintenance Manual

Ip dect service
Hide thumbs Also See for NeXspan S:
Table of Contents

Advertisement

Quick Links

DRAFT
IP DECT service
Installation and Maintenance Guide
NeXspan IP PBX
AMT/PTD/PBX/0062/1/2/EN
01/2007

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the NeXspan S and is the answer not in the manual?

Questions and answers

Related Manuals for Aastra NeXspan S

Summary of Contents for Aastra NeXspan S

  • Page 1 DRAFT IP DECT service Installation and Maintenance Guide NeXspan IP PBX AMT/PTD/PBX/0062/1/2/EN 01/2007...
  • Page 2 The user is reminded that the use of PBXs at workplace must be in accordance with the recommendations of the IT law in force. The user's attention is also drawn to any clauses applicable in laws relating to the confidentiality of calls transmitted by means of telecommunications.

  • Page 3: Table Of Contents

    C O N T E N T S INTRODUCTION ......................5 PURPOSE OF THIS DOCUMENT..................5 SCOPE ..........................5 AUDIENCE ..........................5 REFERENCE DOCUMENTS....................5 ABBREVIATIONS AND DEFINITIONS ................7 ABBREVIATIONS .........................7 DEFINITIONS ........................8 ABOUT THE IP DECT SERVICE................10 GENERAL INFORMATION ....................10 RULES AND LIMITATIONS FOR USE ................10 SPECIFICATIONS AND PERFORMANCES...............11 3.3.1 SPECIFICATIONS ..........................11 3.3.2 PERFORMANCES AND CAPACITIES..................11...
  • Page 4 3.13 M92X MOBILE TERMINALS....................30 3.13.1 PHYSICAL DESCRIPTION OF AN M92X MOBILE ..............30 3.13.2 CONFIGURING AN M92X MOBILE TERMINAL ................32 3.14 OPX MOBILE TERMINALS....................34 3.14.1 PHYSICAL DESCRIPTION OF AN OPENPHONE 27..............34 3.14.2 CONFIGURING AN OPENPHONE 27 ...................35 3.14.3 PHYSICAL DESCRIPTION OF AN OPENPHONE 28..............37 3.14.4 CONFIGURING AN OPENPHONE 28 ...................39 IMPLEMENTING THE IP DECT SERVICE ..............

  • Page 5: Introduction

    1.1 PURPOSE OF THIS DOCUMENT This document describes how to install and put into service the DECT service on an IP network associated with the following PBXs: • NeXspan S/L/D (F6) • NeXspan 50 and NeXspan 500 (F4) • NCS (F5) 1.2 SCOPE...
  • Page 6 DECT standards (ETSI standards): ETS 300-175: Digital European Cordless Telephone Common Interface ETS 300-176: Digital European Cordless Telephone approval test specification ETS 300-444: Digital European Cordless Telephone General Access Profile Electromagnetic compatibility: System components comply with the following safety and electromagnetic compatibility recommendations: ETS 300-329: Radio Equipment Systems;...

  • Page 7: Abbreviations And Definitions

    Digital Enhanced Cordless Telecommunications Equipment Installation Code Equipment Manufacturer Code iPBX range comprising NeXspan 50 and NeXspan 500 iPBX range comprising NeXspan L (XL), NeXspan S (XS) and NeXspan C (XC) Fixed Part Sub-number Generic Access Profile HTTP Hyper Text Transfer Protocol...

  • Page 8: Definitions

    2.2 DEFINITIONS DECT Digital Enhanced Cordless Telecommunications • The standard (ETS 300 175) basically specifies the air interface. Voice and data can both be transmitted via this interface. • Its basic technical characteristics are: • Frequency range: approx. 1,880 – 1,900 GHz (approximately 20 MHz bandwidth) •...
  • Page 9 While in motion, the PP continuously performs measurements to determine which RFP is best received. The best received RFP is defined as the active RFP. To prevent the PP from rapidly switching back and forth between two RFPs that can be almost equally well received, certain threshold values apply (similar to a Schmitt trigger circuit).

  • Page 10: About The Ip Dect Service

    3 ABOUT THE IP DECT SERVICE 3.1 GENERAL INFORMATION The IP DECT service is meant for NeXspan S/L/D, NCS, NeXspan 50 and NeXspan 500 PBXs. The IP DECT system contains the following items: ♦ The mobile terminal which gives the user access to PBX telephony features ♦...

  • Page 11: Specifications And Performances

    ♦ A single PARI number per IP DECT network ♦ All the radio fixed parts on a DECT network have the same PARI ♦ A DECT network may contain several DECT RFP clusters. 3.3 SPECIFICATIONS AND PERFORMANCES 3.3.1 SPECIFICATIONS ♦ Frequency range used for the air interface (handset/radio fixed part): 1,880 –...

  • Page 12: Openmobility Manager

    OPENMOBILITY MANAGER The OpenMobility Manager (OMM) performs the following tasks: ♦ Sending signals to the GSI gateway (IP Stimuli <-> DECT GAP) ♦ IP flow management ♦ Managing sync-over-air functions between RFPs ♦ System management and configuration interface OpenMobility Manager (OMM) may run on one of the RFPs or on a dedicated Linux server. 3.5 IP SIGNALLING Calls between an IP phone and a PP (portable DECT) To establish a call between an IP Phone and a PP, the following IP streams must be established...
  • Page 13 Calls between two PPs To set up a call between two PPs, the same IP streams must be established beforehand. RTP/RTCP streams are established directly between the RFPs managing the PPs, unless the PPs are connected to the same RFP. In this case, no RTP packets are transmitted on the LAN by the RFP.
  • Page 14 Handover during a call from a PP If the PP user is moving and the PP detects a stronger signal from another RFP, it starts the handover process. Upon completion of the handover process, the voice path between the IP phone and the PP is established: •...
  • Page 15 When the PP user moves to a radio coverage area with the next RFP, the PP detects a stronger signal and the handover process starts again. Upon completion of the handover process, the voice path between the IP phone and the PP is established: •...

  • Page 16: User Licence

    3.6 USER LICENCE The OMM must be enabled with a license key (user licence), which depends on the MAC address of some RFPs in the DECT system The license key is entered and managed via the OMM web interface There are several types of licences: ♦...

  • Page 17: Architecture

    3.7 ARCHITECTURE The different types of IP DECT service architectures are: ♦ A DECT network comprising one or more clusters ♦ Several DECT networks with one or more clusters each Note: One OMM per DECT network An RFP cluster consists of a set of synchronised RFPs (all the RFPs of the same cluster belonging to the same DECT network).

  • Page 18: Rfp

    LIMITATIONS: All the SIP (DECT/IP) subscriptions must be declared on the Call Manager with which the GSI gateway (SIP access point) is established. Therefore: If the GSI gateway (SIP access point) is located on an NCS (F5), the SIP subscriptions must be declared on F5.

  • Page 19: Rfp Synchronization

    RFP ONLY MODE In this mode, the RFP converts the data to be transmitted from IP format to DECT format (or vice- versa). Exchanges between the RFP and the PP take place on the air interface via the 12 available DECT time slots: ♦...
  • Page 20 When all the RFPs are started up, the first RFP to synchronise by receiving the radio signal over the IP frame will be considered as the reference RFP for the entire system. The synchronisation is then transmitted to all the RFPs over the air interface. The first RFP to synchronise in turn transmits a signal on the air and becomes the synchronisation source for the next RFPs, and so on.
  • Page 21 Unreliable installation R 101 R 102 R 103 R 104 R 105 R 106 R 107 R 111 R 110 R 109 R 108 Reliable installation R 101 R 102 R 103 R 104 R 105 R 106 R 107 R 111 R 110 R 109...

  • Page 22: Rfp 32 Ip

    3.9 RFP 32 IP 3.9.1 SPECIFICATIONS RFP 32 IP ♦ Power supply: remote power supply from a LAN network (IEEE 802.3af) or mains power supply module (see reference below) ♦ Working room temperature: -5°C to +45°C ♦ Relative humidity: 0% to 95% (without condensation) ♦...

  • Page 23: Rfp 34 Ip

    3.10 RFP 34 IP 3.10.1 SPECIFICATIONS ♦ Power supply: Remote power supply from the LAN (IEEE 802.3af) ♦ Working room temperature: -25°C to +55°C ♦ Relative humidity: 0% to 95% (without condensation) ♦ Storage temperature: -40°C to +70°C ♦ Consumption: 120mA ♦...

  • Page 24: Mobile Terminal M90X

    3.11 MOBILE TERMINAL M90X 3.11.1 PHYSICAL DESCRIPTION OF MOBILE TERMINAL M90X 3.11.1.1 DESCRIPTION The M90x mobile terminal comprises: ♦ The portable handset with its battery ♦ A charger ♦ A power supply cable and mains power unit ♦ A belt clip kit. For more detailed information, refer to document [3].Erreur ! Aucun nom n'a été...

  • Page 25: Configuring An M90X Mobile Terminal

    3.11.2 CONFIGURING AN M90X MOBILE TERMINAL 3.11.2.1 REGISTERING AN M90X MOBILE TERMINAL PRELIMINARY OPERATIONS Check that the mobile is not already registered. To cancel the previous registration, refer to the section “Cancelling the registration of an M90xx portable handset” Check that the handset has been declared on the OMM interface (see the section “Portable Parts”).
  • Page 26 Press the key to select base 1 2 3 4 5 6 7 8. Normally, 1 blinks and you just have to press the OK key. "Enter code" appears on the display Press OK . The set displays successively: • "Please wait"...

  • Page 27: M910 Mobile Terminals

    3.12 M910 MOBILE TERMINALS 3.12.1 PHYSICAL DESCRIPTION OF AN M910 MOBILE TERMINAL 3.12.1.1 DESCRIPTION The M910 mobile terminal comprises: ♦ a terminal ♦ a charging unit ♦ an adapter ♦ 3 AAA-NiMH batteries For more information on the use of an M910 mobile terminal, refer to document [15].Erreur ! Aucun nom n'a été...

  • Page 28: Configuring An M910 Mobile Terminal

    ♦ Locking keys ♦ Integrated directory supporting 50 alphanumerical entries ♦ Adjustable ring tone to distinguish internal calls from external calls ♦ Keypad keys 1 to 9 programmable in the memory for speed dialling (abbreviated numbers) ♦ Nine languages available: English, French, German, Spanish, Italian, Dutch, Norwegian, Swedish and Portuguese.
  • Page 29 Select the device to which this terminal must be attached. Press Esc to leave this mode. Note : After registering the mobile terminal, to change the PBX name and/or the Int No., use the selection "Menu, Device, OK, Save, OK, Opt, Edit; enter PBX name, OK; enter Int No., OK”.

  • Page 30: M92X Mobile Terminals

    3.13 M92X MOBILE TERMINALS 3.13.1 PHYSICAL DESCRIPTION OF AN M92X MOBILE 3.13.1.1 DESCRIPTION Although M92x and M90x mobile terminals are physically identical, M92x mobile terminals offer the following hardware and software enhancements: ♦ Introduction of new functions: • New graphical display •...
  • Page 31 3.13.1.2 SPECIFICATIONS ♦ Weight: 120 grams ♦ Dimensions: 135 x 58 x 19 mm. ♦ Autonomy: 10 hours talk time, 72 hours in standby mode. ♦ GAP compatibility (CTR22 standard). ♦ Charger: wall or mobile unit. ♦ Full graphic display: 3 lines x 12 characters with 14 icons. ♦...

  • Page 32: Configuring An M92X Mobile Terminal

    3.13.2 CONFIGURING AN M92X MOBILE TERMINAL 3.13.2.1 REGISTERING AN M92X MOBILE TERMINAL PRELIMINARY OPERATIONS Check that the handset is not already registered. To cancel the previous registration, refer to the section “Cancelling the registration of an M92xx portable handset” Check that the handset has been declared on the OMM interface (see the section “Portable Parts”).
  • Page 33 Declare Base number 12345678 Press the key to select base 1, 2, 3, 4 5, 6, 7 or 8. Confirm with the OK key. "Enter code" appears on the display Press OK . The set displays successively: • "Please wait" •...

  • Page 34: Opx Mobile Terminals

    3.14 OPX MOBILE TERMINALS 3.14.1 PHYSICAL DESCRIPTION OF AN OPENPHONE 27 3.14.1.1 DESCRIPTION The OPENPHONE 27 mobile terminal comprises the following items: ♦ A portable handset with its battery ♦ A charger ♦ A power supply cable and mains power unit ♦...

  • Page 35: Configuring An Openphone 27

    3.14.2 CONFIGURING AN OPENPHONE 27 3.14.2.1 REGISTERING AN OPENPHONE 27 PRELIMINARY OPERATIONS Check that the handset is not already registered. To cancel the previous registration, refer to the section “Cancelling the registration of an OPENPHONE 27 portable handset” Check that the handset has been declared on the OMM interface (see the section “Portable Parts”).
  • Page 36 Display the system on which the handset is registered by successively selecting “Menu/Local mode/System/Registration”. Select this system using the arrows and press “Options”. Select the “DELETE” line using the arrows. A warning message “SUR?” appears. Press “OK” to confirm the deletion. The message “No system”...

  • Page 37: Physical Description Of An Openphone 28

    3.14.3 PHYSICAL DESCRIPTION OF AN OPENPHONE 28 3.14.3.1 DESCRIPTION The OPENPHONE 28 mobile terminal comprises the following items: ♦ A portable handset with its battery ♦ A charger ♦ A power supply cable and mains power unit ♦ A belt clip kit ♦...
  • Page 38 ♦ Temperature for transport -25° C to +70° C (without battery) -25° C to +60° C (with battery) ♦ Protection class: protection IP54 against dust and splash. Accessories A/C adapter (Europe) A/C adapter (UK) Charger ‘’Plus” type charger Headset Case Memory card Memory card manager "Plus’’...

  • Page 39: Configuring An Openphone 28

    3.14.4 CONFIGURING AN OPENPHONE 28 3.14.4.1 REGISTERING AN OPENPHONE 28 PRELIMINARY OPERATIONS Check that the handset is not already registered. To cancel the previous registration, refer to the section “Cancelling the registration of an OPENPHONE 27 portable handset” Check that the handset has been declared on the OMM interface (see the section “Portable Parts”).
  • Page 40 3.14.4.2 CANCELLING THE REGISTERATION OF AN OPENPHONE 28 Display the system on which the handset is registered by successively selecting Menu/Local mode/System/Registration, using the interactive keys. Select this system using the t uarrows and press “Options”. Select the “DELETE” line using the t uarrows. A warning message “SUR?”...

  • Page 41: Implementing The Ip Dect Service

    4 IMPLEMENTING THE IP DECT SERVICE 4.1 PRINCIPLE To implement an IP DECT installation, a network infrastructure is required, which comprises at least the following items: ♦ The radio fixed parts (RFPs) ♦ The portable handsets (PP) ♦ The NeXspan iPBX associated with a GSI gateway ♦...

  • Page 42: Configuring The Dhcp Server

    4.2 CONFIGURING THE DHCP SERVER The following items must be taken into account in the DHCP server configuration: ♦ The number of RFPs to install, with their MAC address ♦ OMM if you are using a PC. The following DHCP server configuration information must be provided by the network administrator: ♦...

  • Page 43: Configuring The Tftp Server

    ♦ Option code 66 (TFTP server): IP address of TFTP server • •Option code 66 defined with the IP address type Optional options for each reservation ♦ Public option code 227: Syslog server IP address ♦ Public option code 226: port number of the Syslog server listened to. 4.3 CONFIGURING THE TFTP SERVER OMM software loaded on to the RFPs The installer must make the RFP software available to the administrator, who must install it on...

  • Page 44: Installing And Configuring The Omm

    4.4 INSTALLING AND CONFIGURING THE OMM 4.4.1 STARTING THE RFPS Prerequisites All the RFPs are connected to the network and powered (remotely from the network, or from the mains unit, depending on the model). All the RFPS are initialised at start-up through the downloading of the “RFP software” file ip_rfp.cnt from the TFTP server.
  • Page 45 LED RED ON Start-up wait for link up BOOTER LED red flashing 0.25 Hz LED red retry flashing 0.5 Hz DHCP no answer / offer not o.k. DHCP Wait for 60 seconds wait for reply LED red flashing 2.5 Hz TFTP File download TFTP failed...
  • Page 46 RFP LED status The RFP32 has three separate LEDs for red, orange and green to show the different states during start-up. The RFP31 has only one LED showing all LED states/colours. State LED state Remarks Booter (Startup) RED on Wait for link up Booter DHCP RED flashing 0.5 Hz Launch a DHCP request and wait...
  • Page 47 COMMUNICATION SET UP DURING START-UP BETWEEN THE DHCP, TFTP SERVERS AND THE OMM DHCP server DISCOVER (Broadcast, RFP @MAC) OFFER (@IP for RFP) TFTP server TFTP Request for omm_sip.tftp file BOOT loading omm_sip.tftp file loading Application End of transfer DHCP server APPLICATION DISCOVER (Broadcast, RFP @MAC)
  • Page 48 EXAMPLES First “DHCP DISCOVER” request from the RFP First “DHCP OFFER” reply from the DHCP server @IP RFP (195.196.1.204) TFTP server IP @I OpenMobility OMM IP @ (195 196 1 203) Page 48 01/2007 AMT/PTD/PBX/0062/1/2EN...
  • Page 49 Second “DHCP DISCOVER” request from the RFP Second “DHCP OFFER” reply from the DHCP server Page 49 01/2007 AMT/PTD/PBX/0062/1/2EN...
  • Page 50 OMM in RFP mode There is no initialisation difference between the RFP declared as OMM and the others. This RFP is OMM dedicated through DHCP request. OMM in host mode In this case the OMM software has to be installed on the PC running with Red Hat Linux. The network parameters with which the OMM works in this mode depend on this PC’s network configuration.
  • Page 51 4.4.1.1.3 AINTAINING THE RUNNING ON A The OMM is installed as a wizard and runs automatically at system start. You can start and stop the OMM on a shell as a root user with the command: /etc/init.d/omm_matra [start|stop|restart] You can log to the OMM command line interface via telnet on port 8107. Troubleshooting ♦...

  • Page 52: Connecting To The Omm Application (Openmobility Manager)

    4.5 CONNECTING TO THE OMM APPLICATION (OPENMOBILITY MANAGER) The installer connects via the web interface to the IP address of the equipment (RFP or Linux server PC) hosting the OMM application that manages the SIP DECT STIMULI signalling interface with the GSI gateway. Access to the service is limited to one active session at a time, and is password-protected.

  • Page 53: Licencing

    After login the following options are available: ♦ “System”: configuration of general IP DECT system parameters ♦ “Radio Fixed Parts”: adding, changing and deleting the Radio Fixed Parts ♦ “Portable parts”: configuration of the Portable Parts ♦ “Licensing”: view the licence settings or enter a new licence. If no user action takes place, the OMM logs out the user after 5 minutes.
  • Page 54 Note : During the initial configuration of the IP DECT system, the license is missing and a warning is displayed. Page 54 01/2007 AMT/PTD/PBX/0062/1/2EN...
  • Page 55 4.5.2.1 DEFINING THE RFP LICENCE The RFP licences must be defined as specified in the section “User licences”. ♦ Press the “New” button. ♦ Add the MAC addresses of the RFP licences: • If that has been done, please wait for the green mark(s). Page 55 01/2007 AMT/PTD/PBX/0062/1/2EN...
  • Page 56 4.5.2.2 OBTAINING AND ADDING THE LICENCE KEY AND PARK NUMBER The second step is to enter the serial number generated by the first step along with a transaction number (TAN) from your documentation. This will generate a licence key that has to be entered in the 3rd step.

  • Page 57: System

    4.5.3 SYSTEM 4.5.3.1 SYSTEM SETTINGS The system settings cover the global settings for the OpenMobility Manager application, such as the PBX IP address, the system name and a system-wide authentication code. Encryption is only available if RFP32/34 (not RFP 31/33) are used. Therefore, it can only be enabled if no RFP31/33 has been connected to the OMM.
  • Page 58 4.5.3.1.1 ESTARTING THE To restart the OMM select “System Settings”, then select “Restart”. 4.5.3.2 USER ACCOUNT During initial installation, the OMM application is accessible via the default OMM account. This account can be customised later by declaring a new “Username” and the associated password.
  • Page 59 4.5.3.3 SNMP To manage a large RFP network, an SNMP agent is provided for each RFP. This will give alarm information and allow an SNMP management system (such as HP Open View) to manage this network. All agents are configured in a central place. RFP dependent parameters like sysLocation and sysName are generated.
  • Page 60 The following parameters can be configured using the OMM web service: ♦ Read-only Community ♦ System Contact ♦ Activate Trap Handling ♦ Trap Community ♦ Trap Host IP Address The community names are used for both SNMPv1 and SNMPv2c. The RFP needs an initial OMM connection to receive its SNMP configuration. In case of reset, this configuration does not change.

  • Page 61: Rfp Configuration

    4.5.4 RFP CONFIGURATION All configured RFPs are listed by cluster according to their topographic relations. The RFPs are sorted by their Ethernet address. To ensure correct handover of a PP during a call, all involved RFPs must deliver the same clock signal to the PP.
  • Page 62 An RFP could be deleted by pressing the trash can icon . A similar popup window asks for confirmation showing the current configuration of this RFP. Page 62 01/2007 AMT/PTD/PBX/0062/1/2EN...
  • Page 63 4.5.4.1 DECT CONFIGURATION The DECT function for each RFP can be switched on/off. If the DECT function is active, the RFP can be added to a cluster. 4.5.4.2 STATUS OF AN RFP For each RFP, the status of the DECT subsystem is displayed. The statuses are: Synchronous The RFP is up and running.

  • Page 64: Configuration Of Portables Parts

    4.5.5 CONFIGURATION OF PORTABLES PARTS On the Portable Parts 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. The user can move back and forth in steps of 100 handsets. Since the browser function cannot be used to search for a certain handset in all sub-lists, a search function is available, which allows you to find a handset with a given number or IPEI.
  • Page 65 A similar popup window appears when configuring an existing PP by pressing the tool icon The only difference lies in the delete subscription checkbox. If this option is selected, the PP will be deleted. A PP can be deleted by pressing the trash can icon .
  • Page 66 4.5.5.1 SEARCHING FOR THE IPEI NUMBER ON THE DIFFERENT HANDSETS On Openphone 27 and 28 For Openphone 27 and 28 type handsets, the IPEI number is indicated in a specific menu: Using the interactive keys, successively select “Menu/Local mode/System/IPEI”. Click OK to confirm. The IPEI number is displayed.
  • Page 67 ♦ Click “CALC” to start the calculation. ♦ Note the value of the “EMC”, “PSN” and “CS” fields and enter it in the handset characteristics screen. Information about IPEI number conversion from hexadecimal to decimal The IPEI number is made up of two fields: IPEI = EMC (16 bits) + PSN (20 bits) •...
  • Page 68 Example of an IPEI number read on an M90xx and M92xx type handset Hexadecimal value read on the handset at the address in question (see the preceding paragraph for the address range): 007136B080 Check Digit 01811 0438400 EEEEE PPPPPPP DECIMAL REPRESENTATION Check digit: calculated from the sum of each digit and multiplied by its position in the character string modulo 11.

  • Page 69: Declaration On The Nexspan Ipbx

    4.6 DECLARATION ON THE NEXSPAN IPBX 4.6.1 PRINCIPLE Each DECT/IP handset is considered as an SIP type subscriber by the iPBX. The IP DECT (SIP) subscriber must be declared on the iPBX management interface (see also the NeXspan management documents). Each handset must be registered on the OMM interface (see the corresponding paragraph).
  • Page 70 4.6.2.2 PROCEDURE 1. Back up the OMM configuration file. 2. The backup file is saved as “config.omm.gz”. 3. Decompress this file into a work directory. 4. Open this file with the Windows Bloc note utility. Example: Data zone to recover 5.
  • Page 71 Example for the F6/F5 range The SIP-DECT-subscriber-specific data is extracted from the OMM backup file and inserted into an Excel file, which can be used by the SETUP WIZARD. Informationfrom SIP type the OMM declaration The SIP type subscriber must be added to this file, since this information is not specified in the file from the OMM.
  • Page 72 Example for the F4 range The SIP-DECT-subscriber-specific data is extracted from the OMM backup file and inserted into a file, which can be used by the RESEVD tool. Information from SIP type the OMM declaration The SIP type subscriber must be added to this file. This information is not specified in the file from the OMM.

  • Page 73: Decalring Sip Dect Subscribers Manually On The Ipbx

    4.6.3 DECALRING SIP DECT SUBSCRIBERS MANUALLY ON THE IPBX 4.6.3.1 F6/F5 RANGE Declare the SIP subscribers and their directory number. Menu 1.1.2.1 "Create logical subscribers" Refer to the F6/F5 range operating manuals. 4.6.3.2 F4 RANGE Refer to the F4 range operating manuals. Page 73 01/2007 AMT/PTD/PBX/0062/1/2EN...

  • Page 74: Omm Dect Monitor Tool

    4.7 OMM DECT MONITOR TOOL 4.7.1 DESCRIPTION DECT monitor can be used to improve error detection in the IP DECT system. DECT Monitor is an MS Windows-based standalone application. It gives a real-time overview of the current RFP and PP states in the IP DECT system. DECT Monitor offers the following features: ♦...
  • Page 75 Next, the defined trace options (Event Mask) are sent to the OMM. The options sent to the OMM are always those which were active the last time the application was exited. If the trace option ‘Transaction establish/release’ is activated, the OMM will deliver all existing transactions.
  • Page 76 displayed in the tables, they are always entered in the ‘FP/PP-Events' window and in the log file (provided that this is open). The following colour code is used for RFP-table display: ♦ RFP grey-blue RFP is not active (not connected or disturbance) ♦...
  • Page 77 It is possible to select several optional child windows. They are all listed below and give more information about the IP DECT systems. Most of them are meant for statistics and internal use only. Page 77 01/2007 AMT/PTD/PBX/0062/1/2EN...

  • Page 78: Deploying The Ip Dect Service

    5 DEPLOYING THE IP DECT SERVICE 5.1 DEPLOYMENT KIT If an IP DECT installation must be planned, the distribution of RFPs must meet the following requirements: RFP synchronisation; An appropriate coverage to ensure dialogue between the RFPs and the PP on the entire site. The deployment kit is used to conduct an appropriate study.

  • Page 79: Maintenance

    6 MAINTENANCE 6.1 PP TEST MODE 6.1.1 CHECKING THE OP27 FIRMWARE VERSION To display information concerning the PP version, proceed as follows: ♦ Using the interactive keys, successively select “Menu/Local mode and press OK. ♦ Select “System” (just to highlight it). ♦...
  • Page 80 PARK: 1F-10-FF-F0-21 RFP ID: 02* RFPI 10FFF21 02 Frame error PP: FP: -dBm Field strength RFP ID RPN 02 Phonebook Menu RFP ID: 02* *The ID of RFP with which the PP is currently associated. In this example, the PP is currently connected to RFP number 02. RFP 01 and 00 are also visible.
  • Page 81 ♦ Using the interactive keys, successively select “Menu/Local mode and press OK. ♦ Select “System” (just to highlight it). ♦ Enter the key sequence: ***76# ♦ Select Auto Answer. ♦ Press OK. ♦ Enter a number of seconds during which the phone shall ring before answering the call. ♦...

  • Page 82: Booter

    You can also read syslogs if you type the command ‘logread’ in the telnet user shell. 6.2 BOOTER The booter may be handled automatically via the DHCP Option 254 ‘UPDATE’ (see the corresponding chapter). In any case, you may have a direct command for the booter software, if you use a telnet user session.

  • Page 83: Telnet User Shell

    6.2.3 TELNET USER SHELL Each RFP (OMM included) offers a lot of commands within the telnet shell. Most of them are used for diagnosis and may help experts to resolve failures. Please note that some commands can harm the system’s operation. 6.2.3.1 LOGIN The procedure is as follows:...
  • Page 84 6.2.3.3 RFP CONSOLE COMMANDS If you type ‘ip_rfpconsole’ you can use the following commands on each RFP: IP RFP console commands: heap - shows heap buffer statistics help - Displays Command Help Table - adjust linear echo canceler parameters media - display state of media channels mutex - lists all created MXP mutexes...

  • Page 85: Snmp

    6.2.4 SNMP ♦ To manage a large network of RFP offers, an SNMP agent is provided for each RFP. ♦ The SNMP agent responds to SNMPv1, and SNMPv2c reads requests for the standard MIB-II objects. ♦ The agent supports both SNMPv1 and SNMPv2c alerts ('coldStart' , 'nsNotifyShutdown' , 'authenticationFailure’...

  • Page 86: Application

    ♦ The default gateway is taken from the router option (code 3). ♦ The TFTP server IP address is taken from the siaddr filed in the DHCP message. ♦ The boot image filename is taken from the file field in the DHCP message; if this field is taken, the default filename ‘iprfp.bin’...
  • Page 87 6.2.5.1.2 PDATING THE BOOTER AUTOMATICALLY SO AS TO CHANGE THE VERSION The update of booters with a release number change will be performed automatically when the DHCP client in the application receives a DHCP offer comprising public option 254 with a value ‘UPDATE’.

This manual is also suitable for:

Nexspan lNexspan dNexspan 50Nexspan 500Ncs

Table of Contents