Page 2
All rights and obligations with respect to the subject matter hereof shall be governed by the agreement between you and TASSTA GmbH or its authorized agent. Except as expressly set forth in any such agreement, TASSTA GmbH makes no representations or warranties relating to its products or services,...
T.Bridge uses voice activity detection to determine if someone is speaking over the connected radio transmits the sound from the radio to TASSTA network and vice versa. IMPORTANT: Due to the nature of the connection, the bridging is only limited to voice transmission between the networks.
T.Bridge 4WIRE Deployment Guide Required hardware 2 GHz or faster processor. • • 8 GB of RAM. • Minimum 250 MB of available storage space. • Network card. • Audio interface with input and output jacks. • A mobile radio with analogue audio input that meets the following requirements: The radio must support voice operated switch (VOX) function.
T.Bridge 4WIRE Deployment Guide Software prerequisites Windows 10, Windows 8, or Windows 7; 64 bit only. • • DELIB Driver Library. REV-2206.14/0522 Page 6 of 24...
T.Bridge 4WIRE Deployment Guide Licensing T.Bridge 4wire consumes TBR.4WIRE licenses. Refer to T.Lion documentation for information on checking the current license status. REV-2206.14/0522 Page 7 of 24...
Installation package structure T.Bridge 4wire is distributed as a ZIP archive. The following table contains a list of key TASSTA components and drivers mentioned in this document. All paths are based on the root directory of the installation package.
T.Bridge service. NOTE: If prompted, allow T.Bridge to communicate through Windows Firewall. Installing DELIB Driver Library T.Bridge 4wire requires DELIB Driver Library to work correctly. The distributive is located in delib subfolder of T.Bridge installation package. To install DELIB Driver Library: 1.
Adjust C:\Program Files\TASSTA\Bridge the command line parameters if necessary. Start TASSTA Bridge service. You can do it from the command line: `"%ProgramFiles%\nssm-2.24\win64\nssm" start "TASSTA Bridge". Managing T.Bridge service 1. Open Services from Administrative Tools. Alternatively, execute from Run.
T.Bridge 4WIRE Deployment Guide Restart is required to apply changes to the T.Bridge configuration. 1. Select TASSTA Bridge service. 2. Click Restart Service button in the toolbar or right-click the service and click Restart in the context menu. To temporary stop T.Bridge service 1.
T.Bridge 4WIRE Deployment Guide To back up the active configuration before making changes, execute the command: bridge3 -cfg <CONFIGURATION FILE NAME> -outcfg > <BACKUP FILE NAME> Running T.Bridge interactively While T.Bridge works as a background service by default, you can start it from the command line to view informational messages and errors in real time for troubleshooting purposes.
T.Bridge 4WIRE Deployment Guide Connecting the mobile radio In order to bridge the mobile radio to TASSTA network, connect it to the audio interface of the computer running T.Bridge. You can either use standard audio cables with 3.5mm plugs or a proprietary audio adapter from the radio manufacturer, depending on the radio model.
T.Bridge 4WIRE Deployment Guide Setting up TASSTA network To set up bridging, you should already have T.Lion and T.Commander deployed and configured. The bridged network is integrated with a server on T.Lion node. It is strongly recommended to bridge only one external PMR network per server.
T.Bridge 4WIRE Deployment Guide Configuration T.Bridge configuration is stored in a file located in the installation folder. The configuration data is uses JSON format. Product package already contains the sample configuration file. Refer to Package structure chapter for more information. You can create any number of custom configurations by copying and modifying the existing one.
Page 16
4wire The channel name for the bridged radio. This channel will RootChannelName appear in TASSTA network when T.Bridge is running. If omitted, the base channel will be named "4wire". NOTE: This value is only used if T.Bridge is integrated with...
Audio output device is the unique identifier of the audio device (audio-out jack) which transmits sound OutputDeviceID from TASSTA network to the radio. If you are using the default playback device, provide the empty string ( "" If you want to use an alternative device, provide its ID: 1.
70 and tune the number by ear. Setting this parameter to 0 disables voice detection (once VAD is started, all audio is transmitted). Integrating with TASSTA network T.Bridge 4wire can be integrated with TASSTA network either as a virtual channel with a single user...
TASSTA clients can join that channels to communicate with the bridged network. The channel will appear in TASSTA network when T.Bridge is running. There is no need to create it on the server.
Page 20
T.Bridge 4WIRE Deployment Guide "allowed_groups": ["team2"] Parameter Required Description To integrate with TASSTA server as a virtual channel, the ConsumerDriver value must be tassta IP address / domain name of T.Lion node and a server server port. Use format. address:port Login of the user that is used by T.Bridge to authenticate...
Page 21
T.Bridge 4WIRE Deployment Guide Channel aliases You can provide alternative names (for example, human-readable aliases instead of numbers) for bridged channels using parameter. Use the following syntax: channel_aliases "channel_aliases": { "1": "Channel One", "2": "Channel Two", "<BRIDGED CHANNEL>": "<ALIAS>" Where \ is the actual channel name / ID configured in the bridged system, and \ is the alternative name displayed in TASSTA clients.
Integrating T.Bridge as a user Bridged network can be integrated with TASSTA network as a single user. It allows you to communicate with the bridged network using either one-to-one calls to that user or group calls with the channel the user is joined to.
T.Bridge 4WIRE Deployment Guide Parameter Required Description Set to when connecting to T.Lion 5.5 and above; hash_creds true false for T.Lion 5.4. Do not change the current value. If in doubt, use version_brand TASSTA Logging Writing T.Bridge events to a file might be useful for troubleshooting and audit purposes. To enable logging: 1.