Hytera DMR Conventional Series

IP Multi-site Connect

Application Notes
Version 3.0

Date: 15- September, 2011

Copyright Information

Hytera is the trademark or registered trademark of Hytera Communications Co., Ltd. (the

Company) in PRC and/or other countries or areas. The Company retains the ownership of

its trademarks and product names. All other trademarks and/or product names that may

be used in this document are properties of their respective owners.

The product described in this document may include the Company’s computer programs

stored in memory or other media. Laws in PRC and/or other countries or areas protect the

exclusive rights of the Company with respect to its computer programs. The purchase of

this product shall not be deemed to grant, either directly or by implication, any rights to the

purchaser regarding the Company’s computer programs. Any of the Company’s computer

programs may not be copied, modified, distributed, decompiled, or reverse-engineered in

any manner without the prior written consent of the Company.

Disclaimer

The Company endeavors to achieve the accuracy and completeness of this document,

but no warranty of accuracy or reliability is given. All the specifications and designs are

subject to change without notice due to continuous technology development. No part of

this document may be copied, modified, translated, or distributed in any manner without

the express written permission of us.

If you have any suggestions or would like to learn more details, please visit our website at:

http://www.hytera.com.
 Revision History
Version Date Description Remarks

R1.0 01-28-2011 Initial release

1) Add FAQ

R2.0 05-31-2011 2) Some parameter is added in CPS,

so modify configuration description

1）Add FAQ

R3.0 09-15-2011 2）Some parameter is added in CPS,

so modify configuration description

 Contents

1. Overview ······················································································································· 4

1.1 Definition .............................................................................................................. 4

1.2 Application............................................................................................................ 4

1.3 Principle ............................................................................................................... 5

1.4 Version ................................................................................................................. 6

1.5 Restraint............................................................................................................... 6

1.6 Instructions on UDP Port Configuration for IP Multi-site Connect in R3.5 ............ 7

1.6.1 What is new in the R3.5 ............................................................................. 7

1.6.2 Configuring Related Service ...................................................................... 7

1.6.3 Configuring the UDP Port .......................................................................... 8

2. References·················································································································· 10

3. Requirements···············································································································11

3.1 Requirements on Devices ...................................................................................11

3.2 Requirements on Network...................................................................................11

4. Network Architecture ··································································································· 12

4.1 Four Basic Schemes.......................................................................................... 12

4.1.1 Heavy Overlapping Coverage.................................................................. 12

4.1.2 Non-overlapping Coverage ...................................................................... 12

4.1.3 Minimal Overlapping Coverage................................................................ 13

4.1.4 Multiple Overlapping Coverage................................................................ 14

4.2 Network Topology of IP Multi-site Connect......................................................... 14

4.2.1 Local Area Network.................................................................................. 15

1
 4.2.2 Wide Area Network .................................................................................. 16

4.2.3 WAN and LAN.......................................................................................... 18

4.3 Broadband Wireless Access .............................................................................. 20

4.3.1 Point-to-Point (PTP) and Ethernet Cable ................................................. 20

4.3.2 Point-to-Point (PTP) and Local Area Network (LAN) ............................... 21

4.3.3 Point-to-Point (PTP) Cluster and Local Area Network (LAN) ................... 22

4.3.4 Point-to-Point (PTP) and Wide Area Network (WAN)............................... 22

4.3.5 Point-to-Multipoint (PMP) and Wide Area Network (WAN)....................... 23

4.3.6 Point-to-Multipoint (PMP) Cluster and Local Area Network (LAN) ........... 23

4.3.7 Point-to-Multipoint (PMP) Cluster and Wide Area Network (WAN) .......... 24

5. Equipment Connection and Configuration··································································· 25

5.1 Parameter Configurations .................................................................................. 25

5.2 Ethernet Cable ................................................................................................... 25

5.2.1 Connection Method.................................................................................. 25

5.2.2 Configuring a Terminal ............................................................................. 26

5.2.3 Configuring a Repeater............................................................................ 27

5.3 Local Area Network (LAN).................................................................................. 32

5.3.1 Connection Method.................................................................................. 32

5.3.2 Configuring a Terminal ............................................................................. 33

5.3.3 Configuring a Repeater............................................................................ 34

5.3.3.1 LAN Configuration ......................................................................... 34

5.3.3.2 LAN DHCP Server ......................................................................... 35

5.3.4 Configuring the Switch Device ................................................................. 36

5.4 Wide Area Network (WAN)................................................................................. 37

2
 5.4.1 Connection Method.................................................................................. 37

5.4.2 Configuring a Terminal ............................................................................. 37

5.4.3 Configuring a Repeater............................................................................ 39

5.4.4 Configuring the Switch Device ................................................................. 42

5.4.5 Configuring the Routing Device ............................................................... 42

5.5 Broadband Wireless Access .............................................................................. 42

5.5.1 Connection Method.................................................................................. 42

5.5.2 Configuring a Terminal ............................................................................. 43

5.5.3 Configuring a Repeater............................................................................ 44

5.5.4 Broadband Wireless Access Devices....................................................... 44

5.6 IP Multi-site Access Management ...................................................................... 45

6. Digital Functions Supported in IP Multi-site Connect Mode········································· 47

7. FAQ····························································································································· 48

3
1. Overview
1.1 Definition

IP Multi-site Connect is a function, which enables repeaters in different areas to Switch

data, voice and packets over a TCP/IP-based network.

1.2 Application

IP Multi-site Connect can bring users these typical benefits:

1) To connect two or more conventional communication systems in different areas.

For example, you can use this function to connect two repeaters over a large geographic

area.

2) To construct a more effective communication area with wider coverage.

For example, you can deploy multiple repeaters in a large building to ensure seamless

communication. This can help fight the problems from unfavorable terrains.

3) To broadcast a message to all connected repeaters.

For example, the dispatcher can send an instruction to all repeaters in IP Multi-site

Connect mode in case of an emergency.

4) To connect repeaters working with varied frequency bands.

For example, UHF repeaters and VHF repeaters can be connected so that data and voice

can be exchanged among them.

5) To use multiple IP-based applications.

For example, when IP Multi-site Connect is enabled, you can use multiple IP-based

software (such as Dispatcher) as well as API-based software developed by any third party

to realize more functions.

4
* Consult your dealer for more information on supported software.

* Consult your dealer for more information on development of API-based software.

1.3 Principle

1) IP Multi-site Connect

IP Multi-site Connect is designed to extend the communication coverage by connecting

multiple repeaters in dispersed locations over a TCP/IP-based network.

In IP Multi-site Connect mode, DMR protocol is transported by TCP/IP protocol and a

Hytera-owned protocol at Application Layer. Accordingly, it is reasonable to conclude that

this mode only changes the DMR transmission media without affecting the services of

DMR terminals.

N Sites

One Repeater - Coverage IP Multi-site Connect - Coverage

Figure 1.3-1 Wider Coverage in IP Multi-site Connect Mode

2) TCP/IP Model

The figure below describes how IP Multi-site Connect works:

Application
Hytera-owned transmission protocol
layer
Transport
TCP UDP
layer
Network
IP ICMP
layer
Physical
Subject to specific requirements
layer

Figure 1.3-2 TCP/IP Model

5
z Physical layer: the lowest layer of TCP/IP.

