EXP1240 Admin Guide Technical Reference Document Version 1.9 © July-2013 UNIDEN America EXP1240 Admin Guide, Version 2.
Trademarks UNIDEN and the combinations of its logo thereof are trademarks of UNIDEN America Other product names used in this publication are for identification purposes and maybe the trademarks of their respective companies. Disclaimer The contents of this document are provided in connection with UNIDEN products. UNIDEN makes no representations with respect to completeness or accuracy of the contents of this publication and reserves the right to make changes to product descriptions, usage, etc.
Contents EXP1240 System Guide ........................................................................................ Error! Bookmark not defined. Contents ............................................................................................................................................................ 3 1 About This Document ................................................................................................................................ 6 1.1 Audience ..............................
5.5 Network ................................................................................................................................................. 37 5.6 Management Settings Definitions ......................................................................................................... 41 5.7 Firmware Update Definitions ................................................................................................................ 43 5.8 Time Server ..........................................
10.3 DNS Server Installation/Setup ............................................................................................................. 97 10.4 DHCP Server Setup .............................................................................................................................. 97 10.5 TFTP Server Setup................................................................................................................................ 99 10.6 SIP Server Setup....................................
1 About This Document This document describes the configuration, customization, management, operation, maintenance and trouble shooting of the EXP1240 System (EXP1240 base, and EXP1240 handset) in UNIDEN generic mode. For customer specific modes refer to specific customer agreements, which describe the software operational deviations from this document. For handset detailed user guide refer to [1]. 1.
Chapter 7 Chapter 8 Chapter 9 10 Appendix A 11 Appendix B 12 Appendix C 13 Appendix D 14 Appendix E Registration Management Handsets Firmware Upgrade/Downgrade Management System Functionality Overview Basic Network Servers Configuration VLAN Setup Management EXP1240 Network Planning/Optimization Local central directory file handling Network Operations Learn how to register handset and extensions to base stations Provides the procedure of how to upgrade firmware to base stations and/or handsets and/or re
1.7 References/Related Documentation [1]: [2]: [3]: Handset operation Manual v0.5 How to Deploy EXP1240 System v1.1 Provisioning of EXP1240 System (4) 1.8 Document History Revision 2.0 Author KMR Issue Date 1-Oct-2013 1.9 KMR 17-July-2013 1.
2 Introduction – System Overview In a typical telephony system, the network setup is the interconnection between Base-stations, “fat” routers, repeaters, portable parts, etc. The back-bone of the network depends on the deployment scenario but a ring or hub topology is used. The network has centralized monitoring, and maintenance system. The system is easy to scale up and supports from 1 to 40 bases in the same network.
2.2 Components of EXP1240 System UNIDEN EXP1240 System is made up of (but not limited to) the following components: • At least one UNIDEN Base Station is connected over an IP network and using DECT as air-core interface. • UNIDEN IP DECT wireless Handset. • UNIDEN EXP1240 Configuration Interface; is a management interface for EXP1240 Wireless Solution. It runs on all IP DECT Base stations. Each Base station has its own unique settings. 2.2.
2.
3 Installation of Base Stations After planning the network, next is to determine the proper places or location the relevant base stations will be installed. Therefore, we briefly describe the how to install the base station in this chapter. 3.1 Package – Contents/Damage Inspection Before Package Is Opened: Examine the shipping package for evidence of physical damage or mishandling prior to opening.
3.2 UNIDEN Base station Mechanics The base station front end shows an LED indicator that signals different functional states of the base unit and occasionally of the overall network. The indicator is off when the base unit is not powered.
3.4 Installing the Base Station First determine the best location that will provide an optimal coverage taking account the construction of the building, architecture and choice of building materials. Next, mount the Base Station on a wall to cover range between 50 – 300 meters (i.e. 164 to 984 feet), depending whether it’s an indoor or outdoor installation.
3.5 Find IP address of Base Station To find IP address of the installed base station two methods can be used; Using handset Find IP feature or browser IPDECT feature. 3.5.1 Using handset Find IP feature On the handset press “Menu” key followed by the keys: *47* to get the handset into find bases menu. The handset will now scan for 8660 bases. Depending on the amount of powered on bases with active radios and the distance to the base it can take up to minutes to find a base.
3.6 Login to Base EXP1240 Configuration Interface STEP 1 Connect the Base station to a private network via standard Ethernet cable (CAT-5). STEP 2 Use the IP find menu in the handset (Menu * 4 7 *) to determine the IP-address of the base station by matching the MAC address on the back of the base station with the MAC address list in the handset. STEP 3 On the Login page, enter your authenticating credentials (i.e. username and password). By default the username and password is admin. Click OK button.
4 Making Handset Ready In this chapter we briefly describe how to prepare the handset for use, install, insert and charge new batteries. Please refer to an accompanying Handset User Guide for more information of the features available in the Handset. 4.1 Package – Contents/Damage Inspection Before Package Is Opened: Examine the shipping package for evidence of physical damage or mishandling prior to opening.
Damage Inspection: The following are the recommended procedure for you to use for inspection: 1. Examine all relevant components for damage. 2. Make a “defective on arrival – DOA” report or RMA to the operator. Do not move the shipping carton until it has been examined by the operator. The operator/regional representative will initiate the necessary procedure to process this RMA. They will guide the network administrator on how to return the damaged package if necessary. 3.
Handset Serial Number The serial number (IPEI/IPUI number) of each handset is found either on a label, which is placed behind the battery, or on the packaging label. First, lift off handset back cover and lift the battery and read the serial number. The serial number is needed to enable service to the handset. It must be programmed into the system database via the EXP1240 Configuration interface. Replace Battery Remove Back Cover from Handset. Remove the old battery and replace with a new one. 4.
5 EXP1240 Administration Interface The EXP1240 Administration Interface is also known as EXP1240 Configuration. It is the main interface through which the system is managed and debugged. The EXP1240 Configuration Interface is an in-built HTTP (s) Web Server service residing in each base station. This interface is user friendly interface and easy to handle even to a first time user. Note: Enabling secure web will decrease web server speed perceived by the user.
Extensions Servers Network Management Firmware Update Time Country Security Central Directory Multi cell Repeaters Statistics Configuration Syslog SIP Log Description This is the front end of the Base station’s HTTP web interface. This page shows the summary of current operating condition and settings of the Base station and Handset(s). Administration of extensions and handsets in the system On this page the user can define which SIP/NAT server the network should connect to.
Chapter: EXP1240 Administration Interface EXP1240 Admin Guide, Version 2.
5.2 Home/Status We describe the parameters found in the Welcome front end home/status of the EXP1240 Administration Interface.
5.3 Extensions In this section, we describe the different parameters available whenever the administrator is creating extensions for handsets. Note, it is not possible to add extensions if no servers are defined. As well the section describes the administration of extensions and handsets using the extension list and the extension list menu. Software supports customer configurations with and without the multiline feature. Section 5.3.1 describes “add extensions” without multiline and 5.3.2 with “multiline”.
Empty Mailbox Name Empty Mailbox Number Empty Server Server 1 IP Call waiting feature: Enabled Broadsoft Feature Event Package Disabled Forwarding Unconditional Number Empty Forwarding No Answer Number Empty Disabled Disabled 90 Forwarding On Busy Number Empty Disabled EXP1240 Admin Guide, Version 2.
5.3.1.1 Extensions list (no multiline) The added extensions will be shown in the extension lists. The list can be sorted by any of the top headlines, by mouse click on the headline link. Parameter Idx Extension Server Display Name IPEI State FW info FWU Progress Description Select / deselect for delete, register and deregister handsets Given extension is displayed Server IP or URL Given display name is displayed. If no name given this field will be empty Handset IPEI.
Screenshots In the below table each command is described. Actions Add extension Stop Registration Delete Handset(s) Register Handset(s) Deregister Handset(s) Description Access to the “Add extension” sub menu Manually stop DECT registration mode of the system. This prevents any handset from registering to the system Deregister selected handset(s), but do not delete the extension(s).
5.3.2 Multiline: Add extension With active multiline feature the system distinguish between extensions, physical handsets and maximum 4 lines. To add a physical handset first an extension must be available. The “add extension” is available from the Extension web top. Screenshot By pressing the link the “add extension” menu will appear. In the following the parameters are explained. Parameter Line Name Default Value(s) Empty Handset New Handset EXP1240 Admin Guide, Version 2.
Empty Authentication User Name Authentication Password Display Name Empty Mailbox Name Empty Mailbox Number Empty Server Server 1 IP Call waiting feature: Enabled Broadsoft Feature Event Package Disabled Forwarding Unconditional Number Empty Forwarding No Answer Number Forwarding On Busy Number Empty Empty Disabled Empty Disabled 90 Empty EXP1240 Admin Guide, Version 2.0 Proprietary and Confidential Handset phone number or SIP username depending on the setup.
The location selection feature, which is available in the add extension screen in non-multiline mode, is moved to edit handset from the handset and extension list. Edit handset screen is found by pressing the handset IPEI link. Screenshot Then maximum extensions supported per handset are 4. There are no restrictions for adding more, but only the first four will attempt to SIP register. 5.3.2.1 Multiline: Handset and extensions list Added handset and extensions will be shown in the extension list.
VoIP Idx Extension Display Name Server State X% : FWU ongoing Verifying X%: FWU writing is done and now verifying before swap ”Waiting for charger” (HS) / ”Conn. term. wait” (Repeater): All FWU is complete and is now waiting for handset/repeater restart. Complete HS/repeater: FWU complete Error: Not able to fwu e.g. file not found, file not valid etc Index of the configured SIP extensions. Select/deselect to start SIP registration or delete extension.
5.3.2.3 Multiline: Edit handset Use the mouse to click the handset IPEI link to open the handset edit window. In the handset edit view the handset SIP location can be fixed to either any or a specific base. Screenshot Default Value(s) ANY IPEI Handset IPEI AC Handset AC code Emergency Line No Emergency Line Selected Empty Emergency Number Description Specify a handset to be located at a specific base station or ANY base station.
Actions Add extension Stop Registration Description Access to the “Add extension” sub menu Manually stop DECT registration mode of the system. This prevents any handset from registering to the system Delete Handset(s) Deregister selected handset(s), but do not delete the extension(s). Register Handset(s) Enable registration mode for the system making it possible to register at a specific extension (selected by checkbox) Deregister Handset(s) Deregister the selected handset(s) and delete the extension(s).
Screenshot 5.4 Servers In this section, we describe the different parameters available in the Servers configurations menu. Maximum 10 servers can be configured. Parameter NAT Adaption Default value Disabled Registrar Empty EXP1240 Admin Guide, Version 2.0 Proprietary and Confidential Description To ensure all SIP messages goes directly to the NAT gateway in the SIP aware router. SIP Server proxy DNS or IP address Permitted value(s): AAA.BBB.CCC.
Empty Conference Server Empty Reregistration time 600 SIP Session Timers: Disabled Session Timer Values (s): 1800 SIP Transport Signal TCP Source Port UDP Disabled Secure RTP Disabled Secure RTP Auth Disabled RTP from own base station: Disabled Keep Alive Enabled Show Extension on Handset Idle Screen Hold Behaviour Enabled RFC 3264 EXP1240 Admin Guide, Version 2.
Disabled DTMF Signalling RFC 2833 Codec Priority G.711U G.711A G.726 RTP Packet size 20ms Chapter: EXP1240 Administration Interface Use Own Codec Priority the direction attribute is sendonly, recvonly or inactive dependant of the context RFC 2543: The ”old” way of 36nalyse36ng HOLD. The connection information part of the SDP is set to 0.0.0.0, and the direction attribute is sendonly, recvonly or inactive dependant of the context Default disabled.
5.5 Network In this section, we describe the different parameters available in the network configurations menu. 5.5.1 IP Settings Screenshot DHCP/Static IP Default Values DHCP IP Address NA Subnet Mask NA Default Gateway NA DNS (Primary) NA DNS (Secondary) NA EXP1240 Admin Guide, Version 2.0 Proprietary and Confidential Description If DHCP is enabled, the device automatically obtains TCP/IP parameters.
5.5.2 VLAN Settings Enable users to define devices (e.g. Base station, etc.) with different physical connection to communicate as if they are connected on a single network segment. The VLAN settings can be used on a managed network with separate Virtual LANs (VLANs) for sending voice and data traffic. To work on these networks, the base stations can tag voice traffic it generates on a specific “voice VLAN” using the IEEE 802.1q specification.
5.5.4 NAT Settings We define some options available when NAT aware routers are enabled in the network. Screenshot Parameter Enable STUN STUN Server Default Values Disabled NA STUN Bindtime Determine STUN Bindtime Guard Enable RPORT Enabled Keep alive time Description Enable to use STUN Permitted value(s): AAA.BBB.CCC.DDD (Currently only Ipv4 are supported) or url (e.g.: firmware.Uniden.net).
Parameter Use Different SIP Ports Default Values Disabled Local SIP port SIP ToS/QoS 5060 RTP port 50004 RTP port range RTP TOS/QoS 40 0x104 Chapter: EXP1240 Administration Interface 0xB8 Description If disabled, the Local SIP port parameter specifies the source port used for SIP signalling in the system. If enabled, the Local SIP Port parameter specifies the source port used for first user agent (UA) instance. Succeeding UA’s will get succeeding ports.
5.6 Management Settings Definitions The administrator can configure base stations to perform some specific functions such as configuration of file transfers, firmware up/downgrades, password management, and SIP/debug logs. Parameter Base Station Name: Management Transfer Protocol HTTP Management upload script Default value EXP1240 HTTP Management password Empty TFTP Empty EXP1240 Admin Guide, Version 2.
Configuration server address Base Specific File Multi Cell Specific File Empty Configuration File Download Disabled SIP Log Server Address Upload of SIP Log Empty Syslog Server IP-Address Syslog Server Port Syslog Level NA The file name must be the chain id of the system. E.g 00087b0a00b3.cfg Permitted value(s): Format of file is chain ID.
There are three ways of configuring the system. 1. Manual configuration by use of the Web server in the base station(s) 2. By use of configuration files that are uploaded from a disk via the “Configuration” page on the Web server. 3. By use of configuration files which the base station(s) download(s) from a configuration server. For further details refer to doc reference [3]. 5.
Empty Required Version base Empty Version of firmware to be upgraded (or downgraded) on handset type or repeater. Valid Input(s): 8-bit string length. E.g. 280 Note: Value version 0 will disable firmware upgrade for handsets and/or repeater Note: Two handset types must be serial firmware upgraded. First type 8630 then type 8430. Version of firmware to be upgraded (or downgraded) on Base station. Base units are referred to as gateways over here. Valid Input(s): 8-bit string length. E.g.
5.8 Time Server In this section, we describe the different parameters available in the Time Server menu. The Time server supplies the time used for data synchronisation in a multi-cell configuration. As such it is mandatory for a multi-cell configuration. The system will not work without a time server configured. As well the time server is used in the debug logs and for SIP traces information pages, and used to determine when to check for new configuration and firmware files.
Default Values Empty Allow broadcast NTP Refresh time (h) Checked Time Zone 0 Daylight Saving Time (DST) Disabled DST Fixed By Day Use Month and Date DST Start Month March DST Start Date 25 DST Start Time 3 DST Start Day of Week DST Start Day of Week, Last in Month DST Stop Month DST Stop Date Monday The window time in seconds within which time server refreshes. Valid Inputs: positive integer Refers to local time in GMT or UTC format.
5.9 Country The country setting controls the in-band tones used by the system. To select web interface language go to the management page.
5.10 Security The security section is used for loading of trusted certificates and for selecting if only trusted certificates are used. Furthermore, web password and use of secure web server (via HTTPS) can be configured. The Security web is divided into three sections: Certificates importing and activation, Password admin and Secure web server handling.
5.10.2 Password and Secure web In the below the password and secure web server parameters are defined. Screenshot Default Values Admin Admin Empty Empty HTTPS Disabled Description Can be modified to any supported character and number Can be modified to any supported character and number Change to new password Confirm password to reduce accidently wrong changes of passwords When enabled the web interface will work as a secure web server.
5.11 Central Directory and LDAP The EXP1240 System support two types of central directories, a local central directory or LDAP directory. 5.11.1 Local Central Directory Select local and save for local central directory. Parameter Local Default Values Local Server Empty Filename Empty Phonebook reload interval (s) 0 5.11.1.1 Description Drop down menu to select between local central directory and LDAP based central directory The parameter is used if directory file is located on server.
5.11.2 LDAP Select LDAP Server and save for LDAP server configuration. Screenshot Parameter LDAP Server Default Values LDAP Server Server Empty EXP1240 Admin Guide, Version 2.0 Proprietary and Confidential Description Drop down menu to select between local central directory and LDAP based central directory. LDAP Server is displayed when LDAP server is selected. IP address of the LDAP server. Valid Inputs: AAA.BBB.CCC.
Port Sbase Empty Empty LDAP filter Empty Bind Empty Password Name Empty Empty Work Number Empty Home Number Empty Mobile Number Empty The server port number that is open for LDAP connections. Search Base. The criterion depends on the configuration of the LDAP server. Example of the setting is CN=Users, DC=umber, DC=loc LDAP Filter is used to as a search filter, e.g. setting LDAP filter to (|(givenName=%*)(sn=%*)) the IP-DECT will use this filter when requesting entries from the LDAP server.
Default values Disabled System chain ID Empty Synchronization 60 sec time (s) Data Sync: Multicast Primary Data Sync IP Empty Multi cell debug None EXP1240 Admin Guide, Version 2.0 Proprietary and Confidential Description Enable this option to allow the Base unit to be set in multi-cell mode (can be set either as master or slave in the multi-cell chain system – refer to MAC-units in Chain section for details).
5.12.2 DECT System Settings Description of DECT Settings for Specific Base units is as follows: Screenshot Parameter DECT system RFPI Default values Not able Allow multi primary: Disabled Auto create multi primary: Disabled Auto configure DECT sync source tree Enabled Description This is a radio network identity accessed by all Base units in a specific multi-cell system. It composed of 5 octets. It is actually 5 different variables combined together.
Parameter Number of SIP accounts before distributed load Default Values 8 SIP Server support for multiple registrations per account Disabled Description The maximum number of handsets or SIP end nodes that are permitted to perform location registration on a specific Base unit before load is distributed to other base units. Note: A maximum of 8 simultaneous calls can be routed through each Base unit in a multi-cell setup. Permitted Input: Positive Integers (e.g.
DECT Sync source Connected: The relevant Base station(s) is online in the network Connection Loss: Base station unexpectedly lost connection to network This Unit: Current Base station whose http Web Interface is currently being accessed With setting “Auto configure DECT sync source tree” set to Enable, this three will automatically be generated. If manual configured the administrator should choose the relevant “multi cell chain” level its wants a specific Base unit be placed.
Screenshot: Example of part of DECT Chain tree with repeaters Screenshot: Example of part of DECT Chain tree with units in Base Group but not in tree by various reasons. Chapter: EXP1240 Administration Interface When a base or repeater has not joined the tree it will be shown with read background below the tree. EXP1240 Admin Guide, Version 2.
5.13 Repeaters Within this section we describe the repeater parameter, and how to operate the repeater. 5.13.1 Add repeater From repeaters web select “Add Repeater” Screenshot Then select “DECT Sync mode” Screenshot Parameters DECT sync mode Manually User controlled by manually assign “Repeater RPN” and “DECT sync source RPN”. The parameters are selected from the drop down menu. Screenshot EXP1240 Admin Guide, Version 2.0 Proprietary and Confidential Chapter: EXP1240 Administration Interface 5.13.
Parameters Idx IPEI RPN Description System counter Repeater unique DECT identifier SINGLE CELL SYSTEM: The base has always RPN00, first repeater will then be RPN01, second repeater RPN02 and third RPN03 (3 repeaters maximum per base) DECT sync source 5.13.1.2 MULTI CELL SYSTEM: Bases are increment by 2^2 in hex, means first base RPN00 second base RPN04 etc.
5.13.3 Repeaters list Parameters IDx RPN IPEI DECT sync Source DECT sync Mode State FW info FWU Progress Description Repeater unit identity in the chained network. Permitted Output: Positive Integers The Radio Fixed Part Number is an 8-bit DECT cell identity allocated by the installer. The allocated RPN within the EXP1240 must be geographically unique. Permitted Output: 0 to 255 (DEC) OR 0x00 to 0xFF (HEX) Contains the unique DECT serial number of the repeater.
5.14 Statistics The statistic feature is divided into four administrative web pages, which can be access from any base. 1. System 2. Calls 3. Repeater 4. DECT data All four views have an embedded export function, which export all data to comma separated file. By pressing the clear button all data in the full system is cleared. 5.14.1 System data The system data web is access by http://ip/SystemStatistics.html and data is organised in a table as shown in below example.
5.14.2 Call data The call data web is access by http://ip/CallStatistics.html and data are organised in a table as shown in below example. Screenshot The table is organised with headline row, data pr. base rows and with last row containing the sum of all base parameters.
5.14.3 Repeater data The table is organised with headline row, data pr. base rows and with last row containing the sum of all base parameters.
5.14.4 DECT data The DECT data web is access by http://ip/DectStatistics.html and data is organised in a table as shown in below example. Screenshot Chapter: EXP1240 Administration Interface Please note 3 frequencies are manually removed in the example system. EXP1240 Admin Guide, Version 2.
5.15 Settings – Configuration File Setup This page provides non editable information showing the native format of entire EXP1240 Configuration parameter settings. The settings format is exactly what is used in the configuration file. The configuration file is found in the TFTP server. The filename for the configuration server is .cfg. The configuration file is saved in the folder /Config in the TFTP sever.
0101000014 [N](01):accept called from task 7 0101000014 [N](01):TrelAccept success [4]. Listening on port 10010 0101000019 [N](01):RemCfg: Download request of Config/00087b077cd9.cfg from 10.10.104.63 using TFTP 0101000019 [W](01):Load of Config/00087b077cd9.cfg from 10.10.104.63 failed To dump the log simply copy and page the full contents. 5.17 SIP Logs This page shows SIP server related messages that are logged during the operation of the EXP1240 system.
6 Multi-cell Setup & Management This chapter seeks to describe how to install, add and synchronize one or multiple base stations to the network. There are two main procedures involved: 1) Proper placement of the base stations (which is called network dimensioning). The present chapter does not address this issue. Refer to Chapter 12 for details. 2) Creating and adding base station profiles to the network via the EXP1240 Configuration Tool (to form a multi-cell system).
6.1.1 Time Server Setup Navigate to the Time settings and configure it. Scroll on the left column and click on Time url link to Open the Time Settings Page. Use the PC time feature or enter the relevant parameters on this page and press the Save and Reboot button. Make sure there is contact to the “Time server” otherwise the Multi-cell feature will not work. You can verify whether the Time server is reachable af rebooting the base station by verifying the correct Time Server IP address is still in place.
6.1.3 Multi-cell Setup Click on Multi Cell URL link in the EXP1240 Configuration to view the current Multi cell settings status of the current base station. Brand new base stations have Multi cell system feature disabled by default. Chapter: Multi-cell Setup & Management STEP 7 EXP1240 Admin Guide, Version 2.
STEP 8 Next, the system administrator needs to create and Enable Multi Settings profile for the current base station. On the Multi Cell settings Page, choose Enable option from the drop down menu of the Multi cell system parameter. Enable the Multi cell debug option if the system administrator wants some Multi-cell related logs to be catalogued by the system. STEP 9 On the same Multi Cell Settings page > Enter the relevant values for System chain ID and Synchronization time (s) respectively.
The Multi Cell data synchronization ONLY works when the relevant Time Server is set in the system before Server/Subscriber profile is added or created. Refer to STEP 5. IMPORTANT: Base stations must be rebooted after the time server has been set. STEP 10 Repeat STEP 1-9 as explained above for each base stations. IMPORTANT: It takes up to 5 minutes (synchronization time) to add a new base station to a Multi Cell System. 6.
Navigate back to the Multi cell settings page by clicking Multi-cell URL link at the left column. The revised Multi cell settings page shows the relevant base stations synchronized together. By default, the system uses the first registered base station as the master base unit. STEP 13 On the Multi-cell settings page, scroll to the DECT system settings and Enable or Disable the “Auto configure DECT sync option source tree” (See description in the table below).
6.3 Summary of Procedure – Creating a Chain We enumerate the short version of how to add 3 base stations units in a multi-cell setup. This can be applied for up to 40 base units. This procedure is divided into four (4) main stages. Apply this procedure if all base units are straight from production. 6.3.1 Stage 1 Skip this stage if relevant base stations are already in the network. a) Add 3 base stations i.e.
6.4 Practical Configuration of Multi-cell System In this chapter we describe what exactly to configure in the EXP1240 Configuration Interface ensure these scenarios really work. 6.4.1 Case ##1: Isolated Buildings Disable Multi Cell option of Base Stations EXP1240 Admin Guide, Version 2.0 Proprietary and Confidential Chapter: Multi-cell Setup & Management The optimal configuration for isolated buildings is standalone base stations setting. In this setting, you must: A.
6.4.2 Case ##2: Location with co-located partners Example includes Department shops, Retail location with co-located photo kiosk or pharmacy, etc. To illustrate this setup, two slave base stations are synchronised to one master base in the two office blocks. Here is diagram to illustrate Case ##2. The procedure: STEP 1 Follow the steps described in section 0 STEP 2 On the Network page of each base define the DECT sync source settings as illustrated in the table below.
6.4.3 Case ##3: Large to Medium Sized Enterprises In this scenario, we have five slave bases synchronised to one master base. The master base is located in office block B while the slave bases are spread across the whole enterprise. No base station is deployed in the lift because it has high attenuation properties that will drastically reduce radio signals.
6.4.4 Case ##4: Large Enterprises at Different Locations The procedure: STEP 1 Follow the steps described in sections 6 STEP 2 On the Network page of each base define the DECT sync source settings as illustrated in the table below. STEP 3 Save and reboot each base to complete case ## 4 setup STEP 4 Important for this configuration is to enable “Allow multi primary” on the multi cell page.
XX XX:XX:XX… XXX.XXX… Connected 3: RPN:0C 10 XX XX:XX:XX… XXX.XXX… Connected 3: RPN:0C 14 XX XX:XX:XX… XXX.XXX… Connected 4: RPN:10 18 XX XX:XX:XX… XXX.XXX… Connected 6: RPN:18 1C XX XX:XX:XX… XXX.XXX… Connected 6: RPN:18 20 XX XX:XX:XX… XXX.XXX… Connected 7: RPN:1C Primary for Offices Primary for Enterprises Chapter: Multi-cell Setup & Management 0C EXP1240 Admin Guide, Version 2.
7 Registration Management - Handset In this chapter we briefly describe how to register handsets in the EXP1240 Network. A precondition for handset registration is a proper configured single or multi-base system. For this refer to chapter 6.1. 7.1 Register handset to base (non multiline) This section describes how to register the wireless handset to the base station. NOTE: Minimum one server must be registered to the base (system), otherwise a handset cannot be registered to the system.
Start the registration procedure on the handset by following step “a” to “d” below. a) Select main menu “Connectivity” c) Type in the “AC code” and press “OK” to start the registration. The default AC code is “0000”. b) Select menu ”Register” d) After a while the handset is registered, and the idle display is shown. NOTE: The unique handset IPEI is displayed on sheet “Extensions” when the handset is successfully registered.
7.2 Register handset to base (multiline) This section describes how to register the wireless handset to a system with active multiline feature. NOTE: Minimum one server must be registered to the base (system), otherwise a handset cannot be registered to the system. Please see chapter 6.1.2. STEP 1 Login to a base station. STEP 2 Select “Extensions” URL and click “Add extension” link STEP 3 Fill out the form and click “Save”.
c) Type in the “AC code” and press “OK” to start the registration. The default AC code is “0000”. b) Select menu ”Register” d) After a while the handset is registered, and the idle display is shown STEP 6 Confirm the registration from the unique handset IPEI is displayed in column “IPEI” when the handset is successfully registered.
STEP 8 Confirm the SIP registration by SIP State in right column. Chapter: Registration Management - Handset Note: The web page must be manually updated by pressing “F5” to see that the handset is SIP registered; otherwise the handset SIP state isn’t displayed on the web page. EXP1240 Admin Guide, Version 2.
7.3 Register handset to base and specific extension (multiline) This section gives an example of controlling handset registration to a specific extension. STEP 1 Login to a base station. STEP 2 Select “Extensions” URL and click “Add extension” link STEP 3 Fill out the form and click “Save”. In the example below we add the extension “2512” with display name “Reserved” STEP 5 Enter the IPEI of handset which must register to this particular extension and press “Save” EXP1240 Admin Guide, Version 2.
STEP 6 STEP 7 STEP 8 Check mark the handset Idx in left column and press “Register Handset(s)” With the handset run the handset registration procedure using AC code “0000” Confirm the registration success by “Handset State” column. Note: It is possible with similar procedure to register using a different AC code than 0000 simply by changing the AC code in step 5.
8 Firmware Upgrade Procedure This step-by-step chapter describes how to upgrade or downgrade base station(s) and/or handset(s) / repeater (s) to the relevant firmware provided by UNIDEN. 8.1 Network Dimensioning In principle, a number of hardware and software components should be available or be satisfied before base station/handset update can be possible.
The admin from the service provider’s side must create the relevant firmware directory in the server where both old and new firmware(s) can be placed in it. (See the STEP above) Chapter: Firmware Upgrade Procedure EXP1240 Admin Guide, Version 2.0 Proprietary and Confidential 87 8.
8.3.1 Base: On the TFTP server root, create directory “Beatus”. Copy Base station firmware to the named directory. IMPORTANT: The BeatUs directory name cannot be changed. 8.3.2 Handsets/Repeaters: On the TFTP server root, create directory “Pegasus” or “Raffle” or “Razor” or “DECT4024” depending on type. IMPORTANT: The Raffle, Pegasus, DECT4024 directory names cannot be changed. EXP1240 Admin Guide, Version 2.
8.4 Firmware Update Settings Scroll down and Click on Firmware Update URL link in the EXP1240 Configuration Interface to view the Firmware Update Settings page. Type IP address and firmware path followed by save. For Http download the firmware update server settings must be entered as follows: On the Firmware Update Settings page > scroll down to the Update Gateways section > Enter the relevant firmware version of the base station to upgrade or to downgrade. Enter 202 for base version V0202.
After entering required version choose Start update button > select OK button from the dialog window to start the update/downgrade procedure. The relevant base station(s) will automatically reboot and retrieve the firmware specified from the server and update itself accordingly. The base firmware update behaviour is: Base will fetch the fwu file for approximately 3 minutes, then reboot and start flashing the LED - indicated by LED fast flashing for approximately 3 minutes and reboots in new version.
The log window of the TFTP server: 8.6 Handset(s) and Repeater Firmware Upgrade NOTE: To disable handset/repeater firmware process type version 0 in the required version field, followed by the save button. It is recommended to use version 0 after all units are upgraded. NOTE: For handset TFTP/HTTP download only one handset type can be downloaded at the same time. In case two handset models are defined for fwu at the same time fwu will fail. 8.6.
Handset firmware update time from start to complete takes minimum 40 minutes. 8.6.2 Monitor Repeater firmware upgrade Repeater firmware upgrade status is monitored on the Repeater page, right column. Repeater firmware upgrade time from start to complete takes minimum 20 minutes. 8.6.3 Verification of Firmware Upgrade The firmware upgrade is confirmed by the FWU Progress status in the second and first right column on the handset extension list or repeater list.
9 Functionality Overview So far we have setup our EXP1240 System. Next, in this chapter we list what features and functionalities are available in the system. The EXP1240 System supports all traditional and advanced features of most telephony networks. In addition, 3rd party components handle features like voice mail, call diversion, conference calls, etc.
Components System Features Support for re-INVITE Support for fail-over SIP proxy Message Waiting Indication Support for “302” response between UA ! SIP Server Internal Synchronization Internal Synchronization lock, timing and transmission Management Features Assignment of Base-stations Logging calls and internal events, and tracking use of resources Logging system faults TFTP server for software upgrade.
RFC3892 RFC3960 RFC4475 SIPS SRTP Web server The Session Initiation Protocol (SIP) Referred-By Mechanism Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP) Session Initiation Protocol (SIP) Torture Test Messages Will limit number of active calls pr. base when enabled. Embedded web server HTTP/HTTPS Automatic DST Tone Scheme Ethernet features VLAN DHCP Support Static IP TLS 1.0 TFTP HTTP HTTPS TCP/IP/UDP SNTP Quality of service DHCP option DNS srv DECT DECT CAP CAT-IQ v1.
Call log Phone Book Chapter: Functionality Overview DND Call Forward Multiple calls Call identification Calling Name Identification Presentation (CNIP) Calling Line Identification Presentation (CLIP) Call Hold List of registered handsets 50 mixed between Incoming, outgoing, missed calls Common Phonebook with up to 3000 entries (Import via csv format) Common Phonebook LDAP V2.
Appendix 10 Appendix A: Basic Network Server(s) Configuration In this chapter we describe how to setup the various server elements in the system. 10.1 Server setup In the EXP1240 network, the server environment is installed as a centralized system. The main server types hosted on the network include SIP, DNS/DHCP and HTTP/TFTP Servers. These servers can be hosted both in one or multiple windows and/or Linux Server environment.
The network administrator should contact the relevant vendors for detail information or step-by-step procedure on how to install and setup DHCP process or service on windows/Linux servers. In this section, we will provide some hints of how to resolve potential problems to be encountered you setup DHCP Servers. Windows Server: 1) Clients are unable to obtain an IP address if a DHCP client does not have a configured IP address; it generally means that the client has not been able to contact a DHCP server.
10.5 TFTP Server Setup There are several TFTP servers in the market place; in this section we describe how to setup a commonly used TFTP Server. 10.5.1 TFTP Server Settings • Configure the relevant TFTP virtual folder in the server. The TFTP virtual folder is the file folder, visible for TFTP clients under a certain name. You can set security settings separately for every virtual TFTP folder. Next, set rights to access TFTP folders according to the relevant clients. EXP1240 Admin Guide, Version 2.
10.6 SIP Server Setup SIP server is one of the main components of an EXP1240 network, dealing with the setup of all SIP calls in the network. A SIP server is also referred to as a SIP Proxy or a Registrar. Although the SIP server is the most important part of the SIP based phone system, some servers only handles call setup and call tear down. It does not actually transmit or receive any audio. This is done by the media server in RTP.
Video Codecs Media & RTP Settings header Choose the relevant option or enter the settings in IP configuration, External IP, Local Network. Some SIP Servers supports dynamic codec support. Codecs are algorithm used to compress or decompress speech or audio signals. The user should select the relevant Codecs and other speech compression techniques whose traffic will be routed to the EXP1240 network. The user should enable this option if EXP1240 network supports video telephony.
Chapter: Appendix A: Basic Network Server(s) Configuration EXP1240 Admin Guide, Version 2.
11 Appendix B: Using Base with VLAN Network In this chapter we describe how to setup a typical VLAN in the network. 11.1 Introduction In this chapter, we describe how to setup VLAN to typical network. There are three main stages involved in this procedure: 1) Configure a VLAN Aware Switch to a specific (un)tagged VLAN ID, so the EXP1240 system can process untagged frames forwarded to it. 2) Setup the Time Server (NTP Server) and other relevant network servers.
• • All switch ports can communicate with one another at the Data Link Layer, if they become members of the same VLAN. The physical location of an end station does not define its LAN boundary. 1. An end station can be physically moved from one switch port to another without losing its “view of the network”. That is, the set of stations it can communicate with at the Data Link Layer remains the same, provided that its VLAN membership is also migrated from port to port. 2.
An illustration of IEEE 802.1Q VLAN tag in Ethernet frame is as follows: 11.3 How VLAN Switch Work: VLAN Tagging VLAN functionality can be implemented via explicit frame tagging by switches and end stations. Network switches and end stations that know about VLANs are said to be VLAN aware. Network switches and end stations that can interpret VLAN tags are said to be VLAN tag aware. VLAN-tagaware switches and end stations add VLAN tags to standard Ethernet frames–a process called explicit tagging.
• IP subnet-based VLAN: The NIC assigns a unique VLAN ID for each IP subnet it belongs to. Therefore, the VLAN ID of outbound frames is different for different destination subnets. An inbound frame is dropped if the IP subnet and VLAN ID do not match. 11.5 Base station Setup After the admin have setup the Backbone switch, next is to configure the Base stations via HTTP interface. STEP 1 Connect the Base station to a private network via standard Ethernet cable (CAT-5).
11.7 VLAN Setup: Base station Chapter: Appendix B: Using Base with VLAN Network STEP 7 Navigate to the Network URL > On the network page enter the relevant settings in the VLAN section > VLAN Id should be the same as those configured into the backbone. EXP1240 Admin Guide, Version 2.
12 Appendix C: EXP1240 Network Planning/Optimization In this chapter, we describe EXP1240 radio network planning techniques including dimensioning, detailed capacity and coverage planning, and network optimisation. 12.1 Network Requirements Network requirement is essential to determine elements necessary to achieve the overall expectations of the customer.
Overlaps are necessary to maintain seamless handover and to establish synchronization chains. A good example may be a cafeteria during lunch hour where temporary concentrations of handsets may occur. The overlap carries the excess call load to adjacent Base stations to provide uninterrupted services to subscribers. 12.4 Cell Coverage / Capacity Planning 12.4.
12.4.2 Capacity Planning Another aspect of capacity planning should address the user growth pattern of a typical EXP1240 network. How many users will be using this network in for example two years window, etc. Based on these estimations, the network dimensioning can be planned orderly bearing in mind the EXP1240 capacity. 12.5 Network Dimensioning After the network requirements are clearly defined, the number of users that are expected to use the network must be estimated.
Core Network Equipment: This equipment is at the premises of the service operator or data centre. Depending on the network requirements the following devices should be available: VLAN/NAT aware router(s), Session Border Controller, DHCP/TFTP/FTP Servers, STUN Server, Media Server, Access Gateway, SIP Server, etc. 12.6 Environmental Considerations • • • • • • Ensure that the installation area is clean and dry.
Open Areas/ Large Halls: Base stations and repeaters can be deployed in open areas for buildings that contain a central open space area with windows to the other areas. This provides a good coverage for the rooms in the inner circle on all floors (e.g. hotels). In large halls, Base stations/repeater should be installed vertically in the middle of the space below the drop ceiling.
Collect statistics of the network an example is illustrated in the table below: Parameters Value Comments ## Call Setup failures ## Dropped calls ## HO successes ## HO failures Traffic Blocking Rate (%) Traffic Blocking (Erl) Receiver level (dBm) Receiver Quality (%) After collecting the necessary information, you should fine tune signalling and radio resource sharing parameters. Network optimisation is a continuous process during and after the launch of the network.
13 Appendix D: Local Central directory file handling In this appendix the Local Central Directory file format, import and configuration is described. 13.1 Central Directory Contact List Structure The structure of Contact List is simple. The figure below shows an example of structure of Contact List in Text format and in Xml format. Contact name must not contain more than 23 characters and contact number must not contain more than 21 digits. .csv or .
13.3 Import Contact List to Central Directory On the Central Directory page, the admin should click on Browse button and the Choose File to Load dialog window will be shown. Next, click on the Load button. This will import the contents of contacts in the selected file into the relevant Base station. The figure below shows the import procedure is in process. EXP1240 Admin Guide, Version 2.
13.4 Central directory using server Alternative way to import a Contact List is to get it from a server. First click on Management URL to get Management Settings page, then select the protocol of your server (TFTP/HTTP) in Management Transfer Protocol, then save the setting by clicking Save. Go back to Central Directory page and enter Server IP address (inclusive the path in the end of the address) and Filename of the contact list, then save the setting by clicking Save. (See example below).
14 Appendix E: Network Operations 14.1 Introduction In this chapter, we will provide an overview of the operation of the network during system start-up, location registration and speech calls including illustration of different call scenarios. 14.2 System Start Up When a Base station Unit is powered up, it achieves IP address from DHCP server and time from the TimeServer. Optionally the base retrieves its configuration from a file on the TFTP server.
14.6 Handover 14.6.1 RTP Stream Remains at Initial Base Station When the call is set up, the handset is located at base station 1. Thus, the DECT communication takes place between the handset and station 1, and the SIP signalling as well as the RTP stream takes place between base station 1 and the SIP server/media gateway. The figure below illustrates this application: Stage 1: Before handover the handset is located at BS 1.
If the handset makes yet another handover, the RTP stream will still be relayed via the base station at which, the call was established (here base station 1). This is illustrated as follows: After handover to BS n the handset is located at BS n, and the RTP stream is relayed via BS 1. 14.7 Roaming By roaming means the handset moves its SIP and DECT registration from one base station to another base station. Roaming can only be initiated from idle.
Chapter: Appendix E: Network Operations An illustration of Handset moving to another base station, but call control is still handled by the initial base station. EXP1240 Admin Guide, Version 2.
