21
Standard NetLinx API (SNAPI) R 1.8.0
Audio Conferencer Functions (Cont.)
Name
Component
Channel Level Command
Constant
Notes
queryDB(si)
IPhonebookComponent
PHONEBOOKNEXT-
<key>[,<count>,<posi-
tion>]
Request next <count> records starting with
record <position> for the phonebook
search associated with search key <key>.
If <count> is not present, it is assumed to
be 1. If <position> is not present, it is
assumed th be the next record in the
search result set based on the last
PHONEBOOKNEXT or PHONEBOOK-
PREV command. Responses with
PHONEBOOKNEXT-<key>,<count>,<posi-
tion> where <key> is the search key,
<count> is the number of records to expect
and <position> is the position of the first
record to be returned between 1 through
the total number of records.
queryDB(si)
IPhonebookComponent
PHONEBOOKPREV-
<key>[,<count>]
Request previous <count> records for the
phonebook search associated with search
key <key>. If <count> is not present, it is
assumed to be 1. Responses with
PHONEBOOKPREV-
<key>,<count>,<position> where <key> is
the search key, <count> is the number of
records to expect and <position> is the
position of the first record to be returned
between 1 through the total number of
records.
queryDB(si)
IPhonebookComponent
PHONEBOOKRE-
FRESH-
<key>[,<count>]
Refresh <count> records starting with the
last starting position used with a PHONE-
BOOKNEXT or PHONEBOOKPREV com-
mand for the phonebook search associated
with search key <key>. If <count> is not
present, it is assumed to be 1. Responses
with PHONEBOOKNEXT-
<key>,<count>,<position> where <key> is
the search key, <count> is the number of
records to expect and <position> is the
position of the first record to be returned
between 1 through the total number of
records.
searchDB(sr)
IPhonebookComponent
PHONEBOOK-
SEARCH-
<key>,ID=<id>
Search the phonebook database for
records with ID equal to <id>. If <id> is "*",
all records are returned. <key> is a search
key used in other search operations, such
as closeSearchDB(). It can be any string
you like, such as a panel device number or
internal key that makes sense for your pro-
gram. All future DB operation associated
with this search will reference this key
value.
Summary of Contents for CAFE DUET
Page 16: ...Standard NetLinx API SNAPI R 1 8 0 12 ...
Page 28: ...Standard NetLinx API SNAPI R 1 8 0 24 ...
Page 34: ...Standard NetLinx API SNAPI R 1 8 0 30 ...
Page 40: ...Standard NetLinx API SNAPI R 1 8 0 36 ...
Page 46: ...Standard NetLinx API SNAPI R 1 8 0 42 ...
Page 52: ...Standard NetLinx API SNAPI R 1 8 0 48 ...
Page 58: ...Standard NetLinx API SNAPI R 1 8 0 54 ...
Page 142: ...Standard NetLinx API SNAPI R 1 8 0 138 ...
Page 148: ...Standard NetLinx API SNAPI R 1 8 0 144 ...
Page 156: ...Standard NetLinx API SNAPI R 1 8 0 152 ...
Page 172: ...Standard NetLinx API SNAPI R 1 8 0 168 ...
Page 184: ...Standard NetLinx API SNAPI R 1 8 0 180 ...
Page 192: ...Standard NetLinx API SNAPI R 1 8 0 188 ...
Page 206: ...Standard NetLinx API SNAPI R 1 8 0 202 ...
Page 226: ...Standard NetLinx API SNAPI R 1 8 0 222 ...
Page 240: ...Standard NetLinx API SNAPI R 1 8 0 236 ...
Page 244: ...Standard NetLinx API SNAPI R 1 8 0 240 ...
Page 252: ...Standard NetLinx API SNAPI R 1 8 0 248 ...
Page 268: ...Standard NetLinx API SNAPI R 1 8 0 264 ...
Page 302: ...Standard NetLinx API SNAPI R 1 8 0 298 ...
Page 328: ...Standard NetLinx API SNAPI R 1 8 0 324 ...
Page 343: ...Standard NetLinx API SNAPI Devices 339 Standard NetLinx API SNAPI R 1 7 0 ...