z Network layer: also called IP layer. It is responsible for routing IP packets.

z Transport layer: to set up a session between the source host and the destination

host. It consists of Transmission Control Protocol (TCP) and User Datagram Protocol

(UDP).

z Application layer: to combine and realize the function of Session Layer and

Presentation Layer. It provides application-specific protocols.

As can be seen from the above figure, our IP Multi-site Connect function uses UDP at

Transport Layer and self-owned transmission protocol at Application Layer. At Network

Layer and Physical Layer, different protocols and devices may apply depending on actual

requirements.

1.4 Version

1) R3.0: to release IP Multi-site Connect for the first time;

2) R3.5: to improve IP Multi-site Connect; to release the function "Roaming" and the

application "Repeater Diagnostic and Control" (RDAC);

* R1.0 is designed to give a rough introduction to IP Multi-site Connect, and more

information will be available after R3.5.

* Consult your dealer for more information on DMR conventional series software.

1.5 Restraint

The use of IP Multi-site Connect may be subject to the following conditions:

1) The repeater must operate in Digital mode;

2) The repeater configurations;

6
3) The network type and the configurations of network devices.

1.6 Instructions on UDP Port Configuration for IP

Multi-site Connect in R3.5

The UDP protocol, used for peer-to-peer service, is adopted for the IP Multi-site Connect

feature at the transmission layer. The terminal is capable of IP Multi-site Connect

services via the UDP port.

1.6.1 What is new in the R3.5

In R3.0, the remote RDAC feature is not supported in IP Multi-site Connect mode. In

addition, the IP Multi-site Networking UDP Port is used for providing networking and

digital services.

In R3.5 and later version, the Remote RDAC UDP Port is added for the remote RDAC

feature, and the IP Multi-site Service UDP Port for the digital feature. Thus the IP

Multi-site Networking UDP Port is only used for networking.

1.6.2 Configuring Related Service

To use the features with R3.5 and later version normally, it is required to configure the

services relating IP Multi-site Connect.

Currently there are two services available: IP Multi-site Service and Remote RDAC.

IP Multi-site Service indicates that the terminal can provide digital services such as voice,

data, emergency alarm and supplementary service. These services will not be available

with the terminal unless IP Multi-site Service is checked in the CPS.

7
Options: checked/ unchecked; Default: unchecked.

Note: it is recommended to check this option and configure the appropriate port if this

service is required.

Remote RDAC indicates that the user is allowed to remotely control and diagnose the

repeater in IP Multi-site Connect mode. This service is not available via the RDAC

application unless Remote RDAC is checked in the CPS.

Options: checked/ unchecked. Default: unchecked.

Note: it is recommended to check this option and configure the appropriate port, if this

service is required.

1.6.3 Configuring the UDP Port

To set the UDP port for different service, do as follows:

Master UDP Port is used for the slave repeater to search for the master repeater. This

option is available for slave repeaters only. The Master UDP Port of the slave repeater

must be consistent with the IP Multi-site Networking UDP Port of the master repeater in

the IP multi-site connect system. Otherwise, the slave repeater can not connect to the

master one.

Range: 0~65535; Default: 50000.

IP Multi-site Networking UDP Port is used for networking.

Range: 0~65535; Default: 50000

Note: the value of this port must be different from that of other UDP ports.

IP Multi-site Service UDP Port is used for providing digital services.

Range: 0~65535; Default: 50001.

Note: the value of this port must be different from that of other UDP ports.

Remote RDAC UDP Port is used for providing RDAC service remotely.

8
Range: 0~65535; Default: 50002.

Note: the value of this port must be different from that of other UDP ports.

9
2. References

N/A

10
3. Requirements

3.1 Requirements on Devices

1) Repeaters (see Hytera device list for details)

2) Terminals (see Hytera device list for details)

3) Switch devices (consult your supplier for details)

4) Routing devices (consult your supplier for details)

5) Broadband wireless access devices (consult your supplier for details)

6) Network cables

3.2 Requirements on Network

1) The IP network can either be a dedicated network or an internet provided by Internet

Service Provider (ISP).

2) A number of technologies are supported by the ISPs, including dial-up, xDSL, cable

modem, broadband wireless access, canopy, ISDN, satellite internet access, and so on.

Currently, the IP network is not applicable to dial-up connection due to narrow bandwidth

or satellite internet access due to large delay.

3) Sufficient bandwidth is required for IP network.

4) In IP network, there must be a static IP address and UDP port for Master repeater and

Slave repeater. For the latter, it is unnecessary to fix its IP address and UDP port.

5) The repeater can locate behind the firewall, router or NAT.

6) IP address instead of proxy server shall be used to access the WAN.

11
4. Network Architecture

4.1 Four Basic Schemes

4.1.1 Heavy Overlapping Coverage

In the overlapping areas, different frequencies are used, while in the non-overlapping

areas, the same frequency is employed but different color codes are required for roaming

service. In this scenario, a user may be in the coverage involving 3 to 4 sites at the same

time, and it takes about 10 minutes to move from one site to another.

TX=F1 TX=F3
RX=F2 RX=F4
CC=1 CC=3

TX=F5 TX=F1
RX=F6 RX=F2
CC=2 CC=4

Figure 4.1.1-1 Heavy Overlapping Coverage

4.1.2 Non-overlapping Coverage

This scheme is designed for countryside or part of a small city. It involves multiple

separate sites and no overlapping coverage is present. In the non-overlapping areas, the

same frequency is used while different color codes are required for roaming service. In

this scenario, a user can only enjoy the coverage from one site at the same time, and it

takes several hours to move from one site to another.

12
 TX=F1 TX=F1
RX=F2 RX=F2
CC=1 CC=2

TX=F3 TX=F1
RX=F4 RX=F2
CC=3 CC=4

Figure 4.1.2-1 Non-overlapping Coverage

4.1.3 Minimal Overlapping Coverage

This scheme is designed for communication services along the road, railway, river or

coastline. It involves multiple sites and minimal overlapping coverage. The overlapped

areas share a single frequency, but different color codes are required for roaming service.

In this scenario, a user can enjoy the coverage involving one or two sites at the same time,

and it takes about an hour to move from one site to another.

TX=F1
RX=F2
CC=4

TX=F3
RX=F4
CC=3

TX=F1
RX=F2
CC=2

TX=F5
RX=F6
CC=1

Figure 4.1.3-1 Minimal Overlapping Coverage

13
4.1.4 Multiple Overlapping Coverage

This scheme is designed for a high-rise building or a deep well. It involves multiple sites

standing close from each other and multiple overlapping coverage. Since the coverage of

each site is limited due to adverse geology conditions, frequency reuse is seldom

available, and quick signal attenuation occurs frequently. In this scenario, a user can enjoy

the coverage from one or two sites at the same time, and it takes about 1 minute to move

from one site to another.

TX=F1
RX=F2
CC=1

TX=F3
RX=F4
CC=2

TX=F5
RX=F6
CC=3

TX=F7
RX=F8
CC=4

Figure 4.1.4-1 Multiple Overlapping Coverage

4.2 Network Topology of IP Multi-site Connect

The network topology of IP Multi-site Connect can operate with many networks or can

connect all Wide Area Channels (WACH) via a physical network, depending upon the

repeater location and the network connection. Typically, there are two kinds of network

topologies:

z Local area network (LAN)

