Cisco Cisco Meeting Server 2000
Cisco Meeting Server Release 2.0 : Deployments with Call Control Guide
6
2 Configuring a SIP Trunk to Cisco Unified
Communications Manager
Communications Manager
This chapter explains how to set up a SIP Trunk between Cisco Unified Communications
Manager and a Meeting Server. The Meeting Server must either be configured as a Core server
in a split server deployment, or as a single combined server.
Manager and a Meeting Server. The Meeting Server must either be configured as a Core server
in a split server deployment, or as a single combined server.
Cisco recommends setting up a secure SIP trunk, however if your company policy is for traffic
within your organization to be non secure, then a non-secure SIP trunk can be configured.
However, the escalation of a 2-way call on Cisco Unified Communications Manager to a
conference on the Meeting Server, requires the Cisco Unified Communications Manager to
communicate with the API of the Cisco Meeting Server. The API requires HTTPS
communication, so certificates need to be created and uploaded to both the Cisco Meeting
Server and Cisco Unified Communications Manager, and Cisco Unified Communications
Manager needs to trust the Meeting Server's certificate, in order for escalated ad hoc calls to
work.
within your organization to be non secure, then a non-secure SIP trunk can be configured.
However, the escalation of a 2-way call on Cisco Unified Communications Manager to a
conference on the Meeting Server, requires the Cisco Unified Communications Manager to
communicate with the API of the Cisco Meeting Server. The API requires HTTPS
communication, so certificates need to be created and uploaded to both the Cisco Meeting
Server and Cisco Unified Communications Manager, and Cisco Unified Communications
Manager needs to trust the Meeting Server's certificate, in order for escalated ad hoc calls to
work.
If you are just allowing scheduled or rendezvous calls between the Meeting Server and Cisco
Unified Communications Manager, and you set the SIP trunk as non-secure, then certificates
are not required. Definitions of call types are given in
Unified Communications Manager, and you set the SIP trunk as non-secure, then certificates
are not required. Definitions of call types are given in
Note: If you are not your organization's Cisco Unified Communications Manager server
administrator, then Cisco strongly advises you to seek the advice of your local administrator on
the best way to implement the equivalent on your server’s configuration.
administrator, then Cisco strongly advises you to seek the advice of your local administrator on
the best way to implement the equivalent on your server’s configuration.
2.1 Configuring a secure SIP trunk
Follow the steps in
and
to set up the secure SIP trunk, then
to enable escalation of a 2-way call on Cisco Unified Communications Manager to a
conference on the Meeting Server.
2.1.1 Configuration required on the Meeting Server
Follow the Cisco Meeting Server deployment guides to configure your Meeting Server, once
configured:
configured:
1. SSH into the MMP of the Meeting Server
2. If you have not already done so, specify a listening interface using the MMP command
callbridge listen
3. Generate a private key and Certificate Signing Request (.csr) file for the Call Bridge, call it
"cucm-trust.csr"
2 Configuring a SIP Trunk to Cisco Unified Communications Manager