Other Button
Use the Other button to access the following configuration elements.
Media profile | Adds one or more media profiles. |
Translations rules | Adds one or more translation rules. |
SIP features | Adds one or more SIP features. |
SIP manipulations | Specifies how to handle SIP headers and configuration rules. |
SPL | Adds one or more SPL plugins. |
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.
- 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.
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.
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.
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.
- 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 |
Default: None. |
||||||||||||||||||||||||
Comparison type |
Default: Case-sensitive. |
||||||||||||||||||||||||
Format |
|
||||||||||||||||||||||||
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.
|
||||||||||||||||||||||||
Media type (SDP descriptor for SDP media rule) |
|
||||||||||||||||||||||||
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 |
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.
The following table describes the pre-defined parameters.
The following table describes the Operators.
|
||||||||||||||||||||||||
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.
|
||||||||||||||||||||||||
Type (SDP descriptor for SDP line rule) |
|
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.
- 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.
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.
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.
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.
- 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.
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.