Polycom ReadiVoice Manual

ReadiVoice®
Operator Guide

ReadiVoice Operator Guide
ii Proprietary & Confidential
Trademark Information
Polycom®, the Polycom logo design, ReadiVoice®, InnoVox®, and the Voyant logo are registered
trademarks of Polycom, Inc. Voyant TechnologiesTM is a trademark of Polycom, Inc. All other trademarks
are the property of their respective owners.
Patent Information
The accompanying product is protected by one or more U.S. and foreign patents and/or pending patent
applications held by Polycom, Inc.
Catalog No. 3725-70004-009D
v. 2.56.x
© 2005 Polycom, Inc. All rights reserved.
Polycom Inc.
1765 West 121st Avenue
Westminster, CO 80234-2301 U.S.A.
No part of this document may be reproduced or transmitted in any form or by any means, electronic or
mechanical, for any purpose, without the express written permission of Polycom, Inc. Under the law,
reproducing includes translating into another language or format.
As between the parties, Polycom, Inc. retains title to, and ownership of, all proprietary rights with respect
to the software contained within its products. The software is protected by United States copyright laws
and international treaty provision. Therefore, you must treat the software like any other copyrighted
material (e.g. a book or sound recording).
Every effort has been made to ensure that the information in this manual is accurate. Polycom, Inc. is not
responsible for printing or clerical errors. Information in this document is subject to change without notice.

Proprietary & Confidential iii
Contents
About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
1 Introducing the ReadiVoice System
What is the ReadiVoice System? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
How ReadiVoice Conferencing Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Starting and Joining a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Controlling a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Managing Your ReadiVoice System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Operator Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Provisioning Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Administration Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Components of the ReadiVoice System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
ReadiVoice-PSTN Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
ReadiVoice-IP Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
ReadiVoice-IP Call Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
“Dialing” in ReadiVoice-IP Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
ReadiVoice Call Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
How Quick-Start and Conference Continuation Affect Call Flow . . . 12
How One-Click Conference Affects Call Flow . . . . . . . . . . . . . . . . . . . . 12
How A Two-Password Configuration Affects Call Flow . . . . . . . . . . . 14
How IP Tributaries Affect ReadiVoice-IP Call Flow . . . . . . . . . . . . . . . 14
2 Operator Tasks
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Opening the Operator Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Registering and Unregistering for Bridges . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Unregistering from Bridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Registering for Bridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

ReadiVoice Operator Guide
iv Proprietary & Confidential
Answering Operator Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Registering for a Conference Without a Request . . . . . . . . . . . . . . . . . . . . . 23
Speaking Privately with a Participant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Placing a Participant on Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Dialing a Participant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Disconnecting a Participant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Viewing Talker Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Muting Participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Muting One Participant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Muting All Participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Making a Conference Listen Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3 Operator Interface
About the Operator Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Parts of the Operator Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Bridges Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Groups Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Requests Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Conference List Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Conference View Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Operator Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Conf Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Figures
Proprietary & Confidential v
Figures
Figure 1-1 ReadiVoice-PSTN system diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Figure 1-2 ReadiVoice-PSTN INCR signaling flow . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Figure 1-3 ReadiVoice-IP system diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 1-4 ReadiVoice call flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 2-1 Logging into the Operator application . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 2-2 The Operator window after you log in . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 2-3 Bridges tab showing one bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 2-4 Dialing yourself to establish an operator voice path . . . . . . . . . . . . . . 21
Figure 2-5 Conference View tab with operator request . . . . . . . . . . . . . . . . . . . . . 22
Figure 2-6 Dialing out to add a participant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Figure 3-1 Operator login dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 3-2 ReadiVoice Operator window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 3-3 Bridges tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 3-4 Info field for a bridge (detail) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 3-5 Groups tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 3-6 Requests tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 3-7 Conference List tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 3-8 Conference View tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

ReadiVoice Operator Guide
vi Proprietary & Confidential

