Samsung | DECT-8000 | Multi-cell System - Nycomm Holding Page

Quick Guide: How to Setup Multi-cell in
SME VoIP Network
Source: MYA
Version 0.5
Page | 1
Adding Multiple Base Stations to Network
(Multi-cell System)
Contents
Contents............................................................................................................................................................. 2
Document History .............................................................................................................................................. 2
Introduction: Base station Installation .............................................................................................................. 3
Abbreviations ..................................................................................................................................................... 3
References ......................................................................................................................................................... 3
Multi-cell System ............................................................................................................................................... 4
Multi-cell Configuration ..................................................................................................................................... 4
SME Configuration Interface ............................................................................................................................. 5
Adding Base stations via SME Configuration Interface ..................................................................................... 5
Synchronizing the Base stations ...................................................................................................................... 13
Summary of Procedure – Creating a Chain...................................................................................................... 17
Stage 1 ................................................................................................................................................. 17
Stage 2 ................................................................................................................................................. 17
Stage 3 ................................................................................................................................................. 17
Stage 4 ................................................................................................................................................. 17
Practical Configuration of Multi-Cell System ................................................................................................... 18
Case ##1: Isolated Buildings ............................................................................................................ 18
Case ##2: Location with co-located partners .................................................................................. 18
Case ##3: Large to Medium Sized Enterprises ................................................................................. 19
Case ##4: Large Enterprises at Different Locations ......................................................................... 20
Adding Extension/Handset Registration .......................................................................................................... 22
Example: Creating Multi-Cell Using 2 Bases/Handsets .................................................................................... 24
Source: MYA
Version 0.5
Page | 2
Introduction: Base station Installation
This document 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 usually called network dimensioning). The
present document does not address this issue. Please refer to accompanying document
2) Creating and adding base station profiles to the network via the SME Configuration Tool (to
form a multi-cell system).
This document describes the second procedure.
This documentation is valid for Base station firmware version 00.49 and above.
Abbreviations
For the purpose of this document, the following abbreviations hold:
DHCP:
DNS:
HTTP:
IOS:
NAT:
PCMA:
PCMU:
SME:
STUN:
Dynamic Host Configuration Protocol
Domain Name Server
Hyper Text Transfer Protocol
Internetworking Operating System
Network Address Translator
A-law Pulse Code Modulation
mu-law Pulse Code Modulation
Small and Medium scale Enterprise
Session Traversal Utilities for NAT
References
[1]:
Source: MYA
Version 0.5
SME VoIP System Description – Installation & Configuration; Network Deployment, V1.1
Page | 3
Multi-cell System
A multi-cell system has a coordinated installation of intra-system synchronized base stations, which
enables seamless inter-cell handover for moving handsets.
It provides increased mobility, higher total capacity and higher quality than a corresponding number of
standalone base stations.
All handsets subscribed to a multi-cell system will benefit from high voice quality, and full coverage
over the whole multi-cell system coverage area.
Multi-cell Configuration
A total of 40 Base stations can be hosted in a typical SME multi-cell system. At each time, a maximum
of 6 levels can be formed in a multi-cell chain.
Level 1 is when Base unit 1 synchronizes to Master Base unit, and Level 2 is when Base unit 2 uses Base
unit 1 as its synchronization source, in that order. We can illustrate the configuration with the figure
below (Refer to STEP 13 to STEP 15 for details on how to actually set it up via SME HTTP web
interface):
Source: MYA
Version 0.5
Page | 4
SME Configuration Interface
RTX have offered HTTP interface in base station that can be used as HTTP Web Server. The SME
Configuration Interface can be retrieved from this HTTP Web Server in each Base station.
The HTTP Web Server is enabled in the base station by default.
This procedure is valid for Base station firmware version 00.49 and above. The system
administrator must update the relevant Base station(s) to the latest firmware before
proceeding to the next section. Refer to accompanied document [1]
Adding Base stations via SME Configuration Interface
Here are the recommended steps to add Base stations to network:
STEP 1
Connect the Base station to a private network via standard Ethernet cable (CAT-5).
STEP 2
Open any standard browser and enter the address:
http://ipdect<MAC-Address-Base-Station>
for e.g. http://ipdect00087B00AA10. This will retrieve the HTTP Web Server page from
the base station with hardware address 00087B00AA10.
STEP 3
Skip this step if you were successful with STEP 2. If the MAC-address method as
described above does not work, then use a standard network protocol analyzer (for e.g.
Wireshark) to eavesdrop the IP address allocated to the base unit by the DHCP server. You can
download Wireshark follow its documentation to know how it is done.
Enter the IP address into the address bar of the browser to retrieve base station HTTP Web
Server Page.
Source: MYA
Version 0.5
Page | 5
STEP 4
On the Login page, enter your authenticating credentials (i.e. username and password is
default “admin”). Click OK button.
STEP 5
Once you have authenticated, the browser will display front end of the SME
Configuration Interface. The front end will show relevant information of the base station (in
this case MAC-Addr: 00087B00AA10 as highlighted in the snap-shot below).
Source: MYA
Version 0.5
Page | 6
TIME SERVER SETUP
STEP 6
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. Enter the relevant parameters on this page and
press the Save button.
Make sure there is contact to the “Time server” otherwise the Multi-cell feature will not work.
Set this Time Settings to synchronise the base station(s) time to the NTP server time. Next Save
the settings and reboot the base station.
Source: MYA
Version 0.5
Page | 7
A successful reboot will reset the time in the base station.
SIP SERVER (OR PBX SERVER) SETUP
STEP 7
Create the relevant SIP server (or PBX Server) information in the system. Each service
provider/customer should refer SIP server vendor on how to setup SIP servers.
Click the link “Server” at the left hand column of home page, you can add your SIP server for
base station use.
Next, from the Server page, click on the Add Server URL and enter the relevant SIP server
information (an example is shown below).
Choose “No” on NAT adaption parameter if NAT function of the SIP aware router is not
enabled. Enter the relevant parameters based on the description in the table below. Select
Save button.
Source: MYA
Version 0.5
Page | 8
Parameter
Description
NAT Adaption
To ensure all SIP messages goes directly to the NAT gateway in the SIP aware
router. NAT Adaption option should be “No” or otherwise choose “Yes”
Possible value(s): Yes, No
SIP Server proxy DNS or IP address
Permitted value(s): AAA.BBB.CCC.DDD:<Port-Number>
Note: Specifying the Port Number is optional.
This is usually Session Border Controller DNS or IP address (OR SIP server
outbound proxy address)
Set the Outbound proxy to the address and port of private NAT gateway so that
SIP messages sent via the NAT gateway.
Permitted value(s): AAA.BBB.CCC.DDD
Examples: “192.168.0.1”, “192.168.0.1:5062”,
“nat.company.com” and “sip:nat@company.com:5065”.
The window period (in seconds) when base stations SIP registers with SIP server.
Permitted value(s): Positive integer
This directive defines the window period (usually 30 secs.) to re-open port of
relevant NAT-aware router(s), etc.
Valid Input(s): Enable, Disable
Conversion of decimal digits (and '*' and '#') into sounds that share similar
characteristics with voice to easily traverse networks designed for voice
Valid Option(s)
In band: Meta-data (for e.g.: tone digits) and control information sent in the
same voice band, using the same VoIP codec as the human voice (for e.g. G.711,
G.729, etc.)
SIP INFO: Carries application level data along SIP signalling path (for e.g.: Carries
DTMF digits generated during SIP session OR sending of DTMF tones via data
packets in the same internet layer as the Voice Stream, etc.).
RFC 2833: DTMF handling for gateways, end systems and RTP trunks (for e.g.:
Sending DTMF tones via data packets in different internet layer as the voice
stream)
Both: Enables SIP INFO and RFC 2833 modes.
Defines the codec priority that base stations uses for audio compression and
transmission.
Possible Option(s): PCMU, PCMA, iLBC, etc.
Registrar
Outbound Proxy
Re-registration
time
Keep Alive
DTMF Signalling
Codec Priority
Source: MYA
Version 0.5
Page | 9
MULTI-CELL SETUP
STEP 8
Scroll down and Click on Multi Cell url link in the SME VoIP Configuration to view the
current Multi cell settings status of the current base station. Normally, most brand new base
stations have Multi cell system feature disabled by default.
Description of Settings for Specific Base units is as follows:
Parameter
Multi cell system
System chain ID
Synchronization
time (s)
Multi cell debug
Source: MYA
Version 0.5
Description
Enable this option to allow the Base unit to be set in multi-cell mode (can be set as master
or slave in the multi-cell chain system).
Valid Inputs: Enable, Disable
This is an identifier (usually in string format for e.g. 2275) that is unique for a specific
multi-cell system.
Note: There can be several multi-cell systems in SME network.
Valid Input: 8 bit String
This specifies the period or window in seconds elements/nodes (for e.g. Base units) in a
specific Multi-cell should synchronise to each other.
Enable this feature, if you want the system to catalogue low level multi-cell debug
information or traces.
Page | 10
STEP 9
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 10 On the same Multi Cell Settings page > Enter the relevant values for System chain ID
and Synchronization time (s) respectively. The System chain ID is a geographically unique
DECT cell identity allocated to bridge several base stations together in a chain. An example is
2275. The Synchronization time (s) parameter is defined as window/period of time in seconds
a specific base station synchronises to the master base station unit (by default 60).
Source: MYA
Version 0.5
Page | 11
Click on Save button to keep modified changes of multi cell settings into the base
station.
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 6.
IMPORTANT:
Base stations must be rebooted after the time server has been set.
STEP 11
Repeat STEP 1-10 as explained above for N number of base stations.
IMPORTANT:
It takes up to 5 minutes (synchronization time) to add a new base station to a Multi Cell System.
Source: MYA
Version 0.5
Page | 12
Synchronizing the Base stations
STEP 12 On each SME VoIP Configuration interface for the base station(s) navigate to the
Home/Status page and Click the Reboot button.
This will trigger Are you sure you want to reboot gateway? window. Click OK button on
this window. A successful restart of the base stations will lead to a display of the page:
Gateway has been reset.
STEP 13 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.
Source: MYA
Version 0.5
Page | 13
STEP 14 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).
Usually the DECT system RFPI parameter is computed by the system (Its often greyed in a
multi-cell system configuration).
Parameter
DECT system
RFPI
Source: MYA
Version 0.5
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.
RFPI Format: XX XX XX XX XX (where XX are HEX values)
Access Rights Class (ARC):
Defines network identity structure used by terminals especially in multi-cell environment.
Fixed/default Value=1 (Private multi-cell system).
RFPI: 1X XX XX XX XX
Equipment Installer's code (EIC):
Code that allows terminals to distinguish between separate DECT networks.
Min: 0x0000, Max: 0xFFFF; RTX_EIC: 0x16E6 (May change)
RFPI: 11 6E 6X XX XX
Fixed Part Number(FPN):
Is a geographically unique identity transmitted to DECT networks to help PP distinguish
between base station communications in different cells/multi-cell systems.
Min: 0x001, Max: 0xFFF; E.g. FPN: 0x049
RFPI: 11 6E 60 49 XX
Location Area Length (Lal):
A unique code sent to the terminal during location registration to determine the size of
the location or cell area.
Type: 8-bit value (from 0x00 to 0xFF). E.g Lal=0x04
RFPI: 11 6E 60 49 04
Page | 14
Auto configure
DECT sync
source tree
Enable this to allow the network to automatically synchronise the multi-cell chain/tree
Permitted Inputs: Enable, Disable
Note: This parameter is not available to all base unit firmware
STEP 15 Scroll to the SIP system settings section, configure and save the parameter based on the
description below:
Parameter
Description
## of SIP accounts
before distributed
load
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 units in a
multi-cell setup.
Permitted Input: Positive Integers (for e.g. 30)
SIP Support for
multiple
registrations per
account
Enable this option so it is possible to use same extension (i.e. SIP Account) on multiple
phones (SIP end nodes). These phones will ring simultaneously for all incoming calls.
When a phone (from a SIP account group) initiates a handover from Base X to Base Y, this
phone will de-register from Base X, and register to Base Y automatically.
Note: Choose Yes when the SIP server supports this feature otherwise choose No for the
Sip server does not support this feature.
Permitted Input: Yes, No
STEP 16 Next, on the MAC-units in chains section, you can manually configure the
synchronisation source tree of the multi-cell system. 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). Usually the DECT system RFPI parameter is
computed by the system (Its often grayed in a multi-cell system)
Parameters
ID
RPN
Source: MYA
Version 0.5
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 stations’ and
repeater’s RPN must only differ on least significant bits that are masked out by the
handover mask.
Page | 15
MAC Address
Version
Status
DECT Sync
source
Dect Property
Source: MYA
Version 0.5
Permitted Output: 0 to 255 (DEC) OR 0x00 to 0xFF (HEX)
Contains the hardware Ethernet MAC address on the base station. It varies from Base
station to Base stations.
Min. Value: 0 ( i.e. last 4 HEX digits of 0x00087B070000, may change in the future)
Max. value: 65535 ( i.e. last 4 HEX digits of 0x00087B07FFFF, may change in the future)
Base station current firmware version.
Permitted Output: positive Integers (for e.g. 34)
Current Base station behaviour in the SME network.
Possible Outputs
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
The administrator should choose the relevant “multi cell chain” level its wants a specific
Base unit be placed. Maximum number of “multi-cell chain” levels is 6.
Base station characteristics in connection to the current multi cell network.
Possible Output(s)
Master: 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
Page | 16
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 N number of base units. The procedure below is valid ONLY for base station firmware
version 00.36 and above.
This procedure is divided into four (4) main stages. Apply this procedure if all base unit are straight
from production.
Stage 1
Skip this stage if relevant base stations are already in the network.
a) Add 3 base stations i.e. RFP1, RFP2, RFP3 > Disable the “Multi cell system” option and “Save”
b) RFP1, RFP2, RFP3: Reboot from the HTTP SME Configuration Main Page
c) RFP1, RFP2, RFP3: Default by pressing reset button 12-sec.
Stage 2
Choosing 1st base unit i.e. RFP1 as Master
a) RFP1: Define Time server and “Save” from the Time page
b) RFP1: Reboot
c) RFP1: Press “Add server” and define SIP server IP and “Save” from the Servers page
d) RFP1: Multi cell system = enable and “Save” from the Multi-cell page
e) RFP1: Reboot (Verify from Debug log “SYNCMGR: This base is ready to be master in a Chain”)
Stage 3
Choose another base unit,RFP2 as Slave1
a) RFP2: Multi cell system = enable and “Save”
b) RFP2: Reboot (Verify from Debug log “SYNCMGR: This base is ready to join into another
Chain”)
c) RFP1, RFP2: Wait 2min for stable Master-Slave chain (check for the message: SYNCMGR:
Socket#10 creation success)
Stage 4
Choose the 3rd base unit, RFP3 as Slave2
d) RFP3: Multi cell system = enable and “Save”
e) RFP3: Reboot (Verify Debug log “SYNCMGR: This base is ready to join into another Chain”)
f) RFP1, RFP3: Wait 2min for stable Master-Slave chain (SYNCMGR: Socket#10 creation success)
g) RFP3: Check mark ID2/RPN08 and select dropdown “1 – RPN: 04” and “Save”
h) RFP3: Reboot (SYNCMGR: Socket#8 creation success)
Multi-cell chain of 3 base stations have been created successfully. Next step involves adding
extensions to the system.
Source: MYA
Version 0.5
Page | 17
Practical Configuration of Multi-Cell System
Case ##1: Isolated Buildings
Example includes Branch or small office, Retail outlet or store, etc.
The optimal configuration for isolated buildings is standalone base stations setting. In this setting, you
must disable the Multi-cell parameter of each base station.
Disable Multi Cell option of Base Stations
Case ##2: Location with co-located partners
Example includes Department shops, Retail location with co-located photo kiosk or pharmacy, etc.
Here is diagram to illustrate Case ##2.
Source: MYA
Version 0.5
Page | 18
Multi Cell Page of Base Stations
Recommended settings of MAC-units in Chain section of page (Other different settings exist):
RPN
Ver
MAC Addr
IP Addr
IP Status
DECT sync
source
00
XX
XX:XX:XX…
XXX.XXX…
Connected
1: RPN:04
04
XX
XX:XX:XX…
XXX.XXX…
Connected
1: RPN:04
08
XX
XX:XX:XX…
XXX.XXX…
Connected
1: RPN:04
DECT
Property
Master
Note:
It is not necessary to deploy a dedicated Base unit at the car park area because it is likely no telephony
traffic or call will be placed at the area.
Case ##3: Large to Medium Sized Enterprises
Example: Corporate headquarters, Harbor areas, Campus
Source: MYA
Version 0.5
Page | 19
Multi Cell Page of Base Stations
Recommended settings of MAC-units in Chain section of page (Other valid setting exists):
RPN
Ver
MAC Addr
IP Addr
IP Status
DECT sync
source
00
XX
XX:XX:XX…
XXX.XXX…
Connected
1: RPN:04
04
XX
XX:XX:XX…
XXX.XXX…
Connected
2: RPN:08
08
XX
XX:XX:XX…
XXX.XXX…
Connected
3: RPN:0C
0C
XX
XX:XX:XX…
XXX.XXX…
Connected
4: RPN:10
10
XX
XX:XX:XX…
XXX.XXX…
Connected
4: RPN:10
14
XX
XX:XX:XX…
XXX.XXX…
Connected
4: RPN:10
DECT
Property
Master
Note:
The number of chains cannot exceed 7 levels.
Case ##4: Large Enterprises at Different Locations
Government departments/agencies geographically separated from each other, University campus,
Hospital etc.
Source: MYA
Version 0.5
Page | 20
Multi Cell Page of Base Stations
Recommended settings of MAC-units in Chain section of page (Other valid setting exists):
DECT sync
RPN
Ver
MAC Addr
IP Addr
IP Status
source
00
XX
XX:XX:XX…
XXX.XXX…
Connected
0: RPN:00
04
XX
XX:XX:XX…
XXX.XXX…
Connected
0: RPN:00
08
XX
XX:XX:XX…
XXX.XXX…
Connected
1: RPN:04
0C
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
Source: MYA
Version 0.5
DECT
Property
Master for
HQ
Master for
Offices
Master for
Enterprises
Page | 21
Adding Extension/Handset Registration
Here is the recommended procedure of adding extension(s) and registering one or more handsets to
the Multi-cell system which was just created.
ADDING EXTENSIONS TO SYSTEM
STEP 17
Choose the “Extensions” URL at the left hand column of home page.
STEP 18 Select the Add Extension URL and enter the relevant entries (an example is shown
below with 3020 as the extension). Click on the Save button.
HANDSET REGISTRATION
STEP 19 The extension page will show the figure below, if you save successfully the entries
safely. Enable the check option and choose the option “Register Handset” URL.
Source: MYA
Version 0.5
Page | 22
STEP 20 Next, take the handset you will like to register > power it up > In the idle mode navigate
to the Menu > Choose Connectivity > Select Register.
STEP 21 On the Connectivity dialog and after choosing Register option > Enter the Access code
(by default is 0000) > Press OK > Successful registration displays Extension(s) registered.
STEP 22 Open the HTTP interface of relevant base unit > On the Home/Status page, you can
check the current status of the SIP end node (which is the same as the handset). (In the
example below you can check the status of an extension 8000)
Source: MYA
Version 0.5
Page | 23
Example: Creating Multi-Cell Using 2 Bases/Handsets
In this chapter, we assume a user have single functioning standalone Base unit and will like to add
another base unit. Here is the procedure:
The multi-cell system contains one Master and can have more than one Slave. Slave will have the
information synchronized with Master.
BEFORE CONFIGURING THE BASE STATIONS
STEP 1
Reset the relevant bases (BS1 and BS2) to the default state.
STEP 2
Take each base station and long press on the side a small button (after the bases restart
or powers up) until the LED in front lit RED for 5 sec (continue pressing even when you see
ORANGE):
-> Long press reset button ->
to RED for 5 secs (no flashing) ->
finish.
-> Wait until LED stay
-> Power down and up the BS again to
CONFIGURATION OF BASE STATIONS
STEP 3
For each base station [BS 1 and BS 2] navigate to multi-cell configuration page by
clicking “Multi-cell” > On this page select the “Enable” option for Multi cell system parameter
and fill in a number for System chain ID, press Save. Press reboot button on the “Home” page
to reboot BS 1 and BS 2 and wait for 1 to 3 mins
Source: MYA
Version 0.5
Page | 24
STEP 4
After a successful restart, on each base [BS 1 and BS 2] Multi-cell page you will find the
other base connected and synchronized (the IP status shows This Unit or Connected) to the
system as illustrated below.
STEP 5
For [BS 1] Add server and extension to BS 1 similar to earlier sections.
STEP 6
[BS 1] Register HS to the extension and verify whether its successful from the “Home”
page and Handset UI
Source: MYA
Version 0.5
Page | 25
Source: MYA
Version 0.5
Page | 26
Download PDF

advertising