Polycom 8 Manual De Usuario
Chapter 4 - New Meeting Window
4-42
Figure 4-1: Typical SIP Conferencing Layout
Dial-in Scenario—SIP Environment
Participants can dial in to an Entry Queue, or directly to a conference or to a
Meeting Room. Using an Entry Queue minimizes the number of conferences
that require registration with the SIP server, as it can use a single URI address
or a limited number of addresses for all the dial-in connections.
A new conference reservation or Entry Queue is defined. The conference or
the Entry Queue registers with the SIP proxy. The SIP participant registers
with the registrar, and provides authentication if required (non-trusted mode).
Usually, for SIP conferencing, an Ad Hoc Entry Queue is used. In this
scenario, the first participant dials the Entry Queue and creates a new
conference, while the other conference participants dial directly to the
conference using the conference name or numeric ID. The SIP participant
uses the Entry Queue URI to access the Entry Queue.
The Entry Queue URI is dialed in the format:
Entry Queue name@domain name.
For example,
Meeting Room. Using an Entry Queue minimizes the number of conferences
that require registration with the SIP server, as it can use a single URI address
or a limited number of addresses for all the dial-in connections.
A new conference reservation or Entry Queue is defined. The conference or
the Entry Queue registers with the SIP proxy. The SIP participant registers
with the registrar, and provides authentication if required (non-trusted mode).
Usually, for SIP conferencing, an Ad Hoc Entry Queue is used. In this
scenario, the first participant dials the Entry Queue and creates a new
conference, while the other conference participants dial directly to the
conference using the conference name or numeric ID. The SIP participant
uses the Entry Queue URI to access the Entry Queue.
The Entry Queue URI is dialed in the format:
Entry Queue name@domain name.
For example,
EQ1@polycom.com
- where the Entry Queue name is EQ1.
When dialing from a Microsoft Windows Messenger endpoint (which does not
have DTMF capabilities), the first participant (who, in Ad Hoc conferencing,
creates the new conference) enters the Entry Queue name followed by the
target conference name and the numeric ID in the format:
EQ name(target conference name)(target conference numeric ID).
For example,
have DTMF capabilities), the first participant (who, in Ad Hoc conferencing,
creates the new conference) enters the Entry Queue name followed by the
target conference name and the numeric ID in the format:
EQ name(target conference name)(target conference numeric ID).
For example,
EQ1(sales)(12345)
.
In this example, the Entry Queue name is EQ1, and a new On Going
Conference by the name sales with the numeric ID 12345 will be created on
the MCU.
Conference by the name sales with the numeric ID 12345 will be created on
the MCU.
The other conference participants can connect to the conference directly by
entering either sales or 12345.
Participants can connect to an Entry Queue, and then they are routed to the
destination conference using the conference password or the conference
numeric ID (depending on the MCU configuration).
entering either sales or 12345.
Participants can connect to an Entry Queue, and then they are routed to the
destination conference using the conference password or the conference
numeric ID (depending on the MCU configuration).
You do not need to add the domain name to the conference name as it is
automatically added by Microsoft Windows Messenger when sending the
request to the SIP server.
automatically added by Microsoft Windows Messenger when sending the
request to the SIP server.