Chapter 3
Basic Operation
3-8
Endpoint's Dial-in Numbers Not Registered to a Gatekeeper
Scenario
Dial-in String
Create this conference 172.22.30.40##1001
Create this conference and set:
Conference password: 111 1
Chairperson password: 2222
172.22.30.40##1001##1111##2222
Create this conference and
invite:
Participant 1 - IP address:
172.22.30.1
Participant 2 - IP address:
172.22.30.2
172.22.30.40##1001*172.22.30.1*172.22.30.2
Create this conference, set the
above passwords, and invite
above participants
172.22.30.40##1001##1111##2222*172.22.30.1*
172.22.30.2
SIP Endpoint
For an SIP endpoint, if the endpoint has been registered t o the same SIP
server as RMX, its dial-in number consists of the static route doma in name of
RMX and conference information (such as the confere nce ID, conference
password, chairperson password and participant addr ess) in the form below:
[Conference ID][$$Conference password][$$Chairperson
password][*Participant's TEL URI/SIP URI]@<RMX's static route domain name>
Here, the character within the <> symbols are mandatory, and those within
the [ ] symbols are optional.
For example:
RMX static route domain name: polycom.com
ID of the conference to be created: 1001
The table below shows the strings dialed by the endpoint under different
scenarios:
SIP Endpoint's Dial-in Numbers Registered to a Server
Scenario Dial-in String
Create this conference 1001@polycom.com
Create this conference and set:
Conference password: 111 1
Chairperson password: 2222
1001$$1111$$2222@polycom.com
Create this conference and invite:
Participant 1 - TEL URI/E.164123
Participant 2 - TEL URI/E.164321
1001*123*321@polycom.com
Create this conference, set the
above passwords, and invite above
participants 1001$$1111$$2222*123*321@polycom.com