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",
"user_id_offset": 10000,
"user_session_offset": 10000,
"channel_id_offset": 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"]
}
]}
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. |
user_id_offset |
Yes | An offset to create unique identifiers for bridged users. Positive integer. |
user_session_offset |
Yes | An offset to create unique identifiers for bridged users' sessions. Positive integer. |
channel_id_offset |
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, channels are named as configured in the bridged system. 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. |
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 \
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.
Important: |
If |