Proprietary & Confidential vii
About this Manual
This introduction provides a brief overview of the ReadiVoice Operator Guide,
describes the conventions used in this manual, and explains how to get
additional information or support.
Purpose
This manual introduces you to the ReadiVoice Operator application and
describes the procedures that operators use in responding to users’ requests
for help. These procedures include:
•Registering and unregistering for groups and bridges
•Answering operator requests
•Registering for and monitoring a conference without a request
•Speaking privately with a participant
•Placing and retrieving a participant on hold
•Dialing participants
•Disconnecting a participant
•Muting and unmuting participants
•Joining and leaving a conference
•Ringing a locked conference
•Monitoring talk slots and troubleshooting line noise problems
Some ReadiVoice systems have group operators. A group operator works with
conferences from a specific subscriber group or groups. If you log in as a group
operator, everything looks and works as described here, but you only see
conferences and operator requests from your group or groups.
As an operator, you should also familiarize yourself with the ReadiVoice
Subscriber Guide and ReadiVoice Provisioning Guide.

ReadiVoice Operator Guide
viii Proprietary & Confidential
Document Conventions
This document uses the following typographical conventions.
Typeface Usage
bold Names of fields, screens, windows, dialog boxes,
and other user interface elements; for example:
1Type the number into the Phone Number
field and click Dial.
2Click Cancel to close the dialog box.
italics New terms, book titles, or emphasis; for example:
According to the VERITAS Cluster Server User
Guide, crash tolerant applications are sometimes
referred to as cluster friendly applications.
code Computer output, command references within text,
and filenames; for example:
Performs the initial configuration and reads the
.vcsrc file
code, bold Command line entries, for example:
>> Type cp ../default_group.ini
group.ini
.
code, bold & italics Command line variables, for example:
>> Type cp ../default_group.ini
groupnn.ini
replacing nn with the
subscriber group number.
SMALL CAPS Specific keys on the keyboard, for example:
>> Move the cursor by pressing TAB or
SHIFT+TAB.

About this Manual
Proprietary & Confidential ix
Customer Support
Recognizing that technology alone cannot solve today’s complex challenges,
Polycom Global Services provides the industry’s best technical support staff
and programs to let you concentrate on the task at hand. ReadiVoice users can
select from a variety of support solutions to obtain the level of support that
best meets their needs.
Before contacting your Polycom Global Services representative for technical
assistance, gather as much information as possible about your situation. Any
information you can provide helps us assess the problem and develop an
appropriate solution.
Polycom Global Services Telephone and Email
If you have comments or questions about ReadiVoice or if you need technical
assistance, contact:
Polycom Global Services on the Web
For more information about Polycom Global Services, go to
http://www.polycom.com and select the Support Solutions link under the
Global Services category.
Polycom Technical Publications Department
If you have comments or questions about this or any other ReadiVoice
documentation, contact:
Polycom Technical Publications Department
1765 West 121st Avenue
Westminster, CO 80234-2301 U.S.A.
Email: [email protected]
•Polycom Global Services in U.S.A 800-827-7782
•Denver metro or outside U.S.A. 303-223-5223
•Email: [email protected]

ReadiVoice Operator Guide
xProprietary & Confidential

Proprietary & Confidential 1
1
Introducing the ReadiVoice System
This chapter offers a general overview of the ReadiVoice conferencing system
and its features, functionality, and components.
What is the ReadiVoice System?
The ReadiVoice is the industry-leading, on-demand conferencing system. It
provides an easy-to-use, reliable, scalable, and full-featured conferencing
solution.
A ReadiVoice conference may contain up to 300 participants, including the
conference leader(s).
How ReadiVoice Conferencing Works
The ReadiVoice system is subscriber-based. A subscriber is someone, such as a
chairperson or conference leader, for whom you’ve set up conferencing access.
Each subscriber has access to a specified number of conferencing ports and can
use them at any time.
Through the provisioning process, you add subscribers to the ReadiVoice
system’s database. Each subscriber is given an access phone number for dialing
into the system and a subscriber password that identifies the subscriber. An
access number can be shared by many subscribers or private (assigned to only
one subscriber). If the access number is shared, the subscriber is also given
either:
•An access code that everyone uses to access the subscriber’s conferences.
•A participant password that participants use to access the subscriber’s
conferences (the subscriber uses the subscriber password).
Each conferencing subscriber is a member of a subscriber group. Subscriber
groups are logical groupings of related subscribers who share the same default
settings and options (for instance, a specific prompt set). You can create groups
for specific purposes or you can use one subscriber group for all subscribers.

