Name | Date | Size | #Lines | LOC | ||
---|---|---|---|---|---|---|
.. | - | - | ||||
boards/ | 18-Mar-2025 | - | 10 | 8 | ||
src/ | 18-Mar-2025 | - | 257 | 183 | ||
CMakeLists.txt | D | 18-Mar-2025 | 278 | 12 | 8 | |
Kconfig.sysbuild | D | 18-Mar-2025 | 494 | 16 | 12 | |
README.rst | D | 18-Mar-2025 | 2.5 KiB | 78 | 55 | |
overlay-bt_ll_sw_split.conf | D | 18-Mar-2025 | 183 | 6 | 2 | |
prj.conf | D | 18-Mar-2025 | 388 | 19 | 15 | |
sample.yaml | D | 18-Mar-2025 | 909 | 31 | 30 | |
sysbuild.cmake | D | 18-Mar-2025 | 660 | 25 | 18 |
README.rst
1.. zephyr:code-sample:: bluetooth_ccp_call_control_server 2 :name: Call Control Profile (CCP) Call Control Server 3 :relevant-api: bluetooth bt_ccp bt_tbs 4 5 CCP Call Control Server sample that registers one or more TBS bearers and advertises the 6 TBS UUID(s). 7 8Overview 9******** 10 11Application demonstrating the CCP Call Control Server functionality. 12Starts by advertising for CCP Call Control Clients to connect and set up calls. 13 14The profile works for both GAP Central and GAP Peripheral devices, but this sample only assumes the 15GAP Peripheral role. 16 17This sample can be found under :zephyr_file:`samples/bluetooth/ccp_call_control_server` in the Zephyr tree. 18 19Check the :zephyr:code-sample-category:`bluetooth` samples for general information. 20 21Requirements 22************ 23 24* BlueZ running on the host, or 25* A board with Bluetooth Low Energy 5.2 support 26 27Building and Running 28******************** 29 30When building targeting an nrf52 series board with the Zephyr Bluetooth Controller, 31use ``-DOVERLAY_CONFIG=overlay-bt_ll_sw_split.conf`` to enable the required feature support. 32 33Building for an nrf5340dk 34------------------------- 35 36You can build both the application core image and an appropriate controller image for the network 37core with: 38 39.. zephyr-app-commands:: 40 :zephyr-app: samples/bluetooth/ccp_call_control_server/ 41 :board: nrf5340dk/nrf5340/cpuapp 42 :goals: build 43 :west-args: --sysbuild 44 45If you prefer to only build the application core image, you can do so by doing instead: 46 47.. zephyr-app-commands:: 48 :zephyr-app: samples/bluetooth/ccp_call_control_server/ 49 :board: nrf5340dk/nrf5340/cpuapp 50 :goals: build 51 52In that case you can pair this application core image with the 53:zephyr:code-sample:`bluetooth_hci_ipc` sample 54:zephyr_file:`samples/bluetooth/hci_ipc/nrf5340_cpunet_iso-bt_ll_sw_split.conf` configuration. 55 56Building for a simulated nrf5340bsim 57------------------------------------ 58 59Similarly to how you would for real HW, you can do: 60 61.. zephyr-app-commands:: 62 :zephyr-app: samples/bluetooth/ccp_call_control_server/ 63 :board: nrf5340bsim/nrf5340/cpuapp 64 :goals: build 65 :west-args: --sysbuild 66 67Note this will produce a Linux executable in :file:`./build/zephyr/zephyr.exe`. 68For more information, check :ref:`this board documentation <nrf5340bsim>`. 69 70Building for a simulated nrf52_bsim 71----------------------------------- 72 73.. zephyr-app-commands:: 74 :zephyr-app: samples/bluetooth/ccp_call_control_server/ 75 :board: nrf52_bsim 76 :goals: build 77 :gen-args: -DOVERLAY_CONFIG=overlay-bt_ll_sw_split.conf 78