Integrating T.Bridge as a channel

Bridged network can be integrated with TASSTA network as a virtual channel. All channels / groups from the radio will be presented as sub-channels. 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.

Open T.Bridge configuration file in a text editor and provide connection parameters for TASSTA network in ConsumerConfig section:

"ConsumerDriver": "tassta",
"ConsumerConfig": {
    "server": "example.tassta.com:65001",
    "user": "bridge",
    "pass": "T-Bridge123",
    "offset": {
        "user_id": 10000,
        "user_session": 10000,
        "channel_id": 10000
    },
    "hash_creds": true,
    "version_brand": "TASSTA",
    "channel_aliases": {
        "5050": "EMERGENCY",
        "6000": "Announcements"
    },
    "acl": [
        {
            "channel": "1",
            "allowed_users": ["user1", "user2"],
            "allowed_groups": ["team1", "team2"]
        },
        {
            "channel": "2",
            "allowed_groups": ["team2"]
        }
    ],
    "audio_preprocessor_to_bridge": {
        "agc_level": 0.2,
        "agc_max_gain": 150,
        "agc_increment": 250,
        "agc_decrement": -250
    },
    "audio_preprocessor_from_bridge": {
        "agc_level": 0.2,
        "agc_max_gain": 150,
        "agc_increment": 250,
        "agc_decrement": -250
    }
}

Channel aliases

You can provide alternative names (for example, human-readable aliases instead of numbers) for bridged channels using channel_aliases parameter. Use the following syntax:

"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.

Channel access

acl parameter allows you to restrict access to bridged channels, so they can only be accessed by selected TASSTA users and teams. Use the following syntax:

"acl": [
    {
        "channel": "1",
        "allowed_users": ["user1", "user2"],
        "allowed_groups": ["team1", "team2"]
    },
    {
        "channel": "2",
        "allowed_groups": ["team2"]
    }
]

Where:

• channel is the channel name / ID from the bridged system.
• allowed_users is the list of users (usernames) on the server who are allowed to access the channel.
• allowed_groups is the list of teams on the server who are allowed to access the channel.

Automatic gain control

You may encounter too quiet or too loud sound when the voice is transmitted between bridged networks. It may be caused by hardware or connection API specifics. To mitigate the problem, balance the sound using automatic gain control settings:

"audio_preprocessor_to_bridge": {
    "agc_level": 0.2,
    "agc_max_gain": 150,
    "agc_increment": 250,
    "agc_decrement": -250
},
"audio_preprocessor_from_bridge": {
    "agc_level": 0.2,
    "agc_max_gain": 150,
    "agc_increment": 250,
    "agc_decrement": -250
}

Where:

• agc_level is the maximum sound level at the output, percentage from 0 to 1.
• agc_max_gain is the maximum gain in dB, positive integer.
• agc_increment is the maximum energy increase in dB per second, positive integer.
• agc_decrement is the maximum gain reduction in dB per second, negative integer.

You can configure automatic gain control for both directions: from the bridged system to TASSTA network (audio_preprocessor_from_bridge), and from the TASSTA network to the bridged system (audio_preprocessor_to_bridge), depending on your specific conditions.

If this parameter is not provided, the audio is transmitted as is, without any preprocessing.