Motorola

Setting up Dummy and LogCollector for a TETRAPack connection

Disclaimer

Hardware requirements

Prep work

CTS Setup

  1. Get a clear view of how the CTS is configured, and its necessary configuration files: bssparams.txt, set_x_gp, gm, sc, sub.csv, etc. Please make sure everything works as a standalone site before starting this entire endeavour!
  2. You also need good way to remotely connect to the CTS management interface (VNC is a good option).
  3. Plan ahead and make a list of the BrandMeister TGs you want your CTS to handle. Add them already to set_x_gp and gm.csv, reboot everything and make sure they already work locally in standalone mode.
  4. Open up bssparams.txt on your CTS, and do the following edits. Don't change anything else at this state: 
    ## Base-Station Parameters ################################################################
#### Set the name to something simple, short, no special caracters
/base-station/name = "CTSBS";
#### set this to id 1
/base-station/base-station-id = 1;
#### add or replace:
/base-station/standalone-mode = false;
#### add or replace:
/base-station/use-local-site-fall-back = false;

## Air Interface BLE Parameters ###########################################################
/base-station/BLE/neighbour-cells = 191;

## SDS Gateway Parameters #################################################################
#### Remove all other lines, replace by:
/system/sds-gateway/host-1 = { issi = 262999; ip-address = "44.225.64.18";};
/system/sds-gateway/host-2 = { issi = 250999; ip-address = "44.225.64.19";};
/system/sds-gateway/host-3 = { issi = 16777184; ip-address = "44.225.64.20";};
# These ISSIs will be used for SMS and GPS services (via GWPC emulation, IP addresses don't matter)

## E1 Layout Parameters ###################################################################
### Remove all other E1 layout lines, and replace byt this:
/network/E1-layout/time-slot-01 = { source-type = "SIGNALLING"; };
/network/E1-layout/time-slot-02 = { source-type = "SIGNALLING"; };
/network/E1-layout/time-slot-03 = { source-type = "SIGNALLING"; };
/network/E1-layout/time-slot-04 = { source-type = "SIGNALLING"; };

#### Real BS transceivers
/network/E1-layout/time-slot-17 = { source-type = "BS"; base-station-id = 1; l-transceiver-id = 11; };

#### Dummy's emulated BS transceivers
/network/E1-layout/time-slot-22 = { source-type = "BS"; base-station-id = 8; l-transceiver-id = 11; u-transceiver-id = 12;};
/network/E1-layout/time-slot-23 = { source-type = "BS"; base-station-id = 8; l-transceiver-id = 13; u-transceiver-id = 14;};
/network/E1-layout/time-slot-24 = { source-type = "BS"; base-station-id = 8; l-transceiver-id = 15; u-transceiver-id = 16;};
/network/E1-layout/time-slot-25 = { source-type = "BS"; base-station-id = 8; l-transceiver-id = 17; u-transceiver-id = 18;};

#### Dummy's emulated GWPC encoders
/network/E1-layout/time-slot-26 = { source-type = "DISP"; };
/network/E1-layout/time-slot-27 = { source-type = "ISDN"; };
/network/E1-layout/time-slot-28 = { source-type = "ISDN"; };
/network/E1-layout/time-slot-29 = { source-type = "ISDN"; };
/network/E1-layout/time-slot-30 = { source-type = "ISDN"; };


## Network Topology Parameters ############################################################
#### Remove all other network topology parameters, and replace by this. Don't forget to change CTSNAME to the same name as in line 3!
/network/topology/gateway-pc     = { name = "Gateway Server"; E1-connection-1 = "BS-8"; };
/network/topology/base-station-1 = { name = "CTSBS"; E1-connection-1 = "BS-8"; };
/network/topology/base-station-8 = { name = "DUMMY"; E1-connection-1 = "BS-1"; E1-connection-2 = "GW-PC"; };
  5. Save and reboot the CTS, make sure it still works.
  6. Copy bssparams.txt over to your local PC, you'll need it for your Raspberry Pi.
  7. Write down the IP address of your CTS BSC computer (mine was 10.10.15.31, but yours will probably be different). 

Software Stack Install

  1. Prepare an SD card with a 64-bit Raspbian Bookworm (Debian 12)
  2. Update/Upgrade the OS after boot:
    sudo apt update && sudo apt upgrade
reboot

  3. Add the Osmocom repo, as per Osmocom's documentation:
    sudo su
