|Port range settings records successfully retrieved.
Port range settings records have not changed since the last get.
Note: The API client must provide the "plcm-port-range-settings"
ETag value in the "If-None-Match" HTTP header to ensure conditional
This will improve network performance by reducing bandwidth
If the API client chooses to exclude an ETag value from a previous,
search in the "If-None-Match" header, then the HTTP response will
search results in the message body.
The "plcm-port-range-settings" ETag can be accessed from the initial
search result's HTTP
response header. Also, subsequent searches require the identical search
to ensure an equivalent ETag value. This also assumes no other
client made changes to
the Port range settings on the server.
||User has insufficient permissions to perform the operation.
The request contained ETags in both the header (header-ETag) and the
body (body-ETag) and they do not match.
The resource has changed on the server. The API client must retrieve
the latest resource version, apply the resource modifications,
then update to the server.
The API client must supply the ETag in the message body that is
the "entity-tag" XML tag. Refer to the "plcm-port-range-settings.xsd"
If the message body does not contain the ETag value, the server will
look for the ETag in the "If-Match" header.