1. ACLI Reference Guide
  2. ACLI Configuration Elements A-M
  3. allowed-elements-profile > rule-sets > header-rules

allowed-elements-profile > rule-sets > header-rules

This configuration subelement is used to configure SIP whitelists which controls the passage of unknown headers and parameters in request and response traffic.

Parameters

header-name
the name of the header in the whitelist that theOracle Communications Session Border Controller allows from incoming messages. It is case-insensitive and supports abbreviated forms of header names. For example, “Via”, “via”, or “v” all match against the same header. A header name of “request-uri” refers to the request URI of requests, while a header name of “*” applies to any header-type not matched by any other header-rule. The default value is “*”. This default value provides the ability to have header-rules for commonly known headers that remove unknown parameters, but leave unknown headers alone.
unmatched-action
the action for the Oracle Communications Session Border Controller to perform when an incoming header’s parameters do not match the relevant allowed parameters specified for this header-name. This parameter applies to non-matching header names only (not non-matching URI parameters).
  • Default: reject
  • Values:
    • reject—Rejects all incoming messages that have header parameters that do not match the parameters specified in this header-name.
    • delete — Deletes the non-matching elements from incoming messages with header parameters that do not match those specified in this header-name.
allow-header-param
The header parameter that the Oracle Communications Session Border Controller allows from the headers in incoming messages. You can enter up to 255 characters, including a comma (,), semi-colon (;), equal sign (=), question mark (?), at-symbol (@), backslash (\), or plus sign (+). The default value is “*”, which allows all header parameters to pass through. If you leave this field empty, no header parameters are allowed.
  • Deafult: *
allow-uri-param
the URI parameter that the Oracle Communications Session Border Controller allows from the headers in incoming messages. You can enter up to 255 characters, including a comma (,), semi-colon (;), equal sign (=), question mark (?), at-symbol (@), backslash (\), or plus sign (+). The default value is “*”, which allows all URI parameters to pass through. If you leave this field empty, no URI parameters are allowed.
  • Deafult: *
allow-uri-user-param
the URI user parameter that the Oracle Communications Session Border Controller allows from the headers in incoming messages. You can enter up to 255 characters, including a comma (,), semi-colon (;), equal sign (=), question mark (?), at-symbol (@), backslash (\), or plus sign (+). The default value is “*”, which allows all URI user parameters to pass through. If you leave this field empty, no URI user parameters are allowed.
  • Deafult: *
allow-uri-header-name
the URI header name that the Oracle Communications Session Border Controller allows from the headers in incoming messages. You can enter up to 255 characters, including a comma (,), semi-colon (;), equal sign (=), question mark (?), at-symbol (@), backslash (\), or plus sign (+). The default value is “*”, which allows all URI header name parameters to pass through. If you leave this field empty, no URI header name parameters are allowed.
  • Deafult: *

Path

header-rulesheader-rules is a subelement under rule-sets under the allowed-elements-profile element under the session router path. The full path from the topmost ACLI prompt is: configure terminal >terminal > session-router > allowed-elements-profile rule-sets header-rules