Name

org.bluez.Telephony1 - BlueZ D-Bus Telephony Audio Gateway API documentation

Interface

Service: org.bluez
Interface: org.bluez.Telephony1 [experimental]
Object path: [variable prefix]/{hci0,hci1,...}/dev_{BDADDR}/telephony#
Used by: bluetoothctl-telephony(1)

object Dial(string uri)

The uri is comprised of the URI scheme followed by the Caller ID (this could be a telephone number or username), separated by a colon.

Examples of common URI schemes can be found in Internet Assigned Numbers Authority (IANA) URI Schemes: https://iana.org/assignments/uri-schemes/uri-schemes.xhtml

This initiates a new outgoing call. Returns the object path to the newly created call.

For HFP the URI is "tel:" followed by the telephone number.

The telephone number must be a string containing the following characters: [0-9+*#,ABCD]{1,80} The character set can contain numbers, +, *, #, , and the letters A to D. Besides this sanity checking no further number validation is performed. It is assumed that the gateway and/or the network will perform further validation.

If telephone number is an empty string, it will try to call last dialed number.

NOTE: If an active call (single or multiparty) exists, then it is automatically put on hold if the dial procedure is successful.

Possible Errors:

org.bluez.Error.InvalidState
org.bluez.Error.InvalidArguments
org.bluez.Error.NotSupported
org.bluez.Error.Failed

Examples:

bluetoothctl: > telephony.dial <number> [telephony]

void SwapCalls()

Swaps Active and Held calls. The effect of this is that all calls (0 or more including calls in a multi-party conversation) that were Active are now Held, and all calls (0 or more) that were Held are now Active.

GSM specification does not allow calls to be swapped in the case where Held, Active and Waiting calls exist. Some modems implement this anyway, thus it is manufacturer specific whether this method will succeed in the case of Held, Active and Waiting calls.