OSMOCOM_REPO="https://downloads.osmocom.org/packages/osmocom:/latest/Debian_12" 
wget $OSMOCOM_REPO/Release.key
mv Release.key /etc/apt/trusted.gpg.d/osmocom-latest.asc
echo "deb [signed-by=/etc/apt/trusted.gpg.d/osmocom-latest.asc] $OSMOCOM_REPO/ ./" > /etc/apt/sources.list.d/osmocom-latest.list
apt update
  4. Install Osmocom E1D:
    sudo apt install osmo-e1d
  5. Add the TetraPack repository:
    wget https://packages.tetrapack.online/install/public.key
mv public.key tetrapack.asc
sudo apt-key add tetrapack.asc
sudo echo "deb [arch=arm64] http://packages.tetrapack.online/repository/ bookworm main" > /etc/apt/sources.list.d/tetrapack.list
sudo apt update
  6. Install TetraPack dummy and cts-logcollector
    sudo apt install tetrapack-dummy cts-logcollector
  7. Plug in the icE1USB to your Rpi, recover the interface serial number:
    sudo lsusb -d 1d50:6145 -v 2> /dev/null | grep iSerial
  8. Open (with for instance nano) /etc/osmocom/osmo-e1d.cfg, copy/paste this:
    log syslog daemon
e1d
 interface 0 icE1usb
  usb-serial [interface serial number]
  line 0
  9. Reload the service: 
    sudo systemctl restart osmo-e1d

Dummy - E1 Link setup

  1. Make sure Dummy is off with: 
    sudo systemctl stop dummy@default.service
  2. Open/Create /opt/TetraPack/bssparams.txt, and copy/paste the contents from the file created at the CTS setup step. Edit the following lines 
    
## System Parameters #####################################################################
### Edit/Replace
/system/name = "DUMMY";


## Base-Station Parameters ################################################################
### Edit/Replace
/base-station/name = "DUMMY";
/base-station/base-station-id = 8;
  3. Open/Create /opt/TetraPack/default.env 
    # E1D interface and line in format [interface number].[line number]
DUMMY_LINE=0.0

# Path to CTS topology file (bss3.txt or bssparams.txt)
DUMMY_TOPOLOGY=/opt/TetraPack/bssparams.txt

# IP address and mask for CTS VTUN interface
DUMMY_NETWORK="192.168.0.8 mask 255.255.255.0"

# Specific options (multiple values can be delimited with comma):
# replace-forwarded-link-status - replace IP-forwarded status for both E1 lines status of local BSs/GWPC to up
# emulated-bs-line1-down        - set E1-1 status of emulated BS to down
# emulated-bs-line2-down        - set E1-2 status of emulated BS to down
# emulated-gwpc-line1-down      - set E1-1 status of emulated GWPC to down
# emulated-gwpc-line2-down      - set E1-2 status of emulated GWPC to down
DUMMY_OPTION=

# Server connection URI in format http(s)://[user]:[password]@[address]/[path and parameters]
# If you care about securely stored password, please put credentials into /opt/TetraPack/.netrc (man netrc)
# REPLACE <YOUR DMR-ID> and <YOUR HOTSPOT/REPEATER PASSWORD> with your radio ID and password :)
DUMMY_CONNECTION="http://<YOUR DMR-ID>:<YOUR HOTSPOT/REPEATER PASSWORD>@core.tetrapack.online:8081/dummy/?mode=bs+gwpc"

# Instance name for D-BUS IPC interface
DUMMY_INSTANCE=default
  4. Save everything, cross your fingers and connect E1.1 from your BSC to the left port of icE1usb, like so:

    image.png

  5. The matching LED on the port should stop blinking, and the red LED on E1-1 should turn off. 
  6. Try to start dummy from the console: 
    cd /opt/TetraPack
./run.sh default.env

# First, read starup messages and check that configuration (default.env and bssparams.txt) parsed successfuly
# Second, check connection: if you see, in blue, "Q.921 connection established", congratulations! Your E1 link works!
# You should also see "Socket Connection Established" - this means, connection to server established
  7. If everything works, Ctrl+C to stop the console instance, and enable the service + start it 
    sudo systemctl start dummy@default.service

LogCollector - CTS Management interface setup

  1. Connect the USB/Ethernet interface to the Pi, and connect an Ethernet cable from BSC management port to the usb dongle. 
  2. Stop LogCollector: 
    sudo systemctl stop cts-logcollector@default.service
  3. Set a static IP on the interface (probably eth1) on the same range as the BSC, by editing /etc/dhcpcd.conf and adding this: 
    # Don't forget to edit your ip address to match the range of your BSC!