z Wide area network (WAN)

In most cases, LAN and WAN together constitute the network topology. In the following

14
sections, details on LAN and WAN will be given respectively.

* The same network configurations may apply to analog/digital repeaters,

enabled/disabled repeaters, wide area/local repeaters or any device developed by a third

party based on IP Multi-site Connect protocols.

4.2.1 Local Area Network

In IP Multi-site Connect mode, these networks are supported:

z Dedicated LAN

z A company’s LAN

z Dedicated radio communication system

Despite variable LAN configurations, the IP Multi-site Connect network system can work

properly once all devices are in the same LAN or connected to some other networks via a

router or NAT. In order for the system to operate at its best, however, the technicians must

have a good knowledge of bandwidth required by related devices.

Additionally, only the Master repeater needs a static IPv4 address, which the other

network devices can use to connect the wide area system.

The following figure shows an example of IP Multi-site Connect operating with LAN. Note

that the network devices may belong to different wide area systems, for example, there

are multiple dispatching centers.

15
 IP Multi-site
Connect Device

Network
IP Multi-site IP Multi-site
Connect Device Connect Device

LAN

IP Multi-site IP Multi-site
Connect Device Connect Device

IP Multi-site
Connect Device

Figure 4.2.1-1 IP Multi-site Connect Network Operating with LAN

4.2.2 Wide Area Network

The biggest advantage of IP Multi-site Connect lies in that it can connect dispersed sites

quickly through the internet provided by an ISP, which provides a range of technologies for

IP Multi-site Connect:

z Dedicated T1

z DSL (typically ADSL)

z Cable modem

z Broadband wireless access such as Canopy

z ISDN

z Frame relay

z others

16
At present, the IP network is not applicable to dial-up connection due to narrow bandwidth

or satellite internet access due to large delay. In order for the system to operate at its best,

the system engineering personnel must have a good knowledge of bandwidth and time

delay required by related devices. In addition, a sound understanding of bandwidth and

time delay between two sites is also required, especially between two distant sites. In

general, the time delay of satellite access across 5 continents is unacceptable, whereas

this problem does not exist with cable communication.

It is necessary to note that a repeater's communication request will be sent to all other

repeaters in the same system. In other words, the bandwidth required by a site correlates

with the sum of repeaters in the system. When a new repeater is added, all other

repeaters would require extra bandwidth.

The IP Multi-site Connect network can work with many routers, NAT and firewalls. It is

recommended to install the repeater behind these devices.

Most routers have a useful function -- secure VPN (Virtual Private Network). The VPN will

not pose a burden on the bandwidth but may result in time delay.

To receive unrequested messages from other repeaters, the Master repeater needs a

static IPv4 address, which the other network devices can use to connect the wide area

system. Additionally, the router, NAT or firewall connecting Master repeater must be

configured properly as well.

The following figure shows an example of IP Multi-site Connect operating with WAN.

Note that the network devices may belong to different wide area systems, for example,

there are multiple dispatching centers.

17
 IP Multi-site
Connect Device

Network
Router

IP Multi-site IP Multi-site
Connect Device Router Router Connect Device

WAN

IP Multi-site IP Multi-site
Connect Device Router Router Connect Device

Router

IP Multi-site
Connect Device

Figure 4.2.2-1 IP Multi-site Connect Network Operating with WAN

4.2.3 WAN and LAN

Generally, WAN and LAN together constitute the network topology, for example, multiple

remote sites or the LAN of two sites can be connected via an ISP.

For WAN, its required bandwidth is related to the number of network devices in IP

Multi-site Connect system, that is, the value shall be the sum of required bandwidth of

each network device; for a site, since the communication request of a repeater will be sent

to all other repeaters in the same system, the ISP bandwidth required for a site is the sum

of all other sites’ bandwidth. When a new repeater is added, all other repeaters would

require extra bandwidth.

Similar to WAN, to receive messages from other repeaters, the Master repeater needs a

static IPv4 address, which the other network devices can use to connect the wide area

system. In a LAN, the repeater containing a static IP address is deemed as the Master

18
repeater by default.

Likewise, the router, NAT or firewall connecting Master repeater must be configured

properly to receive unrequested messages from other repeaters.

For the IP Multi-site Connect network to work over IPv4, the routers in wide area network

must support ”HairPinning” – a function that will send the source address a message

indicating how to reach the destination.

The following figure shows an example of IP Multi-site Connect operating with WAN and

LAN.

Note that the network devices may belong to different wide area systems, for example,

there are multiple dispatching centers.

IP Multi-site
Connect Device

Network
Router

IP Multi-site IP Multi-site
Connect Device Connect Device

LAN WAN
广域网 LAN
Router Router

IP Multi-site IP Multi-site
Connect Device Connect Device

Router

IP Multi-site
Connect Device

Figure 4.2.3-1 IP Multi-site Connect Network System Operating with WAN and LAN

Note: the number of IP devices has an impact on the bandwidth requirement of WAN.

19
4.3 Broadband Wireless Access

IP Multi-site Connect provides a number of schemes for broadband wireless access to

meet your actual needs.

The typical schemes are illustrated as below.

* You can contact your dealer for more information on how to use broadband wireless

access devices (PTP, PMP SM, PMP AP, etc).

4.3.1 Point-to-Point (PTP) and Ethernet Cable

Figure 4.3.1-1 By Point-to-Point (PTP) and Ethernet Cable

20
4.3.2 Point-to-Point (PTP) and Local Area Network (LAN)

Figure 4.3.2-1 By Point-to-Point (PTP) and Local Area Network (LAN)

21
4.3.3 Point-to-Point (PTP) Cluster and Local Area Network

(LAN)

Figure 4.3.3-1 By Point-to-Point (PTP) Cluster and Local Area Network (LAN)

4.3.4 Point-to-Point (PTP) and Wide Area Network (WAN)

LAN2
WAN
LAN1

Figure 4.3.4-1 By Point-to-Point (PTP) and Wide Area Network (WAN)

22
4.3.5 Point-to-Multipoint (PMP) and Wide Area Network (WAN)

LAN2
WAN
LAN1

Figure 4.3.5-1 By Point-to-Multipoint (PMP) and Wide Area Network (WAN)

4.3.6 Point-to-Multipoint (PMP) Cluster and Local Area

Network (LAN)
IP Valid IP Valid

PMP AP PMP AP
Device Device

PMP SM PMP SM PMP SM PMP SM

Device Device Device Device

API Tx WACH1 API Tx WACH1

SW SW
1 Rx WACH2 2 Rx WACH2

Master Repeater Slave Repeater

Figure 4.3.6-1 Point-to-Multipoint (PMP) Cluster and Local Area Network (LAN)

23
4.3.7 Point-to-Multipoint (PMP) Cluster and Wide Area Network

(WAN)

LAN2
LAN1

WAN

Figure 4.3.7-1 Point-to- Multipoint (PMP) Cluster and Wide Area Network (WAN)

24
5. Equipment Connection and Configuration

5.1 Parameter Configurations

The appropriate configuration scheme shall be selected on the basis of network topology

and the actual application. In general, the involved parameters include:

1) Terminal parameters

2) Repeater parameters

3) Routing parameters

4) Broadband wireless access parameters

* Routing devices contain firewall, NAT, router and etc. You can contact your dealer for

their specific configurations.

* Broadband wireless access devices include Canopy and etc. You can contact your

dealer for their specific configurations.

5.2 Ethernet Cable

5.2.1 Connection Method

An Ethernet cable is required to connect two repeaters in this scheme. The disadvantage

of the scheme lies in poor expandability.

25
 Slot Operation Slot Operation
Slot1 or Slot2 Slot1 or Slot2

Terminal B Terminal A

IP Multi-site Connect Rpt IP Multi-site Connect Rpt

Config Config
Slot1（and/or）Slot2 Slot1（and/or）Slot2

Repeater Repeater

Ethernet Cable

Figure 5.2.1-1 Ethernet Cable Connection

5.2.2 Configuring a Terminal

A terminal may be a portable radio or mobile radio. Please refer to Hytera DMR

Conventional Series Terminal List. You can contact your dealer for details.

As the terminal works the same way in both IP Multi-site Connect mode and single

repeater mode, you can refer to the parameter settings in the single repeater mode to

configure it.

To configure a terminal, do as follows:

1) Configure the settings applicable to single repeater mode.

2) Do define the “Slot Operation” option; otherwise, the terminal only operates in DM

mode. For the terminal and repeater, ensure that the same slot must be selected in the

configuration. For example:

2.1) If the “Slot Operation” option is set to ”Slot 1” for the terminal and “IP Multi-site

Connect” to ” Slot 2” for the repeater, the terminal only operates in single repeater mode

rather than in IP Multi-site Connect mode.

26
 2.2) If the “Slot Operation” option is set to ”Slot 1” or “Slot 2” for the terminal and “IP

Multi-site Connect” to ”None” for the repeater, the terminal only operates in single repeater

mode rather than in IP Multi-site Connect mode.

2.3) If the “Slot Operation” option is set to ”Slot 1” for the terminal and “IP Multi-site

Connect” to ”Slot 1” or “Slot1&Slot2” for the repeater, the terminal can operate in IP

Multi-site Connect mode.

3) The Color Code for the terminal must be consistent with the current repeater. Otherwise,

the terminal can not work in the system.

Figure 5.2.2-1 Time Slot and Color Code Configuration

5.2.3 Configuring a Repeater

The simplest IP Multi-site Connect network can be established by connecting two

repeaters back to back. In other words, you can use an Ethernet cable to connect two

repeaters directly. Generally, this scheme is used for cross-band communication or

network service demonstration.

To configure a Master repeater, do as follows:

1) Run the CPS and read the existing configuration data.

27
 Figure 5.2.3-1 Setting ID for the Master Repeater

2) Go to “General Setting->IP Multi-site Network”, and set the “Repeater Type” option

to “IP Multi-site Master”.(See Figure 5.2.3-2 )

3) Leave the “Authentication Key” field at its default values.

4) Be sure that the DHCP option is not selected.

Input static values for the Ethernet IP, Gateway IP, and Netmask. As for all repeaters in the

system, the Ethernet IP and gateway IP shall share the same network address (192.168.2.

×××). (See Figure 5.2.3-2)

Ethernet IP (192.168.2.102): The Master repeater’s static address must be unique in the

system.

Gateway IP (192.168.2.228): this defines an abstract gateway address. There is no

gateway for this configuration, but it is necessary to define an abstract address. The

address must be unique and it is highly recommended that the last digit should not be set

to “0”

Netmask: it defines the IP addresses range-192.168.2.x (x=0-255).

28
 Figure 5.2.3-2 Setting IP Multi-site Network Parameters for the Master Repeater

5) Leave “IP Multi-site Service UDP Port” at the default value. This parameter is used for

keeping network connections.

6) Leave “P2P Firewall Open Timer[sec]” at the default value.

7) To enable DMR service, the “IP Multi-site Service” must be selected, and leave its

related parameter “IP Multi-site Service UDP Port” at the default value.

8) To enable RDAC feature, the “Remote RDAC” must be selected, and leave the related

parameter “Remote RDAC UDP Port” at the default value.

9) Go to “Channel->Digital Channel->CH D1->IP Multi-site Connect”, and choose the

desired slot from the dropdown list. Then, the corresponding slot works as a wide area

channel.

29
 Fig 5.2.3-3 Setting IP Multi-site Connect for the Master Repeater

10) Finally write the new configuration data into the Master repeater via CPS.

To configure a Slave repeater, do as follows:

1) Run the CPS and read the existing configuration data.

Figure 5.2.3-4 Setting ID for the Slave Repeater

2) Go to “General Setting->IP Multi-site Network”, and set the “Repeater Type” option

to “IP Multi-site Slave”.(See Figure 5.2.3-5)

3) Leave the “Authentication Key” field at its default values.

4) Configure the “Master IP”, “Master UDP port” and “Ethernet IP address” in accord

with the Master repeater.

5) Be sure that the DHCP option is not selected.

6) The proper static values must be entered for the Ethernet IP, Gateway IP and Netmask,

making it possible to share the same subnet with Master repeater. (See Figure 5.2.3-5)

Ethernet IP (192.168.2.12): The Slave repeater’s static address must be unique in the

system.

Gateway IP (192.168.2.228): Configured in accordance with the Master repeater.

30
Netmask: Configured in accordance with the Master repeater.

7) Leave “IP Multi-site Service UDP Port” at the default value. This parameter is used for

keeping network connections.

8) Leave “P2P Firewall Open Timer[sec]” at the default value.

9) To enable DMR service, the “IP Multi-site Service” must be selected, and leave its

related parameter “IP Multi-site Service UDP Port” at the default value.

10) To enable RDAC feature, the “Remote RDAC” must be selected, and leave the

related parameter “Remote RDAC UDP Port” at the default value.

11) Leave the “Jitter Buffer Length” at the default value. Its definition is given in the help

file of CPS supplied by Hytera. Only qualified technicians are allowed to change this

parameter.

Fig 5.2.3-5 Setting IP Multi-site Network Parameters for the Slave Repeater

12) Go to “Channel->Digital Channel->CH D1->IP Multi-site Connect”, and choose the

31
desired slot from the dropdown list. Then, the corresponding slot works as a wide area

channel.

Figure 5.2.3-6 Setting IP Multi-site Connect for the Slave Repeater

13) Finally write the new configuration data into the Slave repeater via CPS.

5.3 Local Area Network (LAN)

5.3.1 Connection Method

This scheme is used to connect a switch or multiple switches within the LAN, achieving

seamless communication in the same area.

32
 Slot Operation Slot Operation
Slot1 or Slot2 Slot1 or Slot2

Terminal B Terminal A
Repeater Repeater

IP Multi-site Con. Rpt Switch Switch IP Multi-site Con. Rpt

Config Config
Slot1（and/or）Slot2 Slot1（and/or）Slot2
Cable

Repeater Cable Repeater

Cable
Slot Operation Slot Operation
Slot1 or Slot2 Slot1 or Slot2

Terminal C Terminal D

Figure 5.3.1-1 Local Area Network Connection

5.3.2 Configuring a Terminal

A terminal means a portable radio or mobile radio. Please refer to Hytera DMR

Conventional Series Terminal List. You can contact your dealer for details.

As the terminal works the same way in both IP Multi-site Connect mode and single

repeater mode, you can refer to the parameter settings in single repeater mode to

configure it.

To configure a terminal, do as follows:

1) Configure the settings applicable to single repeater mode.

2) Do define the “Slot Operation” option; otherwise, the terminal only works in DM mode.

For the terminal and repeater, ensure that the same slot must be selected in the

configuration. For example:

33
2.1) If the “Slot Operation” option is set to ”Slot 1” for the terminal and “IP Multi-site

Connect” to ” Slot 2” for the repeater, the terminal only operates in single repeater mode

rather than in IP Multi-site Connect mode.

2.2) If the “Slot Operation” option is set to ”Slot 1” or “Slot 2” for the terminal and “IP

Multi-site Connect” to ”None” for the repeater, the terminal only operates in single

repeater mode rather than in IP Multi-site Connect mode.

2.3) If the “Slot Operation” option is set to ”Slot 1” for the terminal and “IP Multi-site

Connect” to ”Slot 1” or “Slot1&Slot2” for the repeater, the terminal can operate in IP

Multi-site Connect mode.

3) The Color Code for the terminal must be consistent with the current repeater. Otherwise,

the terminal can not work in the system.

Figure 5.3.2-1 Setting Slot Operation and Color Code

5.3.3 Configuring a Repeater

5.3.3.1 LAN Configuration

Adopting the Back to Back configuration, IP Multi-site Connect in the LAN can be

achieved by a switch.

The advantage of this scheme is that more IP access devices, Repeater Diagnostic and

Control (RDAC) applications and PC applications can be added to the system. In addition,

34
it is useful for explaining network topologies.

There is no DHCP server and Gateway for this LAN configuration. Thus the configuration

is consistent with that of “Ethernet Cable”. However, the following points should be taken

into account.

1) The same Authentication Key must be specified for all repeaters and RDAC

applications in the system.

Note: RDAC will be released in R3.5. You can contact your dealer for more information.

2) Go to “General Setting->IP Multi-site Network”, and input the same value in the

“Authentication Key” field for the Master repeater and the Salve repeater.

Figure 5.3.3.1-1 Setting Authentication Key

3) If a repeater is to be added to an existing LAN, its Ethernet IP, Gateway IP and netmask

must work with all devices in LAN properly. Refer to 5.2.3 for more details about how to

create a new LAN or private network.

4) Refer to 5.2.3 for more details about how to configure “IP Multi-site Connect”.

5.3.3.2 LAN DHCP Server

A DHCP server is introduced to the IP Multi-site Connect system within the LAN. The

configuration is consistent with that of “LAN Configuration”; however the following points

should be taken into account.

1) A static IP address shall be assigned to the Master repeater in the system, while the IP

addresses for other Slave repeaters and RDAC applications shall be allocated by the

35
DHCP server dynamically.

2) Any static IP address assigned to an IP site must be outside the range of dynamic IP

addresses assigned by the DHCP server, but within the range of IP address for the

subnet.

3) The IP address for the Slave repeater shall be assigned dynamically as shown in figure

5.3.3.2-1.

Figure 5.3.3.2-1 Setting DHCP

5.3.4 Configuring the Switch Device

The configuration depends on the type of Switch devices. Please consult your dealer for

more information on their configurations!

36
5.4 Wide Area Network (WAN)

5.4.1 Connection Method

This scheme is used to connect multiple sites across different areas. The key to this

scheme is the routing device, which can link with multiple repeaters in different locations

to achieve IP Multi-site Connect in the WAN.

* Routing devices include firewall, NAT, router and etc.

LAN1 LAN2
Slot Operation
Slot1 or Slot2 Switch Slot Operation
Slot1 or Slot2

Terminal B Cable Terminal A

Repeater Router Repeater

Cable

IP Multi-site Con. Rpt IP Multi-site Con. Rpt

Config WAN Config
Slot1(and/or) Slot2 Slot1 (and/or) Slot2

Cable
Router

Repeater Repeater
Cable
Slot Operation Slot Operation
Slot1 or Slot2 Slot1 or Slot2
Switch
Terminal C Terminal D

Figure 5.4.1-1 WAN Connection

5.4.2 Configuring a Terminal

* A terminal means a portable radio or mobile radio. Please refer to Hytera DMR

Conventional Series Terminal List. You can contact your dealer for details.

As the terminal works the same way in both IP Multi-site Connect mode and single

repeater mode, you can refer to the parameter settings in single repeater mode to

37
configure it.

To configure a terminal, do as follows:

1) Configure the settings applicable to single repeater mode.

2) Do define the “Slot Operation” option; otherwise, the terminal only works in DM mode.

For the terminal and repeater, ensure that the same slot must be selected in the

configuration. For example:

2.1) If the “Slot Operation” option is set to ”Slot 1” for the terminal and “IP Multi-site

Connect” to ” Slot 2” for the repeater, the terminal only operates in single repeater mode

rather than in IP Multi-site Connect mode.

2.2) If the “Slot Operation” option is set to ”Slot 1” or “Slot 2” for the terminal and “IP

Multi-site Connect” to ”None” for the repeater, the terminal only operates in single repeater

mode rather than in IP Multi-site Connect mode.

2.3) If the “Slot Operation” option is set to ”Slot 1” for the terminal and “IP Multi-site

Connect” to ”Slot 1” or “Slot1&Slot2” for the repeater, the terminal can operate in IP

Multi-site Connect mode.

3) The Color Code for the terminal must be consistent with the current repeater. Otherwise,

the terminal can not work in the system.

Figure 5.4.2-1 Setting Slot Operation and Color Code

38
5.4.3 Configuring a Repeater

As usual, the IP Multi-site Connect system contains many Wide Area Networks and

Local Area Networks linked by routers. The public network is a typical example, which is

capable of connecting many LANs to the WAN by ADSL.

In the above system, the IP address for the Master repeater is assigned to LAN1 statically,

as the following figure shows.

Figure 5.4.3-1 Setting IP Address for the Master Repeater

The Ethernet IP (e.g. the Master repeater’s IP address) is beyond the range of IP

addresses assigned by the DHCP Server, but still within the range of IP addresses for the

subnet (as specified by the Gateway Netmask for the devices on the LAN). Thus the

Gateway IP address shall conform to the LAN1 IP address of the router.

As a result, all Slave repeater and RDAC applications shall get the IP address assigned

by their respective LAN DHCP servers.

Figure 5.4.3-2 Assigning IP Address by the DHCP Server

The WAN address used by the Master repeater must be shared by all Slave repeaters and

RDAC applications.

39
 Figure 5.4.3-3 Setting the WAN Address for the Slave Repeater

When configuring the Slave repeaters and RDAC application, the WAN address of router

in LAN 1 shall be applied to the IP address field of Master repeater, because the IP

addresses of all devices are configured within the router netmask, so they can not be

identified in the WAN. Thus, “Port Forwarding” must be configured for all LAN1 routers,

forwarding the incoming packet from the defined port of the WAN to the Master repeater.

In the current configuration, the UDP port in the WAN is the same as in the Master

repeater. In reality, different UDP ports can be defined to the WAN and the Master

repeater, as long as all Slave repeaters and RDAC applications share the same port in the

WAN.

The following points should be taken into account in this configuration:

1）Do not configure "Port Forwarding" for the Slave repeater and RDAC applications,

since their routers can perform it automatically.

2) The public IP addresses for all Slave repeaters and RDAC applications are notified by

