View source for Hytera/Repeaters ← Hytera/Repeaters

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: Users.

You can view and copy the source of this page.

Templates used on this page:

Return to Hytera/Repeaters.

Retrieved from "https://wiki.brandmeister.network/index.php/Hytera/Repeaters"
No image
Hytera R988
Vendor Hytera
Model R988
Firmware A8.00.09.001
Website unspecified
Modes
DMR Yes D-Star Yes
Tetra Yes P25 Yes
Terminal support
Group call Yes Voice call Yes
SMS Yes IP Yes
GPS Yes ARS/RRS Yes
DMR Protocol support
Talker Alias Yes In call GPS Yes



Hytera[edit]

Here is a link to all you wanted to know about Hytera. Some quick points, Hytera is the parent to HYT but NOT TYT. Hytera prides itself on being the world leader in DMR Tier II and III standards based systems. Worldwide it is only second to Motorola in the public safety market. https://en.wikipedia.org/wiki/Hytera

Hytera Model Breakdown[edit]

Hytera distinguishes its models by the use of Letters and Numbers Typically in a LL-NNN format which is explained below. X is used as a null placeholder for the model breakout.

Letters[edit]

LX: Radio Type

XL: Radio Capability

Numbers[edit]

#XX: Class of equipment

X#X: Interface Type

XX#: Country Code

Tested equipment[edit]

Repeater models:

Firmwares:

Until further notice, we highly recommend sysops to keep Hytera repeaters on firwmare v8 when connecting to BrandMeister. Updating to a non tested version may break connectitvity to the network in case they changed something in the protocol.

Configuration guide[edit]

Configuration of Hytera Repeater
================================

IP MultI-Site Connect
---------------------
Manual Set DNS On/Off:              checked
DNS Server IP:                      8.8.8.8 (for example :-)
Repeater Type:                      IP Multi-Site Slave
Jitter Buffer Length:               8
Master UDP-Port:                    50000
IP Multi-Site Networking UDP-Port:  50000
IP Multi-Site Service:              checked
IP Multi-Site Service UDP Port:     50001
Remote RDAC:                        checked
Remote RDAC UDP-Port:               50002
Master Domain On/Off:               checked
Domain Names:                       master.example.com (for example :-)

New generation of hytera repeaters (HR106x series) don't support RDAC, they use SNMP instead. Also it is important to forward local SNMP port on your router, external port should match the port configured in codeplug. 

SNMP
---------------------
SNMP Trap Port:                 50001
SNMP Trap IP:                   ip address of master server
SNMP Trap Interval:             10
SNMP Local Port:                can be any >= 161
Broadcast Trap Enable:          checked
GPS Trap Enable:                checked
Local Machine Info Trap Enable: checked
XNMS Access Code:               should not be 'public'. change it.

Issues with connectivity[edit]

Authentication[edit]

Typically the Hytera repeater has issues with an empty Network Authentication Key field. When you clear the password, it is still sending encrypted connection requests to the server. To solve this problem, you need to fill some text into the password field and upload the codeplug into the repeater then clear the password and upload the codeplug again.

NAT traversal[edit]

BrandMeister has NAT traversal mechanism for Hytera repeaters. If you have experience with network DMR+ you need to switch off all existing rules of port forwarding.

Version 9 firmware[edit]

Dropping out calls: set Repeater Repeat priority to "IP Connect Repeating" under "General Settings" -> "Accessories"

Photo 2019-08-28 08-59-21.jpg

Specific cases[edit]

To avoid problems with strong NAT or multiple repeaters behind single IP we created special tool TellusAgent. TellusAgent is a simple daemon that can run on very cheap hardware such as Raspberry Pi and act as a proxy server for repeater. TellusAgent supports single port IPv4/IPv6 connection on the uplink side and can be run multiple times on the single host inside your intranet.

TellusAgent should be run as many times as many repeaters you have connected by (one instance proxifies single repeater only)

Arguments: 

    --connect-port <local port for Master service>
    --control-port <local port for RDAC service>
    --media-port <local port for DMR service>
    --server-address <domain name of BrandMeister DMR Server>
    --server-port <service port of BrandMeister DMR Server>
    --service-mode <set of bits>
        bit 0 - print to standard output
        bit 1 - print to system log
        bit 2 - run as daemon

Source Code of TellusAgent

https://code.brandmeister.network/r3abm/TellusAgent

Unexpected VSWR alarm[edit]

With latest firmware (A8) there seems to be some bug with false VSWR alarms. Uncheck the forward power / VSWR alarm options, to get rid off those annoying messages until they fix in some later release.


Wrong frequency on Dashboard or other strange behavior[edit]

After changing the frequency on Hytera RD625 - BM dashboard still shows original frequency, not the actual. Repeater normally operates without problems. Looking into the Logs - BM is seeing that the master sends the wrong frequency. (Still the original one before the change) Following will not help: reboot, power OFF / ON, change of channel.

Solution was that I took from another CPS file from another repeater, modified it and applied to RD625 in question.

The probable cause of this problem was the upgrade from version 7.0.x to 7.6.x. When this upgrade happens – it should convert repeaters codeplug to newer CPS and it probably was not successful.

On new generation repeaters (HR10xx) It is strongly advised that you set up only one zone, with one channel.