Centralized Conferencing Manipulation Protocol (CCMP) Parameters
Created
- 2011-09-30
Last Updated
- 2012-03-26
Available Formats
CCMP Message Types
Registration Procedure(s)
- Specification Required
Expert(s)
- Unassigned
Reference
- RFC 6503: Centralized Conferencing Manipulation Protocol
Available Formats
| Message | Description | Reference |
|---|---|---|
| optionsRequest | Used by a conference control client to query a conference server for its capabilities, in terms of supported messages. | RFC 6503 |
| optionsResponse | Returns a list of CCMP messages supported by the specific conference server. | RFC 6503 |
| blueprintsRequest | Used by a conference control client to query a conferencing system for its capabilities, in terms of available conference blueprints. | RFC 6503 |
| blueprintsResponse | The blueprintsResponse returns a list of blueprints supported by the specific conference server. | RFC 6503 |
| blueprintRequest | Sent to retrieve the conference object associated with a specific blueprint. | RFC 6503 |
| blueprintResponse | Returns the conference object associated with a specific blueprint. | RFC 6503 |
| confsRequest | Used by a conference control client to query a conference server for its scheduled/active conferences. | RFC 6503 |
| confsResponse | Returns the list of the currently activated/scheduled conferences at the server. | RFC 6503 |
| confRequest | Used to create a conference object and/or to request an operation on the conference object as a whole. | RFC 6503 |
| confResponse | Indicates the result of the operation on the conference object as a whole. | RFC 6503 |
| userRequest | Used to request an operation on the "user" element in the conference object. | RFC 6503 |
| userResponse | Indicates the result of the requested operation on the "user" element in the conference object. | RFC 6503 |
| usersRequest | Used to manipulate the "users" element in the conference object, including parameters such as the "allowed-users-list", "join-handling", etc. | RFC 6503 |
| usersResponse | Indicates the result of the request to manipulate the "users" element in the conference object. | RFC 6503 |
| sidebarsByValRequest | Used to retrieve the "sidebars-by-val" element of the target conference object. | RFC 6503 |
| sidebarsByValResponse | Returns the list of the sidebar-by-val conferences within the target conference object. | RFC 6503 |
| sidebarsByRefRequest | Used to retrieve the "sidebars-by-ref" element of the target conference object. | RFC 6503 |
| sidebarsByRefResponse | Returns the list of the sidebar-by-ref conferences associated with the target conference object. | RFC 6503 |
| sidebarByValRequest | Used to request an operation on a sideber-by-val conference. | RFC 6503 |
| sidebarByValResponse | Indicates the result of the request to manipulate a sidebar-by-val conference. | RFC 6503 |
| sidebarByRefRequest | Used to request an operation on a sidebar-by-ref conference. | RFC 6503 |
| sidebarByRefResponse | Indicates the result of the request to manipulate a sidebar-by-ref conference. | RFC 6503 |
| extendedRequest | Provides for extensibility of the CCMP message types. Each extension is characterized by an extensionName that MUST be included in the extendedRequest. | RFC 6503 |
| extendedResponse | Returns the XML elements as defined for the specific extensionName. | RFC 6503 |
CCMP Response Codes
Registration Procedure(s)
- Specification Required
Expert(s)
- Unassigned
Reference
- RFC 6503: Centralized Conferencing Manipulation Protocol
Available Formats
| Number | Default Reponse String | Description | Reference |
|---|---|---|---|
| 200 | Success | The request was successfully processed. | RFC 6503 |
| 400 | Bad Request | The request was badly formed in some fashion. | RFC 6503 |
| 401 | Unauthorized | The user was not authorized for the specific operation on the conference object. | RFC 6503 |
| 403 | Forbidden | The specific operation is not valid for the target conference object. | RFC 6503 |
| 404 | Object Not Found | The specific conference object was not found. | RFC 6503 |
| 409 | Conflict | A requested operation cannot be successfully completed by the server. For example, the modification of an object cannot be applied because the client version of the object is obsolete and the requested modifications collide with the up-to-date state of the object stored at the server. | RFC 6503 |
| 420 | User Not Found | The user who is the target of the requested operation is unknown. | RFC 6503 |
| 421 | Invalid confUserID | The "confUserID" of the sender in the request is invalid. | RFC 6503 |
| 422 | Invalid Conference Password | A request to access/manipulate a password-protected conference object contained an invalid "conference-password" parameter. | RFC 6503 |
| 423 | Conference Password Required | A request to access/manipulate a password-protected conference object did not contain a "conference-password" parameter. | RFC 6503 |
| 424 | Authentication Required | The server wants to authenticate the request through the "subject" parameter but the parameter is not provided in the request. | RFC 6503 |
| 425 | Forbidden Delete Parent | The conferencing system cannot system cannot delete the specific conference object because it is a parent for another conference object. | RFC 6503 |
| 426 | Forbidden Change Protected | The target conference object cannot be changed (e.g., due to policies, roles or privileges). | RFC 6503 |
| 427 | Invalid Domain Name | The domain name in an AUTO_GENERATE_X instance in the conference object is not within the conference server's domain of responsibility. | RFC 6503 |
| 500 | Server Internal Error | The conference server experienced some sort of internal error. | RFC 6503 |
| 501 | Not Implemented | The specific operation is not implemented on the conferencing system. | RFC 6503 |
| 510 | Request Timeout | The request could not be processed within a reasonable time (as specified by the conferencing system). | RFC 6503 |
| 511 | Resources Not Available | The conference server cannot execute a command because of resource issues, e.g. it cannot create a conference because the system has reached its limits on the number of conferences. | RFC 6503 |