the Master repeater upon connecting the Slave repeaters.

3) The Slave repeaters on a certain LAN do not need to be configured with same UDP

port, as the router will distribute a unique port during forwarding.

4) The public IP address and port assigned by the router to a given Slave repeater will be

taken back if they are not in use within a pre-defined time limit. In this case, all Slave

repeaters and RDAC applications must transmit “Keep Alive” message regularly. The

frequency for transmitting such messages can be set in the “P2P Firewall Open Timer

(sec)” field. Make sure that the value of this field is less than the duration which the router

keeps alive.

Figure 5.4.3-4 Setting P2P Firewall Open Timer (sec)

5) The IP address of the Master repeater must be configured into the WAN address rather

than the LAN address, as for all Slave repeaters and RDAC applications on the Master

repeater’s LAN. Otherwise, repeaters from other LANs can not link with RDAC

40
applications.

6) The LAN 1 and LAN 2 routers must support “HairPinning”, which ensures that the WAN

address can not be replaced by the subnet address.

7) Some routers that support partial “HairPinning” may not support all repeaters and

RDAC applications on the Master repeater’s LAN. But they can still support other

repeaters and RDAC applications, which are not in the same LAN as the Master repeater

8) The Delay will be introduced by the IP network.

9) The detailed configuration of IP Multi-site Connect is shown in Figure 5.4.3-5.

Note: not all routers are able to support “Port Forwarding”.

Figure 5.4.3-5 Setting IP Multi-site Network

10) Some private network (e.g. Intranets) is capable of addressing all devices by their IP

addresses. When a device is connected to this network, the DHCP server will assign the

IP address to it and adjust the router to map the packet to the appropriate Master repeater.

41
Meanwhile, a static IP address is required for the Master repeater.

5.4.4 Configuring the Switch Device

The configuration varies greatly according to different Switch devices. Please consult your

dealer for more information on configurations!

5.4.5 Configuring the Routing Device

The configuration varies greatly according to different routing devices. Please consult your

dealer for more information on the specific configuration!

5.5 Broadband Wireless Access

5.5.1 Connection Method

This scheme is used to link multiple sites across areas. The key to this solution is that

broadband wireless access devices and Canopy are employed to facilitate the

communication of multiple repeaters in dispersed locations. For instance, communication

can be achieved by means of the wireless link including microwave, WiFi, 3G and 4G. It is

an ideal solution for emergency communication.

42
 Slot Operation
Slot1 or Slot2

Slot Operation
Terminal B BWA Device Slot1 or Slot2
Repeater

Terminal A
IP Multi-site Con. Rpt
Config
Slot1（and/or）Slot2
IP Multi-site Con. Rpt
Config Cable
Slot1（and/or）Slot2

BWA Device Repeater

Cable

Figure 5.5.1-1 Broadband Wireless Access

5.5.2 Configuring a Terminal

A terminal means a portable radio or mobile radio. Please refer to Hytera DMR

Conventional Series Terminal List. You can contact your dealer for details.

As the terminal works the same way in both IP Multi-site Connect mode and single

repeater mode, you can refer to the parameter settings in single repeater mode to

configure it.

To configure a terminal, do as follows:

1) Configure the settings applicable to single repeater mode.

2) Do define the “Slot Operation” option; otherwise, the terminal only works in DM mode.

Ensure that the same slot must be specified for the terminal and repeater in the system.

For example:

2.1) If the “Slot Operation” option is set to ”Slot 1” for the terminal and “IP Multi-site

Connect” to ” Slot 2” for the repeater, the terminal only operates in single repeater mode

rather than in IP Multi-site Connect mode.

43
2.2) If the “Slot Operation” option is set to ”Slot 1” or “Slot 2” for the terminal and “IP

Multi-site Connect” to ”None” for the repeater, the terminal only operates in single repeater

mode rather than in IP Multi-site Connect mode.

2.3) If the “Slot Operation” option is set to ”Slot 1” for the terminal and “IP Multi-site

Connect” to ”Slot 1” or “Slot1&Slot2” for the repeater, the terminal can operate in IP

Multi-site Connect mode.

3) The Color Code for the terminal must be consistent with the current repeater. Otherwise,

the terminal can not work in the system.

Figure 5.5.2-1 Slot Operation and Color Code

5.5.3 Configuring a Repeater

The repeater is configured as per the specific network used in broadband wireless access

mode. For further details, refer to “Ethernet Cable”, “Local Area Network” and ”Wide Area

Network”.

If you have any question, please contact your dealer.

5.5.4 Broadband Wireless Access Devices

The configuration varies greatly according to different broadband wireless access devices.

Please consult your dealer for more information on configurations!

44
5.6 IP Multi-site Access Management

To achieve better resource efficiency and flexible networking, you can use the CPS to

include the terminal/group ID to be called into a list for access management. The repeater

will only retransmit the call whose ID is included in the ID list after receiving a call request.

Other call requests shall be discarded to reduce network load.

How to configure IP Multi-site Access Management

1. Go to “General Setting -> Access Manager” from the navigation tree on the left.

Then you will see the figure 5.6-1 IP Multi-site Access Management

Figure 5.6-1 IP Multi-site Access Management

2. In the above interface, you can:

(1) Enable or disable access management by checking or unchecking IP Multi-site

Access Management option.

(2) Set the ID list and ID quantity. 32 lists are available at most.

(3) Set the Start ID and End ID to define the ID range (1~16776415). Please note that the

45
End ID must be greater than the Start ID. The difference can be up to 255.

(4) Set the call type, including Private Call and Group Call.

3. After the above steps are finished, write the configuration data into the repeater.

46
6. Digital Functions Supported in IP Multi-site Connect
Mode

Terminals (portable radio and mobile radio) are capable of providing a set of digital

services (R3.0) in IP Multi-site Connect mode, as the following table shows.

Functions

Voice Supplementary Data Emergency

Other Functions
Service Service Service Service

PTT ID and Emergency Dual WACH

Private Call Message
Alias Alarm (Slot1 & Slot 2)

Radio Enable/ Emergency

Group Call *GPS WACH and LACH
Radio Disable Call

Emergency
Basic and
All Call Remote Monitor *ADK Alarm
Full Encryption
w/Call

Revert
Radio Check Pseudo Trunking
Channel

Alert Call Lone Worker Time-out Timer (TOT)

Man Down *Scan

The specific function is subject to the software version.

* : indicates that the function is partially available at present. For more information,

please consult your dealer.

Table 6-1 Digital Functions Supported in IP Multi-site Connect Mode

47
7. FAQ

7.1 Can other repeaters work normally when one of the

repeaters fails

Yes. The entire network is similar to a peer-to-peer network. The Master repeater is used

for registration and broadcasting address. If a Slave repeater disconnects, the Master

repeater can detect and broadcast it to other Slave repeaters; if the Master repeater

disconnects, all Slave repeaters still can work. However, new address can not be added

and the status of other repeaters can not be acquired until the Master repeater restores to

normal operation.

7.2 How to select frequency and color code in IP

Multi-site Connect network

You can select the proper networking scheme as per your actual needs, as stated in

section 4.1. In the overlapping area, it is recommended that the frequency of the repeater

be different, but the color code can be the same or varied. For adjacent repeaters sharing

the same frequency, it is better to use different color code to avoid probable interference.

7.3 What is the difference between IP Multi-site

Connect network system and simulcast system

1) In a simulcast system, the Switch center or server is a must, which is used to receive

and transmit data and time sequence. And the repeater acts as a transceiver. Therefore,

the Switch center or server shall be available at any time, and a hot backup is required If

necessary.

48
For IP Multi-site Connect network, there is no independent Switch center or server. One

repeater operates as the master one and other repeaters as the slave ones. Each works

independently.

2) The simulcast system is capable of time sequence synchronization, enabling the

transceiver to use the same frequency in overlapping area, but in IP Multi-site Connect

network, different repeaters shall use different frequencies to achieve quality

communication.

3) At present, the IP Multi-site Connect network supports 15 repeaters at most, while the

simulcast system has no limit on the number of repeaters.

7.4 How to upgrade a single repeater system to IP

Multi-site Connect network system

Terminals (portable radio and mobile radio) in single site mode can communicate with

those in IP Multi-site Connect mode. If you want to upgrade the single repeater system,

you just need to upgrade the existing software and configure all parameters again for the

repeater and terminal.

The API application configured for the terminal in single repeater system can work

normally in IP Multi-site Network without update.

7.5 What factors shall be considered when

establishing an IP Multi-site Connect network

The network establishment and configuration are determined by the devices and IP

network. You’d better get help from the network administrator due to the complicate

networking environments.

49
Some common factors are listed below:

1) Ensure that there is no conflicting IP address, which can break off communication. If

the DHCP option is selected, the static IP address might as well be outside the range of

the addresses which are available to be allocated. It can avoid the conflicting address

assigned by the DHCP server.

2) The Quality of Service (QoS) can be introduced to the router in the Ethernet network to

assure you quality communication, provided that there are other networking devices

acting as IP networking ones in IP Multi-site Connect network. In addition, it is necessary

to enhance the communication priority and reserve adequate bandwidth.

3) Be sure that the UDP port is free from restriction of the firewall. Otherwise, it can block

the IP address or the UDP port operated in IP network. For more information, please

consult the local network administrator or ISP.

4) It is better to choose an ISP who can provide unlimited traffic services, because the

voice transmission over internet may lead to heavy traffic. For an IP Multi-site Connect

network containing 5/15 repeaters, 20/65 GB traffic is required per month.

7.6 Router, Switch and Firewall scenarios

Routers operate at the third layer of the OSI architecture, namely, the network layer, which

is responsible for logic addressing including routing functions and corresponding IP

protocol. Accordingly, routers are usually deployed on the edge of the networks to connect

different networks. For instance, routers are required for communication between

sub-networks as the following diagram shown.

50
 Router C
Net C

Router B

Net B
Net A
Router A

Figure 7.6-1 ：Diagram of the route

The router is mainly deployed in the following scenarios upon networking :

1) It is used to connect other networks, such as the public network. (For example, Special

line or XDSL via PPPoE dial).

2) It is used to connect one sub-network to another. For example, if 192.168.2.X is

attached to 192.168.1.X, the router is required for communication between edges of these

two networks.

Switch operate at the second layer of the OSI architecture, namely, link layer, which is

responsible for connecting desired network function units as per the user’s requirements.

For example, to establish a local area network, connect the computers and other network

devices via Switch. In this way, data can be normally transmitted between these devices.

A firewall is a kind of barrier to access between the LAN and WAN, or between the private

network and public network. It can permit data transmissions based upon a set of rules. To

some extent, the firewall can also perform basic routing functions.

7.7 Required Bandwidth Calculation

Generally, the required bandwidth is calculated on the basis of the amount of data

transferred by one repeater in the IP Multi-site system. When two time slots in digital

51
channel are utilized simultaneously, such amount of data (including some additional data)

is about 25Kbps. If the total number of the repeaters in the system is N, the bandwidth can

be calculated according to the expression : (N - 1) * 25 Kbps.

7.8 Compatibility between Ethernet and Other Links

Different links (such as microwave, optical fiber, T1 and E1) may exist upon networking.

Actually, most links are compatible with the Ethernet. Therefore, to build the IP Multi-site

system containing different links, bridges are needed between the Ethernet and other links.

For example, microwave bridges are required for communication between the microwave

link and the Ethernet.

Figure 7.8-1 ：Diagram of the Ethernet and Microwave Linking

7.9 Recommended Router and Switch

Router: CISCO 1841, CISCO 2801

Switch: ( To be confirmed and tested. For more information, please consult your dealer.)

7.10 System Safety

To access the network composed of RD98X, the terminal must comply with relevant

application layer protocol and provide authorization code during registration. The protocol

command is encrypted. To connect the terminal via public network, it is recommended to

52
use firewall.

7.11 How many repeaters we supported in a wide area

systems under a single master

From the DMR Tier II protocol, given a slot timing of 30ms each (dual slot = 60ms), when

operating under the IP Multi-site interconnect system, each repeater shall need to transfer

all the voice/data to all slave repeaters in a given 30ms. With a 30% reserve margin for

other activity that could arise and to guarantee the wide area system voice/data transfer

performance, this has tighten the transfer time from 30ms to 21ms!. Given this design goal,

we have enhanced the slave repeaters IP data transfer rate and has successfully increase

the slave repeaters support from 16 in R3.0 to 22 in R3.5! Please note that the Hytera

RND team is still optimizing the slave amount and is continually researching to increase

the slave amount to be close to 30, promising more delighters to customer upcoming.

Please stay tune for a higher number of slave repeaters in upcoming release! (Given a

single slot wide area system operation, the amount of slave repeaters supported shall

goes up to 44 slave repeaters, as compare to 22 repeaters in a dual slot wide area system

operation)

7.12. How to access Internet with ADSL

Internet

Phone Line

Modem

Repeater

Router

53
 Figure1: Internet Access with ADSL

The way of accessing Internet with ADSL is shown in figure 1. That is how IP Multi-site

Connect works. To achieve Internet access, these configurations are required:

1. Connect the repeater with the router, as shown in figure 1. Please note that the

master repeater can access the Internet directly via a modem.

2. For master repeater, the Ethernet IP and Gateway IP shall be configured manually;

but for slave repeater, you can use DHCP to assign the Ethernet IP automatically. Please

note that the Master IP under IP Multisite Master and IP Multisite Slave must be

consistent.

3. Configure the router and modem (see the following section for details). Generally,

default configurations are recommended.

Caution: In case of connected computer or repeater ping failure, it is recommended to use

mapping polity instead of DZM policy to avoid attach from the wide area network.

4. When the above configurations are done, make dial-up access to Internet.

To ensure normal Internet access, it is recommended to use CISCO router (model: CISCO

1841). The modem is supplied by your Internet Service Provider.

CISCO 1841 shall be configured as follows:

FE0/1 WAN address is obtained via dial-up, and FE 0/0 address is 192.168.1.1. The

dynamic IP address of slave repeater is configured by DHCP. Its range is 192.168.1.2

~192.168.1.255.

When the router is connected to a computer, power it up and run the commands below:

(1) To configure VPDN

HyteraRouter1>enable

//to enter administrator mode

54
HyteraRouter1#configure terminal

//to enter configuration mode

HyteraRouter1(config)#vpdn enable

//to enable the router’s virtual private dial-up network (VPDN)

HyteraRouter1(config)#vpdn-group office

