e45830893f
The CCP API for the Call Control Profile works on top of the TBS API, and will eventually replace parts of the TBS API. Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no>
77 lines
2.5 KiB
ReStructuredText
77 lines
2.5 KiB
ReStructuredText
.. zephyr:code-sample:: bluetooth_ccp_call_control_server
|
|
:name: Call Control Profile (CCP) Call Control Server
|
|
:relevant-api: bluetooth bt_ccp bt_tbs
|
|
|
|
CCP Call Control Server sample that registers one or more TBS bearers and advertises the
|
|
TBS UUID(s).
|
|
|
|
Overview
|
|
********
|
|
|
|
Application demonstrating the CCP Call Control Server functionality.
|
|
Starts by advertising for CCP Call Control Clients to connect and set up calls.
|
|
|
|
The profile works for both GAP Central and GAP Peripheral devices, but this sample only assumes the
|
|
GAP Peripheral role.
|
|
|
|
This sample can be found under :zephyr_file:`samples/bluetooth/ccp_call_control_server` in the Zephyr tree.
|
|
|
|
Check the :zephyr:code-sample-category:`bluetooth` samples for general information.
|
|
|
|
Requirements
|
|
************
|
|
|
|
* BlueZ running on the host, or
|
|
* A board with Bluetooth Low Energy 5.2 support
|
|
|
|
Building and Running
|
|
********************
|
|
|
|
When building targeting an nrf52 series board with the Zephyr Bluetooth Controller,
|
|
use ``-DOVERLAY_CONFIG=overlay-bt_ll_sw_split.conf`` to enable the required feature support.
|
|
|
|
Building for an nrf5340dk
|
|
-------------------------
|
|
|
|
You can build both the application core image and an appropriate controller image for the network
|
|
core with:
|
|
|
|
.. zephyr-app-commands::
|
|
:zephyr-app: samples/bluetooth/ccp_call_control_server/
|
|
:board: nrf5340dk/nrf5340/cpuapp
|
|
:goals: build
|
|
:west-args: --sysbuild
|
|
|
|
If you prefer to only build the application core image, you can do so by doing instead:
|
|
|
|
.. zephyr-app-commands::
|
|
:zephyr-app: samples/bluetooth/ccp_call_control_server/
|
|
:board: nrf5340dk/nrf5340/cpuapp
|
|
:goals: build
|
|
|
|
In that case you can pair this application core image with the
|
|
:zephyr:code-sample:`bluetooth_hci_ipc` sample
|
|
:zephyr_file:`samples/bluetooth/hci_ipc/nrf5340_cpunet_iso-bt_ll_sw_split.conf` configuration.
|
|
|
|
Building for a simulated nrf5340bsim
|
|
------------------------------------
|
|
|
|
Similarly to how you would for real HW, you can do:
|
|
|
|
.. zephyr-app-commands::
|
|
:zephyr-app: samples/bluetooth/ccp_call_control_server/
|
|
:board: nrf5340bsim/nrf5340/cpuapp
|
|
:goals: build
|
|
:west-args: --sysbuild
|
|
|
|
Note this will produce a Linux executable in :file:`./build/zephyr/zephyr.exe`.
|
|
For more information, check :ref:`this board documentation <nrf5340bsim>`.
|
|
|
|
Building for a simulated nrf52_bsim
|
|
-----------------------------------
|
|
|
|
.. zephyr-app-commands::
|
|
:zephyr-app: samples/bluetooth/ccp_call_control_server/
|
|
:board: nrf52_bsim
|
|
:goals: build
|
|
:gen-args: -DOVERLAY_CONFIG=overlay-bt_ll_sw_split.conf
|