80125
80125
Response Code | Reason String | Description |
---|---|---|
200 | Success | The request has been successfully processed. |
300 | Low-level request error | A generic low-level request error has occurred. |
301 | Bad syntax | The XML syntax of the message is not correct. |
302 | Invalid value | The message contains an invalid parameter value. |
303 | Conflicting values | The message contains values that cannot be used together. |
400 | Semantic errors | The received CLUE protocol message contains semantic errors. |
401 | Version not supported | The protocol version used in the message is not supported. |
402 | Invalid sequencing | The received message contains an unexpected sequence number (e.g., sequence number gap, repeated sequence number, or sequence number outdated). |
403 | Invalid identifier | The clueId used in the message is invalid or unknown. |
404 | Advertisement expired | The sequence number of the advertisement the 'configure' message refers to is out of date. |
405 | Subset choice not allowed | The subset choice is not allowed for the specified Multiple Content Capture. |
See RFC 8847.
]]>Message | Description | Reference |
---|---|---|
options | Sent by the CI to the CR in the initiation phase to specify the roles played by the CI, the supported versions, and the supported extensions. | RFC 8847 |
optionsResponse | Sent by the CI to the CR in reply to an 'options' message, to establish the version and extensions to be used in the subsequent exchange of CLUE messages. | RFC 8847 |
advertisement | Sent by the MP to the MC to specify the telepresence capabilities of the MP expressed according to the CLUE framework. | RFC 8847 |
ack | Sent by the MC to the MP to acknowledge the reception of an 'advertisement' message. | RFC 8847 |
configure | Sent by the MC to the MP to specify the desired media captures among those specified in the 'advertisement'. | RFC 8847 |
configureResponse | Sent by the MP to the MC in reply to a 'configure' message to communicate whether or not the configuration request has been successfully processed. | RFC 8847 |
Number | Default Reason String | Description | Reference |
---|---|---|---|
200 | Success | The request has been successfully processed. | RFC 8847 |
300 | Low-level request error | A generic low-level request error has occurred. | RFC 8847 |
301 | Bad syntax | The XML syntax of the message is not correct. | RFC 8847 |
302 | Invalid value | The message contains an invalid parameter value. | RFC 8847 |
303 | Conflicting values | The message contains values that cannot be used together. | RFC 8847 |
400 | Semantic errors | The received CLUE protocol message contains semantic errors. | RFC 8847 |
401 | Version not supported | The protocol version used in the message is not supported. | RFC 8847 |
402 | Invalid sequencing | The received message contains an unexpected sequence number (e.g., sequence number gap, repeated sequence number, or sequence number outdated). | RFC 8847 |
403 | Invalid identifier | The clueId used in the message is invalid or unknown. | RFC 8847 |
404 | Advertisement expired | The sequence number of the advertisement the 'configure' message refers to is out of date. | RFC 8847 |
405 | Subset choice not allowed | The subset choice is not allowed for the specified Multiple Content Capture. | RFC 8847 |