Cisco Cisco Meeting Server 2000 开发者指南
Cisco Meeting Server Release 2.0 : API Reference Guide
100
Note: GET of /system/cdrReceivers/<cdr receiver id>allows you to retrieve the configuration for
a single specified CDR receiver.
a single specified CDR receiver.
10.4.2 Setting the CDR Receivers URI
Set the CDR receiver URI through the API (as well as the Web Admin Interface). You can issue a
PUT or a POST on the /system/cdrReceivers node.
PUT or a POST on the /system/cdrReceivers node.
Use POST and specify a "url" value to create and configure the CDR receiver in one operation,
or use PUT to initially create the CDR receiver but configure the “url” separately later.
or use PUT to initially create the CDR receiver but configure the “url” separately later.
Parameters
Type/Value
Description/Notes
uri *
String
Full URL to which CDRs will be sent.
If the creation is successful, you should receive a “200 OK” response and a "Location:
/api/v1/system/cdrReceivers/<cdr receiver id>" object reference; if too many CDR receivers
are already configured, you will receive a "tooManyCdrReceivers" error (in a "failureDetails"
section).
/api/v1/system/cdrReceivers/<cdr receiver id>" object reference; if too many CDR receivers
are already configured, you will receive a "tooManyCdrReceivers" error (in a "failureDetails"
section).
Note: If you perform a PUT with an empty "url" to the legacy /system/cdrReceiver node, any
GUID associated with that CDR receiver is removed, and effectively that CDR receiver is no
longer present. If you later PUT a non-empty "url" value to the same (legacy) node, a new GUID
will be generated for that CDR receiver.
GUID associated with that CDR receiver is removed, and effectively that CDR receiver is no
longer present. If you later PUT a non-empty "url" value to the same (legacy) node, a new GUID
will be generated for that CDR receiver.
If you perform a PUT with an empty "url" to a non-legacy CDR receiver
(/system/cdrReceivers/<cdr receiver id>) then that CDR receiver remains with the same GUID,
but no "url" value. It will continue to show up in GET operations. This is because there is an
explicit "DELETE" method (section 4.4) for the new CDR receiver objects, whereas for the
legacy CDR receiver the only deconfiguration method is to set its location to the empty value.
(/system/cdrReceivers/<cdr receiver id>) then that CDR receiver remains with the same GUID,
but no "url" value. It will continue to show up in GET operations. This is because there is an
explicit "DELETE" method (section 4.4) for the new CDR receiver objects, whereas for the
legacy CDR receiver the only deconfiguration method is to set its location to the empty value.
To set or update the URIs of the CDR receivers via the Web Admin Interface use the
Configuration > CDR settings page.
Configuration > CDR settings page.
10.5 Global Profile Methods
10.5.1 Retrieving the Global Profile
GET to /system/profiles returns the values described in the following section.
10.5.2 Setting the Global Profile
You can set (or unset) the callLegProfile ID value under api/v1/system/profiles to impose (or
remove) a top-level profile.
remove) a top-level profile.
10 System Related Methods