External SBC



[tags: DMA]

Resource Root

https://localhost:8443/api/rest/ext-sbc

Summary


Resources Methods
https://localhost:8443/api/rest/ext-sbc

GET  Retrieves a list of external SBCs.

POST  Add a new external SBC.

https://localhost:8443/api/rest/ext-sbc/debug-postliminary

POST  Test a postliminary script to a dial rule for an external SBC.

https://localhost:8443/api/rest/ext-sbc/{ext-sbc-id}

DELETE  Deletes information about an external SBC.

GET  Retrieves information about an external SBC.

PUT  Updates information about an external SBC.

Resources


https://localhost:8443/api/rest/ext-sbc


Methods

GET


Retrieves a list of external SBCs. [tags: DMA]

Request

Response

Status Representation Description
200 application/vnd.plcm.plcm-ext-sbc-list+xml
application/vnd.plcm.plcm-ext-sbc-list+json
sbcs list successfully retrieved
304
SBCs information has not changed since the last search.

Note: The API client must provide the "plcm-ext-sbc-list" 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, identical
search in the "If-None-Match" header, then the HTTP response will contain the
search results in the message body.

The "plcm-ext-sbc-list" ETag can be accessed from the initial search result's HTTP
response header. Also, subsequent searches require the identical search filter
to ensure an equivalent ETag value. This also assumes no other client made changes to
external SBCs on the server.

POST


Add a new external SBC. [tags: DMA]

Request

Representations

application/vnd.plcm.plcm-ext-sbc+xml
application/vnd.plcm.plcm-ext-sbc+json

Response

Status Representation Description
201 External SBC created successfully.
400 text/plain
Bad request.
409 application/vnd.plcm.plcm-error+xml
application/vnd.plcm.plcm-error+json
The ext-sbc already exists.
409 application/vnd.plcm.plcm-error+xml
application/vnd.plcm.plcm-error+json
RAS port is not valid
409 application/vnd.plcm.plcm-error+xml
application/vnd.plcm.plcm-error+json
IP address is required or not valid.
409 application/vnd.plcm.plcm-error+xml
application/vnd.plcm.plcm-error+json
SBC name is required.
409 application/vnd.plcm.plcm-error+xml
application/vnd.plcm.plcm-error+json
If authentication is enabled. Authentication name is required.
409 application/vnd.plcm.plcm-error+xml
application/vnd.plcm.plcm-error+json
If authentication is enabled. Password is required.

https://localhost:8443/api/rest/ext-sbc/debug-postliminary


Methods

POST


Test a postliminary script to a dial rule for an external SBC.
It lets you specify parameters of a call and the dial string and see what effect the script has on the dial string.

[tags: DMA]

Request

Representations

application/vnd.plcm.plcm-dial-rule-preliminary-debug-request+xml
application/vnd.plcm.plcm-dial-rule-preliminary-debug-request+json

Response

Status Representation Description
200 application/vnd.plcm.plcm-dial-rule-preliminary-debug-result+xml
application/vnd.plcm.plcm-dial-rule-preliminary-debug-result+json
The debug session was completed.
403 application/vnd.plcm.plcm-error+xml
application/vnd.plcm.plcm-error+json
Unable to get permission. Administrator user role required.

https://localhost:8443/api/rest/ext-sbc/{ext-sbc-id}


Template Parameters

Name Type Description
domain xs:string Domain arg doc
ext-sbc-id xs:string Ext-sbcname-id arg doc

Methods

DELETE


Deletes information about an external SBC.
[tags: DMA]

Request

Query Parameters

Name Type Description
type xs:string
Specifies an enumerated type that will indicate that the resource should be read by its
human-readable name or immutable, unique identifier such as a UUID, integer, etc.

The purpose of allowing the API client to specify an enumerated type ensures the option
to read this resource by its human-readable name. Unfortunately, the name can be modified
in the system and, as a result, will invalidate the resource URL. However, the API client
has the option of reading this resource by its immutable, unique identifier that can be
retrieved in the entity body.

