SME VoIP System Guide Technical Reference Document Version 2.6 © Jan-2016 RTX A/S, Denmark SME VoIP System Guide, Version 2.
Trademarks RTX and the combinations of its logo thereof are trademarks of RTX A/S, Denmark. 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 RTX products. RTX 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 SME VoIP System Guide .................................................................................................................................... 1 ........................................................................................................................................................................... 1 Contents ............................................................................................................................................................
5.4 Servers ................................................................................................................................................... 35 5.5 Network ................................................................................................................................................. 40 5.6 Management Settings Definitions ......................................................................................................... 44 5.7 Firmware Update Definitions ...........
10 Appendix A: Basic Network Server(s) Configuration ......................................................................... 105 10.1 Server setup ....................................................................................................................................... 105 10.2 Requirements .................................................................................................................................... 105 10.3 DNS Server Installation/Setup .................................
14.5 Incoming Calls .................................................................................................................................... 125 14.6 Handover ........................................................................................................................................... 126 Chapter: About This Document 14.7 Roaming .............................................................................................................................................
1 About This Document This document describes the configuration, customization, management, operation, maintenance and trouble shooting of the SME VoIP System (RTX8663 base, RTX8630 handset, RTX8430 handset, RTX8830 ruggedized handset and RTX4024 Repeater) in RTX 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 8 Chapter 9 10 Appendix A 11 Appendix B 12 Appendix C 13 Appendix D 14 Appendix E Handsets Firmware Upgrade/Downgrade Management System Functionality Overview Basic Network Servers Configuration VLAN Setup Management SME VoIP Network Planning/Optimization Local central directory file handling Network Operations stations Provides the procedure of how to upgrade firmware to base stations and/or handsets and/or repeaters To gain detail knowledge about the system features.
1.7 References/Related Documentation [1]: [2]: [3]: RTX8430 Handset_Manual_Operations_v1.1 RTX8630 Handset_Manual_Operations_v1.2 RTX8830_Handset_Manual_Operations V1.3 How to Deploy SME VOIP System v1.4 Provisioning of SME VoIP System (10) Revision 2.2 Author KMR Issue Date 24-July-2014 2.1 KMR 2-April-2014 2.0 KMR 1-Oct-2013 1.9 KMR 17-July-2013 1.8 2.3 2.4 2.5 2.
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 50 bases in the same network.
2.2 Components of SME VoIP System RTX SME VoIP system is made up of (but not limited to) the following components: • At least one RTX Base Station is connected over an IP network and using DECT as air-core interface. • RTX IP DECT wireless Handset. • RTX SME VoIP Configuration Interface; is a management interface for SME VoIP 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/Repeater 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 RTX 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 of Base Station To find IP of the installed base station two methods can be used; Using handset Find IP feature or browser IPDECT 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 8663 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 SME 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 SME VoIP Configuration interface. Replace Battery Remove Back Cover from Handset. Remove the old battery and replace with a new one. 4.
5 SME VoIP Administration Interface The SME VoIP Administration Interface is also known as SME VoIP Configuration. It is the main interface through which the system is managed and debugged. The SME VoIP Configuration Interface is an in-built HTTP Web Server service residing in each base station. This interface is a user friendly interface and easy to handle even to a first time user. Note: Enabling secure web is not possible. For secure configuration use secure provisioning.
Network Management Firmware Update Time Country Security Central Directory Multi cell Repeaters Alarm Statistics Configuration Syslog SIP Log On this page the user can define which SIP/NAT server the network should connect to. Typically the user configures the Network settings from here. NAT provisioning: allows configuration of features for resolving of the NAT – Network Address Translation. These features enable interoperability with most types of routers.
5.2 Home/Status We describe the parameters found in the Welcome front end home/status of the SME VoIP Administration Interface. Parameter System information Phone Type System Type RF Band Current local time Operation time RFPI-Address MAC-Address IP-Address Firmware version Firmware URL Base Station Status SIP identity status Reboot Forced Reboot Description This base current multi-cell state Always IPDECT This base customer configuration This base RF band setting.
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 Empty Disabled Disabled 90 Forwarding On Busy Number Empty Disabled SME VoIP System Guide, Version 2.6 Proprietary and Confidential Password: SIP authentication password.
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 Display Name Server Server Alias IPEI State FW info FWU Progress Description Select / deselect for delete, register and deregister handsets Given extension is displayed Given display name is displayed. If no name given this field will be empty Server IP or URL Given server alias is displayed.
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). Enable registration mode for the system making it possible to register at a specific extension (selected by checkbox) Deregister the selected handset(s) and 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 SME VoIP System 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 BroadWorks Shared Call Appearance Disabled Broadsoft Feature Event Package Disabled Forwarding Unconditional Number Empty Forwarding No Answer Number Empty Empty Disabled Empty SME VoIP System Guide, Version 2.6 Proprietary and Confidential Handset phone number or SIP username depending on the setup.
Forwarding On Busy Number Disabled 90 Empty Number to which incoming calls must be re-routed to when SIP node is busy. Forwarding On Busy Number must be enabled to function. Note: Feature must be enabled in the SIP server before it can function in the network 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.
Handset Type FW Info FWU Progress VoIP Idx Extension Display Name Server Server Alias State Name of the handset type Firmware version of handset Possible FWU progress states: Off: Means sw version is specified to 0 = fwu is off Initializing: Means FWU is starting and progress is 0%. 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.
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. Chapter: SME VoIP Administration Interface Screenshot SME VoIP System Guide, Version 2.
Parameter Location Default Value(s) ANY IPEI Handset IPEI AC Handset AC code Alarm Line No Alarm Line Selected Empty Alarm Number Alarm Profiles Shared Call Appearance Settings Not configured Not configured Description Specify a handset to be located at a specific base station or ANY base station. A location of a handset controls the DECT registration and the SIP registrations. Binding a handset to a specific base will bind the SIP registrations to this base. Shows the handset IPEI.
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 Server Alias NAT Adaption Default value Empty Disabled SME VoIP System Guide, Version 2.6 Proprietary and Confidential Description Parameter for server alias To ensure all SIP messages goes directly to the NAT gateway in the SIP aware router.
Empty Outbound Proxy Empty Conference Server Empty Call Log Server Empty Reregistration time 600 SIP Session Timers: Disabled Session Timer Values (s): 1800 SME VoIP System Guide, Version 2.6 Proprietary and Confidential Chapter: SME VoIP Administration Interface Registrar If the system receives a SIP response to a REGISTER request with a “Via” header that includes the “received” parameter (ex: “Via: SIP/2.0/UDP 10.1.1.1:4540;received=68.44.20.
UDP Disabled Use One TCP/TLS Connection per SIP Extension: Disabled RTP from own base station: Disabled Keep Alive Enabled Show Extension on Handset Idle Screen Hold Behaviour Enabled Attended Transfer Behaviour Hold 2nd Call RFC 3264 SME VoIP System Guide, Version 2.6 Proprietary and Confidential Select UDP, TCP, TLS 1.0 When SIP Transport is set to TCP or TLS, a TCP (or TLS) connection will be established for each SIP extension.
Disabled DTMF Signalling RFC 2833 DTMF Payload Type Remote Caller ID Source Priority Codec Priority 101 RTP Packet size 20ms Secure RTP Disabled Secure RTP Auth Disabled FROM G.711U G.711A G.726 SME VoIP System Guide, Version 2.6 Proprietary and Confidential Chapter: SME VoIP Administration Interface Use Own Codec Priority If "Hold 2nd Call" is selected, the 2nd call will be held before REFER is sent.
SRTP Crypto Suites concurrent calls is possible per base in a single or multicell system. AES_CM_128_HMAX_SHA1_32 Field list of supported SRTP Crypto Suites. The device is AES_CM_128_HMAX_SHA1_80 born with two suites. Chapter: SME VoIP Administration Interface Note: Within servers or even with multi servers, extensions must always be unique. This means same extension number on server 1 cannot be re-used on server 2. SME VoIP System Guide, Version 2.
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 SME VoIP System Guide, Version 2.6 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.rtx.net).
RTP Collision Detection Local SIP port SIP ToS/QoS Enabled Enable: If two sources with same SSRC, the following RTX is discarded. Disabled: No check – device will accept all sources. 5060 RTP port 50004 RTP port range RTP TOS/QoS 40 The source port used for SIP signalling Permitted values: Port number default 5060. Priority of call control signalling traffic based on both IP Layers of Type of Service (ToS) byte. ToS is referred to as Quality of Service (QoS) in packet based networks.
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: Default value SME VoIP Management Transfer Protocol HTTP TFTP Empty SME VoIP System Guide, Version 2.6 Proprietary and Confidential Description It indicates the title that appears at the top window of the browser and is used in the multicell page.
files of the Configuration server. The configuration upload script is a file located in e.g. TFTP server or Apache Server which is also the configuration server. Permitted value(s): / Example: /CfgUpload Note: Must begin with (/) slash character. Either / or \ can be used. Password that should be entered in order to have access to the configuration server. HTTP client credentials are formed by “User name” and the “HTTP Management password”.
30 This defines the frequency of how response timeout Permitted values: Positive integer, unit is in seconds 0 This defines the text messaging time to live Permitted values: Positive integer, unit is in seconds Empty Syslog Server IP-Address Syslog Server Port Syslog Level Empty Permitted value(s): AAA.BBB.CCC.DDD or Requires a predefined folder named: \SIP Enable this option to save low level SIP debug messages to the server.
Chapter: SME VoIP Administration Interface SME VoIP System Guide, Version 2.
5.7 Firmware Update Definitions In this page, the system administrator can configure how base stations and SIP nodes upgrade/downgrade to the relevant firmware. Handset firmware update status can be found in the extensions page and repeater firmware update status in the repeater page. Base firmware update status is found in the multicell page.
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.
Parameter Time Server Default Values Empty Allow broadcast NTP Refresh time (h) Checked Set timezone by country/region Time Zone Checked Set DST by country/region Daylight Saving Time (DST) Checked 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 system administrator can Enable or Disable DST manually.
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 certificates and for selecting if only trusted certificates are used. Furthermore, web password can be configured. The Security web is divided into three sections: Certificates (trusted), SIP Client Certificates (and keys) and Password administration. To setup secure fwu and configuration file download select HTTPs for the Management Transfer Protocol (refer to management web).
5.10.2 SIP Client Certificates To be able to establish a TLS connection in scenarios, where the server requests a client certificate, a certificate/key pair must be loaded into the base. This is currently supported only for SIP. To load a client certificate/key pair, both files must be selected at the same time, and it is done by pressing “select files” under “Import SIP Client Certificate and Key Pair” and then select the certificate file as well as the key file at the same time. Afterwards, press load.
5.11 Central Directory and LDAP The SME VOIP system support two types of central directories, a local central directory or LDAP directory. For both directories caller id look up is made with match for 6 digits of the phone number. 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.
formats are not the original csv format. The central directory feature can handle up to 3000 contacts. For further details of the central directory feature refer to appendix. 5.11.2 LDAP Select LDAP Server and save for LDAP server configuration. Screenshot Parameter LDAP Server Default Values LDAP Server Server Empty SME VoIP System Guide, Version 2.6 Proprietary and Confidential Description Drop down menu to select between local central directory and LDAP based central directory.
Port Sbase Empty Empty LDAP filter Empty Bind Empty Password Virtuel Lists Name Empty Disabled Empty Work Number Empty Home Number Empty Mobile Number Empty 5.11.3 The server port number that is open for LDAP connections. Search Base. The criteria 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.
5.12 Multi-cell Parameter Definitions In this section, we describe the different parameters available in the Multi-cell configurations menu. 5.12.1 Settings for Base Unit Description of Settings for Specific Base units is as follows: Screenshot Parameter Multi cell system Default values Disabled System chain ID Empty Synchronization 60 sec time (s) SME VoIP System Guide, Version 2.
Data Sync: Multicast Primary Data Sync IP Empty Multi cell debug None If no keep-alive packets are received within a period of 2*NETWORK_SYNC_TIME, the base will be indicated as lost in the multi cell configuration. The parameter is also used with “Auto create multi primary” feature. To select between multicast or Peer to Peer data synchronisation mode. The multicast port range and IP addresses used is calculated from the chain id.
Allow multi primary: Disabled Auto create multi primary: Disabled Auto configure DECT sync source tree Enabled This feature is used for multi-location setups. Allows two or more primary in the same system. The two cells will be unsynchronized and handover will not be possible. “Auto Configure DECT sync source tree” must be enabled for this feature to also be enabled By enabled the system can generate cells in case a base goes into faulty mode.
50/3 Chapter: SME VoIP Administration Interface System combination (Number of base stations/Repeaters per base station): roams to another base station Enabled: The old SIP registration will be deleted with a SIP Deregistration, when a handset roams to another base station Select between basic base configurations. 50/3 : 50 bases and 3 repeaters 127/1 : 127 bases and 1 repeater 254/0 : 254 bases and 0 repeater The configuration cannot be modified after a system is established.
5.12.4 Base Station Group The Base station group list various parameter settings for base stations including chain level information. Parameters ID RPN Version MAC Address IP Status DECT Sync source Description Base 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 SME must be geographically unique.
Base Station Name Possible Output(s) Primary: Main Base station unto which all other nodes in the chain synchronises to. Locked: The Base unit is currently synchronized and locked to the master Base unit. Searching: Base unit in the process of locating to a Master/slave as specified in Dect sync source Free Running: A locked Base unit that suddenly lost synchronisation to the Master. Unknown: No current connection information from specific Base unit Assisted lock: Base has lost DECT sync.
Screenshot: Example of part of DECT Chain tree with units in Base Group but not in tree by various reasons. Chapter: SME VoIP Administration Interface When a base or repeater has not joined the tree it will be shown with read background below the tree. SME VoIP System 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 Description Repeater name. If no name specified the field will be empty Manually: User controlled by manually assign “Repeater RPN” and “DECT sync source RPN” Local Automatical: Repeater controlled by auto detects best base signal and auto assign RPN.
5.13.1.1 Manually User controlled by manually assign “Repeater RPN” and “DECT sync source RPN”. The parameters are selected from the drop down menu. Screenshot DECT sync source Description System counter 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) MULTI CELL SYSTEM: Bases are increment by 2^2 in hex, means first base RPN00 second base RPN04 etc.
5.13.1.2 Local Automatical Repeater controlled by auto detects best base signal and auto assign RPN. The RPN and DECT sync source are greyed out. The repeater RPN is dynamic assigned in base RPN range. With local automatical mode repeater on repeater (chain) is not supported. 5.13.2 Register Repeater Adding a repeater makes it possible to register the repeater. Registration is made by select the repeater and pressing register repeater.
Parameters IDx RPN Name/IPEI DECT sync Source DECT sync Mode Chapter: SME VoIP Administration Interface 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 SME must be geographically unique. Permitted Output: 0 to 255 (DEC) OR 0x00 to 0xFF (HEX) Contains the name and the unique DECT serial number of the repeater.
5.14 Alarm In the Alarm Settings menu, it is controlled how an alarm appears on the handset. For example if the handset detects “Man Down”, then it is defined in this menu what alarm signal this type of alarm will send out and if a pre-alarm shall be signaled etc. The parameters that can be configured are: Parameters Description Idx Indicates the index number of a specific alarm.
Howling signalled. The maximum value is 255. Enable/disable if howling shall be started in the handset, when the alarm is signalled. If disabled, only the configured signal is sent (call or message). This alarm feature is only available on some types of handsets (e.g. the RTX8830) After configuration, the handset must be rebooted. 5.14.1 Use of Emergency Alarms As described above, it can be configured if it shall be possible to stop an alarm from the handset.
5.15 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.15.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.
source Base free running is the number of times a base has been free running Number of time a base has changed sync source Free Running DECT Source Changed 5.15.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.15.3 Repeater data Parameters Idx/Name Operation D-H:M:S Busy Busy Duration D-H:M:S Max Active Searching Recovery DECT Source Changed Wide Band Narrow Band Description Base IP address and base station name from management settings Total operation time for the repeater since last reboot or reset Duration is the time from data was cleared or system has been firmware upgraded. Busy Count is the number of times the repeater has been busy.
5.15.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: SME VoIP Administration Interface Please note 3 frequencies are manually removed in the example system. SME VoIP System Guide, Version 2.
5.16 Settings – Configuration File Setup This page provides non editable information showing the native format of entire SME VoIP 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.18 SIP Logs This page shows SIP server related messages that are logged during the operation of the SME 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 SME 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 SME VoIP 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 SME VoIP System 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.
STEP 12 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 number of base units. This procedure is divided into four (4) main stages. Apply this procedure if all base unit 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 SME VoIP Configuration Interface ensure these scenarios really work. 6.4.1 Case ##1: Isolated Buildings Disable Multi Cell option of Base Stations SME VoIP System Guide, Version 2.6 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 SME VoIP System Guide, Version 2.
7 Registration Management - Handset In this chapter we briefly describe how to register handsets in the SME VoIP 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. SME VoIP System 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” SME VoIP System 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 RTX. 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.
8.3 Create Firmware Directories 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) SME VoIP System Guide, Version 2.6 Proprietary and Confidential Chapter: Firmware Upgrade Procedure NOTE: If TFTP server timeout settings are too short firmware upgrade might not complete. Recommended time out setting is more than 3 seconds.
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. SME VoIP System Guide, Version 2.
8.4 Handset Firmware Update Settings Scroll down and Click on Firmware Update url link in the SME VoIP Configuration Interface to view the Firmware Update Settings page. Type IP address and firmware path followed by save. 8.5 Handset(s) and Repeater Firmware Upgrade On the Firmware Update Settings page enter the relevant handset/repeater firmware for each type (e.g. 273 for V273) to upgrade or downgrade > press Save button to initialize the process of updating all handsets.
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.5.1 Monitor handset firmware upgrade Handset firmware update time from start to complete takes minimum 40 minutes. 8.5.
8.5.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. The “FWU info” column contains the software version and the “FWU Progress” column contains the status. In case status is “Complete”, the unit is firmware upgraded.
8.6.1 Base firmware confirmation Base station firmware version status in a multicell environment can be seen in the multicell base station group overview page, column 4. 8.6.2 Verification of Firmware Upgrade Syslog information when Management Syslog level is set to “Debug” [ FWU Downloading File tftp://10.1.24.101/FwuPath/Beatus/BeatusSw_4181_v0202.
9 Functionality Overview So far we have setup our SME VoIP system. Next, in this chapter we list what features and functionalities are available in the system. The SME VOIP system supports all traditional and advanced features of most telephony networks. In addition, 3rd party components handle features like voice mail, call forward, conference calls, etc.
Note: Only with additional module, this is an extra option that requires a board connector mounted in Gateway. Per default not mounted. SIP RFC2327 RFC2396 RFC2833 RFC2976 RFC3261 RFC3262 RFC3263 RFC3264 RFC3265 RFC3311 RFC3325 RFC3326 RFC3489 RFC3515 RFC3550 RFC3581 RFC3842 RFC3891 RFC3892 RFC3960 RFC4475 SIPS SRTP Web server SDP: Session Description Protocol Uniform Resource Identifiers (URI): Generic Syntax In-Band DTMF/Out of band DTMF support The SIP INFO method SIP 2.
VoIP Accounts Simultaneous Calls Call features Call log Phone Book Chapter: Functionality Overview DND Call Forward 30 VoIP accounts per base – (maximum 254 bases per installation) Total 1000 VoIP accounts / system Maximum 1000 handsets per installation 4 Wideband calls (g.722) or 10 single cell, 8 multi cell narrowband calls (PCMA, PCMU, G.726) or mixed wideband and narrowband.
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 SME 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. SME VoIP System Guide, Version 2.
10.6 SIP Server Setup SIP server is one of the main components of an SME 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 SME network. The user should enable this option if SME network supports video telephony.
Chapter: Appendix A: Basic Network Server(s) Configuration SME VoIP System 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 SME system can process untagged frames forwarded to it. 2) Setup the Time Server (NTP Server) and other relevant network servers.
The physical location of an end station does not define its LAN boundary. 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.
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). STEP 2 Use one of the two methods to find the base IP STEP 3 On the Login page, enter your authenticating credentials (the username and password is admin by default unless it is changed). Click OK button.
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. SME VoIP System Guide, Version 2.
12 Appendix C: SME VoIP Network Planning/Optimization In this chapter, we describe SME VoIP 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 SME VoIP 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 SME 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. SME VoIP System 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.
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.
DECT Connection Base station 1 Audio Control Base station 2 Base station n SIP Control RTP Stream SIP Server/Media Gateway 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. SME VoIP System Guide, Version 2.
FCC Caution: Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment. This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
IC: This device complies with Industry Canada licence-exempt RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause interference, and (2) this device must accept any interference, including interference that may cause undesired operation of the device. Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence.
