Datasets:
kkboy1
/
LeAudio

Dataset card Data Studio Files
xet
 Community
1
text
stringlengths
1
112
characteristic the call control state machine of tbs does not contain an idle state but one
is shown in figure for clarity the second octet of the call state characteristic identifies
the current state of each call and the final octet holds call flags associated with that call
the format of the ca ll state characteristic is shown in figure
callindex i
octet state i
octet callflags i
octet
figure call state characteristic
table lists the state values which are returned in the call state characteristic
state name description
x incoming an incoming call normally causing a ringtone
x dialing an outgoing call has started but the remote party has
not yet been notified the traditional dialtone state
x alerting the remote party is being alerted they have a
ringtone
x active the call is established with an active conversation
x locally held the call is connected but on hold locally see below
x remotely held the call is connected but on hold remotely see
below
x locally and
remotely held the call is connected but on hold both locally and
remotely see below
xxff rfu reserved for future use
table states de fined for the call state characteristic
chapter telephony and media control
local and remote hold
states x x and x refer to calls which have been placed on hold these states are
differentiated by who it was who put the call on hold a value of x indicates that it has
been put on hold locally ie by the user with the phone or pc with this tbs instance a
value of x means that it has been put on hold by the remote party and a value of x
means that both ends on the call have put it on hold
a locally held call can be retrieved brought back to the active state by writing to the control
point a remotely held call needs to be retrieved by the remote party the only local action
that can be applied to a remotely held call is to terminate it
call flags
the final o ctet of the call state characteristic is a bitfield containing information on the call
with the meanings and corresponding values shown in table
bit description value
call direction incoming call
outgoing call
information withheld by server not withheld
withheld
information withheld by
network provided by network
withheld by network
rfu reserved for future use
table call status bits for the call state characteristic
bits and indicate cases where information such as the uri typically the caller id or
friendly name may be deliberately withheld because of either a local or network policy either
or both may be set in which case the fields of the associated characteristics may be empty or
null alternatively the server can fill them with appropriate text such as withheld or
unknown caller the choice of policy and text is implementation specific
ucis and uris
two initialisms you will come across in telephony applications are uri and uci which stand
for uniform resource identifier and uniform caller identifier both are designed to provide
call information which covers a wide variety of telephony applications and bearers
the uniform caller identifier is essentially the bearer for example skype or wtsap the
values for the ucis are listed in the bluetooth uniform c aller identifiers assigned numbers
document and are generally abbreviated to no more than five characters hence whatsapp is
wtsap standard phone numbers use the uci of e or tel signifying a standard
dialer format
section tbs and ccp
the uniform resource ident ifier is a combination of the uci and the caller id ie the callers
number or username depending on the application it can be used for either an incoming
call where it is the caller id or an outgoing call an application can use the uci portion o f
a uri for an outgoing call to select the appropriate telephony application to make the call
uris are expressed as a utf string
the tbs call control point characteristic
as weve seen with bap and ascs a client can move a server around its state mac hine by
writing to a control point characteristic in this case its the tbs call control point
characteristic this requires a single opcode followed by a parameter which depends on the
specific opcode as indicated in figure
opcode
octet parameter
varies
figure the tbs call control point characteristic
table shows the curr ent opcodes and describes their purpose
opcode name parameter description
x accept callindex accepts the incoming call
x terminate callindex terminate the call associated with
callindex regardless of its state
x local hold callindex places an active or incoming call with
callindex on local hold
x local
retrieve callindex moves a locally held call to the active
state
x originate uri starts a call to the uri
x join list of callindex
values joins the calls identified in the list of
callindex values
x
xff rfu reserved for future use
table call control point characteristic opcodes for moving around the tbs state machine
the opcodes of table are requests to the server which it passes to its relevant telephony
application some of these accept terminate and originate refer to actions which will be
taken locally by the telephony application local hold and retrieve generally need to be
passed back to the network and join is almost always a network function depending on the
specific telephony bearer and application not all of these functions may b e available they
may also fail based on the current phone resources and the network connection for example