Retrieve one config element: SD.sti-header-mapping-ruleset

get

https://cloud-native-SBC-IP/config/v1/sd/sti-header-mapping-ruleset/{ElementKey}

Retrieve one config element: SD.sti-header-mapping-ruleset

Request

Path Parameters
Query Parameters
  • Integer value of saved revision, or 'latest', 'active' to show the running config, or 'staging' to show complete configuration to be activated

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

return one config element: StiHeaderMappingRuleset
Body ()
Root Schema : schema
Type: object
configure a set of rules for SIP and HTTP header mapping
Show Source
Nested Schema : mapping-rules
Type: array
list of rules required for SIP and HTTP header mapping
Show Source
Nested Schema : StiHeaderMappingRules
Type: object
list of SIP and HTTP header mapping rules
Show Source
  • Read Only: true
    Identifier for the element or sub-element
  • Allowed Values: [ "outbound", "inbound" ]
  • Minimum Length: 1
    Pattern: ^[A-Za-z0-9_][A-Za-z0-9._\-]{0,127}$
    unique identifier for the mapping rule
  • Allowed Values: [ "STI-AS", "STI-VS" ]
  • Pattern: ^$|^[A-Za-z0-9@.!%*_+`'~-]+(\[(([0-9]+)|([~^]))\])?$
    name of the SIP or HTTP header to be picked from the ingress INVITE or HTTP response
  • Pattern: ^$|^[A-Za-z0-9@.!%*_+`'~-]+(;.+)?$
    SIP or HTTP header param based on the source header. If source-header is empty, this should be a key in HTTP body JSON claim
  • Pattern: ^$|^[A-Za-z0-9@.!%*_+`'~-]+(\[(([0-9]+)|([~^]))\])?$
    name of the SIP or HTTP header to be added or modified to the egress INVITE or the HTTP request
  • Pattern: ^$|^[A-Za-z0-9@.!%*_+`'~-]+(;.+)?$
    SIP or HTTP header param based on target header. If target-header is empty, this should be a key in HTTP body JSON claim

404 Response

Not Found
Body ()
Root Schema : ApiValidationError
Type: object
Show Source
Nested Schema : errors
Type: array
Show Source
Nested Schema : Errors
Type: object
Show Source
Back to Top