Other Button

Use the Other button to access the following configuration elements.

Configure Media Profile

You can configure one or more media profiles for the Oracle® Enterprise Session Border Controller to use as a rules for sending and receiving media over the network.

In the following procedure, you can configure:
  • One media profile for a particular SIP SDP encoding, such as G729, by providing a unique name to identify the profile for the particular encoding type.
  • Multiple media profiles for the same SIP SDP encoding by adding a subname to the configuration. The system uses the subname plus the profile name as the unique identifier.
  1. From the Web GUI, click Other, Media profile.
  2. On the Media profile page, click Add, Show advanced, and to the following.
  3. Click OK.
  4. Save the configuration.

Configure Translation Rules

You can configure the Oracle® Enterprise Session Border Controller (E-SBC) to use number translation to change a layer 5 endpoint name according to prescribed rules. For example, to add or to remove a 1 or a + from a phone number sent from or addressed to a device. Use the translation-rules element to create unique sets of translation rules to apply to calling and called party numbers.

In the following procedure, you set the translation type, define the string to add or delete, and set the character position (index) where the add, delete, or replace occurs in the string. The index starts at 0, immediately before the leftmost character, and increases by 1 for every position to the right. Use the $ character to specify the last position in a string.

  1. From the Web GUI, click Other, Translation rules.
  2. On the Translation rules page, click Add, Show advanced.
  3. In the Add Translation rules dialog, do the following.
  4. Click OK.
  5. Save the configuration.

Configure SIP Features

Use the sip-feature dialog to define how the Oracle® Enterprise Session Border Controller (E-SBC) handles option tags in the SIP Supported header, Require header, and the Proxy-Require header.

You can specify whether a SIP feature is applied to a specific realm or globally across all realms. You can also specify the treatment for an option based upon whether is appears in an inbound or outbound packet. You need to configure option tag handling in the SIP feature element only when you want a treatment other than the default.

  1. From the Web GUI, click Configuration, Other, Sip Features.
  2. On the Sip feature page, click Add, and do the following:
  3. Click OK.
  4. Save the configuration.
Enter the tasks the user should do after finishing this task (optional).

SIP Manipulations

SIP header manipulation allows you to add, delete, or modify SIP message attributes on the Oracle® Enterprise Session Border Controller (E-SBC). For example, SIP headers and SIP header elements.

The most common reason for manipulating SIP headers and SIP header elements is to fix an incompatibility problem between two SIP endpoints. For example, Softswitch - PSTN incompatibility or a SIP messaging problem between two different IP PBX platforms in a multi-site deployment where calls between the platforms are unsuccessful due to problems in the SIP messaging.

To enable the SIP header manipulation, create rule sets in which you specify header manipulation rules and, optionally, header element manipulation rules. SIP header elements are the sub-parts of the header, such as the header value, the header parameter, the URI parameter, and so on, excluding the header name. You can specify the actions that you want the system to perform for each header element.

After creating the header manipulation rule set, apply it to a session agent or SIP interface as "inbound" or "outbound."

SIP Manipulations Configuration

Configuring SIP manipulations from the Web GUI is a multi-faceted process performed through a series of nested dialogs that differ depending on the particular header and header element that you want to manipulate. It is not practical to document the entire SIP manipulations configuration process in one procedure. The documentation begins with a global procedure that leads you to a separate procedure for each particular header and header element that you want to manipulate.

To begin, start with the "Configure SIP Manipulations" procedure. When you reach the "Cfg Rules" section in the procedure, click Add to see a list of the header rules that you can create. For further instructions, refer to the following topics for the header rule and corresponding header element rule that you want to create. Note that creating a header element rule within a header rule is optional.
  • Configure Header Rule
  • Configure MIME Rule
  • Configure MIME ISUP Rule
  • Configure MIME SDP Rule

When you finish configuring SIP manipulations, apply the rules to a session agent or SIP interface as "inbound" or "outbound."

SIP Manipulations Rules Attributes and Values Reference