ReadiVoice Operator Guide
2Proprietary & Confidential
Starting and Joining a Conference
Once provisioned, a subscriber can hold a conference at any time. No advance
reservation is necessary or possible. Subscribers can start conferences from
any touchtone telephone by dialing the access phone number and providing
their access code (if any) and subscriber password when prompted.
Participants join a conference by dialing the access phone number and
providing their access code or participant password. If the account permits,
the subscriber can also specify a conference security code that participants
must know to join the conference.
Controlling a Conference
A subscriber can have only one conference active at a time. During a
conference, subscribers can control the conference and dial out to additional
participants using:
Telephone touchtone (DTMF) commands — The ReadiVoice system
supports a complete set of touchtone commands. Subscribers can use these to
control the conference, enable or disable features, and dial out. Participants
can use these to control their own lines and use features to which they’ve been
given access.
The touchtone command set is completely configurable at the system level. In
addition, you can enable or disable specific features at the subscriber group or
individual subscriber level.
The Web-based Moderator interface — The Moderator lets your conferencing
subscribers or their designated moderators set up, start, monitor, and control
their conferences over the Internet. To log into the Moderator, users enter the
subscriber’s access phone number, access code (if any), and password.
The Moderator provides the conference control features that are enabled in the
subscriber profile for the conference. Most commands available to the
subscriber as touchtone commands are also available in the Moderator.
By default, conferences start when the subscriber arrives and end when the
subscriber leaves. This can be modified as follows:
•If the Quick Start option is enabled, participants don’t have to wait on hold
for the subscriber. The conference starts when the first participant arrives.
•If Continuation is enabled, the conference doesn’t end when the subscriber
leaves. It continues until the last participant leaves.
•The system can be configured to end a conference (or call an operator)
containing only one to three lines (configurable) after a specified delay.
You can use this feature to handle problems such as someone forgetting to
hang up a speaker phone in a conference room.
For more detailed information about how subscribers and participants interact
with the system to set up, start, control, and join conferences, see the ReadiVoice
Subscriber Guide.

Introducing the ReadiVoice System
Proprietary & Confidential 3
Managing Your ReadiVoice System
Day-to-day management and operation of your ReadiVoice system is
accomplished using operator/maintenance stations, which are typically standard
PCs connected to your company’s LAN (local area network) or WAN (wide
area network). From these PCs, your company’s staff can access the
Web-based ReadiVoice applications for:
Operators — Respond to operator requests from subscribers (and, if
authorized, participants) to resolve problems, answer questions, or provide
other assistance.
Provisioners — Add, modify, and delete subscriber accounts.
System Administrators — Configure and maintain the ReadiVoice system,
create new subscriber groups, and set up other internal users and their
passwords. They can also perform the provisioning functions.
To use a Web-based ReadiVoice application, users launch a supported
browser (Microsoft Internet Explorer version 5.5 or later), point it to the correct
Internet address (URL) for the application, and log in when prompted.
The Operator application and some parts of the Administration interface also
require a Java virtual machine (plug-in), which the user is prompted to
download if it isn’t already installed. Voyant has certified these Java applets
with the Sun Microsystems Java Runtime Engine (JRE) 1.3.1 and 1.4.2, on
Microsoft Windows 2000 and Microsoft Windows XP.
Operator Interface
The ReadiVoice Operator interface lets operators monitor the conferences on
the system, answer operator requests from their subscribers and participants,
and perform various tasks to assist users.
Operators may have access to all conferences or they may be limited to the
conferences of a specific subscriber group or groups, depending on their login
name and the system configuration.
When someone requests an operator, the system sends an audible and visual
alert to the available operators. An operator can answer the oldest request in
the queue or select a specific request from a list.
Note: These applets should work on other platforms and operating systems and with
newer versions of the JRE, but that depends on proper implementation by the
operating system and Java virtual machine. Polycom hasn’t tested other possible
combinations and can’t be responsible for implementation or compatibility issues
beyond our control.
Note: The ReadiVoice system doesn’t require operators. Providing operator services is
entirely optional.