interface eth1
static ip_address=10.10.15.20
static routers=10.10.15.1
  4. Test if you can connect via telnet: 
    telnet [BSC IP ADDR] 51600
#If you get "220 Network Management Interface is ready.", you're good to go!
  5. Through that telnet interface, you can check if you got a good E1 link with Dummy: 
    login a
cd network
netstat
#Look at the table that pops up, and focus on the "Links" column
#260-rsp
#260-Node    Links     DD      AI    ISDN    DISP
#260---------------------------------------------
#260-BS-1      u -      u       u       -       -
#260-BS-2      ? ?      ?       ?       -       -
#260-BS-3      ? ?      ?       ?       -       -
#260-BS-4      ? ?      ?       ?       -       -
#260-BS-5      ? ?      ?       ?       -       -
#260-BS-6      ? ?      ?       ?       -       -
#260-BS-7      ? ?      ?       ?       -       -
#260-BS-8      u u      u       u       -       -
#260-GWPC      d u      u       -       u       d
#260-
#260 .
#BS-1 should have first link on U, BS-8 should have both U, and GWPC should have D U
#If it's not the case, check the topology with:
cd topology
ls
#Should show this: 
#260-      d-- gateway-pc
#260-      d-- base-station-1
#260-      d-- base-station-8
#If not, check your bssparams.txt on both the CTS and the Pi, something is wrong.
  6. Close the Telnet session (Ctrl+c), open /opt/LogCollector/default.env, and change the ip address: 
    # [IP of basestation] [dummy instance name] [basestation ID (1-8)]
COMMAND_ARGUMENTS=[YOUR BSC IP] default 1
  7. Enable/Restart LogCollector, wait for a bit and see if you get data coming from the CTS when you place a call or attach to a group: 
    sudo systemctl enable cts-logcollector@default.service
sudo systemctl start cts-logcollector@default.service
#Let's monitor syslog to see if it recovers logs from the CTS. You should see a bunch of lines show up.
tail -f /var/log/syslog | grep cts
  8. If it works, great! LogCollector is ready. Ctrl+C to quit tail, carry on to the rest

EBTS

Introduction 

  1. No LST! (No Red Lights on TSC, and No Annoying Notification on the Front of your Radios)
  2. Network Wide Group Calling - TGS Configured in our Core are Routed between ALL Linked BTS Sites
  3. Local Site Private Calling - Having a Linked site allows for 1-1 Private Calling (NOT FULL DUPLEX). Simply Dial the ISSI Number of the radio you wish to dial and hit PTT, this will call the radio and establish a 1-1 Call
  4. Wide Area Private Calling - As Above, Just across the network! - Call your buddys across the world via their ISSI Number.

The aim of this guide is to help you get your EBTS connected to our Virtual Core, and enjoy all TETRA features (+ TPC interconnects, coming soon™). 

Disclaimer

Prep Work

Connection methods

Option 1 - Cisco router

Untitled.jpg

The complete setup will look like this:

Untitled Diagram.drawio.png