Refer to the following table for information about the attributes that you can configure for SIP manipulation rules.

Attributes Values and Descriptions
Action
  • add—Adds a new header, if that header does not exist.
  • delete—Deletes the header, if it exists.
  • find-replace-all—Finds all matching headers and replaces with the header you specified for “Split” and "Join."
  • log—Logs the header.
  • manipulate—Manipulates the elements of this header to the element rules configured.
  • monitor—Monitors the header.
  • store—Stores the header.
  • none—(default) No action is taken.
  • reject—Rejects the header.
  • sip-manip—Manipulates the SIP elements of this header to the element rules configured.

Default: None.

Comparison type
  • boolean—Header is compared to header rule and must match exactly or it is rejected.
  • case-insensitive—Header is compared to header rule regardless of the case of the header.
  • case-sensitive—(default) Header is compared to the header rule and case must be exactly the same or it is rejected.
  • pattern-rule—Header is compared to the header rule and the pattern must be exactly the same or it is rejected.
  • refer-case-insensitive—Header is compared to the header rule regardless of the case in a REFER message.
  • refer-case-sensitive—Header is compared to the header rule and the case must be exactly the same as in the REFER message or it is rejected.

Default: Case-sensitive.

Format
  • ascii-string - A character-encoding scheme that represents text (128 ASCII codes, 7 bits).
  • binary-ascii - An encoding scheme where each byte of an ASCII character is used. Can use up to 256 bit patterns .
  • hex-ascii - An encoding scheme that uses a string of numbers (no spaces) to represent each ASCII character.
Header name The name of the header to which the rule applies. Case-sensitive.
Match value The value that you want to match against the element value for an action to be performed.
Match val type The type of value to match to the match-field entry for the action to be performed.
  • any—(default) Element value in the SIP message is compared with the match-value field entry. If the match-value field is empty, all values are considered a match.
  • fqdn—Element value in the SIP message must be a valid FQDN to be compared to the match-value field entry. If the match-value field is empty, any valid FQDN is considered a match. If the element value is not a valid FQDN, it is not considered a match.
  • ip—Element value in the SIP message must be a valid IP address to be compared to the match-value field entry. If the match-value field is empty, any valid IP address is considered a match. If the element value is not a valid IP address, it is not considered a match.
Media type (SDP descriptor for SDP media rule)
  • m—Media name and transport address
  • i—Media title
  • c—Connection information (optional when configured at the session level)
  • b—Zero or more bandwidth information lines
  • k—Encryption key
  • a—Zero or more media attribute lines
  • t—The session time is active
  • r—Zero or more repeat times
Methods SIP method names to which you want to apply the header rule. For example, INVITE, ACK, BYE. When this field is empty, the system applies the MIME rule to all methods. Default: Blank.
Mime header The parameter name to which the rule applies. The parameter name depends on the element name you entered. For uri-param, uri-user-param, and header-param it is the parameter name to be added, replaced, or deleted. For all other types, it serves to identify the element rule and any name can be used. Alpha-numeric characters. Default: blank.
Msg type
  • any—(default) Requests, replies, and out-of-dialog messages
  • out-of-dialog—Out of dialog messages only.
  • reply—Reply messages only
  • request—Request messages only

Default: Any.

Name The name you want to use for the rule. Default: Blank.
New value The value for a new element or replacement value for an existing element. You can enter an expression that includes a combination of absolute values, pre-defined parameters, and operators.
  • Absolute values—Use double quotes for clarity. You must escape all double quotes and back slashes that are part of an absolute value, and enclose the absolute value in double quotes.
  • Pre-defined values.—Pre-defined parameters always start with a $. For valid values, see the Pre-defined Parameters table.
  • Operators parameters—For valid values, see the Operators table.