ReadiVoice Operator Guide
4Proprietary & Confidential
When operators answer a request or select a conference to monitor, the system
registers them for the conference and displays all the available information
about the conference and its participants.
If an operator’s duties include provisioning as well as answering operator
requests, the operator can switch to the Provisioning interface by clicking the
Provisioning button on the Operator page.
This manual describes the Operator interface and operator tasks.
Provisioning Interface
The ReadiVoice Provisioning interface lets provisioners create and modify
ReadiVoice subscriber accounts. A subscriber account authorizes someone to
use your ReadiVoice system.
To set up an account for a customer, a provisioner enters subscriber and billing
information and defines the subscriber’s conference access and features.
All subscribers belong to a subscriber group. You can use one subscriber group
for everyone, or you can have multiple subscriber groups, each used for a
specific company, access method, or other affinity group. A subscriber group
can have its own default voice prompt set, account settings, and number group
(controlling access numbers and routing).
Like operators, provisioners may have access to all subscriber groups or they
may be limited to a specific subscriber group, depending on their login name
and the system configuration.
The Provisioning interface lets provisioners create new subscriber accounts or
search for an existing account and then edit or disable it.
For more information about the Provisioning interface and provisioning tasks,
see the ReadiVoice Provisioning Guide.
Administration Interface
The ReadiVoice Administration interface lets administrators monitor the
system, create new subscriber groups, customize the interfaces, create and
maintain user logins, set default parameters, and configure bridges.
For more information about the Administration interface and system
administrator tasks, see the ReadiVoice Administration & Maintenance Manual.
Note: We recommend automating your initial subscriber provisioning. Contact Polycom
for help with this. The ReadiVoice system’s Provisioning interface is available for
manual provisioning and for viewing or modifying subscriber account information.

Introducing the ReadiVoice System
Proprietary & Confidential 5
Components of the ReadiVoice System
A ReadiVoice system includes:
•A Conference Allocation and Control System (CACS) server.
•Up to twelve InnoVox media servers (conferencing bridges), providing up
to 5,760 ports in a single system, or one InnoVox media server, providing
4032 ports in a single 13U bridge cabinet.
•An optional boot server from which the bridges boot.
The specific configuration of a ReadiVoice system depends on its capacity
(number of ports), type of media server(s), and options.
The CACS and boot server may be the same server. All system components
mount into a standard 19-inch rack.
Two types of ReadiVoice systems are available. There are both hardware and
software differences between the two types, although the core ReadiVoice
software is the same (merely configured differently). The two types are for
different network environments:
ReadiVoice-PSTN uses the Public Switched Telephone Network (PSTN). The
bridge or bridges make circuit-switched connections over standard digital
telephony spans.
ReadiVoice-IP uses Voice Over IP (VOIP). The bridge makes packet-switched
Internet Protocol (IP) connections over Ethernet.
ReadiVoice-PSTN Systems
The PSTN version of ReadiVoice has two call routing configurations:
Fixed Access — Each access telephone number terminates on a specific bridge
in the system. This configuration is called a non-routed system.
Intelligent Network Call Routing (INCR) — Access telephone numbers
aren’t assigned to specific bridges. Instead, the ReadiVoice system uses a
carrier common channel signaling network (such as SS7 or Tollfree Gateway)
to dynamically route calls among available bridges. This configuration is
called a routed system. A routed system makes more efficient use of the bridges
because you can distribute the conferencing load and specify bridge
availability and priority.
Figure 1-1 provides a high-level view of the major components in a routed
ReadiVoice-PSTN system attached to a carrier common channel signaling
network. A fixed access system is identical, but without the Service Control
Point (SCP) connecting it to the carrier common channel signaling network.
The SCP may or may not be required for a routed system, depending on your
carrier.

ReadiVoice Operator Guide
6Proprietary & Confidential
The SCP (if required), subscriber database, and Web server can physically
reside on the CACS server. In large systems, however, these components may
be distributed among multiple servers in order to distribute the processing
load.
Figure 1-1 ReadiVoice-PSTN system diagram
When a caller dials a ReadiVoice-PSTN subscriber’s access phone number on
a typical routed ReadiVoice system:
1The originating central office switch recognizes the number as requiring
carrier common channel signaling network handling.
2The carrier switch sends a query through the carrier common channel
signaling network to the ReadiVoice CACS, which allocates bridge
resources to that subscriber according to his or her subscriber account
settings.
3The CACS returns a routing solution through the carrier common
channel signaling network to the originating carrier switch. It also
notifies the bridge of the upcoming call and the associated account profile
and features.
Corporate LAN/WAN
Dedicated LAN
Carrier
common
channel
signaling
network
Internet
Operator/Maintenance
Station
Database
SCP (if required)
CACS
PSTN
(See note)
InnoVox
Bridges
Subscriber access via
Web-based Moderator
SCP (if required)
Note: The InnoVox bridges are connected to
the PSTN via a switch certified by the local
country regulatory authority.

