204 |
|
The resource profiles deployment information successfully updated.
Note: The response will only contain both an ETag value
and link to the updated profile resource.
|
400 |
text/plain
|
Condition-type is required. |
400 |
text/plain
|
Condition-identifier is required. |
400 |
text/plain
|
Condition-type is not valid. Support devices,device-groups,models,sites,global. |
400 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Profile-identifier is not valid. The profile with the supplied profile identifier does not exist on the Call Server. |
403 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Unable to get permission. |
404 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Deployment resource does not exist. |
412 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
The deployment resource has changed on the server.
Note: The response will contain the ETag value and link that reflects
the server's profile resource in the HTTP response header.
The API client must supply the ETag in the message body that is bounded by
the "entity-tag" XML tag. Refer to the "plcm-uc-profile-deployment.xsd" for details.
If the message body does not contain the ETag value, the server will
look for the ETag in the "If-Match" header.
|
428 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
The API client must supply the ETag in the message body that is bounded by
the "entity-tag" XML tag. Refer to the "plcm-uc-profile-deployment.xsd" for details.
If the message body does not contain the ETag value, the server will
look for the ETag in the "If-Match" header.
|