200 |
application/vnd.plcm.plcm-naming-sipuri-scheme+xml application/vnd.plcm.plcm-naming-sipuri-scheme+json
|
Retrieval of sipuri naming configuration was successful |
304 |
|
sipuri naming configuration has not changed.
Note: The API client must provide the "plcm-naming-sipuri-scheme" representation's
ETag value in the "If-None-Match" HTTP header to ensure conditional retrieval.
This will improve network performance by reducing bandwidth consumption.
If the API client chooses to exclude an ETag value from a previous
request in the "If-None-Match" header, then the HTTP response will contain the
same information in the message body as the previous request.
The "plcm-naming-sipuri-scheme" ETag can be accessed from the initial request result's HTTP
response header.
If another client has changed the sipuri naming configuration, the ETag value will be out of date
and a request with the outdated ETag will return the full "plcm-naming-sipuri-scheme".
|
401 |
application/vnd.plcm.plcm-error+xml
|
Invalid credentials. |
403 |
application/vnd.plcm.plcm-error+xml
|
Area feature is not available. |
404 |
application/vnd.plcm.plcm-error+xml
|
The scheme does not exist. |