Cisco Cisco TelePresence MCU 4510 Installation Guide
Note: The MCU 5300 series does not have a built-in Gatekeeper.
7. Click Apply changes.
Configuring the Unified CM for Ad hoc conferencing
This deployment assumes you are using a non-secure deployment. If you are using a secure deployment you
will need to generate a certificate and private key. Refer to
will need to generate a certificate and private key. Refer to
for more
information.
Task 1: Adding a SIP trunk connecting to the MCU for Ad hoc
conferences
conferences
From Unified CM version 10.x onwards a SIP trunk between Unified CM and the MCU must be explicitly
configured for ad hoc conferences. The task is not required when running an earlier version of Unified CM.
configured for ad hoc conferences. The task is not required when running an earlier version of Unified CM.
To configure a SIP trunk to the MCU:
1. Go to
Device > Trunk
.
2. Click Add New to create a new SIP trunk.
3. Enter the following into the relevant fields:
Trunk Type
Select SIP Trunk.
Device Protocol
Leave as default: SIP.
Trunk Service Type
Leave as: None(Default).
4. Click Next.
5. Enter the following into the relevant fields, leave other fields as their default values:
Device Name
Enter a trunk name.
Device Pool
Select the appropriate Device Pool.
Location
Set to the appropriate location.
TelePresence MCUs IP address
Enter the MCU's IP address.
SIP Trunk Security Profile
Select Non-secure SIP Trunk Profile from the drop-down list.
SIP Profile
Select Standard SIP Profile for TelePresence Conferencing
Cisco TelePresence MCU Deployment Guide 4.5
Page 39 of 52
Deploying an MCU as a Unified CM media resource