sti-header-mapping-ruleset > mapping-rules
The mapping-rules is a multi-instance sub-element that resides within the sti-header-mapping-ruleset. This element allows you to set up the header mapping feature. You can apply a configured sti-header-mapping-ruleset to sti-server.
Parameters
- id
- Specifies a unique identifier for this mapping-rule.
- source-header
- Specifies the header within a SIP INVITE that uses Stir/Shaken architecture for validating the call.
- target-header
- Specifies the header you modify, based on this rule's source-header parameter, within an HTTP request that the system sends to the Stir/Shaken architecture.
- source-param
- When configured, the system uses this referenced source-param
to fetch the mapping details between the SIP header parameter and the HTTP
header parameters in the HTTP request/response to or from an STI
server.
Note:
If the source-header is null and the direction is inbound, the system identifies this value as a key from the key-value pair from the HTTP Body JSON claim. - target-param
- When configured, the system uses this referenced target-param to insert the mapping details between the SIP header parameter and the HTTP header parameters present in HTTP request/response to or from an STI server.
- direction
- Specifies the direction that this rule affects. Outbound causes
the system to modify headers traffic to the applicable sti-server. Inbound
affects headers from the sti-server.
- Default: outbound
- Values: outbound | inbound
- role
- Specifies the role, Stir/Shaken authentication or verification,
within which this rule applies.
- Default: STI-AS
- Values: STI-AS | STI-VS
Path
mapping-rules is an element under the sti-header-mapping-ruleset path. The full path from the topmost ACLI prompt is: configure terminal > session-router > sti-header-mapping-ruleset > mapping-rules.
Note:
This is a multiple instance configuration element.