TASSTA T.Bridge 4WIRE, Руководство по развертыванию

Страница: 21 / 24

T.Bridge 4WIRE Deployment Guide
REV-2206.14/0522 Page 21 of 24
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.