sip-feature
The sip-feature element defines how the Oracle Communications Session Border Controller’s B2BUA should treat specific option tags in SIP headers.
Parameters
- name
- Enter the option tag name that will appear in the Require, Supported, or Proxy-Require headers of SIP messages
- realm
- Enter the realm with which the feature is associated; to make the feature global, leave this parameter blank
- support-mode-inbound
- Select the treatment of feature (option tag) in a Supported header for an inbound packet
- Default: pass
- Values:
- pass—B2BUA should include the tag in the corresponding outgoing message
- strip—Tag should be excluded in the outgoing message. Use strip mode to not use the extension.
- required-mode-inbound
- Select the treatment of feature (option tag) in a Require header for an inbound packet
- Default: reject
- Values:
- pass—B2BUA should include the tag in the corresponding outgoing message
- reject—B2BUA should reject the request with a 420 (Bad Extension) response. The option tag will be included in an Unsupported header in the reject response.
- proxy-require-mode-inbound
- Select the treatment of feature (option tag) in a Proxy-Require header for an inbound packet
- Default: pass
- Values:
- pass—B2BUA should include the tag in the corresponding outgoing message
- reject—B2BUA should reject the request with a 420 (Bad Extension) response. The option tag will be included in an Unsupported header in the reject response.
- support-mode-outbound
- Select the treatment of feature (option tag) in a Supported header for an outbound packet
- Default: pass
- Values:
- pass—B2BUA should include the tag in the corresponding outgoing message
- strip—Tag should be excluded in the outgoing message
- require-mode-outbound
- Select the treatment of feature (option tag) in a Require header for an outbound packet
- Default: reject
- Values:
- pass—B2BUA should include the tag in the corresponding outgoing message
- reject—B2BUA should reject the request with a 420 (Bad Extension) response. The option tag will be included in an Unsupported header in the reject response.
- proxy-require-mode-outbound
- Select the treatment of feature (option tag) in a Proxy-Require header for an outbound packet
- Default: pass
- Values:
- pass—B2BUA should include the tag in the corresponding outgoing message
- reject—B2BUA should reject the request with a 420 (Bad Extension) response. The option tag will be included in an Unsupported header in the reject response.
Path
sip-feature is an element under the session-router path. The full path from the topmost ACLI prompt is:
Note:
If an option tag is encountered that is not configured as a SIP feature, the default treatments described in each of the field descriptions (name, support-mode, require-mode, and proxy-require-mode) included in this section will apply. Therefore, a sip-feature element only needs to be configured when non-default treatment is required. This is a multiple instance element.