Raspberry Pi Setup

  1. Prepare an SD Card with a 64-Bit version of Raspberry OS Lite(Bookworm being the latest, We Don't Need a GUI). Don't forget to configure SSH and WiFi if you plan to use it. You can also use an additional USB/Ethernet dongle instead of Wifi (you'll need an available ethernet port to connect to the Cisco Router either way).
  2. Update/Upgrade the OS after boot: 
    sudo apt get update && sudo apt upgrade
reboot
  3. Download and run the following configuration script. This will create the bridging interface, and add you to the ZeroTier network:  
    wget https://packages.tetrapack.online/install/tools/EBTS/CiscoBridge.sh | sudo bash
  4. Connect the USB-Ethernet dongle if needed, and reboot. Connect the Cisco Router FastEthernet0/0 port to the dongle, and your WAN network to the Pi's onboard jack (or to the main Pi Ethernet jack if you're using Wifi to get online).


    Sometimes the Pi will pick either the internal Eth or the Dongle Eth to be Eth0. If you notice that you cannot get a connection via your LAN to the Pi, try swapping the connection to the Cisco over.

Cisco Router Setup

  1. Connect your computer to the Console port of the router (via either an USB/RS232 adapter or a native DB9 port if you're lucky enough to still have one). Open up your favourite terminal program (I personally use putty) at 9600 baud. 
  2. Follow these steps to reset your router to factory defaults.
  3. Once you finish step 8 on this before-mentioned guide, type "no" then enter. 
  4. Check your Firmware Version: 
    show version
Cisco IOS Software, C2600 Software (C2600-IPBASEK9-M), Version 12.4(12), RELEASE SOFTWARE (fc1) is Required
  5. If you see any other version than what's mentioned above, reach out to one of the Core Network Team to update it. 
  6. Open the Cisco Router config file you received (see "Prep Work") and copy its content (Ctrl+C). Enable the console and enter configuration mode:  
    config t
Ctrl+V (paste)
end
write mem
  7. Once done, you should be able to ping the Core via: 
    ping 192.168.250.254
  8. Almost there! If for some reason your FastEthernet0/0 interface didn't go up, type:  
    config t
int Fast0/0
no shutdown
end
write mem

Option 2 - icE1usb interface

Please read article FrameRelay-over-E1 Daemon (FRED)

After FRED install please edit /opt/FRED/default.env and run following command:

sudo /opt/FRED/dimetra-setup.sh

EBTS Site Controller

  1. Connect a USB/RS232 (or native DB9, again) from your computer to the service access port of the TSC. Open up BTS Service Software (aka TESS), select Dimetra R8. Password is Sys*mgr123$%. Under Configuration ==> Direct Settings, make sure you selected the right COM Port. 
  2. Select Connection ==> Connect Direct. Turn on the TSC and wait for it to boot up completely. If it's already on, just press on enter, you should get a prompt for a user/password. Defaults should be factory/factory. 
  3. Select Upload Configuration, and download the latest file from the Site Controller. Once done, close the connection via Connection ==> Close Connection.
  4. Open the TSC Configuration file you just pulled via File ==> Open. Edit the Site Configuration via Personality ==> Modify. Click on "Edit Site Controller"
  5. From the Core Team, you should have received the following data: Site ID, BTS IP Address, PVC Primary, PVC Backup and Network Mgr IP Address. Make sure you have them close by, you'll need them now.
  6. Check your configuration matches the screenshots below, and copy over your site-specific data: 

    image.pngimage.png

     

    Untitled.jpgUntitled.jpg

    Untitled.jpgimage.png

     

     

    Untitled.jpgimage.png

     

  7. Once you're finished, double check everything. Save the file, and reconnect to the TSC (Connection ==> Connect Direct). 
  8. Click on Connection ==> Send Files. Select "Configuration Files" and select the file you just saved. In the “File Download” window, enter a version label, check “Use Next” and click on “Update Selected Items”. Press OK to start the transfer. You'll get a prompt to select which configuration file to replace. Select the one with all the minus signs.
  10. Remember when uploading the new configuration to update the "Use Next" Flag
  12. Reset the TSC by issuing the "reset" command on the terminal. Wait for the reboot, and log yourself in again (with factory/factory)
  13. Type the following commands to enable Site Link:  
    .sitelink -e1
.e1config -crdStart 1 -crd 31 -ts16Skip off -portNo 1 -crc on
reset
  14. After reboot, your TSC should now be connected to the Core Network! Enjoy :)

Final Steps

Once you have connected your BTS to the Core Network, Please go to https://map.tetrapack.online and register your user.
When an admin approves your user, you can log in and add your BTS to the map!

You will need the following information available when registering your BTS:
Zerotier Client ID: you will get this when setting up your Pi for Either Cisco or FRED configuration. 
TX Frequency
RX Frequency
Duplex Table
Duplex Spacing

Once the BTS is approved by an Admin it will appear automatically on our BTS Map!

Cable Management Mod for Option 1

I found it quite convenient to put the Pi inside the empty Primary Network Module slot. A small mounting plate with double sided tape, another one for the USB/Eth dongle, and it's already much cleaner! 

Untitled.jpg

Bonus points if you use the Cisco Router's power supply to supply 5V to the Pi! Just solder a couple of wires on the edge card connector at the front of the router's mainboard. Leftmost pin is GND, then 12V (don't solder there!) then 5V. Double and triple check with a multimeter before hooking the Pi up. 

image.pngimage.png

Pins 2 and 6 on the Pi can respectively be used as 5V and GND. An old servo connector does the job quite well! 

Untitled.jpg

Dummy

Intro

* Some revisions of Raspberry Pi 3 have issues with icE1usb connection stability due to USB NIC

P2-TP-Feb2023.pdf

Configuration

Default configuration file is /opt/TetraPack/default.env

# E1D interface and line in format [interface number].[line number]
DUMMY_LINE=0.0

# Path to CTS topology file (bss.txt or bssparams.txt)
DUMMY_TOPOLOGY=/opt/TetraPack/bssparams.txt

# IP address and mask for CTS VTUN interface
DUMMY_NETWORK="192.168.0.8 mask 255.255.255.0"

# Specific options (multiple values can be delimited with comma):
# replace-forwarded-link-status - replace IP-forwarded status for both E1 lines status of local BSs/GWPC to up
# emulated-bs-line1-down        - set E1-1 status of emulated BS to down
# emulated-bs-line2-down        - set E1-2 status of emulated BS to down
# emulated-gwpc-line1-down      - set E1-1 status of emulated GWPC to down
# emulated-gwpc-line2-down      - set E1-2 status of emulated GWPC to down
DUMMY_OPTION=

# Server connection URI in format http(s)://[user]:[password]@[address]/[path and parameters]
# If you care about securely stored password, please put credentials into /opt/TetraPack/.netrc (man netrc)
DUMMY_CONNECTION="http://xxxxxx:password@core.tetrapack.online:8081/dummy/?emulation=bs+gwpc"

# Instance name for D-BUS IPC interface
DUMMY_INSTANCE=default

Connection URL

Parameters:

Topology

bssparams.txt is used to map CTS system topology and E1 layout as well as a system configuration. Parameter /base-station/base-station-id is used as identifier of emulated basestation (identifier of GWPC is hardcoded in CTS).

A capacity (amount of concurrent calls) of emulated basestation depends on amount on configured virtual transceivers for this basestation. Capacity = [count of transceivers] * 4 - 1

Please keep in mind that due to specific of CTS system topology must me configured as a chain of nodes, connected end-to-end. For example if you have two physical BSs, topology file has to be configured in scheme BS1 <-> BS2 <-> emulated BS <-> emulated GWPC. Regarding to this scheme you have to have properly configured termination endpoint in the main configuration (.env):

# emulated-bs-line1-down        - set E1-1 status of emulated BS to down
# emulated-bs-line2-down        - set E1-2 status of emulated BS to down
# emulated-gwpc-line1-down      - set E1-1 status of emulated GWPC to down
# emulated-gwpc-line2-down      - set E1-2 status of emulated GWPC to down
DUMMY_OPTION=emulated-gwpc-line1-down

Multiple instances

You can have several separated CTS systems connected to one or more core servers (for example, production and test). For such case you need to have several .env files for each configuration. use sudo ./setup.sh install to register all instances.

Also it's possible to run dummy in command line - sudo ./run.sh <configuration.env>

CTS Log Collector

CTS Log Collector is an additional software for Dummy. It connects to CTS basestation via TCP to logging ports and forward log entries to locally installed dummy.

The need

CTS Log Collector does following important things:

Configuration

# [IP of basestation] [dummy instance name] [basestation ID (1-8)]
COMMAND_ARGUMENTS=10.0.0.1 default 1

MTS

Motorola's MTS Series of Tetra Base Stations are currently supported in TetraPack.

Installation

curl http://packages.tetrapack.online/install/tools/MTS/mts-setup.sh | sudo bash

CTS Updater

CTS Updater (update-cts.py) is a small script to upload and update CTS configuration or database remotely and without restart. Better to run it on the same Linux system where dummy runs.

Utility creates index data, starts specific embedded ftp server, connects to CTS and initiates update. After updating it stops.

Installation

sudo apt install python3-pip python3-pyftpdlib
sudo pip install telnetlib3

Please make sure, you don't use firewall between your CTS and Linux. Also please make sure you have no ftp servers run on Linux system or use port TCP 21.

Usage

$ sudo ./update-cts.py <IP-address of CTS> [db|cfg] <path to folder>

Exit codes:

Update database
$ ls db1/
sum-gm.csv sum-gp.csv sum-sc.csv sum-sub.csv
$ sudo ./update-cts.py 10.2.0.10 db db1 ; echo $?
Update configuration
$ ls -l cfg1/
bssparams.txt
$ sudo ./update-cts.py 10.2.0.10 cfg cfg1 ; echo $?

CTS

Motorola CTS-x00 is a series of basestations for CompactTETRA product line of Motorola. Literally its OEM-product of DAMM with software from Frequentis.

Following articles is about how to connect it to TetraPack: