SIP Option Tag Handling Configuration

To configure SIP option tag handling:

In Superuser mode, type configure terminal and press Enter.
```
ORACLE# configure terminal
```
Type session-router and press Enter to access the system-level configuration elements.
```
ORACLE(configure)# session-router
```
Type sip-feature and press Enter. The system prompt changes to let you know that you can begin configuring individual parameters.
```
ORACLE(session-router)# sip-feature
ORACLE(sip-feature)#
```
From this point, you can configure SIP option tags parameters. To view all sip-feature parameters, enter a ? at the system prompt.
name—Enter a name for the option tag that will appear in the Require, Supported, or Proxy-Require headers of inbound and outbound SIP messages.

You must enter a unique value.

Note:
Valid option tags are registered with the IANA Protocol Number Assignment Services under Session Initiation Protocol Parameters. Because option tags are not registered until the SIP extension is published as a RFC, there might be implementations based on Internet-Drafts or proprietary implementations that use unregistered option tags.
realm—Enter the name of the realm with which this option tag will be associated. If you want to apply it globally across realms, leave this parameter blank.
support-mode-inbound—Optional. Indicate the support mode to define how the option tag is treated when encountered in an inbound SIP message’s Supported header. The default value is pass. Valid values are:
- pass—Indicates the B2BUA should include the tag in the corresponding outgoing message.
- strip—Indicates the tag should not be included in the outgoing message. Use strip if you do not want the extension used.
require-mode-inbound—Optional. Indicate the require mode to define how the option tag is treated when it is encountered in an inbound SIP message’s Require header. The default value is reject. The valid values are:
- pass—Indicates the B2BUA should include the tag in the corresponding outgoing message.
- reject—Indicates the B2BUA should reject the request with a 420 (Bad Extension) response. The option tag is included in an Unsupported header in the reject response.
require-mode-inbound—Optional. Indicate the require proxy mode to define how the option tag is treated when encountered in an incoming SIP message’s Proxy-Require header. The default is reject. The valid values are:
- pass—Indicates the B2BUA should include the tag in the corresponding outgoing message.
- reject—Indicates the B2BUA should reject the request with a 420 (Bad Extension) response. The option tag is included in an Unsupported header in the reject response.
support-mode-outbound—Optional. Indicate the support mode to define how the option tag is treated when encountered in an outbound SIP message’s Supported header. The default value is pass. Valid values are:
- pass—Indicates the B2BUA should include the tag.
- strip—Indicates the tag should not be included in the outgoing message. Use strip if you do not want the extension used.
require-mode-outbound—Optional. Indicate the require mode to define how the option tag is treated when it is encountered in an outbound SIP message’s Require header. The default value is reject. Valid values are:
- pass—Indicates the B2BUA should include the tag.
- reject—Indicates the B2BUA should reject the request with a 420 (Bad Extension) response. The option tag is included in an Unsupported header in the reject response.
require-mode-outbound—Optional. Indicate the require proxy mode to define how the option tag is treated when encountered in an outgoing SIP message’s Proxy-Require header. The default value is reject. The valid values are:
- pass—Indicates the B2BUA should include the tag.
- reject—Indicates the B2BUA should reject the request with a 420 (Bad Extension) response. The option tag is included in an Unsupported header in the reject response.
  
  The following example shows SIP option tag handling configured for non-default treatment of option tags.
```
sip-feature
        name                           newfeature
        realm                          peer-1
        support-mode-inbound           Strip
        require-mode-inbound           Reject
        proxy-require-mode-inbound     Pass
        support-mode-outbound          Pass
        require-mode-outbound          Reject
        proxy-require-mode-outbound    Reject
        last-modified-date             2004-12-08 03:55:05
```