Cisco Cisco Meeting Server 2000 發佈版本通知
Cisco Meeting Server Release 2.0.1 : Release Notes
12
n
if one or more members with a Cisco PMP plus license has joined a space, then one of their
licenses will be used, if not, then
licenses will be used, if not, then
n
if the person that created the space (the owner) has a Cisco PMP plus license, then the
license of that owner is assigned, if not, then
license of that owner is assigned, if not, then
n
if present a Cisco SMP plus license is assigned,
2.2.6 Determining Cisco Multiparty Licensing Usage
New API objects, and additional fields to existing objects, have been added in release 2.0 to
enable Admins to determine the consumption of Multiparty licenses. See
enable Admins to determine the consumption of Multiparty licenses. See
2.3 Ad hoc call escalation between Cisco Unified Communications
Manager and Cisco Meeting Server
Manager and Cisco Meeting Server
Release 2.0 supports the escalation of a 2-way call on Cisco Unified Communications Manager
to a conference on the Meeting Server via ad hoc call escalation. This section provides an
overview on how to configure Cisco Unified Communications Manager and the Meeting Server.
Cisco Unified Communications Manager needs to be running Release 10.5(2) or later.
to a conference on the Meeting Server via ad hoc call escalation. This section provides an
overview on how to configure Cisco Unified Communications Manager and the Meeting Server.
Cisco Unified Communications Manager needs to be running Release 10.5(2) or later.
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 each needs to trust the other'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 each needs to trust the other's
certificate, in order for escalated ad hoc calls to work.
The following instructions describe setting up a secure SIP trunk between Cisco Unified
Communications Manager and the Meeting Server. If you decide to set up the SIP trunk as non-
secure, you will still need to use certificates. Refer to the “Cisco Meeting Server Deployment
with Call Control” guide for the steps on setting up a non-secure SIP trunk, and for information
on setting up rendezvous and scheduled calls between Cisco Unified Communications Manager
and Cisco Meeting Server.
Communications Manager and the Meeting Server. If you decide to set up the SIP trunk as non-
secure, you will still need to use certificates. Refer to the “Cisco Meeting Server Deployment
with Call Control” guide for the steps on setting up a non-secure SIP trunk, and for information
on setting up rendezvous and scheduled calls between Cisco Unified Communications Manager
and Cisco Meeting Server.
2.3.1 Configuring a secure SIP trunk
Follow the steps below 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.
Server.
Configuration required on the Meeting Server:
Follow the Cisco Meeting Server deployment guides to configure your Meeting Server, once
configured:
configured:
2 New Features/Changes in 2.0