Procedure Notes; Content Of Procedures In This Section; Push Mode Versus Pull Mode; Application Login Prerequisites - Polycom ReadiVoice Developer's Manual

Procedure Notes

Proprietary & Confidential
A typical order for a set of tasks in a simple application is:
Create a connection
1
Log in
2
Start a conference
3
Dial participants
4
Log out
5
End the conference
6
This section covers important information about what data is provided,
prerequisites, and other tips.

Content of Procedures in This Section

The appropriate information for each event depends on whether it's an
administrative procedure like creating a connection, or a simpler CAPI
procedure that uses a straightforward event and response. We've provided
one or the other for each procedure, and both where possible.
Please refer to the "Sample Moderator Application"
working CAPI sample code.

Push Mode Versus Pull Mode

CAPI has two modes, push and pull. (See
Communication: Synchronous and Asynchronous"
Push and Pull Mode"
event in push mode are different from the ones in pull mode. We've written
these procedures for push mode, since push mode is more robust and
somewhat more complex, and summarized the differences here. If you want
to write a procedure in pull mode, read the push procedure, then make
changes as necessary for the different response values listed in the event
reference guide.

Application Login Prerequisites

For any procedures involving the Application login, be sure that the
Application ID and password are set up in ReadiVoice. Refer to the
ReadiVoice subscriber guide for more information.
Application login is for push mode, so be sure to create a push mode
connection to the server.
"Understanding CAPI
on page 31.) The responses you'll get for sending an
Developing CAPI Applications
on page 63, as well, to see
on page 9 and "Using
39