Note 1: The URL form is https://{host}:{port}/api/rest/{resource}/{value}?type={name|id}
Note 2: If the "name" enumeration is specified, then the value should correspond to the name.
Otherwise, the resource cannot not be found.
Note 3: If the "id" enumeration is specified, the value should correspond to the unique
identifier. Otherwise, the resource cannot not be found.
Note 4: The read will default to the "id" type enumeration. As a result, the {value} parameter
can simply specify the unique identifier and the query parameter, "?type=id", is not required.

Response

Status Representation Description
204 Ext-sbc information successfully deleted
404 application/vnd.plcm.plcm-error+xml
application/vnd.plcm.plcm-error+json
No such ext-sbc.

GET


Retrieves information about an external SBC.
[tags: DMA]

Request

Query Parameters

Name Type Description
type xs:string
Specifies an enumerated type that will indicate that the resource should be read by its
human-readable name or immutable, unique identifier such as a UUID, integer, etc.

The purpose of allowing the API client to specify an enumerated type ensures the option
to read this resource by its human-readable name. Unfortunately, the name can be modified
in the system and, as a result, will invalidate the resource URL. However, the API client
has the option of reading this resource by its immutable, unique identifier that can be
retrieved in the entity body.

Note 1: The URL form is https://{host}:{port}/api/rest/{resource}/{value}?type={name|id}
Note 2: If the "name" enumeration is specified, then the value should correspond to the name.
Otherwise, the resource cannot not be found.
Note 3: If the "id" enumeration is specified, the value should correspond to the unique
identifier. Otherwise, the resource cannot not be found.
Note 4: The read will default to the "id" type enumeration. As a result, the {value} parameter
can simply specify the unique identifier and the query parameter, "?type=id", is not required.

Response

Status Representation Description
200 application/vnd.plcm.plcm-ext-sbc+xml
application/vnd.plcm.plcm-ext-sbc+json
Ext-sbc information successfully retrieved.
304
Ext-sbc information has not changed since the last retrieval.
Note: The API client must provide the "plcm-ext-sbc" 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,
identical single ext-sbc retrieval in the "If-None-Match" header, then
the HTTP response will contain the ext-sbc representation in the message
body.

The "plcm-ext-sbc" ETag can be accessed from the initial retrieval result's HTTP
response header. Also, subsequent retrievals require the identical domain and
ext-sbc name to ensure an equivalent ETag value. This also assumes no other client made changes to
ext-sbcs on the server.
404 application/vnd.plcm.plcm-error+xml
application/vnd.plcm.plcm-error+json
No such ext-sbc

PUT


Updates information about an external SBC.
[tags: DMA]

Request

Query Parameters

Name Type Description
type xs:string
Specifies an enumerated type that will indicate that the resource should be read by its
human-readable name or immutable, unique identifier such as a UUID, integer, etc.

The purpose of allowing the API client to specify an enumerated type ensures the option
to read this resource by its human-readable name. Unfortunately, the name can be modified
in the system and, as a result, will invalidate the resource URL. However, the API client
has the option of reading this resource by its immutable, unique identifier that can be
retrieved in the entity body.

Note 1: The URL form is https://{host}:{port}/api/rest/{resource}/{value}?type={name|id}
Note 2: If the "name" enumeration is specified, then the value should correspond to the name.
Otherwise, the resource cannot not be found.
Note 3: If the "id" enumeration is specified, the value should correspond to the unique
identifier. Otherwise, the resource cannot not be found.
Note 4: The read will default to the "id" type enumeration. As a result, the {value} parameter
can simply specify the unique identifier and the query parameter, "?type=id", is not required.

Representations

application/vnd.plcm.plcm-ext-sbc+xml
application/vnd.plcm.plcm-ext-sbc+json

Response

Status Representation Description
204
Ext-sbc information successfully updated.
Note: The response will only contain both an ETag value
and link to the updated ext-sbc resource.
400 text/plain
Bad request.
404 application/vnd.plcm.plcm-error+xml
application/vnd.plcm.plcm-error+json
No such ext-sbc.
403 application/vnd.plcm.plcm-error+xml
application/vnd.plcm.plcm-error+json
You do not have the appropriate ext-sbc role to make this configuration change.
412 application/vnd.plcm.plcm-error+xml
application/vnd.plcm.plcm-error+json

The ext-sbc resource has changed on the server.

Note: The response will contain the ETag value and link that reflects
the server's ext-sbc 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-ext-sbc.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-ext-sbc.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.