Cisco Acano X-series 開発者ガイド
Cisco Meeting Server Release 2.0 : CDR Guide
4
1 Introduction
The Cisco Meeting Server was formerly called the Acano Server. The Cisco Meeting Server is
now hosted on a new preconfigured version of a Cisco UCS server, called the Cisco Meeting
Server 1000. It can also be hosted on the Acano X-Series hardware, or on a specification based
VM server.
now hosted on a new preconfigured version of a Cisco UCS server, called the Cisco Meeting
Server 1000. It can also be hosted on the Acano X-Series hardware, or on a specification based
VM server.
The Meeting Server generates Call Detail Records (CDRs) internally for key call-related events,
such as a new SIP connection arriving at the server, or a call being activated or deactivated.
such as a new SIP connection arriving at the server, or a call being activated or deactivated.
The server can be configured to send these records to a remote system to be collected and
analyzed. There is no provision for records to be stored on a long-term basis on the Meeting
Server, nor any way to browse CDRs on the Meeting Server itself.
analyzed. There is no provision for records to be stored on a long-term basis on the Meeting
Server, nor any way to browse CDRs on the Meeting Server itself.
The CDR system can be used in conjunction with the Meeting Server API, with the call ID and call
leg IDs values being consistent between the two systems to allow cross referencing of events
and diagnostics.
leg IDs values being consistent between the two systems to allow cross referencing of events
and diagnostics.
The Meeting Server supports multiple CDR receivers (currently limited to two) enabling you to
deploy different management tools or multiple instances of the same management tool.
deploy different management tools or multiple instances of the same management tool.
Note: Also refer to the Cisco Meeting Server API Reference guide.
1.1 How to Use this Document
This document is one of a number of reference guides as shown in the figure below.
It is split into sections allowing you to build your knowledge by reading from front to back. In
addition chapters 3, 4, and 5 act as a reference that can be “dipped into”. Each CDR record type
and its fields are described in detail.
addition chapters 3, 4, and 5 act as a reference that can be “dipped into”. Each CDR record type
and its fields are described in detail.
This document describes a “minimum set” of information; the XML nature of the records means
that new elements may appear in new Call Bridge software versions and so you should always
allow for this when parsing the records we generate. A receiver must be able to cope with
additional, new elements, not mentioned in any existing version of the document (while at the
same time we commit to providing what the document says we provide, according to the
structure it describes).
that new elements may appear in new Call Bridge software versions and so you should always
allow for this when parsing the records we generate. A receiver must be able to cope with
additional, new elements, not mentioned in any existing version of the document (while at the
same time we commit to providing what the document says we provide, according to the
structure it describes).
1 Introduction