Introducing the ReadiVoice System
Proprietary & Confidential 7
4The carrier switch uses the routing solution to route the call to the
InnoVox bridge selected by the CACS call router.
Figure 1-2 summarizes this INCR signaling flow.
5When the call reaches the bridge, the ReadiVoice system places it into an
interactive call flow script to guide the caller into the conference. In a
fixed access system, the script collects the access code (if needed). In all
systems, the script handles subscriber identification and collection of the
optional conference security code. Non-subscribers are put on hold until
the subscriber arrives, enters the subscriber password, and starts the
conference.
6If the account permits, the call flow script gives the subscriber an
opportunity to review and change account options prior to starting the
conference.
7Once the subscriber starts the conference, participants are prompted to
enter the conference security code (if applicable) and then placed into the
conference.
Figure 1-4 on page 13 summarizes the ReadiVoice basic call flow after the call
reaches the bridge or on a non-routed system.
If the Quick Start feature is enabled, participants don’t have to wait for the
subscriber. They’re placed directly into conference instead of on hold. If the
Roll Call feature is enabled, callers are prompted to record their name before
entering the conference.
Callers who enter the subscriber or participant password or the conference
security code incorrectly three times are played the appropriate message and
then either sent to an operator (if available) or disconnected, depending on
how your system is configured.

ReadiVoice Operator Guide
8Proprietary & Confidential
Figure 1-2 ReadiVoice-PSTN INCR signaling flow
Start
User dials
ReadiVoice
access phone number
Originating switch
recognizes that the
number requires carrier
common channel
signaling network
handling
Originating switch
initiates carrier common
channel signaling
network query to CACS
Is the conference
underway? Yes
Return associated
PSTN translation
number
Select bridge,
allocate resources
Originating switch
completes call using
translation number
supplied by carrier
common channel
signaling network
Call placed in
ReadiVoice call flow
script
No
Are there enough
ports?
ReadiVoice is not
available. Try again.
(Or special network
handling.)
If applicable, collects
access code.
Are there enough
ports?
Yes
No
Yes

Introducing the ReadiVoice System
Proprietary & Confidential 9
ReadiVoice-IP Systems
All ReadiVoice-IP systems are routed. That is, the CACS uses SIP (Session
Initiation Protocol) signaling over IP to route calls dynamically among
available bridges.
Figure 1-3 provides a high level view of the components in a ReadiVoice-IP
system.
Figure 1-3 ReadiVoice-IP system diagram
Corporate LAN/WAN
IP Over Ethernet
Internet
Operator/
Maintenance
Station
Database
CACS
PSTN
InnoVox
Bridge(s)
Subscriber
access via
Web-based
Moderator
Gateway
I P
123
456
789
*8#
123
456
789
*8#
SIP Phone
SIP Phone
Ethernet
Switch
Conference
Control
Windows XP
SIP Phone
Gigabit
100Base-T

ReadiVoice Operator Guide
10 Proprietary & Confidential
ReadiVoice-IP Call Processing
When a caller dials a ReadiVoice-IP subscriber’s access phone number on a
typical ReadiVoice system:
1The SIP Invite message from the caller‘s SIP user agent (perhaps a SIP
telephone) reaches the call-control portion of the CACS. If the SIP invite
contains no access code:
aThe CACS directs the call to a bridge with a free port and runs a bridge
script that prompts the caller for the access code.
bThe bridge returns that access code to the CACS.
2The CACS uses the access code to identify the subscriber account. Its call
router allocates bridge resources according to the service description of
the subscriber just identified.
3The CACS connects the call to the bridge just chosen.
4When the call reaches the bridge, an interactive call flow script guides the
caller into the conference. The script handles subscriber identification and
collection of the optional conference security code. Non-subscribers are
put on hold until the subscriber arrives, enters the subscriber password,
and starts the conference.
5If the account permits, the call flow script gives the subscriber an
opportunity to review and change account options prior to starting the
conference.
6Once the subscriber starts the conference, participants are prompted to
enter the conference security code (if applicable) and then placed into the
conference.
Figure 1-4 on page 13 summarizes the ReadiVoice basic call flow after the call
reaches the bridge.
If the Quick Start feature is enabled, participants don’t have to wait for the
subscriber. They’re placed directly into conference instead of on hold. If the
Roll Call feature is enabled, callers are prompted to record their name before
entering the conference.