Cisco Acano X-series
Cisco Meeting Server Release 2.0 : Single Combined Meeting Server Deployments
9
be adapted to your deployment.
1.1.2 Management and network interfaces
There are two layers to the Meeting Server: a Platform and an Application.
n
The Platform is configured through the Mainboard Management Processor (MMP). The MMP
is used for low level bootstrapping, and configuration via its command line interface.
is used for low level bootstrapping, and configuration via its command line interface.
Note: On the Acano X-series servers the MMP can be accessed via the serial Console port or
using SSH on the Ethernet interface labeled Admin. In virtualized deployments the MMP is
accessed on virtual interface A.
using SSH on the Ethernet interface labeled Admin. In virtualized deployments the MMP is
accessed on virtual interface A.
n
The Application runs on this managed platform with configuration interfaces of its own. The
application level administration (call and media management) is done via either the Call
Bridge’s Web Admin Interface, or through the API. Either can be configured to run on any one
of the Ethernet interfaces.
application level administration (call and media management) is done via either the Call
Bridge’s Web Admin Interface, or through the API. Either can be configured to run on any one
of the Ethernet interfaces.
On the Acano X-series servers there are five physical Ethernet interfaces labeled Admin, A, B
C and D. In virtualized deployments one Ethernet interface (A) is created, but up to three more
can be added (B, C and D).
C and D. In virtualized deployments one Ethernet interface (A) is created, but up to three more
can be added (B, C and D).
Note: There is no physical separation between the media interfaces A-D on an X-series
server, but the Admin interface is physically separate. Each interface is configured
independently at the IP level. IP forwarding is not enabled in either the Admin or host IP stack.
server, but the Admin interface is physically separate. Each interface is configured
independently at the IP level. IP forwarding is not enabled in either the Admin or host IP stack.
See the appropriate Installation Guide for details.
1.2 Application Programming Interface
The Meeting Server supports an Application Programming Interface (API). The API uses HTTPS
as a transport mechanism and is designed to be scalable in order to manage the potentially very
large numbers of active calls and spaces available in a deployment.
as a transport mechanism and is designed to be scalable in order to manage the potentially very
large numbers of active calls and spaces available in a deployment.
The API includes LDAP server access methods for adding, configuring and modifying LDAP
servers, and support for multi-tenancy for searching calls through an additional Tenant ID. Other
additions include posting to space message boards, the ability to filter the set of active call legs
to just those experiencing "alarm" conditions (for example, packet loss or excessive jitter) and
the ability to retrieve system-wide status values.
servers, and support for multi-tenancy for searching calls through an additional Tenant ID. Other
additions include posting to space message boards, the ability to filter the set of active call legs
to just those experiencing "alarm" conditions (for example, packet loss or excessive jitter) and
the ability to retrieve system-wide status values.
Multi-tenancy means that groups of users can be entirely segmented within the solution as
required by service provider deployments e.g. users will only be able to meet, assign users to
spaces, and search in the directory within the same configured customer groups.
required by service provider deployments e.g. users will only be able to meet, assign users to
spaces, and search in the directory within the same configured customer groups.
Refer to the Cisco Meeting Server API Reference guide for more details.
1 Introduction