TASSTA Documentation Center TASSTA Documentation Center More products
Hide table of contents Hide details Search My account

Integrating T.Bridge as a channel

T.Bridge can integrate with TASSTA network as a virtual channel. All channels from Vocality RoIP will be presented as sub-channels. TASSTA clients can join the 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": {
        "first": "EMERGENCY",
        "second": "Announcements"
    },
    "acl": [
        {
            "channel": "first",
            "allowed_users": ["user1", "user2"],
            "allowed_groups": ["team1", "team2"]
        },
        {
            "channel": "second",
            "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
    }
}
Parameter Required Description
ConsumerDriver Yes To integrate with TASSTA server as a virtual channel, the value must be tassta.
server Yes IP address / domain name of T.Lion node and a server port. Use address:port format.
user Yes Login of the user that is used by T.Bridge to authenticate to the server.
pass Yes Password of the user that is used by T.Bridge to authenticate to the server.
offset/user_id Yes An offset to create unique identifiers for bridged users. Positive integer.
offset/user_session Yes An offset to create unique identifiers for bridged users' sessions. Positive integer.
offset/channel_id Yes An offset to create unique identifiers for bridged channels. Positive integer.
hash_creds Yes Set to true when connecting to T.Lion 5.5 and above; false for T.Lion 5.4.
version_brand Yes Do not change the current value. If in doubt, use TASSTA.
channel_aliases No Verbose aliases for bridged channels displayed in TASSTA clients. If omitted, channel names are taken from the Vocality RoIP configuration.
See Channel aliases for details.
acl No Limit access to bridged channels for TASSTA users. If omitted, the channels can be accessed by all users.
See Channel access for details.
audio_preprocessor_to_bridge No Automatic gain control for voice passed from TASSTA network to Vocality RoIP. If omitted, the audio is left as is.
See Automatic gain control for details.
audio_preprocessor_from_bridge No Automatic gain control for voice passed from Vocality RoIP to TASSTA network. If omitted, the audio is left as is.
See Automatic gain control for details.

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": {
    "one": "Channel One",
    "two": "Channel Two",
    "<BRIDGED CHANNEL>": "<ALIAS>"
}

Where \ is the channel name from Vocality RoIP configuration, 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": "one",
        "allowed_users": ["user1", "user2"],
        "allowed_groups": ["team1", "team2"]
    },
    {
        "channel": "two",
        "allowed_groups": ["team2"]
    }
]

Where:

  • channel is the channel name channel name from Vocality RoIP configuration.
  • 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.
Important:

If acl parameter is not provided, the channel can be accessed by all users on the server.

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 Vocality RoIP to TASSTA network (audio_preprocessor_from_bridge), and from the TASSTA network to Vocality RoIP (audio_preprocessor_to_bridge), depending on your specific conditions.

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

Important:

Improper configuration of the automatic gain control can result in the sound being barely audible. It is recommended to test new settings before deploying them to production.