//to create a VPDN group

HyteraRouter1(config-vpdn)#request-dialin

//to initiate a VPDN tunnel and to create a VPDN subgroup for dial-in request

HyteraRouter1(config-vpdn-req-in)#

HyteraRouter1(config-vpdn-req-in)#exit

HyteraRouter1(config-vpdn)#exit

(2) To configure the router interface connecting ADSL modem

HyteraRouter1(config)#interface fastEthernet 0/1

//to configure external network interface “FE 0/1”

HyteraRouter1(config-if)#no ip address

//not to configure any IP address

HyteraRouter1(config-if)#pppoe enable

//to enable pppoe protocol

HyteraRouter1(config-if)#pppoe-client dial-pool-number 1

//to add pppoe dial-up client to dial-up pool 1

(3) To configure logic dial-up interface

HyteraRouter1(config-if)#interface dialer1

//to configure virtual interface dialer1

HyteraRouter1(config-if)#ip address negotiated

55
//to get IP address from ADSL service provider

HyteraRouter1(config-if)#ip nat outside

//to enable NAT

HyteraRouter1(config-if)#encapsulation ppp

//to encapsulate PPP protocol for this interface

HyteraRouter1(config-if)#dialer pool 1

//to dial up with dial-up pool 1

HyteraRouter1(config-if)#dialer-group 1

HyteraRouter1(config-if)#ppp authentication pap callin

//to enable PPP PAP authentication. When CHAP is used here, “username” in the

command below shall be changed to “hostname”

HyteraRouter1(config-if)#ppp pap sent-username xxxxxx passworkd 0 yyyyyy

//to use the existing user name and password; “0” indicates encryption strength.

HyteraRouter1(config-if)#exit

(4) To configure internal network interface

HyteraRouter1(config)#interface fastEthernet 0/0

//to configure internal network interface “FE 0/0”

HyteraRouter1(config-if)#ip address 192.168.1.1 255.255.255.0

//to configure the IP address

HyteraRouter1(config-if)#ip nat inside

//to enable NAT

HyteraRouter1(config-if)#exit

(5) To configure the router to provide DHCP services for slave repeater

HyteraRouter1(config)#ip dhcp excluded-address 192.168.1.1

56
//to exclude unnecessary address

HyteraRouter1(config)#ip dhcp pool ABC

//to define the address pool

HyteraRouter1(dhcp-config)#import all

//to import DNS and WINS server

HyteraRouter1(dhcp-config)#network 192.168.1.0 255.255.255.0

HyteraRouter1(dhcp-config)#default-router 192.168.1.1

//to set the default gateway

HyteraRouter1(dhcp-config)#exit

(6) To configure NAT

HyteraRouter1(config)#access-list 1 permit 192.168.1.0 0.0.0.255

HyteraRouter1(config)#ip nat inside source list 1 interface dialer1 overload

//to translate the address

(7) To configure default route

HyteraRouter1(config)#ip route 0.0.0.0 0.0.0.0 dialer1

//to define the default route

7.13. What do you need to care when to access

Internet with LAN

When port mapping is not needed, an Ethernet IP address is not required in the internal

57
network. For the slave repeater, it can obtain the IP address dynamically from DHCP.

When port mapping is needed, an Ethernet IP address and port mapping among IP

multi-site service UDP port, IP multi-site networking UDP port, and remote RDAC UDP

port are required as for the master repeater and slave repeater. The need for port

mapping has much to do with the selected router. When IP multi-site networking fails, port

mapping will be a must. If our recommended router is used, neither port mapping nor an

Ethernet IP address for the slave repeater will be required.

Master Repeater

Router A Router B
WAN

LAN LAN

Slave Repeater A Slave Repeater B

The slave repeater A and slave repeater B locate in different LANs, which have different

network addresses (as shown above). In this case, the slave repeater must have an

Ethernet IP address for port mapping so as to connect to the master repeater and other

slave repeaters. Please refer to the appropriate router manual for details. As the

designated IP address may conflict with the IP address of other devices in the LAN, you

can use DHCP to assign an Ethernet IP address dynamically. Such IP address and MAC

address must be set in the router. Please refer to the appropriate router manual for details.

58
7.14. What do you need to care when to access

Internet with two LANs

The way of Internet access with one or two LANs is the same. Only when port mapping is

needed, an Ethernet IP address is required in the internal network. In case of accessing

internet with two LANs, it is necessary to perform port mapping twice as shown below:

Master Repeater

Router A2 Router B2
WAN

LAN A2 LAN B2

Router B1

Router A1
LAN A1 LAN B1

Slave Repeater B
Slave Repeater A

The slave repeater A and slave repeater B locate in different LANs (LAN A1 and LAN B1),

which have different network addresses. In this case, if port mapping is needed, the slave

repeater must have an Ethernet IP address, and then perform the first port mapping by the

router in the LAN A1 or LAN B1, and then the second port mapping by the router in the

LAN A2 or LAN B2.

59
7.15. What are the functions and precautions of jitter

buffer, How to deal with bad communication caused by

network transmission delay

The UPD protocol, used for peer-to-peer service, is adopted for IP Multi-site Connect

feature at the transmission layer. It has no acknowledgements or re-transmissions

mechanism from the receiver to the sender. During transmission, as the UDP data packet

from the same node goes through different intermediate nodes to reach different

destination nodes, the packet jitter and disorder will occur. In addition, the data packet

may be lost when the network communication is poor.

The role of Jitter Buffer feature is to re-order the UDP data packet, buffer it and send it

later, which has no impact on signal. This is because the frame is sent or received at a

regular interval benefiting from the TDMA technology.

A UDP data packet is deemed to be lost if the time gap between it and last UDP data

packet arriving at the same node is over the threshold value. The buffer duration shall be

over this threshold. You can configure this duration according to the number of jitter buffer.

The buffer duration ranges from 1*60 ms (default) to 8*60 ms.

You shall set the buffer duration according to the actual network transmission quality.

Shorter buffer duration means fewer packets to be buffered and less network delay to be

tolerated; on the contrary, more packets will be buffered and more network delay will be

tolerated, but this causes longer retransmission duration. Judging from this, buffer

duration increase is a double-edged sword. On the one hand, it improves UDP data

packet loss; on the other hand, it increases network transmission delay, which may affect

the digital services with acknowledgement required.

Currently, the network delay is measured by using Ping command. In a LAN or private

network where the network delay is generally less than 60ms, it is recommended to use

60
the default duration of jitter buffer. However, in other network where the network delay is

greater than 60ms, the duration is subject to actual requirements.

When the IP Multi-site Connect feature is utilized in a WAN, the jitter buffer may not help a

lot due to bandwidth limitation and network resource preemption. Considering this case, it

is recommended to use the public network or establish your private network for better

communication.

7.16. How does the voice and data delay or loss affect

the communication

In IP Multi-site Connect mode, the repeater will add a silent frame as compensation to the

voice or data packet lost during transmission. Accordingly, the communication with a

terminal will be discontinuous. In case two voice and data packets are lost consecutively,

the repeater will judge the call as abnormal and abort it automatically. Then no repeating

is available unless new voice and data packet or call request is received.

If the data packet delay occurs to the digital service for more than the defined duration in

the Jitter Buffer, the packet will be lost, resulting in acknowledgement failure.

61