Filter
Top Products
Proprietary & Confidential 271
D
ReadiVoice-IP with IP Tributaries
ReadiVoice-IP systems can be configured to enable the IP Tributaries feature.
This feature provides alternative access methods for initiating and entering a
conference. These methods perform authentication and call routing, and thus
can bypass elements of the front-end call flow.
To use this feature, you must provide an authentication mechanism separate
from the ReadiVoice system. The authentication mechanism puts one or more
pieces of the caller’s identifying information into the SIP
INVITE
message used
to access the system.
What are IP Tributaries?
IP tributaries are defined as part of the
TO
header within the SIP
INVITE
message sent to the ReadiVoice CACS. The following sections describe the
content of this
TO
header.
Single Number,
Traditional Access
In the ReadiVoice single number, traditional access call flow, the SIP
INVITE
message has a
TO
header in the following format:
TO: sip:accessnumber@host
When the header has this format, the caller is routed to the ReadiVoice IVR
system and asked to enter identifying information. The caller who keys in this
information is then routed to the conference and enters the traditional
ReadiVoice call flow.
Access Code Included In this type of SIP
INVITE
, the
TO
header includes the access code. It has the
following format:
TO: sip:accessnumber@host;AC=accesscode
When the header has this format, the caller is routed directly to the conference
(rather than being prompted for an access code) and enters the traditional
ReadiVoice call flow.
In this case, the access code has already been validated.