Table Of Contents
Dialing via the Cisco Unified Videoconferencing 3500 MCU
Accessing Conferences via the Cisco Unified Videoconferencing 3500 MCU
Making an Ad Hoc Conference Call
Cisco Unified Videoconferencing 3500 MCU Dialing Conventions for H.323 Endpoints
Starting or Joining an Ad Hoc Conference with H.323 Endpoints
Inviting Multiple H.323 Endpoints with a Single Dial String
Cisco Unified Videoconferencing 3500 MCU Dialing Conventions for SIP Endpoints
Starting or Joining Ad Hoc Conferences with SIP Endpoints
Inviting Multiple SIP Endpoints with a Single Dial String
Dialing into the Cisco Unified Videoconferencing 3500 MCU Configured as a SIP-compliant Endpoint
Dialing into the Cisco Unified Videoconferencing 3500 MCU Configured as a Separate SIP Domain
Using Dialing Conventions with any IP-based Endpoint
Controlling Conferences with DTMF
Dialing via the Cisco Unified Videoconferencing 3500 MCU
This section describes the following topics:
•
Accessing Conferences via the Cisco Unified Videoconferencing 3500 MCU
•
•
Accessing Conferences via the Cisco Unified Videoconferencing 3500 MCU
You can participate in video conferences hosted on the Cisco Unified Videoconferencing 3500 MCU from any phone, terminal, or endpoint on any type of network to which the MCU connects. The MCU can accept calls from H.323, Skinny Client Control Protocol (SCCP), and Session Initiation Protocol (SIP) endpoints, and with Cisco Unified Videoconferencing gateway support, from phones and terminals on networks in the same conference.
You can participate in a conference by dialing from a phone, from an endpoint application, or by using the MCU Conference Control interface.
With appropriate access rights, you can also create conferences, invite other participants and conferences, and use an extensive range of conference control features for enhancing the video conferencing experience.
Making an Ad Hoc Conference Call
All users can create or join an ad hoc (also called dial-in) conference simply by dialing the conference number. Users can invite single or multiple participants in the same operation.
Users can initiate multi-point conferences that run unattended and do not require advance configuration. Users simply dial a number and the MCU automatically sets up the conference. Anyone else who dials that number can join the conference at any time, provided that network resources are available. All that the user requires is a suitable service number—that an Administrator supplies—to combine with a unique number for the conference. A common practice is to use the telephone extension number of the conference creator as the unique number.
Related Topics
•
•
•
Cisco Unified Videoconferencing 3500 MCU Dialing Conventions for H.323 Endpoints
This section describes the dialing conventions relating to H.323 endpoints, including the following topics:
•
•
Starting or Joining an Ad Hoc Conference with H.323 Endpoints
To start or join an ad hoc conference with H.323 endpoints, you dial in using the conference ID number. The conference ID number is composed of a service prefix number that indicates the conference call type and capabilities and a unique number (or numbers) identifying the conference:
<Service prefix> + <Unique number>A conference ID can consist of any combination of the characters 1-9, *, and #. It can be up to 256 characters in length.
For example, you can dial:
601234
where:
•
•
As soon as the MCU accepts the call, you are connected to the existing conference, or the MCU creates a new conference with this conference identifier.
Note
Inviting Multiple H.323 Endpoints with a Single Dial String
With an H.323 endpoint, you can create or join an ad hoc conference and invite single or multiple participants in the same operation using the invite sign (**). You use the invite sign to separate the called numbers in the dialed string:
<conference ID number> + <**> + <invited participant number>For example, you can dial:
601234**5678
where:
•
•
•
Note
Cisco Unified Videoconferencing 3500 MCU Dialing Conventions for SIP Endpoints
You can dial to the MCU from SIP endpoints. You can also invite SIP endpoints to ad hoc conferences on the MCU when each is registered with a SIP proxy server on the IP network. The MCU domain name should be registered on a Domain Name System (DNS) or Microsoft Real Time Communications (RTC) server.
This section includes the following topics:
•
•
•
•
Starting or Joining Ad Hoc Conferences with SIP Endpoints
When starting or joining an ad hoc conference, the dialed string should contain the conference ID number and the Cisco Unified Videoconferencing 3500 MCU domain name:
<conference ID number> @ <mcu.domain.com>For example, you can dial:
601234@mcu.domain name
where:
•
•
Inviting Multiple SIP Endpoints with a Single Dial String
You can dial from a SIP endpoint and invite an H.323 or SIP endpoint when the inviting SIP endpoint is registered in the Cisco Unified Videoconferencing 3500 MCU domain. The Cisco Unified Videoconferencing 3500 MCU adds the default domain to the dialed string when a user name is dialed without a domain:
<conference ID number> + <**> + <invited SIP endpoint>For example, you can dial:
601234**john@mcu.domain.com
where:
•
•
•
Dialing into the Cisco Unified Videoconferencing 3500 MCU Configured as a SIP-compliant Endpoint
Administrators can configure the MCU as a SIP-complaint endpoint. Users can start or join an ad hoc conference by dialing into this MCU from their SIP endpoint. This procedure assumes that the SIP Proxy responsible for the network is capable of routing calls according to the dialed prefix. Check with your SIP Proxy vendor for compliance.
Procedure
Step 1
Step 2
For example, dial:
601234@default.domain
where:
•
•
Dialing into the Cisco Unified Videoconferencing 3500 MCU Configured as a Separate SIP Domain
Administrators can configure the MCU as a separate SIP domain. Users can start or join an ad hoc conference by dialing into this MCU from a SIP-complaint endpoint.
Procedure
Step 1
Step 2
For example, dial:
conference.id@mcu.domain.com
Using Dialing Conventions with any IP-based Endpoint
You can start or join an ad hoc conference from any IP-based endpoint. When dialing from an IP endpoint, configure the dialing software, IP phone, or other device with the appropriate network configuration details (H.323 gatekeeper IP address or SIP proxy IP).
Procedure
To start or join a conference with an IP endpoint, choose one of the following steps:
Step 1
For example, dial 601234.
As soon as the MCU accepts the call, you connect to the existing conference or the MCU creates a new conference with this conference identifier.
-or-
Step 2
For example, dial 601234**5678
As soon as the MCU accepts the call, you connect to the existing conference or the MCU creates a new conference with this conference identifier.
-or-
Step 3
For example, dial 601234**867655001 (<Conference ID number> + <**> + <Gateway service prefix + line number>).
As soon as the MCU accepts the call, you are connected to the existing conference or a new conference is created with this conference identifier.
Controlling Conferences with DTMF
You can control MCU conferences using Dual Tone Multi-Frequency (DTMF) signals from your endpoint remote control or key pad.
Depending on how you set the DTMF forwarding advanced command, the MCU passes out-of-band DTMF signals to all endpoints in the conference, to gateways only or does not pass DTMF signals.
The gateway inserts in-band signals on receiving the DTMF from the MCU. The audio bridge receives these in-band signals and responds accordingly.
Table 1-1 shows available DTMF control signals.