The following table describes the pre-defined parameters.
Pre-defined Parameter Description
$ORIGINAL Original value of the element is used.
$LOCAL_IP IP address of the SIP interface on which the message was received for inbound manipulation; or sent on for outbound manipulation.
$REMOTE_IP IP address the message was received from for inbound manipulation; or being sent to for outbound manipulation.
$REMOTE_VIA_HOST Host from the top Via header of the message is used.
$TRUNK_GROUP Trunk group is used.
$TRUNK_GROUP_CONTEXT Trunk group context is used.
The following table describes the Operators.
Operator Description
+ Append the value to the end. For example:

acme”+”packet

generates acmepacket

+^ Prepends the value. For example:

acme”+^”packet

generates packetacme

- Subtract at the end. For example:

112311”-”11

generates 1123

-^ Subtract at the beginning. For example:

112311”-^”11

generates 2311

Parameter name The parameter name to which the rule applies. The parameter name depends on the element name you entered. For uri-param, uri-user-param, and header-param it is the parameter name to be added, replaced, or deleted. For all other types, it serves to identify the element rule and any name can be used. Alpha-numeric characters. Default: Blank.
Type The type of element on which to perform the action. Default: Blank.
  • header-param—Perform the action on the parameter portion of the header.
  • header-param-name—Perform the action on the header parameter name.
  • header-value—Perform the action on the header value.
  • mime—Perform the action on Multipurpose Internet Mail Extensions (MIME).
  • reason-phrase—Perform the action on reason phrases.
  • status-code—Perform the action on status codes.
  • teluri-param—Perform the action on a SIP telephone Uniform Resource Identifier (URI).
  • uri-display—Perform the action on the display of the SIP URI.
  • uri-header—Perform the action on a header included in a request constructed from the URI.
  • uri-header-name—Perform the action on a SIP URI header name.
  • uri-host—Perform the action on a Host portion of the SIP URI.
  • uri-param—Perform the action on the parameter included in the SIP URI.
  • uri-param-name—Perform the action on the name parameter of the SIP URI.
  • uri-phone-number-only—Perform the action on a SIP URI phone number only.
  • uri-port—Perform the action on the port number portion of the SIP URI.
  • uri-user—Perform the action on the user portion of the SIP URI.
  • uri-user-only—Perform the action on the user portion only of the SIP URI.
  • uri-user-param—Perform the action on the user parameter of the SIP URI.
Type (SDP descriptor for SDP line rule)
  • v—Protocol version
  • o—Originator and session identifier
  • s—Session name
  • i—Session information
  • u—URI of description
  • e—Email address
  • p—Phone number
  • c—Connection information (not required when included in all media)
  • b—Zero or more bandwidth information lines or one or more time descriptions("t=" and "r=" lines)
  • z—Time zone adjustments
  • k—Encryption key
  • a—Zero or more session attribute lines or zero or more media descriptions
  • t—Time the session is active
  • r—Zero or more repeat times

Configure SIP Manipulations

When you need to modify specific components of a SIP message, configure a SIP manipulation rule. For example, you might need to resolve protocol differences between vendors. You can configure rules for SIP headers and for the sub-elements within the headers.

To begin, configure the Name, Description, (Optional) Split Headers, and (Optional) Join Headers attributes. When you reach the "Cfg Rules" section, click Add and select the header rule that you want to create. For further instructions, refer to the topics noted in the Cfg rules "Instructions" cell in the following table.

  1. From the Web GUI, click Configuration, Other, Sip manipulations.
  2. In the SIP manipulation dialog, click Add, and do the following.
  3. When you finish configuring SIP manipulations, and the system returns you to the SIP manipulation page, click Close.
  4. Save the configuration.
  • Apply the rules to a session agent or SIP interface as "inbound" or "outbound."

Configure Header Rule

You can configure SIP header manipulations on the Oracle® Enterprise Session Border Controller (E-SBC) from the "CfgRules" section in the "Configuring SIP Manipulations" procedure.

  • Perform the Configure SIP Manipulations procedure.

