PTC760
TETRA
- It works on EBTS as well as on CTS.
- Group calls, individual calls (duplex and simplex), scan-lists work well. Phone calls require to switch radio to full-duplex mode first (how they are going to make phone calls in half-duplex? ;)).
- PD and SDS don’t work at all. Since I have tested it on EBTS and CTS, it’s FW bug (3.5, from the factory). I was checking with adb and it seems there is a kind of mismatch between NB and Android parts of device. At least in case of PD phase of PDP attach finishes well, CHAP works correctly, the problem comes on the latest part of attach on the radio.
- It has some specific with spacing configuration. Standard spacings 0-4 are hardcoded in FW. User-defined spacing uses index 7.
So if your EBTS/MBTS/MTS uses 7.6 spacing at index 7 there is no problem. But in case of CTS there is a difficult. CTS allows only to configure spacing to indexes 0-4 or so. So since i use CTS as a „hotspot“ with dummy load I decided to switch spacing to index 3 and 8 MHz by moving lower frequency down a bit. Most of CTSs use index 1 with 7.6 to fit to allocation with keeping limitations in mind.
RoIP
Tested on A7 3.5 and A10 4.5 firmwares.
- User name - your ID
- Password - your BM’s hotspot password
- MNI - set what do you use in TMO configuration, most probably its 901 9999
- Server - core.tetrapack.online (domain name, not IP! that's strict)
- Port - use standard 3003
Location / APRS
APRS location information is accepted from the PTC760 via RoIP and RF, configured in the same way as the Dimetra APRS Settings.
The PTC760 also allows you to specify a LIP Location for both TMO/RoIP and DMO separately, meaning your APRS should work between TetraPack and the HAM-TETRA networks seamlessly.
General Location Service Settings
Example Triggers
Control Centers (Destinations)
Remember that on TetraPack there is only 1x destination for Location Data, 200999
What you have to know else:
We have call floor management but without late call entry. So when call will be preempted or overlapped the next one will come only when the it begins. Only Scan List are affected with this specific. In general the late call entry is supported by TetraPack inside each GSSI.
Scan lists and SDSs are supported.
No Comments