EasyManua.ls Logo

Polycom 1500 - Participants (AVC Participants); SIP Participants (All Participants)

Polycom 1500
209 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
RealPresence Collaboration Server (RMX) 1500/1800/2000/4000 Getting Started Guide
Polycom®, Inc. 125
H.323 Participants (AVC Participants)
Dialing is executed in the same way as for conferences, where the Entry Queue ID/Name replaces the
Conference ID/Name.
» H.323 participants dial
[Gatekeeper Prefix][Entry Queue ID/Name].
Example:
Prefix in gatekeeper: 925
Entry Queue ID: 1000
» The participant dials: 9251000
H.323 participants can bypass the Entry Queue IVR voice messages by adding the correct
Conference ID of destination conference to the initial dial string:
[
Gatekeeper Prefix][EQ ID][##Destination Conference ID]
Example:
Conference ID: 1001
» H.323 participants dial: 9251000##1001
H.323 participants can also bypass the conference IVR voice messages by adding the Conference
Password to the initial dial string:
[Gatekeeper Prefix][EQ ID][##Destination Conference ID][##Password]
Example:
Conference ID: 1001
Conference Password: 34567
» H.323 participants dial 9251000##1001##34567
SIP Participants (All Participants)
Using an Entry Queue or Meeting Room minimizes the number of conferences that require registration with
the SIP server and enables using one URI address for all dial-in connections, using the format:
<Entry Queue routing name>@<domain name> or
<Entry Queue routing name>@<MCU signaling IP Address> or
<Meeting_Room_Name>**<password>@MCU signaling IP Address>
Examples:
Entry Queue Routing Name: DefaultEQ
Domain Name: polycom.com
MCU Signaling IP address: 172.22.20.42
» SIP participants dial: DefaultEQ@polycom.com

Table of Contents

Other manuals for Polycom 1500

Related product manuals