Installation guide

SIP-FEATURE CONFIGURATION ELEMENTS N-Z
Version S-C6.1.0 Oracle Communications Session Border Controller ACLI Reference Guide 233
sip-feature
The sip-feature element defines how the Net-Net SBC’s B2BUA should treat
specific option tags in SIP headers.
Syntax sip-feature <name | realm | support-mode-inbound | required-mode-
inbound | proxy-require-mode-inbound | support-mode-outbound |
require-mode-outbound | proxy-require-mode-outbound | select | no
| show | done | exit>
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