Zephyr API Documentation 4.0.0-rc3
A Scalable Open Source RTOS
Loading...
Searching...
No Matches
bt_tbs_register_param Struct Reference

#include <tbs.h>

Data Fields

char * provider_name
 The name of the provider, for example a cellular service provider.
 
char * uci
 The Uniform Caller Identifier of the bearer.
 
char * uri_schemes_supported
 The Uniform Resource Identifiers schemes supported by this bearer as an UTF-8 string.
 
bool gtbs
 Whether this bearer shall be registered as a Generic Telephone Bearer server.
 
bool authorization_required
 Whether the application will need to authorize changes to calls.
 
uint8_t technology
 The technology of the bearer.
 
uint8_t supported_features
 The optional supported features of the bearer.
 

Field Documentation

◆ authorization_required

bool bt_tbs_register_param::authorization_required

Whether the application will need to authorize changes to calls.

If set to false then the service will automatically accept write requests from clients.

◆ gtbs

bool bt_tbs_register_param::gtbs

Whether this bearer shall be registered as a Generic Telephone Bearer server.

A GTBS shall be registered before any non-GTBS services. There can only be a single GTBS registered.

◆ provider_name

char* bt_tbs_register_param::provider_name

The name of the provider, for example a cellular service provider.

◆ supported_features

uint8_t bt_tbs_register_param::supported_features

The optional supported features of the bearer.

See the BT_TBS_FEATURE_* values.

◆ technology

uint8_t bt_tbs_register_param::technology

The technology of the bearer.

See the BT_TBS_TECHNOLOGY_* values.

◆ uci

char* bt_tbs_register_param::uci

The Uniform Caller Identifier of the bearer.

See the Uniform Caller Identifiers table in Bluetooth Assigned Numbers

◆ uri_schemes_supported

char* bt_tbs_register_param::uri_schemes_supported

The Uniform Resource Identifiers schemes supported by this bearer as an UTF-8 string.

See https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml for possible values. If multiple values are used, these shall be comma separated, e.g. "tel,skype".


The documentation for this struct was generated from the following file: