Session Router Configuration

You can configure the following session-router objects from the Configuration tab on the Web GUI:

access-control	Configure a static or dynamic access control list.
account-config	Configure and enable Quality of Service (QoS) accounting.
allowed-elements-profile	Configure an allowed elements profile.
call-recording-server	Configure a call recording server.
class-policy	Configure a classification profile policy.
diameter-manipulation	Configure diameter manipulation rules.
enforcement-profile	Configure an enforcement profile.
enum-config	Configure an ENUM server.
filter-config	Configure a custom filter for SIP monitor and trace.
h323-config	Configure and enable an H.323 protocol.
h323-stack	Configure an H.323 stack.
home-subscriber-server	Configure a home subscriber server.
http-alg	Configure an HTTP proxy.
iwf-config	Configure and enable Inter-Working Function (IWF).
ldap-config	Configure and enable an LDAP server.
local-policy	Configure a session request routing policy.
local-response-map	Configure a local SIP response map.
local-routing-config	Configure the parameters for the local routing table.
media-profile	Configure a media profile and apply it to a media type.
net-management-control	Configure and enable network management controls.
qos-constraints	Configure Quality of Service (QoS) constraints.
response-map	Configure a SIP response map.
service-health	Configure a service tag list.
session-agent	Configure and enable a session agent.
session-constraints	Configure and enable session constraints.
session-group	Configure a session agent group.
session-recording-group	Configure a session recording server group.
session-recording-server	Configure and enable a session recording server.
session-timer-profile	Configure a session timer profile.
session-translation	Configure the translation rules for calling and called numbers.
sip-advanced-logging	Configure logging of specific SIP requests by criteria.
sip-config	Configure and enable signaling and session management.
sip-feature	Configure SIP option tag parameters.
sip-interface	Configure and enable a SIP interface.
sip-manipulation	Configure SIP manipulation.
sip-monitoring	Configure and enable SIP monitor and trace features.
surrogate-agent	Configure a surrogate agent.
survivability	Configure and enable survivability.
translation-rules	Configure and apply session translation rules to an agent and a realm.

Note:

Click Show Advanced in the navigation pane to display all of the Session Router objects in the preceding list.

Configure Access Control

Use the access-control configuration element to manually create an Access Control List (ACL) for the host path in the Oracle® Enterprise Session Border Controller.

1. From the Web GUI, click Configuration, session-router, access-control.
2. In the Add Access Control dialog, click Show advanced, and do the following:

   Realm ID	Enter the ingress realm of traffic destined to the host to apply this ACL.
   Description	Type a brief description of this access-control configuration element.
   Source address	Enter the source address, net mask, port number, and port mask to specify traffic matching for this ACL.
   Destination address	Enter the destination address, net mask, port number, and port mask to specify traffic matching for this ACL in the following format: (ip-address)[/(num-bits)][:(port)][/(port-bits). Not specifying a port mask implies an exact source port. Not specifying an address mask implies an exact IP address.
   Application protocol	Select the application-layer protocol configured for this ACL entry from the drop down list.
   Transport protocol	Select the transport-layer protocol configured for this ACL entry from the drop down list.
   Access	Select the access control type from the drop down list.
   Average rate limit	Enter the average data in bytes per second. Range is 0-4294967295.
   Trust level	Select the trust level for the host from the drop down list.
   Minimum reserved bandwidth	Enter the minimum reserved bandwidth in bytes per second. Range is 0-4294967295.
   Invalid signal threshold	Enter the acceptable invalid signaling message rate allowed within the tolerance window. Range is 0-4294967295.
   Maximum signal threshold	Enter the maximum number of signaling messages allowed within the tolerance window. Range is 0-4294967295.
   Untrusted signal threshold	Enter the maximum number of untrusted signaling messages allowed within the tolerance window. Range is 0-4294967295.
   Deny period	Enter the number for the blocked period for dynamic denied entries. Range is 0-4294967295.
   NAT trust threshold	Enter the number of endpoints behind NAT to deny. Range is 0-65535.
   Max endpoints per NAT	Enter the maximum number of endpoints behind a NAT device. Range is 0-65535.
   NAT invalid message threshold	Enter the acceptable number of invalid messages from behind a NAT device. Range is 0-65535.
   CAC failure threshold	Enter the maximum number of admission failures allowed within the tolerance window. Range is 0-4294967295.
   Untrust CAC failure threshold	Enter the maximum number of untrusted admission failures allowed within the tolerance window. Range is 0-4294967295.

3. Click OK.
4. Save the configuration.

Dynamic ACL for the HTTP-ALG

The dynamic Access Control List (ACL) option for HTTP-Application Layer Gateway (ALG) provides Distributed Denial of Service (DDoS) attack protection for the HTTP port.

When you enable the dynamic ACL option, the system sets the trust level for static flow for the public listening socket defined in http-alg, public to untrusted. Each listening socket creates and manages its ACL list, which allows the listening socket to keep track of the number of received and invalid messages, the number of connections per endpoint, and so on. You can configure a different setting for each http-alg object.

Dynamic ACL for each endpoint is triggered by Session Initialization Protocol (SIP) registration messages. Upon receiving a SIP registration message, the SIP agent creates a dynamic ACL entry for the endpoint. If the 200 OK response is received, the ACL is promoted, allowing the HTTP message to go through the security domain. If SIP registration is unsuccessful, the ACL entry is removed and HTTP ingress messages are blocked from the endpoint. The ACL entry is removed upon incomplete registration renewal or telephone disconnect.

The following example describes the criteria and associated configuration item that result in a denied or allowed connection for both low and medium control levels.

Criteria	Associated Configuration Item	Action
Exceed total number of connections for allowed	http-alg, max-incoming-conns	Connection denied
Exceed total connections per peer	http-alg, per-src-ip-mas-incoming-conns	Connection denied
ACL not promoted	Dynamically set on SIP registration	Connection denied
Exceed maximum number of packets/sec	realm-config, maximum-signal-threshold	Connection denied and peer is promoted
Exceed maximum number of error packets	Realm-config, invalid-signal-threshold	Connection denied and peer is promoted

Oracle recommends setting realm-config, access-control-level to medium.

If a peer is promoted to trusted, the system performs DDoS checks on max number of packets/sec and max number of error packets allowed.

Demotions depend on the ream-config, access-control-trust-level setting for the realm. For more information on realm-config settings, see the ACLI Configuration Guide.

If you want to configure different ACL settings for SIP traffic and for HTTP-ALG traffic, you must configure a realm for each type of traffic.

Enable Dynamic ACL for the HTTP ALG

The Dynamic Access Control List (ACL) for HTTP Application Layer Gateway (ALG) option, which provides Distributed Denial of Service (DDoS) attack protection for the HTTP port, is an option that you must enable.

• Confirm that the session manager is mapped to the Oracle® Enterprise Session Border Controller.

Two ACL entires are required for each registered telephone, where one entry is used for SIP traffic and one is used for HTTP-ALG traffic.

Note:

Enabling dynamic access control for HTTP-ALG traffic reduces the number of available dynamic ACL entries on the session border controller, which may reduce the number of concurrent trusted endpoints that the system can support.

1. From the Web GUI, on the Configuration tab, click Configuration, session-router, http-alg.
2. Click Add.
   The system displays the Add http-alg page.
3. On the Add http-alg page, click Show advanced.
4. In the Add http-alg dialog, do the following:

   Name	Enter a name for this ACL.
   State	Select State to enable this ACL.
   Description	Enter a description of this ACL.
   Realm id	Select the private realm to which to apply this ACL from the drop down list.
   Address	Enter the IP address of the selected private realm.
   Destination address	Enter the destination IP address.
   Destination port	Enter the destination port. Range:1-65535. Default: 80.
   TLS profile	Enter TLS profile to apply from the drop-down list.
   Realm id	Select the public realm identifier from the drop down list.
   Address	Enter the IP address of the selected public realm.
   Port	Enter the listening port number. Range:1-65535. Default: 80.
   TLS profile	Select a TLS profile to apply from the drop-down list.
   Session-manager-mapping	Not applicable to this procedure.
   Dynamic ACL	Select to enable dynamic ACL creation on SIP messages.
   Max incoming conns	Enter a number for the maximum allowed incoming HTTP connections. Range: 0-4294967295.
   Per src IP max incoming conns	Enter a number for the maximum allowed incoming connections per registered IP address. Range: 0-4294967295.

5. Click OK.
6. Save the configuration.

Dynamic Access Control List (ACL) Settings for the HTTP Application Layer Gateway (ALG)

You can set the following parameters for the realm specified in http-alg, public, realm-id.

• access-control-trust-level
• invalid-signal-threshold
• maximum-signal-threshold
• untrusted-signal-threshold
• deny-period

For more information on realm-config settings, see the ACLI Configuration Guide.

Accounting Configuration

The Oracle® Enterprise Session Border Controller (E-SBC) supports RADIUS, an accounting, authentication, and authorization (AAA) system. RADIUS servers are responsible for receiving user connection requests, authenticating users, and returning all configuration information necessary for the client to deliver service to the user.

You can configure the E-SBC to send call accounting information to one or more RADIUS servers. This information can help you to see usage and Quality of Service (QoS) metrics, monitor traffic, and even troubleshoot your system.

For information about how to configure the E-SBC for RADIUS accounting, refer to the Oracle Communications Session Border Controller Accounting Guide. The Accounting Guide contains all RADIUS information, as well as information about:

• Accounting for SIP and H.323
• Local CDR storage on the E-SBC, including CSV file format settings
• Ability to send CDRs via FTP to a RADIUS sever (the FTP push feature)
• Per-realm accounting control
• Configurable intermediate period
• RADIUS CDR redundancy
• RADIUS CDR content control

Configure Call Accounting

Use the account-config element to set the destination parameters for accounting messages.

1. From the Web GUI, click Configuration, account-config, Show Advanced.
2. On the Add account-config dialog, do the following:

   Strategy	Select the lookup algorithm for the accounting server.
   Protocol	Select RADIUS or Diameter.
   State	Select to enable call accounting.
   File output	Select to enable active writing comma delimited records.
   File rotate time	Enter a number from 0-2147483647.
   Options	Add optional parameters.
   FTP push	Select to push files to an FTP server.
   Push receiver	Add push file receiver.
   Account-servers	Add accounting servers.

3. Save the configuration.

Configure RADIUS Call Accounting

You can configure the Oracle Enterprise Session Border Controller to send call accounting information to one or more RADIUS servers. This information can help you to see usage and Quality of Service (QoS) metrics, to monitor traffic, and to troubleshoot the system.

To set the RADIUS call accounting parameters, use the account-config element to specify where and when you want the system to send accounting messages, and the strategy for selecting account servers. Use the following procedure to configure the minimum settings required for RADIUS call accounting.

1. From the Web GUI, click Configuration, session-router, account-config.
2. In the Add Account Config dialog do the following:

   Strategy	Select the strategy from the drop down list to use for selecting the server to which the E-SBC sends accounting messages.
   Protocol	Select RADIUS from the drop down list.
   State	Select to enable the call accounting configuration.
   File output	Select to enable the system to store the .csv file locally.
   File rotate time	Enter the number of minutes from 1-2147483647.
   Options	(Optional) Click Add to add options.
   FTP push	(Optional) Select to enable.
   Push receiver	(Optional) Click Add to add a push receiver to the list.
   Account servers	Click Add to add a RADIUS server to the list.

3. Click OK.
4. Save the configuration.

Configure H.323 Global Settings

Configuring H.323 signaling for theOracle® Enterprise Session Border Controller (E-SBC) requires setting global parameters and parameters for each interface. The global parameters govern how the E-SBC performs general H.323 operations. The E-SBC applies the global settings to all interfaces that you configure to use H.323. For example, you can turn H.323 support on and off for the entire E-SBC, using the global settings. Use the following procedure to configure the global H.323 parameters.

• Configure the basic parameters for physical interfaces, network interfaces, global system parameters, SNMP, trap receiver, accounting support, and any holiday information that you need.
• Decide how you want to configure realms and routing, including the use of session agents and session agent groups, to support H.323 operations.
• Determine the settings that you want to use for the attributes in this procedure.
• Know the names of any Options that you want to add. See "H.323 Signalling Services" in theACLI Configuration Guide for descriptions.

1. Access the h.323-config object.
   Configuration, session-router, session-router, h32, h323-config.
2. On the Add h3232 config page, do the following:

   State	Select to enable the configuration.
   Log level	Select a log level for H.323 stacks from the drop-down list. Default: Notice.
   Response tmo	Set the maximum waiting time for response to a SETUP message in seconds. Default: 4. Range: 1-2147483647
   Connect tmo	Set the maximum waiting time for establishment of a call in seconds. Default: 32. Range: 1-2147483647
   Rfc2833 payload	Enter the payload type used by the H.322 stack in preferred rfc 2833-mode. Default: 101. Range: 96-127
   Alternate routing	Select an alternate route means from the drop-down list. Default: proxy.
   Codec feedback	Select to enable slow-start to fast-start codec negotiation. Default: Disabled.
   Enum sag match	Select to enable matching Session Agent Group names with the hostname from an ENUM query or Local Route Table next-hop entry. Default: Disabled.
   Remove t38	Select to enable removing T.38 fax capabilities in the TCS for IWF calls. Default: Disabled (means T.38 is functional)
   Options	Set any options for H.323 features that you want to use. Click Add, and enter an option. For example, directDial for H.323 destination-based routing. Do one of the following: Click OK to complete the task. Click Apply/Add another, for as many options as needed, and click OK when done.

3. Save the configuration.

Session Manager Mapping

The Oracle® Enterprise Session Border Controller (E-SBC) supports mapping between multiple session managers and multiple SBCs. Such mapping allows the SBC to work in a redundant network configuration where you can map:

• The primary session manager to the primary SBC IP address
• One or more redundant session managers to one or more redundant SBCs

To map a redundant session manager to a redundant SBC, map the private IP address of the redundant session manager to the public SIP IP address configured in HTTP-ALG, Public on the SBC. For instructions, see "Map a Session Manager to a Session Border Controller."

Map a Session Manager to a Session Border Controller

You can map one or more session managers to an Oracle® Enterprise Session Border Controller (E-SBC) to provide redundancy and load balancing.

• Note the private IP address of the session manager and the public SIP interface IP address of the session border controller that you want to map.

Map the private IP address of the session manager to the public SIP interface IP address of the E-SBC.

1. From the Web GUI, go to Configuration, session-router, http-alg.
2. On the http-alg page, click Show advanced, Add.
3. In the Add http-alg dialog, enter the information in the fields and make the selections for the deployment.
4. Click OK.
   The system lists the new map on the http-alg page.
5. Save the configuration.

Configure IWF

You must enable and configure the Oracle® Enterprise Session Border Controller to perform Inter-Working Function (IWF) operations.

• A complete SIP configuration, including SIP interfaces, SIP ports, SIP NAT if needed, and SIP features
• A complete H.323 configuration, including H.323 global and H.323 interface configurations
• Local policy and local policy attributes
• Media profiles
• Session agents and, if needed, session groups

In the following procedure, the system provides dialogs where you can either select existing media profiles and options or add new ones.

1. From the Web GUI, click Configuration, Show advanced, session-router, iwf-config.
2. On the Add iwf config page, click Show Advanced, and do the following:

   State	Select to enable IWF.
   Media profiles	Select the media profiles that you want to use for IWF translations.
   Logging	Select to enable logging SIP messages related to the IWF.
   Add reason hdr	Select to enable SIP-H323 Add Reason header for SIP.
   Slow start no sdp in invite	Select to enable no offer SDP in INVITE for slow start H.323.
   Options	Click Add, and enter an optional feature or parameter. Do one of the following: Click OK. Click Apply/Add another, add another feature or parameter, and click OK. Repeat, as needed.
   Forward source call address	Select to enable adding the h225SourceCallSignalAddress IP for IWF to outgoing SIP INVITEs.

3. Click OK.
4. Save the configuration.

Configure LDAP

The Oracle® Enterprise Session Border Controller (E-SBC) uses Lightweight Directory Access Protocol (LDAP) for interaction between an LDAP client and an LDAP server. Use the ldap-config object in Expert mode to create and enable an LDAP configuration on the E-SBC.

• Confirm that one or more authentication modes exist.
• Confirm that one or more Transport Layer Security (TLS) profiles exist.

In the following procedure, you configure the LDAP server, filters, security, and local policy. Note that you can use multiple ldap-config configurations that reference the same LDAP server within different local-policy policy-attributes to allow for multiple LDAP queries to the same LDAP server.

1. From the Web GUI, click Configuration, session-router, ldap-config.
2. On the LDAP config page, click Add.
3. On the Add LDAP config page, click Show advanced, and do the following:

   Name	Enter a unique name to identify this configuration. Valid values are alpha-numeric characters.
   State	Select State to enable this configuration. When not selected, the E-SBC does not attempt to establish a connection with any corresponding LDAP server.
   LDAP servers	Add one or more LDAP servers to the list that you want to include in this configuration. The IP address is required. Enter the default IP Address in dotted decimal format, for example, 0.0.0.0. When adding more than one server, separate each server address with a space and enclose the list within parentheses. The port number is optional. The E-SBC uses port 389 for LDAP over TCP and port 636 for LDAP over TLS.
   Realm	Select the realm for this configuration.
   Authentication mode	Select the authentication mode for the LDAP bind request. The default is Simple, where no specific password encryption is performed when the sending the bind request. To maintain security, configure LDAP sec type on this page.
   Username	Enter the username that the LDAP bind request uses for authentication before the LDAP server grants access.
   Password	Click Set, enter and confirm the password to pair with the Username that the LDAP bind request uses for authentication before the LDAP server grants access. Click OK.
   LDAP search base	Enter the base Directory Number for LDAP search requests.
   Timeout limit	Enter a timeout limit in seconds. The range is from 1-300.
   Max request timeouts	Enter the maximum number of timeouts allowed. The range is from 0-10.
   TCP keepalive	Select TCP keepalive to enable Transmission Control Protocol (TCP) keepalive signalling.
   LDAP sec type	Select None or LDAPS for the type of LDAP security from the drop down list.
   LDAP TLS profile	Select a TLS profile for this LDAP configuration.
   LDAP transactions	Click Add to add allowed LDAP transaction types to the list. The system displays the Add LDAP config / LDAP Transactions configuration page, where you select the application transaction layer type, the route mode, the operation type for configuring multiple attributes, and add LDAP configuration attributes.

4. Click OK.
5. Save the configuration.

Configure Local Policy

Configure local policy and local policy attributes for session routing based on the next hop parameter. The local policy specifies the protocol the

Use the local-policy element to configure where signalling messages are routed and forwarded.

For the Policy priority parameter, the priority hierarchy from lowest to highest is none, normal, non-urgent, urgent, emergency. None means no priority. Each higher priority handles sessions at its level plus the sessions in the priorities above it. For example, non-urgent also handles sessions for urgent and emergency.

1. From the Web GUI, click Configuration, session-router, local-policy.
2. On the Add local-policy page, click Show advanced, and do the following:

   From address	Click Add, and enter the source IP address, the POTS number, the E.164 number, or the hostname for the local-policy element. This list requires at least one address. You can add as many addresses as necessary. You can use a wildcard or a DS:prefix (dialed string) for this parameter.
   To address	Click Add, and enter the destination IP address, the POTS number, the E.164 number, or the hostname for the local-policy element. This list requires at least one address. You can add as many addresses as necessary. You can use a wildcard for this parameter.
   Source realm	Click Add, and enter one or more valid realms for identifying coming into a realm. The default is *.
   Description	Enter a description of this local-policy.
   State	Select to enable this policy.
   Policy priority	Select the policy priority for this local policy from the drop-down list. The default is none.
   Policy attributes	Click Add Show advanced, and do the following: Next hop. Select the signaling host IP address, SAG, hostname, or ENUM config from the drop-down list. Realm. Select the realm for the next hop from the drop-down list. Not required when the realm is the same as the realm configured for the Session Agent that is the next hop. Action. Select an action for the next hop from the drop-down list. Terminate recursion. Select to terminate route recursion with the next hop. Deselect to include next hops after this one. Cost. Enter the cost configured for local policy to rank policy attributes, representing the cost of a route relative to other routes reaching the same destination address. Enter a number from 0-9999999. State. Select to enable. App protocol. Select the application protocol for signalling the session agent from the drop-down list. Lookup. Select an additional local policy lookup from the drop-down list. Next key. Enter the next stage key for multi-stage local policy lookups.

3. Click OK.
4. Save the configuration.

Add a Local Response Map

Configuring cause and reason mapping for SIP to SIP calls requires a local response map. The entries in the map generate the SIP response and Q850 cause code value for particular error scenarios.

• If you plan to add a Reason header, enable the function in the global SIP configuration.

You can customize the SIP status SIP reason for a local error. For example, the default 503 message for the error that the Oracle® Enterprise Session Border Controller (E-SBC) sends when the licensed session capacity is reached is "503 licensed session capacity reached". You can customize the number for this error message in the SIP Status field, and you can customize the reason in the SIP Reason field. Select licensed-session-capacity-reached from the Local Error list and you can add custom text about the error to the SIP header.

.

Repeat the following procedure to create as many local response map entries as you need.

1. Access the local-response-map entries object.
   Configuration, session-router, how advanced, local-response-map, Add.
2. In the Local response map entries configuration, do the following.

   Local error	Select a local error condition from the drop-down list to trigger this map.
   SIP status	Enter a SIP response code. Range: 100-699.
   Q850 cause	Enter a Q850 cause code. Range: 0-2147483647.
   SIP reason	Enter a SIP response comment in quotation marks.
   Q850 reason	Enter a Q850 cause comment in quotation marks.
   Method	Select a SIP failure response message from the drop-down list to map to a 200 OK. To deactivate this function, make no selection.
   Register response expires	Enter the number of seconds after which the REGISTER response expires. Range: 0-999999999.

3. Click OK.
4. Save the configuration.

Configure Local Routing

Use the local-routing-config element to specify route tables that the Oracle® Enterprise Session Border Controller (E-SBC) uses to direct calls to the next hop and to map an E.164 telephone number to a SIP URI, locally.

1. From the Web GUI, click Configuration, session-router, local-routing-config.
2. On the local routing config page, click Add.
3. On the Add local routing config page, do the following:

   Name	Enter a unique name to use to refer to this local route table when you configure policy attributes. Required.
   File name	Enter the name for the file from which the database corresponding to this local route table is created. Use the .gz format, and place the file in the /code/lrt/ directory. Required.
   Prefix length	Enter the number of digits to use for lookup and cache storage. Range: 0-999999999.
   String lookup	Select to enable lookup by string instead of E.164 phone numbers, when lookup tables contain range entries with alphanumeric prefixes.
   Retarget requests	Select to replace Request-URI in forwarded requests.
   Match mode	Select a lookup matching mode from the drop-down list. Note that this setting has no effect when table entries are ranges.

4. Click OK.
5. Save the configuration.

Configure a Session Agent

You can enable and configure constraints that the Oracle® Enterprise Session Border Controller (E-SBC) applies to regulate session activity with the session agent.

Configure the following before you configure a session agent.

• Media profile
• Out Translation ID
• Local Response Maps
• Codec Policy
• Session Recording Server
• TLS profile
• SIP header manipulation IDs
• LDAP
• One or more target groups

In the following procedure, some constraints affect session agent groups and SIP proxies outside of, and at the edge of the network. For example, the maximum sessions and maximum outbound sessions constraints do not apply to core routing proxies because they are transaction statefull, rather than session statefull. Other constraints, such as maximum burst rate, burst rate window, maximum sustained rate, and sustained rate apply to core routing proxies.

1. From the Web GUI, click Configuration, session-router, session-agent.
2. On the session-agent page, click Add, do the following:

   Host name	Enter the name of the host associated with the agent in host name, FQDN, or IP address format. This field is required and the name cannot include blank spaces. The value entered here must be unique to this agent because no two agents can use the same host name. If you enter the host name as an IP address, you do not have to enter an IP address in the optional IP address parameter. If you enter the host name in FQDN format, and you want to specify an IP address, enter it in the optional IP address parameter.
   IP address	(Optional) Enter the IP address for the host name that you entered in FQDN format if you want to specify the IP address. Otherwise, you can leave this parameter blank to allow a DNS query to resolve the host name.
   Port	Enter the number of the port associated with this agent. 0. If you enter zero, the E-SBC cannot initiate communication with this agent (although it will accept calls). 1025-65535. The default value is 5060. If the transport method value is TCP, the E-SBC will initiate communication on the TCP port of the agent.
   State	Select State to enable this agent.
   App protocol	Select the protocol to use to signal the session agent.
   Transport method	Select the transport mode for connections to this agent. UDP - Default UDP+TCP Dynamic TCP Static TCP Dynamic TLS Static TLS DTLS TLS+DTLS Static SCTP
   Realm ID	Select the name of the realm where this agent is located.
   Egress realm ID	Select the default egress realm to use for session agent pings and for when multiple egress realms are possible. For example, "realm-id is empty, or..."
   Description	Enter descriptive text to identify this agent.
   Constraints	Select to enable the use of constraints on this agent.
   Max sessions	Enter the maximum number of sessions allowed for this constraint. 0-999999999.
   Max inbound sessions	Enter the maximum number of inbound sessions allowed from this session agent. 0-999999999.
   Max outbound sessions	Enter the maximum number of outbound sessions allowed for this constraint. 0-999999999.
   Max burst rate	Enter the maximum number of invites allowed in a burst time period. 0-999999999.
   Max inbound burst rate	Enter the maximum inbound burst rate in INVITEs per second from this session agent. 0-999999999.
   Mac outbound burst rate	Enter the maximum outbound burst rate in INVITEs per second from this session agent. 0-999999999.
   Max sustain rate	Enter the maximum rate of session invitations allowed within the current time period for this constraint. 0-999999999.
   Max inbound sustain rate	Enter the maximum inbound sustain rate of session invitations allowed within the current time period for this constraint. 0-999999999.
   Max outbound sustain rate	Enter the maximum outbound sustain rate of session invitations allowed within the current time period for this constraint. 0-999999999.
   Time to resume	Enter the number of seconds that this session agent is out of service after reaching the constraint limit before attempting to re-initialize.
   In service period	Enter the number of seconds that this session agent is allowed to re-initialize before returning to in-service status.
   Burst rate window	Enter the time period, in seconds, used to measure the burst rate. 0-999999999.
   Sustain rate window	Enter the time period, in seconds, used to measure the sustained rate. 0-999999999.
   Proxy mode	Select a proxy mode for the E-SBC to use when a SIP request arrives from this agent.
   Redirect action	Select a method for the redirect response from this agent. Proxy. Send the response back to the previous hop. Recurse. Recurse on the contacts in the response. Recurse 305, only. Recurse on the contacts in the 305 response, only.
   Loose routing	Select to enable.
   Response map	Select the name of the response map.
   Ping method	Enter the SIP ping method.
   Ping interval	Enter the time, in seconds, to ping this session agent.
   Ping send mode	Select the mode for pinging this session agent. Continuous Keep alive
   Ping all addresses	Select to ping all addresses.
   Ping in service response codes	Enter one or more response codes that keep the session agent in service.
   Options	Add one or more options.
   SPL solutions	Use to add, edit or delete an SPL against this agent.
   Media profiles	Add the name of one or more media profiles.
   In translation id	Select the inbound translation ID.
   Out translation id	Select the outbound translation ID.
   Manipulation string	Enter the string to use in header manipulation rules.
   Manipulation pattern	Enter a regular expression to use in header manipulation rules.
   Trunk group	Specify the name of the trunk group that you must use to reach this agent.
   Max register sustain rate	Enter the maximum register sustain rate.
   Invalidate registrations	Select to invalidate all registrations going to this session agent.
   RFC2833 mode	Select the preferred mode for RFC2833.
   RFC2833 payload	Enter a number for the RFC2833 payload type.
   Codec policy	Select the codec policy to apply to this session agent.
   Refer call transfer	Select the refer method for call transfer.
   Refer notify provisional	Select the provisional mode for sending a NOTIFY message. None. The system sends no intermediate NOTIFY message. Initial. The system sends an intermediate 100 Trying NOTIFY message. All. The system sends an intermediate 100 Trying NOTIFY message, plus a NOTIFY for each non-100 provisional received by the E-SBC.
   Reuse connections	Select the protocol for SIP reuse connection.
   TCP keepalive	Select an option for the TCP keepalive function.
   TCP reconn interval	Enter the re-connection interval for TCP re-connection.
   Max register burst rate	Enter the number of seconds allowed for the maximum register burst rate.
   KPML interworking	Select a status for KPML Interworking.
   Monitoring filters	Add one or more monitoring filters.
   Auth attribute	Add one or more authentication attributes.
   Session recording server	Select a session recording server.
   Session recording required	Select to enable.
   Hold refer reinvite	Select to enable.

3. Click OK.
4. Save the configuration.

SIP hold-refer-reinvite

When SIP hold-refer-reinvite is enabled for REFER with Replaces, the system queues the outgoing Invite populated from the received REFER based on the dialog state.

In a deployment where a call goes through the Oracle® Enterprise Session Border Controller (E-SBC) before going to an Interactive Voice Response (IVR) server, the E-SBC proxies the intermediate reinvite that the IVR sends to the transfer target. If the intermediate reinvite is in either the pending state or the established state when the IVR initiates the transfer to the transfer target, the E-SBC terminates the call prematurely. The hold-refer-reinvite option allows the E-SBC to queue the Out Going INVITE from the received REFER request when the previously proxied reinvite request is in either the pending state or the established state. The result is a successful call.

Enable the SIP hold-refer-reinvite option from the ACLI command line or the Web GUI in Expert mode.

Enable hold-refer-reinvite

The SIP hold-refer-reinvite parameter for REFER with Replaces is a parameter that you enable to prevent premature call termination in a deployment where calls are proxied by the Oracle® Enterprise Session Border Controller.

• Confirm that refer-reinvite is added to realm/SA/SipInterface options.
• Confirm that refer-call-transfer is enabled on realm/SA/SipInterface
• Confirm that the session agent on which you want to enable hold-refer-reinvite is configured.

To enable hold-refer-reinvite, select a configured session agent and enable the parameter on the selected agent.

1. From the Web GUI, click Configuration, session-router, session-agent.
2. On the Session Agent page, select the agent and click Edit.
3. On the Modify Session Agent page, select Hold refer invite.
4. Click OK.
5. Save the configuration.

• Enable the refer-hold-reinvite parameter in the realm configuration.
• Enable the refer-hold-reinvite parameter in the session agent configuration.

Configure a Session Group

Use the sesison-group element to define a signalling endpoint configured to apply traffic shaping attributes and information about next hops and previous hops.

1. From the Web GUI, click Configuration , session-router, session-group.
2. On the session group page, click Add, Show advanced.
3. On the Add session group page, do the following:

   Group name	Enter the unique name of the session agent group element in the name format.
   Description	Enter a description of this session group.
   State	Select to enable.
   App protocol	Select an application protocol from the drop-down list.
   Strategy	Select a strategy from the drop-down list. Hunt. System selects the session agent in list order. Least Busy. System selects the session agent with the fewest number of sessions relative to the max-outbound-sessions constraint of the session-agent element. Low Sus Rate. System selects the session agent with the lowest sustained rate of session initiations and incitations. Prop Dist. System uses the proportional distribution strategy to distribute traffic among all available session agent elements, based on session constraint limits. Round Robin. System selects each session agent, one per session, in the order in which it is listed in the destination list. After all each session agents on the list is used, the system begins at the top of the list and repeats the cycle.
   Dest	Add one or more destinations to the list for this session agent group. The destination must correspond to a valid group name in another session agent group or to a valid hostname. Do one of the following, after adding a destination. Click OK. Click Apply/Add another, add another destination, and click OK. Repeat, as needed.
   Trunk group	Add one or more trunk groups and context to the list for this session agent group. To use the default context case, omit : and the context. Preface with the + character to add, the - character to remove, and exclude and to remove and replace. Do one of the following, after adding a trunk group. Click OK. Click Apply/Add another, add another trunk group, and click OK. Repeat, as needed.
   Sag recursion	Select to enable session agent group recursion for this session agent group.
   Stop sag recursion	Enter the list of SIP response codes that terminate recursion in the session agent group. You can enter the response codes in an comma-separated list or as a range. Default: 401, 407.

4. Click OK.
5. Save the configuration.

Configure Session Recording Group

The Oracle® Enterprise Session Border Controller (E-SBC) uses the session-recording-group attribute under session-router to define a collection of session recording servers.

• Enable the SIP Session Recording licence. See "Getting Started."
• Configure multiple session recording servers. See "Session-recording-server Attribute."
• Determine the load balancing strategy that you want the E-SBC to use. See "Load Balancing."

In the configuration, you list the session recording servers that you want in the group, select a load balancing strategy, and set the number of simultaneous SIP dialogs.

1. Access the system-config object.
   Configuration, session-router, session-recording-group.
2. On the session recording group page, click Add.
3. In the Add session recording group dialog, do the following:

   Name	Enter a unique name for the session recording group. You may need this name when configuring realm-config, session-agent, and sip-interface. Valid values: Alpha-numeric characters.
   Description (Optional)	Enter a description for the session recording group. Valid values: Alpha-numeric characters.
   Session recording servers	Click Add, enter the name of the session recording server, and do one of the following: Click OK. Click Apply/Add another, add another session recording server, and click OK. Repeat, as needed.
   Strategy	Enter the load balancing strategy that you want the E-SBC to use when sending recordings to the session reporting server. Round robin—Go to the next session recording server on the list, since the last session. Hunt—Look for a session recording server, starting with the first one on the list.
   Simultaneous recording servers	Enter the number of simultaneous SIP dialogs that the E-SBC establishes to the session reporting servers in the session reporting group per communication session. Valid values: 1 - 10. Default: 0.

4. Click OK.
5. Save the configuration.
6. Save the configuration.

Configure Advanced Logging

From the Configuration tab, define sip-advanced-logging and advanced-log-condition. The criteria that you configure remaps the message logging and modifies the system configuration. You must save and activate these changes to the configuration.

When configuring multiple sip-advanced-logging configurations, note the following.

• The system evaluates each configuration individually in an OR relationship.
• The system evaluates all conditions and they must all match in an AND relationship.

1. From the Web GUI, go to Configuration, session-router, Show Advanced, sip-advanced-logging, Show Advanced, and click Add.
2. On the Add SIP Advanced Logging page, do the following:

   Name	Type a name to display on the log message for this set of criteria.
   Level	Select one: zero, none, emergency, critical, major, minor, warning, notice, info, trace, debug, or detail.
   Scope	Select one: request-only, transaction, session, or session-and-media.
   Matches-per-window	Type a number between 1 and 999999999.
   Window-size	Type a number between 1 and 999999999.
   Conditions	Click Add, and do the following: Match type: Select one or more with either "and" or "or" between items: request-type, recv-agent, recv-realm, request-uri-user, request-uri-host, to-header-user, to-header-host, from-header-user, from-header-host, or call-id. Match value: Type the string that you want to match the incoming message. For example, to match "To-header-user" to the value 1234@<companyname>.com, type 1234.

3. Save the configuration.

Disable Advanced Logging

From the Configuration tab, clear the advanced logging settings.

1. From the Web GUI, go to Configuration, session-router, Show Advanced, sip-advanced-logging.
2. On the SIP Advanced Logging page, clear all of the settings.
3. Save the configuration.

Configure Advanced Logging

From the Configuration tab, define sip-advanced-logging and advanced-log-condition. The criteria that you configure remaps the message logging and modifies the system configuration. You must save and activate these changes to the configuration.

When configuring multiple sip-advanced-logging configurations, note the following.

• The system evaluates each configuration individually in an OR relationship.
• The system evaluates all conditions and they must all match in an AND relationship.

1. From the Web GUI, go to Configuration, session-router, Show Advanced, sip-advanced-logging, Show Advanced, and click Add.
2. On the Add SIP Advanced Logging page, do the following:

   Name	Type a name to display on the log message for this set of criteria.
   Level	Select one: zero, none, emergency, critical, major, minor, warning, notice, info, trace, debug, or detail.
   Scope	Select one: request-only, transaction, session, or session-and-media.
   Matches-per-window	Type a number between 1 and 999999999.
   Window-size	Type a number between 1 and 999999999.
   Conditions	Click Add, and do the following: Match type: Select one or more with either "and" or "or" between items: request-type, recv-agent, recv-realm, request-uri-user, request-uri-host, to-header-user, to-header-host, from-header-user, from-header-host, or call-id. Match value: Type the string that you want to match the incoming message. For example, to match "To-header-user" to the value 1234@<companyname>.com, type 1234.

3. Save the configuration.

Configure SIP

Use the sip-config element to define parameters for communications between the Session Initiation Protocol (SIP) and the Oracle® Enterprise Session Border Controller (E-SBC).

• Configure at least one home realm, egress realm, and transcoding realm.

1. From the Web GUI, click Configuration, session-router, sip-config.
2. On the SIP config page, do the following:

   State	Select to enable SIP operations.
   Dialog transparency	Select to preserve call IDs and tags.
   Home realm id	Select the home realm to connect to the E-SBC from the drop-down list.
   Egress realm	Select the default egress realm from the drop-down list.
   Nat mode	Select a Network Address Translation (NAT) mode from the drop-down list. None. No SIP-NAT function. Public. Means the home realm is public address space. Encrypt any URI from an external realm. Private. Means the home realm is private address space. Encrypt any URI from the home realm.
   Registrar domain	Enter the domain name of the SIP registrar server.
   Register host	Enter the hostname for the SIP registrar server.
   Registrar port	Enter the port number of the SIP registrar server. Range: 1024-65535.
   Init timer	Enter the time, in milliseconds, for the initial request retransmission timer. Range: 0-4294967295.
   Max timer	Enter the maximum time, in milliseconds, for the request retransmission timer. Range: 0-4294967295.
   Trans expire	Enter the time, in seconds, for the transaction expiration timer. Range: 0-4294967295.
   Initial invite trans expire	Enter the transaction expiration time for the initial INVITE. Range: 0-999999999. If you enter 0, the system uses the sip-config-inv-trans expiration time. Default is 0.
   Invite expire	Enter the INVITE transaction expiration time. Range: 0-4294967295.
   Enforcement profile	Enter the name of the enforcement profile.
   Red max trans	Enter the maximum number of redundancy synchronization transactions to keep on active. Range: 0-50000.
   Options	Add any optional parameters and features.
   SIP message len	Enter the maximum SIP message length. Range: 0-65535.
   Enum sag match	Select to enable matching the name of this Session Agent Group to the hostname portions of ENUM NAPTR and LRT replacement URIs.
   Extra method stats	Select to enable tracking method statistics for more entities.
   Extra enum stats	Select to enable tracking ENUM statistics per server address.
   Registration cache limit	Enter the maximum allowed number of registration cache entries.
   Register use to for lp	Select to enable To header routing for REGISTER.
   Refer src routing	Select to enable refer source realm routing.
   Atcf stn sr	Enter the Session Transfer Number (STN-SR) allocated by Access Transfer Control Function (ACTF) in the REGISTER message.
   Atcf psi dn	Enter the PSI-DN allocated by Access Transfer Control Function (ATCF) in the REGISTER message.
   Atcf route to sccas	Select to enable routing the Access Transfer Control Function (ATCF) handover rate to SCCAS.
   Eatf stn sr	Enter the E-TN-SR allocated by EATF in the INVITE handover message.
   Sag lookup on redirect	Select to enable lookup of the Session Agent Group name on a redirect.
   Set disconnect time on bye	Select to enable, if the disconnect time is set on receiving the BYE request.
   Msrp delayed bye	Enter the maximum time, in seconds, to delay forwarding a BYE for an MSRP session. 0 = no delay. Range: 1-60.
   Transcoding realm	Enter the name of the realm where transcoding agents reside.
   Transcoding agents	Create a list of transcoding agents. Click Add, enter the name of a transcoding agent, and do one of the following: Click OK. Click Apply/Add another, add another calling translation rule, and click OK. Repeat, as needed.
   Create dynamic sa	Select to enable the creation of dynamic session agents for service route.
   Node functionality	Select a node functionality from the drop-down list.
   Match SIP instance	Select to enable matching registration cache entries using the SIP instance parameter.
   Sa routes stats	Select to enable tracking session agent statistics for routes resolved by DNS.
   Sa routes traps	Select to enable generating traps when session agent routes change state.
   Rx SIP reason mapping	Select to enable mapping RX disconnect events to the SIP Reason header.
   Add ue location in pani	Select to enable adding the UE location string in the PANI header, when available.
   Hold emergency calls for loc info	Enter a time to hold emergency calls until the E-SBC receives location information from PCRF over the RX interface. Range: 0-4294967295.

3. Click OK.
4. Save the configuration.

Configure Pooled Transcoding

You must configure a transcoding realm and transcoding agents on the Access Session Border Controller, when used in a pooled transcoding deployment model. Set the parameters as part of the global SIP configuration.

• Configure a realm as the separate realm for the public SIP interface for exclusive communication with the Transcoding Session Border Controller (T-SBC) in a pooled transcoding deployment
• Configure one or more agents
• Configure SIP
• Configure the Access Session Border Controller (A-SBC)
• Configure the Transcoding Session Border Controller (T-SBC)

1. Access the sip-config object.
   Configuration, session-router, sip-config.
2. On the SIP Config page, do the following.

   Transcoding realm	Enter the name of a configured realm designated as the separate realm for the public SIP interface for exclusive communication with the Transcoding Session Border Controller (T-SBC) in a pooled transcoding deployment.
   Transcoding agents	Add any IP address, IP address - port combination, session agent, hostname, or session agent group to use as a transcoding agent. You can add multiple entries to the list. For example, you might list an IPv6 address and port, a session agent, and a session agent group.

3. Click OK.
4. Save the configuration.

Configure SIP-feature

Use the sip-feature element 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, session-router, sip-feature.
2. On the Sip feature page, do the following:

   Name	Enter the action tag name to display in the Require, Supported, and Proxy-Require headers of SIP messages.
   Realm	Do one of the following: Select the realm with which to associate this configuration. Leave this parameter blank to make this configuration global.
   Support mode inbound	Select the action tag in the Supported header in an inbound packet from the drop-down list.
   Require mode inbound	Select the action tag in the Require header for an inbound packet from the drop-down list. Default is reject.
   Proxy require mode inbound	Select the action tag in the Proxy-Require header in an inbound packet from the drop-down list.
   Support mode outbound	Select the action tag in the Supported header in an outbound packet from the drop-down list.
   Require mode outbound	Select the action tag in the Require header for an outbound packet from the drop-down list.
   Proxy require mode outbound	Select the action tag in the Proxy-Require header for an outbound packet from the drop-down list.

3. Click OK.
4. Save the configuration.

Configure SIP Interface

Use the sip-interface element to define SIP signaling.

• Confirm that a TLS profile exists.
• Confirm that rules exist for inbound and outbound SIP manipulation.

Configure a SIP interface for each network or realm to which you want to connect the Oracle® Enterprise Session Border Controller.

1. From the Web GUI, click Configuration, session-router, sip-interface.
2. On the SIP Interface page, click Add.
3. On the Add SIP Interface page, do the following:

   State	Select to enable this SIP interface.
   Realm id	Select the realm in which to apply this SIP interface from the drop-down list.
   Description	Enter a description of this SIP interface.
   SIP ports	Specify the following parameters for the ports that the SIP proxy or B2BUA uses for connections. Address. Enter the IP address of the host associated with the sip-port entry. Port. Enter the port number for this sip-port. Default is 5060. Range 1025-65535. Transport protocol. Select the transport protocol associated with this SIP port. Default is UDP. Valid values are: DTLS, SCTP, TCP, TLS, and UDP. TLS profile. Enter the TLS profile name. Allow anonymous. Select the type of anonymous connection to allow from agents. Default is All. Valid values include: All Allow all anonymous connections. Agents-only Allow requests from agents, only. Realm-prefix Allow session agent and address matching the realm prefix. Registered Allow session agent and registered endpoints, where REGISTER is allowed from any endpoint. Register-prefix Allow all connections from a session agent that match agents-only, realm-prefix, and registered agents.
   Nat traversal	Select a Network Address Translation (NAT) traversal mode for SIP from the drop-down list. None. NAT traversal is disabled. Always. The system performs Hosted NAT Traversal (HNT), when the SIP-Via and the transport address do not match. Rport. The system performs HNT, when the VIA rport parameter is present and the SIP-Via and transport addresses do not match.
   Registration caching	Select to enable non-HNT registration caching.
   Route to registrar	Select to enable routing requests to the registrar.
   In manipulationid	Select an inbound SIP manipulation rule from the drop-down list.
   Out manipulationid	Select an outbound SIP manipulation rule from the drop-down list.
   Service tag	Enter the service tag for this interface.

4. Click OK.
5. Save the configuration.

Configure SIP Manipulation

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.

Use the sip-manipulation element to add, modify, delete, split, and join SIP headers and to specify SIP header rules. 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, session-router, sip-manipulation, Show advanced.
2. In the SIP manipulation dialog, click Add and do the following:

   Name	Enter the exact name of the header to which this rule applies. Alpha-numeric. No spaces. Case-sensitive.
   Description	Enter a description of the purpose of this set of rules. Alpha-numeric.
   Split headers	Create a list of headers that you want the system to split and treat separately before executing any manipulation rules. Click Add, enter the header, and do one of the following: Click OK. Click Apply/Add another, add another header, and click OK. Repeat, as needed.
   Join headers	Create a list of headers that you want the system to join and treat as one header after executing any manipulation rules. Click Add, enter the header that you want the system to join, and do one of the following: Click OK. Click Apply/Add another, add another header, and click OK. Repeat, as needed.
   cfg rules	Click Add, select one of the following header rules from the menu, and see the corresponding documentation for further instructions. header rule—"Configure Header Rule" mime rule—"Configure MIME Rule" mime isup rule—"Configure MIME ISUP Rule" mime sdp rule—"Configure MIME SDP Rule"

3. When you finish configuring SIP manipulations, and the system returns you to the SIP manipulation page, save and activate the configuration.

• Apply the rules to a session agent or SIP interface as "inbound" or "outbound."

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.

   Name	Enter a unique name for this rule.
   Content type	Enter the name of the content type header to which to apply this rule.
   Isup spec	Select an ISUP encoding specification from the drop-down list for the ISUP body.
   Isup msg types	(Optional) Create a list of one or more ISUP message types to which the mime-isup rule applies. For example, IAM, ACM. When no methods are listed, this rule applies to all types. Click Add, enter the message type, and do one of the following: Click OK. Click Apply/Add another, add another message type, and click OK. Repeat, as needed.
   Msg type	Select the message type from the drop-down list to which this rule applies.
   Methods	(Optional) Create a list of methods to which this rule applies. For example, INVITE, ACK, CANCEL. When no methods are listed, this rule applies to all methods. Click Add, enter the method, and do one of the following: Click OK. Click Apply/Add another, add another method, and click OK. Repeat, as needed.
   Action	Select an action from the drop-down list for the header rule.
   Comparison type	Select a comparison type from the drop-down list to use for the match value.
   Match value	Enter the value to match against the current object.
   New value	Enter the new value for the object. You must escape quoted display names within quotes. For example, \"MyName\".
   CfgRules (instructions for configuring mime-header-rule)	(Optional) Click Add, mime-header-rule, and do the following. Name. Enter a unique name for this header element rule. Mime header name. Enter header name within the MIME part to which to apply the rule. Action. Select an action from the drop-down list to apply to the element rule. Comparison type. Select the type of comparison from the drop-down list to use for the match value. Match value. Enter the match value to compare against the current object. New value. Enter a new value for the object. Quoted display named must be escaped within quotes. For example, \"MyName\" . Click OK. The system displays the SIP manipulation / Mime isup rule dialog. Do one of the following: Add another mime-header-rule. Add an isup-param-rule, using the steps in the corresponding table cell. Finish the MIME ISUP rule configuration by completing steps 3-6.
   CfgRules (instructions for configuring isup-param-rule)	(Optional) Click Add, isup-param-rule, Show advanced, and do the following. Name. Enter a unique name for this header element rule. Type. Enter the parameter type that specifies the part of the isup body to manipulate. Format. Select a format from the drop down list for the encode - decode mode of the binary body form string form-ascii. Action. Select an action from the drop-down list to apply to the element rule. Comparison type. Select the type of comparison from the drop-down list to use for the match value. Match value. Enter the match value to compare against the current object. New value. Enter a new value for the object. Quoted display named must be escaped within quotes. For example, "\"MyName\" " . Click OK. The system displays the SIP manipulation / Mime isup rule dialog. Do one of the following: Add another isup-param-rule. Add an mime-header-rule, using the steps in the corresponding table cell. Finish the MIME ISUP rule configuration by completing steps 3-6.

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.

   Name	Enter a unique name for this rule.
   Msg type	Select the message type from the drop-down list to which this rule applies.
   Methods	(Optional) Create a list of methods to which this rule applies. For example, INVITE, ACK, CANCEL. When no methods are listed, this rule applies to all methods. Click Add, enter the method, and do one of the following: Click OK. Click Apply/Add another, add another method, and click OK. Repeat, as needed.
   Action	Select an action from the drop-down list for the header rule.
   Comparison type	Select a comparison type from the drop-down list to use for the match value.
   Match value	Enter the value to match against the current object.
   New value	Enter the new value for the object. You must escape quoted display names within quotes. For example, \"MyName\".
   CfgRules (instructions for configuring mime-header-rule)	(Optional) Click Add, mime-header-rule, and do the following. Name. Enter a unique name for this header element rule. Mime header name. Enter header name within the MIME part to which to apply the rule. Action. Select an action from the drop-down list to apply to the element rule. Comparison type. Select the type of comparison from the drop-down list to use for the match value. Match value. Enter the match value to compare against the current object. New value. Enter a new value for the object. Quoted display named must be escaped within quotes. For example, \"MyName\" . Click OK. The system displays the SIP manipulation / Mime sdp rule dialog. Do one of the following: Add another mime-header-rule. Configure the sdp-session-rule and sdp-media-rule options, using the steps in the corresponding table cells. Finish the MIME SDP rule configuration by completing steps 3-6.
   CfgRules (instructions for configuring sdp-session-rule)	(Optional) Click Add, sdp-session-rule , and do the following. Name. Enter a unique name for this header element rule. Action. Select an action from the drop-down list to apply to the this rule. Comparison type. Select the type of comparison from the drop-down list to use for the match value. Match value. Enter the match value to compare against the current object. New value. Enter a new value for the object. Quoted display named must be escaped within quotes. For example, \"MyName\". CfgRules (Optional) Click Add, sdp-line-rule. Name. Enter a unique name for this rule. Type. Enter a descriptor type to specify the SDP line to manipulate. Action. Select an action from the drop-down list to apply to this rule. Comparison type. Select the type of comparison from the drop-down list to use for the match value. Match value. Enter the match value to compare against the current object. New value. Enter a new value for the object. Quoted display named must be escaped within quotes. For example, \"MyName\". Click OK. The system displays the SIP manipulation / Mime sdp rule / Sdp session rule dialog. (Optional) Add another sdp-line-rule. Click OK. The system displays the SIP manipulation / Mime sdp rule dialog. Do one of the following: Add another sdp-session-rule. Configure the mime-header-rule and sdp-media-rule options, using the steps in the corresponding table cells. Finish the MIME SDP rule configuration by completing steps 3-6.
   CfgRules (instructions for configuring sdp-media-rule)	(Optional) Click Add, sdp-media-rule. Name. Enter a unique name for this header element rule. Media type. Enter the media type to manipulate. For example, audio or video. Action. Select an action from the drop-down list to apply to the element rule. Comparison type. Select the type of comparison from the drop-down list to use for the match value. Match value. Enter the match value to compare against the current object. New value. Enter a new value for the object. Quoted display named must be escaped within quotes. For example, "\"MyName\" " . Click OK. CfgRules (Optional) Click Add, sdp-line-rule. Name. Enter a unique name for this rule. Type. Enter a descriptor type to specify the SDP line to manipulate. Action. Select an action from the drop-down list to apply to this rule. Comparison type. Select the type of comparison from the drop-down list to use for the match value. Match value. Enter the match value to compare against the current object. New value. Enter a new value for the object. Quoted display named must be escaped within quotes. For example, \"MyName\". Click OK. The system displays the SIP manipulation / Mime sdp rule / Sdp media rule dialog. (Optional) Add another sdp-line-rule. Click OK. The system displays the SIP manipulation / Mime sdp rule dialog. Do one of the following: Add another sdp-media-rule. Configure the mime-header-rule and sdp-sesison-rule options, using the steps in the corresponding table cells. Finish the MIME SDP rule configuration by completing steps 3-6.

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 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.

   Name	Enter a unique name for this rule set. Valid values: Alpha-numeric.
   Header name	Enter the name of the header to which this rule applies. Case-sensitive.
   Action	Select an action from the drop-down list for the header rule.
   Comparison type	Select a comparison type from the drop-down list to use for the match value.
   Msg type	Select the message type from the drop-down list to which this rule applies.
   Methods	(Optional) Create a list of methods to which this rule applies. For example, INVITE, ACK, CANCEL. When no methods are listed, this rule applies to all methods. Click Add, enter the method, and do one of the following: Click OK. Click Apply/Add another, add another method, and click OK. Repeat, as needed.
   Match value	Enter the value to match against the current object.
   New value	Enter the new value for the object. You must escape quoted display names within quotes. For example, \"MyName\".
   CfgRules	(Optional) Click Add, element-rule, and do the following. Name. Enter a unique name for this header element rule. Parameter name. Enter a parameter to which to apply the rule. Type. Select an element type from the drop-down list to which to apply the rule. Action. Select an action from the drop-down list to apply to the element rule. Match val type. Select a value from the drop-down list to apply to the element rule. Comparison type. Select the type of comparison from the drop-down list to use for the match value. Case-sensitive. Match value. Enter the match value to compare against the current object. New value. Enter a new value for the object. Quoted display named must be escaped within quotes. For example, \"MyName\" . Click OK. The system displays the SIP manipulation / Header rule page. Do one of the following: Add another element-rule. Finish the Header rule configuration by completing steps 3-6.

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.

   Name	Enter a unique name for this rule.
   Content type	Enter the name of the content-type header to which to apply this rule.
   Msg type	Select the message type from the drop-down list to which this rule applies.
   Methods	(Optional) Create a list of methods to which this rule applies. For example, INVITE, ACK, CANCEL. When no methods are listed, this rule applies to all methods. Click Add, enter the method, and do one of the following: Click OK. Click Apply/Add another, add another method, and click OK. Repeat, as needed.
   Format	Select the encode - decode format from the drop-down list for the MIME content.
   Action	Select an action from the drop-down list for the header rule.
   Comparison type	Select a comparison type from the drop-down list to use for the match value.
   Match value	Enter the value to match against the current object.
   New value	Enter the new value for the object. You must escape quoted display names within quotes. For example, \"MyName\".
   CfgRules (instructions for configuring mime-header-rule)	(Optional) Click Add, mime-header-rule, and do the following. Name. Enter a unique name for this header element rule. Mime header name. Enter header name within the MIME part to which to apply the rule. Action. Select an action from the drop-down list to apply to the element rule. Comparison type. Select the type of comparison from the drop-down list to use for the match value. Match value. Enter the match value to compare against the current object. New value. Enter a new value for the object. Quoted display named must be escaped within quotes. For example, \"MyName\" . Click OK. The system displays the SIP manipulation / Mime rule dialog. Do one of the following: Add another mime-header-rule. Finish the MIME rule configuration by completing steps 3-6.

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 SIP Monitoring

Use the sip-monitoring element to configure SIP Monitor and Trace features and to set filters for SIP monitoring.

• Confirm that a session agent, a realm, or both are configured, or you must set filtering on a global basis for Monitor and Trace to occur.

You must configure the sip-monitoring object to enable filtering. The only required setting is State, which enables sip-monitoring. You can optionally monitor all filters or you can specify one or more filters to monitor. You can specify a time for short session duration monitoring and you can select interesting events to monitor.

Note:

Interesting Events are always enabled on a global-basis on the Oracle® Enterprise Session Border Controller.

1. From the Web GUI, click Configuration, session-router, sip-monitoring.
2. On the SIP monitoring page, click Show advanced, and do the following:

   Match any filter	Select to enable.
   State	Select to enable the sip-monitoring configuration.
   Short session duration	Enter a number of minutes from 0-999999999.
   Monitoring filters	Click Add to add one or more custom monitoring filters to the list to use when monitoring on a global-basis. Enter the name of the filter, and do one of the following: Click OK. Click Apply/Add another, add another media attribute, and click OK. Repeat, as needed.
   Interesting events	Click Add, and select either short-session or local-rejection.
   Trigger window	Enter a number from 0-999999999.

3. Click OK.
4. Save the configuration.

Surrogate Registration

The Oracle® Enterprise Session Border Controller surrogate registration feature lets the Oracle® Enterprise Session Border Controller explicitly register on behalf of a Internet Protocol Private Branch Exchange (IP-PBX). After you configure a surrogate agent, the Oracle® Enterprise Session Border Controller periodically generates a REGISTER request and authenticates itself using a locally configured username and password, with the Oracle® Enterprise Session Border Controller as the contact address. Surrogate registration also manages the routing of class from the IP-PBX to the core and from the core to the IP-PBX.

Configure Surrogate Registration

Surrogate registration allows the Oracle® Enterprise Session Border Controller (E-SBC) to explicitly register on behalf of an Internet Protocol Private Branch Exchange (IP-PBX). Surrogate registration also manages the routing of calls from the IP-PBX and from the core to the IP-PBX. The E-SBC uses the configuration information of the surrogate agent that corresponds to a specific IP-PBX to send REGISTER requests. You can configure the number of requests to send.

Configure a surrogate agent for each IP-PBX proxy that you want the E-SBC to register.

Note:

To view all surrogate agent configuration parameters, enter a ? at the surrogate-agent prompt.

1. From the Web GUI, click configuration, session-router, show advanced, surrogate-agent, show advanced.
2. On the Surrogate Agent page, click Add.
3. On the Add Surrogate Agent page, do the following:

   Register host	Enter the registrar’s hostname to be used in the Request-URI of the REGISTER request. This name is also used as the host portion of the AoR To and From headers.
   Register user	Enter the user portion of the AoR (Address of Record).
   Description	Optional. Enter a description of this surrogate agent.
   Realm ID	Enter the name of realm where the surrogate agent resides (where the IP-PBX proxy resides). There is no default.
   State	Set the state of the surrogate agent to indicate whether the surrogate agent is used by the application. The default value is enabled.
   Customer host	Optional. Enter the domain or IP address of the IP-PBX, which is used to determine whether it is different than the one used by the registrar.
   Customer next hop	Enter the next hop to this surrogate agent: session agent group: <session agent group name> session agent: <hostname> or <IPV4>
   Register contact host	Enter the hostname to be used in the Contact-URI sent in the REGISTER request. This should always point to the E-SBC. If specifying a IP address, use the egress interface’s address. If there is a SIP NAT on the registrar’s side, use the home address in the SIP NAT.
   Register contact user	Enter the user part of the Contact-URI that the E-SBC generates.
   Password	If you are configuring the auth-user parameter, you need to enter the password used when the registrar sends the 401 or 407 response to the REGISTER request.
   Register expires	Enter the expires in seconds for the REGISTER requests. The default value is 600,000 (1 week). The valid range is 0-999999999.
   Replace contact	This specifies whether the E-SBC needs to replace the Contact in the requests coming from the surrogate agent. If this is enabled, Contact will be replaced with the Contact-URI the E-SBC sent in the REGISTER request. The default value is disabled. The valid values are enabled and disabled.
   Options	Optional. Enter non-standard options or features.
   Route to registrar	This indicates whether requests coming from the surrogate agent should be routed to the registrar if they are not explicitly addressed to the E-SBC. The default value is enabled. The valid values are enabled and disabled.
   AoR count	Enter the number of registrations to do on behalf of this IP-PBX. If you enter a value greater than 1, the E-SBC increments the register-user and the register-contact-user values by that number. For example, if this count is 3 and register-user is john then users for three different register messages will be john, john1, john2. It does the same for the register-contact-user values. The default value is 1. The valid range is 0-999999999.
   Auth user	Enter the authentication user name you want to use for the surrogate agent. This name is used when the E-SBC receives a 401or 407 response to the REGISTER request and has to send the REGISTER request again with the Authorization or Proxy-Authorization header. The name you enter here is used in the Digest username parameter. If you do not enter a name, the E-SBC uses the value of the register-user parameter.
   Max register attempts	Enter the total number of times to attempt registration until success. Range 1-10
   Registry retry time	Enter the time to wait after an unsuccessful registration before re-attempting. Range 30-3600
   Count start	Enter the starting value for numbering when performing multiple registrations. Range 0-9999999999
   Register mode	Select automatic (default) or triggered (upon trigger from PBX).
   Triggered inactivity interval	Enter the maximum time with no traffic from the corresponding PBX. (Valid only with Triggered inactivity interval.) Range 5 -300
   Triggered OoS response	503 (Default. Send 503 response for core network failure) or drop response (Do not respond to PBX or core network failure

4. Click OK.
5. Save the configuration.

• Add the surrogate agent as a session-agent under session-router.

Remote Site Survivability Configuration

You must enable remote site survivability on the Oracle® Enterprise Session Border Controller (E-SBC) and set the ping method for the session agent before the E-SBC can perform remote site survivability operations.

The process for configuring remote site survivability includes the following procedures.

1. Enable remote site survivability mode on the E-SBC.
2. Configure a ping method for the session agent to use to determine when the E-SBC is not responding.

Note:

The system does not require a reboot after activating or modifying remote site survivability.

Configure Remote Site Survivability

You must enable remote site survivability on the Oracle® Enterprise Session Border Controller (E-SBC) and set the parameters before the system can enter and exit survival mode.

• Configure at least one session agent.

1. From the Web GUI, click Configuration, session-router, session-router, survivability.
2. At the bottom of the left pane, click Show advanced.
3. On the Add survivability page, do the following:

   State	Select to enable Survivability.
   Reg expires	Enter the number of seconds that the Oracle® Enterprise Session Border Controller waits before entering the remote site survivability mode when the registration expires.
   Prefix length	Enter the maximum number of digits allowed for a phone extension. Range: 0-10.
   Session agent hostname	Select the agent hostname or the session agent group name from the drop down list.

4. Click OK.
5. Save and activate the configuration.

• Configure a ping method on the session agent. See "Configure a Session Agent."

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 Configuration, session-router, translation-rules.
2. On the Translation rules page, click Show advanced, and do the following:

   Id	Enter the identifier or name for this rule.
   Type	Select the address translation type from the drop-down list. Add. Add one or more characters to the address. Delete. Delete one or more characters from the address. None. Disable the translation rule. Replace. Replace one or more characters in the address.
   Add string	Enter the string to add to the original address during address translation. For example, do not use characters such as @ and $. Valid values are alpha-numeric characters.
   Add index	Enter the index for the Add string. Use the $ character to append the string at the end of the address. Valid values are alpha-numeric characters.
   Delete string	Enter the string to be deleted from the original address during address translation. Unspecified characters are denoted by the @ character. Valid values are alpha-numeric characters. Note: The @ character only works if the type parameter is set to delete. This parameter supports wildcard characters or digits only. For example, valid entries are: delete-string=@@@@@, or delete-string=123456. An invalid entry is delete-string=123@@@. When the type is set to replace, this value is used in conjunction with the add-string value. The value specified in the delete-string field is deleted and the value specified in the add-string field is inserted. If no value is specified in the delete-string parameter and the type field is set to replace, then nothing is inserted into the address.
   Delete index	Enter the index for the string to delete.

3. Click OK.
4. Save the configuration.