The following procedure is the continuation of the "Configure SIP Manipulations" procedure. It begins with adding header-rule to "CfgRules" and includes the optional element-rule sub-element configuration.

  1. From the "CfgRules" section of the SIP manipulation configuration page, click Add, and select header-rule from the list.
  2. In the SIP manipulation / Header rule dialog, do the following.
  3. Click OK.
    The system displays the Add SIP manipulation page.
  4. Click OK.
    The system displays the SIP manipulation page.
  5. Click Close.
  6. Save the configuration.

Configure MIME Rule

You can configure a Multi-Purpose Internet Mail Extensions (MIME) data files exchange profile on the Oracle® Enterprise Session Border Controller (E-SBC) from the "CfgRules" section in the "Configuring SIP Manipulations" procedure.

  • Configure SIP Manipulations.

The following procedure is the continuation of the "Configure SIP Manipulations" procedure. It begins with adding mime-rule to "CfgRules" and includes the optional mime-rule sub-element configuration.

  1. From the "CfgRule"s section of the SIP manipulation configuration page, click Add, and select mime-rule from the list.
  2. In the SIP manipulation / Mime rule dialog, click Show advanced, and do the following.
  3. Click OK.
    The system displays the Add SIP manipulation page.
  4. Click OK.
    The system displays the SIP manipulation page.
  5. Click Close.
  6. Save the configuration.

Configure MIME ISUP Rule

You can configure a Multi-Purpose Internet Mail Extensions (MIME) - ISDN User Part (ISUP) signaling profile on the Oracle® Enterprise Session Border Controller (E-SBC) from the "CfgRules" section in the "Configuring SIP Manipulations" procedure.

  • Perform the "Configure SIP Manipulations" procedure.

The following procedure is the continuation of the "Configure SIP Manipulations" procedure. It begins with adding mime-isup-rule to "CfgRules" and includes the optional mime-header-rule and isup-param-rule sub-element configurations.

  1. From the "CfgRules" section of the SIP manipulation configuration page, click Add, and select mime-isup-rule from the list.
  2. In the SIP manipulation / Mime isup rule dialog, click Show advanced, and do the following.
  3. Click OK.
    The system displays the Add SIP manipulation page.
  4. Click OK.
    The system displays the SIP manipulation page.
  5. Click Close.
  6. Save the configuration.

Configure MIME SDP Rule

You can configure a Multi-Purpose Internet Mail Extensions (MIME) - Session Description Protocol (SDP) multimedia communications session profile on the Oracle® Enterprise Session Border Controller (E-SBC) from the "CfgRules" section in the "Configuring SIP Manipulations" procedure.

  • Perform the "Configure SIP Manipulations" procedure.

The following procedure is the continuation of the "Configuring SIP Manipulations" procedure. It begins with adding the mime-sdp-rule to "CfgRules" and includes the optional mime-header-rule, sdp-session-rule, sdp-media-rule, and sdp-line-rule sub-element configurations.

In step 2 of this procedure, you can configure as few or as many of the "CfgRules" sub-element options that you want.
  • If you do not configure an optional sub-element, proceed to step 3.
  • If you configure an optional sub-element, you can configure another one or proceed to step 3.
  1. From the "CfgRules" section of the SIP manipulation configuration page, click Add, and select mime-sdp-rule from the list.
  2. In the SIP manipulation / Mime sdp rule dialog, do the following.
  3. Click OK.
    The system displays the Add SIP manipulation page.
  4. Click OK.
    The system displays the SIP manipulation page.
  5. Click Close.
  6. Save the configuration.

Add an SPL

Add an SPL plug-in, which is a customized script, to quickly implement a feature on the Oracle® Enterprise Session Border Controller (E-SBC). The SPL plug-in augments running the software image on the E-SBC, and provides new features when you need them without having to upgrade the software.

  • Confirm the name and location of the SPL plug-in that you want to add.

Use the following procedure to integrate an Oracle-signed plug-in with the E-SBC operating system. Note that the E-SBC) does not load an unsigned SPL or one with invalid signatures.

  1. From the Web GUI, click Other, SPL.
  2. In the Spl config dialog, do the following:
  3. Click OK.
  4. Save the configuration.