The system requires an initial configuration of attributes, such as modes and IP addresses, before it can function in the network.

1. Logon to the Oracle® Enterprise Session Border Controller.
   The system displays the Set initial configuration wizard.
2. Run the Set Initial Configuration Wizard, and click Complete.
   The system saves the configuration, activates the configuration, and re-boots.

You can reconfigure the system from the Web GUI.

1. Log on to the system.
2. Access the Set Initial Configuration Wizard: Configuration, Wizards, Set Initial Configuration.
3. Run the Set Initial Configuration Wizard and change the attributes, as needed.
4. Click Complete.
   The system saves a backup of the existing configuration, saves the new configuration, activates the new configuration, and automatically re-boots.

You can configure the Oracle® Enterprise Session Border Controller (E-SBC) to generate Syslogs for system management and Process logs for debugging.

The E-SBC generates the following types of logs.

• Syslogs conform to the standard used for logging servers and processes as defined in RFC 3164. In configuration, you specify the Syslog server.
• Process logs are proprietary Oracle logs that the system generates on a per-task basis and are used mainly for debugging purposes. Because process logs are more data inclusive than Syslogs, their contents usually include Syslog log data. In configuration, you specify the log level.

Syslog and process log servers are both identified by an IPv4 address and port pair.

Simple Network Management Protocol (SNMP) supports the monitoring of devices attached to the network for conditions that might need administrative attention.

Session Initiation Protocol (SIP) is an IETF-defined signaling protocol widely used for controlling communication sessions such as voice and video calls over Internet Protocol (IP). You can use the protocol for creating, modifying, and terminating two-party (unicast) or multiparty (multicast) sessions. Sessions may consist of one or several media streams.

The Oracle® Enterprise Session Border Controller (E-SBC) Denial of Service (DoS) protection functionality protects soft switches and gateways with overload protection, dynamic and static access control, and trusted device classification and separation in layers 3-5.

DoS protection prevents the E-SBC host processor from being overwhelmed by a targeted DoS attack from the following:

• IP packets from an untrusted source, as defined by provisioned and dynamic ACLs
• IP packets for unsupported and disabled protocols
• Nonconforming and malformed packets to signaling ports
• Volume-based attack of valid and invalid call requests, signaling messages, and so on.

The Server Edition and VM Edition support of DoS protection differs from the Oracle Hardware Platforms Edition due to the absence of Oracle network interface hardware. Consequently, DoS protection is implemented in software and consumes CPU cycles when responding to attacks.

The Server Edition and VM Edition handle media packet fragments differently, processing them in the data path rather than in the host application code. Protection against fragment attacks occurs because the system never keeps fragments for more than 5 milliseconds.

Palladion is the Oracle Communication Experience Manager.

The manager is powered by the Palladion Mediation Engine, a platform that collects SIP, DNS, ENUM, and protocol message traffic received from Palladion Probes. The mediation engine stores the traffic in an internal database, and analyzes aggregated data to provide comprehensive multi-level monitoring, troubleshooting, and interoperability information.

Palladion simplifies the operation of software-based Palladion probes by enabling the transmission of Internet Protocol Flow Information Export (IPFIX) data to one or more Palladion Mediation Engines, possibly on different sub-nets.

You can deploy the Oracle® Enterprise Session Border Controller (E-SBC) in pairs to deliver High Availability (HA). Two E-SBCs operating in this way are called an HA node. Over the HA node, call state is shared, keeping sessions and calls from dropping in the event of a service disruption.

When two E-SBCs work together in an HA node, one operates in active mode and the other one operates in standby mode.

• The active E-SBC checks itself for internal process and IP connectivity issues. If it detects that it is experiencing certain faults, it hands over its role as the active system to the standby E-SBC.
• The standby E-SBC is the backup system, fully synchronized with the active E-SBC session status. The standby E-SBC monitors the status of the active system so that, if needed, it can assume the active role without the active system having to instruct it to do so. If the standby system takes over the active role, it notifies network management using an SNMP trap.

To produce seamless switch overs from one E-SBC to the other, the HA node uses shared virtual MAC and virtual IP addresses for the media interfaces in a way that is similar to Virtual Router Redundancy Protocol (VRRP). Sharing addresses eliminates the possibility that the MAC and IPv4 address set on one E-SBC in an HA node will be a single point of failure. The standbyE-SBC sends ARP requests using a utility IPv4 address and its hard-coded MAC addresses to obtain Layer 2 bindings.

When there is a switch over, the standby E-SBC issues gratuitous ARP messages using the virtual MAC address, establishing that MAC on another physical port within the Ethernet switch. To the upstream router, the MAC and IP are still alive, meaning that existing sessions continue uninterrupted.

In the HA node, the E-SBCs advertise their current state and health to one another in checkpointing messages so that each system is apprised of the other’s status. Using Oracle’s HA protocol, the E-SBCs communicate with UDP messages sent out and received on the interfaces carrying heartbeat traffic between the active and standby devices.

The standby E-SBC assumes the active role when:

• It has not received a checkpoint message from the active E-SBC for a certain period of time.
• It determines that the health score of the active E-SBC has decreased to an unacceptable level.
• The active E-SBC relinquishes the active role.

The Acme Packet 1100 supports High Availability (HA), but the configuration differs from other Oracle® Enterprise Session Border Controllers (E-SBC) because there is only one management interface on this device.

Unlike other E-SBCs, which provide two management interfaces and two media interfaces, the Acme Packet 1100 provides 1 management interface and 2 media interfaces. For HA, you must create a second management interface object on the Acme Packet 1100 with wancom0 for the name and VLAN for the sub-port-id. You can configure only one management interface in an HA pair with these settings and the system does not support more than one HA interface with a VLAN tag.

You can configure the packet capture function on the Oracle® Enterprise Session Border Controller (E-SBC) to view packet traffic on your network. For example, you might want to confirm the network configuration or to perform troubleshooting.

The remote site survivability feature enables an Oracle® Enterprise Session Border Controller (E-SBC) that is deployed in a Remote Office/Branch Office (ROBO) site to detect the loss of communication over SIP-based telephony to the Enterprise’s core call processing Data Center.

When loss of communication is detected over the SIP service, the ROBO E-SBC dynamically switches into Survivable Mode, handling call processing locally and providing limited additional server functionality.

Remote Site Survivability:

• Works with or without High Availability (HA).
• Is configurable in real-time, with no reboot required to enable this feature.
• Allows configuration by way of the E-SBC Web GUI.
• Maintains Historical Recording (HDR) statistics about being in survivability mode, such as:
  • Whether or not the E-SBC is in survivable mode using the ACLI command, show health.
  • Length of time the E-SBC was in survivable mode (records the number of times and the amount of time in survivability mode).
  • Number of SIP messages handled in survivable mode.
  • Number of SIP users registered locally in survivable mode (both existing based on cache, and separately - new registrations).

You can perform the minimum configuration needed to connect a PBX to the Oracle® Enterprise Session Border Controller (E-SBC) from the Configuration tab in Basic mode.

1. Access the PBX configuration object: Configuration, Devices, Add, PBX.
   The system displays the Add PBX dialog.
2. In the Add PBX dialog, do the following:

   PBX name	Enter the name to assign to this PBX in the Enterprise network. For example, PBX1. Valid values: Alpha-numeric characters.
   Description	Enter a description for this PBX. For example, PBX for Enterprise. Valid values: Alpha-numeric characters.
   Hostname	Enter the hostname of the Oracle® Enterprise Session Border Controller to which this PBX is connected. For example, SBC1. Valid values: Alpha-numeric characters.
   IP Address	Enter the IP address of this PBX in dotted decimal format. For example, 1.1.1.1. Default is 0.0.0.0.
   IP Port	Enter the IP port for this PBX. Default: 5060. Range: 1025-65535.
   Enable Refer Call Transfer	Select to enable. Default: Disabled.
   Enable SIP Monitoring and Tracing	Select to enable. Default: Disabled.
   Maximum Sessions	Enter the maximum number of concurrent sessions. Default: 0. Range: 0-999999999,
   Maximum Inbound Sessions	Enter the maximum number of concurrent inbound sessions. Default: 0. Range: 0-999999999,
   Maximum Outbound Sessions	Enter the maximum number of concurrent outbound sessions. Default: 0. Range: 0-999999999,
   Enable Connectivity Check	Select to enable. Default: Disabled.
   Connectivity Check Interval	Enter the connectivity check interval. Default 30. Range: 0-9999.
   Connectivity Check Method	Select a connectivity check method from the drop-down list.
   Inbound Manipulation	Select inbound manipulation from the drop-down list.
   Outbound Manipulation	Select outbound manipulation from the drop-down list.
   Inbound Translation Rules	Click the field and select a rule from the list.
   Outbound Translation Rules	Click the field and select a rule from the list.
   Trust Mode	Select a trust level from the drop-down list.
   Invalid Message Threshold	Enter the invalid message threshold. Default: 0. Range: 0-9999.
   Maximum Message Threshold	Enter the maximum message threshold. Default: 0. Range: 0-9999.
   SPL Options	Enter the name of the SPL option.

3. Click OK.
4. Save the configuration.

You can perform the minimum configuration needed to make connect a SIP Trunk to the Oracle® Enterprise Session Border Controller (E-SBC) from the Configuration tab in Basic mode.

1. Access the Trunk configuration object: Configuration, Devices, Add, Trunk.
   The system displays the Add SIP Trunk dialog.
2. In the Add SIP Trunk dialog, do the following:

   Trunk Name	Enter the name to assign to this SIP Trunk in the Service Provider network. For example, SIPT1. Valid values: Alpha-numeric characters.
   Description	Enter a description for this SIP Trunk. For example, SIP Trunk for Service Provider. Valid values: Alpha-numeric characters.
   Hostname	Enter the hostname of the Oracle® Enterprise Session Border Controller, to which this SIP Trunk is connected. For example, SBC1. Valid values are alpha-numeric characters.
   IP Address	Enter the IP address of this SIP Trunk in dotted decimal format. For example, 1.1.1.1. Default: 0.0.0.0.
   IP Port	Enter the IP port for this SIP Trunk. Default: 5060. Range: 1025-65535.
   Enable SIP Monitoring and Tracing	Select to enable.
   Maximum Sessions	Enter the maximum number of concurrent sessions. Range: 0-999999999.
   Maximum Inbound Sessions	Enter the maximum number of concurrent inbound sessions. Range: 0-999999999.
   Maximum Outbound Sessions	Enter the maximum number of concurrent outbound sessions. Range: 0-999999999.
   Enable Connectivity Check	Select to enable.
   Connectivity Check Interval	Enter the connectivity check interval. Default 30. Range: 0-9999.
   Connectivity Check Method	Select a connectivity check method from the drop-down list.
   Inbound Manipulation	Select inbound manipulation from the drop-down list.
   Outbound Manipulation	Select outbound manipulation from the drop-down list.
   Inbound Translation Rules	Click the field and select a rule from the list.
   Outbound Translation Rules	Click the field and select a rule from the list.
   Trust Mode	Select a trust level from the drop-down list.
   Invalid Message Threshold	Enter the invalid message threshold. Default: 0. Range: 0-9999.
   Maximum Message Threshold	Enter the maximum message threshold. Default: 0. Range: 0-9999.
   SPL Options	Enter the name of the SPL option.

3. Click OK.
4. Save the configuration.

A remote worker is a device that you set up outside of your network, which you connect to the Oracle® Enterprise Session Border ControllerE-SBC) from the remote location.

1. Access the Remote Worker configuration object: Configuration, Devices, Add, Remote Workers.
2. In the Add Remote Worker dialog, do the following:

   Name	Enter a name for this remote worker. Valid values: Alphanumeric characters.
   Description	(Optional) Enter a description of this remote worker.

3. Click OK.
4. Save the configuration.

1. Access the SIP Device configuration object: Configuration, Devices, Add, Device.
   The system displays the Add device dialog.
2. In the Add device dialog, do the following:

   Device name	Enter the name to assign to this device in the Enterprise network. For example, device1. Valid values: Alpha-numeric characters.
   Description	Enter a description for this device. For example, device for Enterprise. Valid values: Alpha-numeric characters.
   Hostname	Enter the hostname of the Oracle® Enterprise Session Border Controller to which this device is connected. For example, SBC1. Valid values: Alpha-numeric characters.
   IP Address	Enter the IP address of this device in dotted decimal format. For example, 1.1.1.1. Default is 0.0.0.0.
   IP Port	Enter the IP port for this device. Default: 5060. Range: 1025-65535.
   Enable Refer Call Transfer	Select to enable. Default: Disabled.
   Enable SIP Monitoring and Tracing	Select to enable. Default: Disabled.
   Maximum Sessions	Enter the maximum number of concurrent sessions. Default: 0. Range: 0-999999999.
   Maximum Inbound Sessions	Enter the maximum number of concurrent inbound sessions. Default: 0. Range: 0-999999999.
   Maximum Outbound Sessions	Enter the maximum number of concurrent outbound sessions. Default: 0. Range: 0-999999999.
   Enable Connectivity Check	Select to enable. Default: Disabled.
   Connectivity Check Interval	Enter the connectivity check interval. Default 30. Range: 0-9999.
   Connectivity Check Method	Select a connectivity check method from the drop-down list.
   Inbound Manipulation	Select inbound manipulation from the drop-down list.
   Outbound Manipulation	Select outbound manipulation from the drop-down list.
   Inbound Translation Rules	Click the field and select a rule from the list.
   Outbound Translation Rules	Click the field and select a rule from the list.
   Trust Mode	Select a trust level from the drop-down list.
   Invalid Message Threshold	Enter the invalid message threshold. Default: 0. Range: 0-9999.
   Maximum Message Threshold	Enter the maximum message threshold. Default: 0. Range: 0-9999.
   SPL Options	Enter the name of the SPL option.

3. Click OK.
4. Save the configuration.

A session recording server is either a third-party call recorder or the Record and Store Server on the Oracle® Enterprise Session Border Controller (E-SBC) for recording the media transmitted in session between multiple user agents.

1. Access the Session Recording Server configuration object: Configuration, Devices, Recording Server, Add.
2. On the Add Session Recording Server page, do the following:

   Recording Server Name	Enter the name to assign to this recording server. Valid values: Alpha-numeric characters.
   Description	Enter a description for this recording server. Valid values: Alpha-numeric characters.
   IP Address	Enter the IP address of this recording server in dotted decimal format. For example, 1.1.1.1. Default is 0.0.0.0.
   IP Port	Enter the IP port for this recording server. Default: 5060. Range: 1025-65535.

3. Click OK.
4. Save the configuration.

You can add up to five SIP interfaces to both the Enterprise side and the Service Provider side of your Oracle® Enterprise Session Border Controller (E-SBC). You can associate a SIP interface with any configured network interface.

1. Access the SIP Interface configuration object: Configuration, Devices, Add, SIP Interface.
   The Web GUI displays the Choose Side dialog.
2. In the Choose Side dialog, click either Enterprise or Service Provider.
   The Web GUI displays the Add SIP Interface configuration page.
3. In the Add SIP Interface configuration, do the following:

   Interface Name	Enter the name to assign to this SIP Interface. Valid values: Alpha-numeric characters.
   Description	Enter a description of this interface.
   Network Interface
   IP Address	Enter the IP address of this SIP interface in dotted decimal format. For example, 1.1.1.1. Default: 0.0.0.0.
   SIP Port	Enter the SIP port for this SIP interface. Default: 5060. Range: 1025-65535.
   IP Transport	Select an IP transport protocol from the drop-down list. Default: UDP. Valid values: UDP | TCP | TLS.
   TLS Profile	Select a TLS profile from the drop-down list that you want to associate with this interface.
   Allowed Requests From	Default: Agents Only. Valid Values: Agents Only | Registered | All.
   Enable Registration Caching	Select to enable registration caching for all User Agents, not just ones behind a Network Address Translation. Default: Disabled.
   Registration Interval	Set the registration entry interval, in seconds, for a non-HNT endpoint. Default: 3600 seconds. Range: 0-7200.
   Enable Routing All Calls to Registrar	Select to enable routing calls to the registrar. Default: Enabled.
   Transfer Calls on REFER	Select to enable transferring calls on REFER. Default; Disabled.
   Allowed SIP Methods	Add one or more SIP methods that you want to allow. Valid values: INVITE | REGISTER | PRACK | OPTIONS | INFO | SUBSCRIBE | NOTIFY | REFER | UPDATE | MESSAGE | PUBLISH.
   Media Start Port	Enter the number of the starting media port. Default: 10000. Range: 1-65535.
   Media End Port	Enter the number of the ending media port. Default: 20000. Range: 1-65535.
   Enable RFC2833 Payload Type	Select to enable RFC2833 payload type. Default: Disabled.
   Enable Media Release in Network Interface	Select to enable the release of media for specific call flows between SIP peers or realms on two network interfaces of the same E-SBC, regardless of the attached media topology . Default: Disabled.
   Enable Symmetric Latching	Select to enable Symmetric Latching for the RTP/RTCP flow. Default: Disabled.
   Enable QoS	Select to enable QoS reporting. Default: Disabled.
   Allowed Codecs	Enter one or more codecs that you want to allow.
   Add Codes on Egress	Enter one or more codecs to add on egress.
   Order Codecs
   Force Ptime	Select to enable setting a forced packetization time on egress. Default: Disabled.
   Packetization Time	Set the media packetization time in milliseconds. Default: ? Range: ?
   DTMF in Audio	Specify how to handle DTMF in the audio stream. Default: Disabled. Valid values: Disabled | Dual | Preferred.
   Enable Media Security	Select to enable the media security policy that specifies the role of the E-SBC in the security negotiation. Default: Disabled.
   SDES Profile	Select an SDES profile from the drop-down list that you want to associate with this interface.
   Media Security Mode	Select a media security mode for Real-Time Transport Protocol from the drop-down list. Default: RTP. Valid values: RTP | SRTP | Any (means either RTP or SRTP).
   Media Security Protocol	Select a media security protocol from the drop-down list.
   Enable ToS Marking Rewrite	Select to enable ToS marking re-write.
   ToS Value for Audio Packets	Set the ToS value for audio packets.
   ToS Value for SIP Packets	Set the ToS value for SIP packets.
   Inbound Manipulation	Select inbound manipulation from the drop-down list.
   Outbound Manipulation	Select outbound manipulation from the drop-down list.
   Inbound Translation Rules	Click the field and select a rule from the list.
   Outbound Translation Rules	Click the field and select a rule from the list.
   Trust Mode	Select a trust level from the drop-down list. Default; None. Valid values: None | Low | Medium | High.
   Invalid Message Threshold	Enter the invalid message threshold. Default: 0. Range: 0-9999.
   Maximum Message Threshold	Enter the maximum message threshold. Default: 0. Range: 0-9999.
   Untrusted Message Threshold	Enter the untrusted message threshold. Default: 0. Range: 0-9999.
   Deny Period	Default: 0. Range: 0-7200.
   Session Recording Server	Select a Session Recording Server from the drop-down list.
   Session Recording Mandatory	Select to make session recording mandatory.
   SIP Options	Enter a list of SIP options that you want.

1. Access the Accounting configuration object: Configuration, Management, Accounting.
2. In the Account Config dialog, do the following:

   Strategy	Select the lookup algorithm from the drop-down list for the accounting server.
   Protocol	Select a protocol from the drop-down list.
   State	Select to enable call accounting.
   Generate Start	Select an event trigger from the drop-down list for session accounting recording .
   Generate Interim	Click Add, and select one or more events to collect in a session. Default: Reinvite-Response.
   Generate Event	Click Add, and select one or more Diameter events to collect in a session. Leave blank to disable.
   File Output	Select to enable active writing of comma delimited records.
   File Path	Enter the local, comma delimited CDR output storage directory. Do not use /boot or /code file systems. Default: /opt/logs/.
   File Rotate Time	Enter a number for the time, in minutes, for the file rotation interval. Range: 0-2147483647.
   Options. Add optional parameters.	Click Add, and enter one or more options.
   FTP Push	Select to push files to an FTP server.
   FTP Address	Enter the IPv4 address of the FTP server.
   FTP User	Enter the FTP server User Name.
   FTP Password	Enter the FTP server Password.
   FTP Remote path	Enter the remote FTP server path for comma delimited CDR files.
   Push Receiver	Click Add, and do the following: Server—Enter the server IP address. Port—Enter the server port. Range: 1-65535. Admin state—Select to enable. Remote path—Enter the remote path name. File name prefix—Enter the prefix for file names pushed to the server. Priority—Enter the priority of the push receiver. Range 0 (highest)-4 (lowest). Protocol—Select a protocol from the drop-down list for pushing to the server. Enter the server User Name. Enter the server Password, and click Set. Public key—Enter the public key. Click OK.
   CDR Output Redundancy	Select to enable.
   Interim State ID Type	Click Add, and select one or more interim state ID types.
   Account Servers	Click Add, and do the following: Hostname—Enter the hostname of the remote server. Min round trip—Enter the minimum time allowed to and from the remote server in milliseconds. Range: 10-5000. Max inactivity—Enter the maximum time allowed for remote server inactivity in seconds. Range: 1-300. Restart delay—Enter the delay time before retrying an inactive remote server in seconds. Range: 1-300. Bundle vsa—Select to enable. Secret—Enter the authentication secret. NAS ID—Enter the remote network accounting server ID. Domain name sufix—Enter the suffix to use for all domain names. Watchdog ka timer— Enter the time interval for keep alive messages in seconds. Range: 0, 6-65535. Diameter in manip—Enter the inbound Diameter manipulation to apply. Diameter out manipv—Enter the outbound Diameter manipulation to apply. Click OK.
   Prevent Duplicate Attrs	Select to enable preventing duplicate accounting attributes.
   VSA ID Range	Enter a comma delimited range of accounting attributes to include in CDRs. Note: Blank means that all attributes are included.
   CDR Output Inclusive	Select to enable the inclusion of all empty fields.
   Diam Attr ID Range	Enter a comma delimited range of accounting attributes to include in Diameter Rf accounting records. Note: Blank means that all attributes are included.
   Msg Queue Size	Enter the maximum number of accounting records to store in memory. Default: 5000. Range: 5000-150000.
   Diam Send Throttle	Enter the maximum number of accounting records to send to the Diameter server without yielding to other tasks. Default 20. Range: 2-20.
   Diam Srv Ctx Rel	Enter the 3GPP release number of the service specific document.
   Diam Srv Ctx Mnc Mcc	Enter the Mobile Country Code / Mobile Network Code tuple. Format: MNC.MCC.
   Diam Srv Ctx Ext	Enter the operator-specific extension information.
   Diam Ssrvc Attr ID Range	Enter a comma delimited range of Acme accounting attributes to include in Diameter Rf accounting records. Note: Blank means that all attributes are included.
   Max ACR Retries	Enter the maximum number of ACR retries. Range: 0-4.
   ACR Retry Interval	Enter the interval time between ACR retries in seconds. Default: 10. Range: 5-20.

3. Click OK.
4. Save the configuration.

Configure a Simple Network Management Protocol (SNMP) community to support the monitoring of devices, such as the Oracle® Enterprise Session Border Controller (E-SBC), attached to the network for conditions that warrant administrative attention.

1. Access the SNMP Community configuration object: Configuration, Management, SNMP Community.
2. On the SNMP community page, click Add, and do the following:

   Community Name	Enter an SNMP community name of an active community where this E-SBC can send and receive SNMP information.
   Access Mode	Select the access level for all Network Management Systems (NMS) defined within this SNMP community.
   IP Address	Enter an Pv4 address that is valid within this SNMP community.

3. Click Close.
4. Save the configuration.

You can define one or more SNMP trap receivers on an Oracle® Enterprise Session Border Controller (E-SBC) for redundancy or to segregate alarms with different severity levels to individual trap receivers.

1. Access the Trap Receiver configuration object: Configuration, Management, Trap Receiver.
2. On the Trap receiver page, click Add.
3. On the Add trap receiver page, do the following.

   IP Address	Enter the IPv4 address and port number of an authorized NMS in dotted decimal format. Default: 0.0.0.0:162.
   Filter Level	Select the filter level threshold from the drop-down list that indicates the severity level at which a trap is sent to the trap receiver.
   Community Name	Enter the SNMP community name to which this trap receiver belongs.

4. Click OK.
5. Save the configuration.

The Web server is a software application that helps to deliver Web content that you can access through the Internet. The Web server runs the Enterprise application called the Web GUI.

Every Web server has an IP address and sometimes a domain name. For example, if you enter the URL http://www.acmepacket.com/index.html in your browser, the browser sends a request to the Web server with domain name is acmepacket.com. The server fetches the page named index.html and sends it to the browser.

If you enter http://132.45.6.5, and this address has been configured by your Administrator to access the Web GUI, the server fetches the page and displays the Web GUI logon page to your browser.

Host routes let you insert entries into the Oracle® Enterprise Session Border Controller (E-SBC) routing table. These routes affect traffic that originates at the E-SBC host process. Host routes are used primarily for steering management traffic to the correct network.

When traffic is destined for a network that is not explicitly defined on an E-SBC, the default gateway is used. If you try to route traffic to a specific destination that is not accessible through the default gateway, you need to add a host route. Host routes can be thought of as a default gateway override.

Certain SIP configurations require that the default gateway is located on a front media interface. In this scenario, if management applications are located on a network connected to a rear-interface network, you need to add a host route for management connectivity.

When source-based routing is used, the default gateway must exist on a front media interface. Host routes might be needed to reach management applications connected to a wancom port in this kind of situation.

The Network Interface configuration object specifies a logical network interface. In order to use a network port on a network interface, you must configure both the physical interface and the corresponding network interface configuration elements.

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.

1. Access the Media Profile configuration object: Others, Media profile.
2. On the Media Profile page, do the following.

   Name	Set the name for this media profile. For example, PCMU, G723, G729. Valid values: Alpha-numeric characters.
   Subname	Set the encoding sub-name used for the Codec variation. Valid values: Alpha-numeric characters. You must use a combination of alpha and numeric characters.
   Media Type	Set the media type to use in SDP m lines. For example, audio, video, data.
   Payload Type	Set the payload type to use in SDP media lines. Valid values: Alpha-numeric characters. Note: The Payload type value must be numeric if you use the RTP/AVP transport method.
   Transport	Set the transport protocol to use in the SDP RTPMAP attribute. Default: RTP/AVP. Valid values: RTP/AVP | UDP.
   Clock Rate	Set the clock rate to use in the SDP RTPMAP attribute in Hz. For example, 8000 in narrowband Codecs and 16000 in wideband Codecs. Range: 0-4294967295. Note: When configured with 0, the default, the system uses the clock rate for the Codec.
   Req Bandwidth	Set the amount of bandwidth required in Kilobits. Range: 0-999999999.
   Frames per Packet	Enter the maximum number of frames per packet. Range: 0-256.
   Parameters	Add one or more parameters. Note: For each parameter, use the + character to add and the - character to remove. For example, +silenceSupression=0.
   AS Bandwidth	Set the SDP b=AS value for this codec. Default: 0. Range: 0-4294967295.

3. Click OK.
4. Save the configuration.

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.

1. Access the Translation Rules configuration object: Configuration, Others, Translation rules.
2. On the Translation rules page, click Add, and do the following:

   ID	Enter a descriptive ID name for this translation rule. Valid values: Alpha-numeric characters.
   Type	Select the one of the following translation rules that you want to from the drop-down list. Add—Adds a character or string of characters to the address. Delete—Deletes a character or string of characters from the address. None—(Default) Disables the translation rule function. Replace—Replaces a character or string of characters within the address.
   Add String	Enter the index for the Add string. Use the $ character to append the string at the end of the address. Valid values: 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: Alpha-numeric characters.
   Delete String	Enter the string that you want deleted from the original address during address translation. Denote unspecified characters with the @ character. Valid values: 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 Delete string.

3. Click OK.
4. Save the configuration.

Use the SIP Feature configuration object 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.

1. Access the SIP Features configuration object: Configuration, Others, Sip Features.
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. Default: Strip. Valid values: Pass | Strip.
   Require Mode Inbound	Select the action tag in the Require header for an inbound packet from the drop-down list. Default: Reject. Valid values: Pass | Reject.
   Proxy Require Mode Inbound	Select the action tag in the Proxy-Require header in an inbound packet from the drop-down list. Default: Reject. Valid values: Pass | Reject.
   Support Mode Outbound	Select the action tag in the Supported header in an outbound packet from the drop-down list. Default: Pass. Valid values: Pass | Strip.
   Require Mode Outbound	Select the action tag in the Require header for an outbound packet from the drop-down list. Default: Reject. Valid values: Pass | Reject.
   Proxy Require Mode Outbound	Select the action tag in the Proxy-Require header for an outbound packet from the drop-down list. Default: Pass. Valid values: Pass | Reject.

3. Click OK.
4. Save the configuration.

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

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.

1. Access the SPL configuration object: Configuration, Other, SPL.
2. In the SPL Config dialog, do the following:

   State	Select State to enable the plugin.
   Name	Enter the name of plugin to load.

3. Click OK.
4. Save the configuration.

The Oracle® Enterprise Session Border Controller provides a configuration element data field referred to as a tag. You enter information into the tag field for descriptive and grouping purposes. You can establish your own criteria for labeling configuration elements with these tags. Tag fields have no operational effect on signaling services.

The following configuration objects display the Tags text field:

• Agents
• Users
• Routes

You can enter any text that you want into the field and you can apply as many tags to a configuration object as needed. You can filter the element list searches using tags as a means of organizing these objects. Applicable element list search fields include a down arrow that exposes a tag drop-down list, from which you select the tag on which to filter the list. Tags have no operational function other than supporting this kind of filtering.

Codec policies describe how to manipulate SDP messages as they cross the Oracle® Enterprise Session Border Controller (E-SBC). The E-SBC bases its decision to transcode a call on codec policy configuration and the SDP. Each codec policy specifies a set of rules to be used for determining which codecs are retained or removed, and how they are ordered within SDP.

When configuring transcoding, you create a codec policy and associate the policy to a realm. In the codec policy, you specify:

• Which codecs to allow and which codecs to deny within a realm.
• Which codecs to add to the SDP m= lines for an egress realm.
• The preferred order of codecs shown in an SDP m= line.
• The packetization time to enforce within a realm for transrating.

You can limit throughput bound for DNS ALG by using the DNS ALG Constraints configuration element. The system performs message throttling on request messages, and the responses are automatically throttled because DNS-ALG is transaction stateful. The system displays a list of configured DNS ALG Constraints in the DNS Config dialog, which allows you to create constraint profiles and apply them to multiple DNS configuration objects.

1. Access the DNS ALG Constraints configuration object: Configuration, Media Manager, DNS ALG Constraints.
2. On the DNS ALG Constraints page, click Add.
3. On the Add DNS ALG Constraints page, do the following:

   Name	Enter a unique name for this constraint.
   State	Select to enable.
   Max Burst Rate	Set the maximum burst rate in requests per second. Default: 0. (0 = unlimited.) Range: 0-4294967295.
   Max Sustain Rate	Set the maximum sustain rate in requests per second. Default: 0. (0 = unlimited.) Range: 0-4294967295.
   Max Inbound Burst Rate	Set the maximum inbound burst rate in requests per second. Default: 0. (0 = unlimited.) Range: 0-4294967295.
   Max Inbound Sustain Rate	Set the maximum inbound sustain rate in requests per second. Default: 0. (0 = unlimited.) Range: 0-4294967295.
   Max Outbound Burst Rate	Set the maximum outbound burst rate in requests per second. Default: 0. (0 = unlimited.) Range: 0-4294967295.
   Max Outbound Sustain Rate	Set the maximum outbound sustain rate in requests per second. Default: 0. (0 = unlimited.) Range: 0-4294967295.
   Time to Resume	Set the time to wait, in seconds, after the constraints are exceeded to resume monitoring. Default: 0. (0 = unlimited.) Range: 0-4294967295.
   Burst Rate Window	Set the time, in seconds, over which to compute the burst rate. Default: 0. (0 = unlimited.) Range: 0-4294967295
   Sustain Rate Window	Set the time, in seconds, over which to compute the sustain rate. Default: 0. (0 = unlimited.) Range: 0-4294967295.
   Max Latency	Set the maximum round trip time, in seconds. Default: 0. (0 = unlimited.) Range: 0-4294967295.

4. Click OK.
5. Save the configuration.

Use the DNS Config element to configure the DNS ALG service.

1. Access the DNS Config configuration object: Configuration, Media Manager, DNS Config.
2. On the Add DNS Config page, to the following:

   Client Realm	Select the realm from the drop-down list from which the system receives DNS queries.
   Description	Enter a description of this configuration.
   Constraint Name	Select a DNS-ALG constraint from the drop-down list to apply to this configuration.
   Trap on Status Change	Select to enable. Default: Disabled.
   Extra DNSALG Stats	Select to enable. Default: Disabled.
   DNS Max TTL	Set the maximum number of TTL seconds for a DNS response. Default: 86400. Range: 30-2073600.
   Client Address List	Click Add to add one or more client address lists, and do one of the following: Click OK. Click Apply/Add another, add another client address list, and click Click OK. Repeat as needed.
   Server DNS Attributes	Click Add to add server DNS attributes, and do the following: Server Realm—Select the server realm from the drop-down list. Domain Suffix—Click Add, add a domain suffix list and click OK, or add another domain suffix list, click OK, and repeat as needed. Server Address List—Click Add, add a server address list and click OK, or add another server list, click OK, and repeat as needed. Source Address—Enter the source IPv4 address. Source Port—Enter the source port. Range: 1025-65535. Transaction Timeout—Enter the time in seconds for the DNS transaction timeout. Range: 0-999999999. 0 = unlimited. Address Translation—Click Add, enter the Server Prefix and Client Prefix.

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

Interactive Connectivity Establishment - Session Traversal Utility for NAT (ICE STUN lite mode) enables a Advanced Media Termination client to perform connectivity checks, and can provide several STUN servers to the browser. ICE STUN support requires configuring an ICE Profile under Realm Config, where you define the STUN behavior.

1. Access the ICE Profile configuration object: Configuration, Media Manager, ICE Profile.
2. In the Add ICE Profile dialog, do the following:

   Name	Set a unique name for this ice profile. Default: Empty.
   Stun Conn Timeout	Set the maximum time interval, in seconds, between the first STUN binding request received in a media session and the time when a valid STUN binding request containing the USE CANDIDATE attribute is received. Default: 10. Range: 0-9999.
   Stun Keepalive Interval	Set the interval, in seconds, since the last media packet or STUN binding request response after which a STUN keep alive message is sent. Default: 15. Range: 0-300. Zero means do not send keep-alive messages. The value must be less than the value set for subsq-guard-timer.
   Stun Rate Limit	Set the number of STUN binding requests that you want the SBC to process per minute. Default: 100. Range: 0-99999. Zero means impose no limit.

3. Click OK.

Use the Media Manager element to define parameters used in the media steering functions performed by the Oracle® Enterprise Session Border Controller, including the flow timers.

1. Access the Media Manager configuration object: Configuration, Media Manager, Media Manager.
2. On the Media Manager page, do the following:

   State	Select to enable Media Manager.
   Flow Time Limit	Enter the time limit, in seconds, for a media flow. Default: 86400. Range: 0-4294967295.
   Initial Guard Timer	Enter the time limit, in seconds, for a media flow guard timer. Default: 300. Range: 0-4294967295.
   Subsq Guard Timer	Enter the time limit, in seconds, for a subsequent media flow guard timer. Default: 300. Range: 0-4294967295.
   TCP Flow Time Limit	Enter the time limit, in seconds, for a TCP flow. Default: 86400. Range: 0-4294967295.
   TCP Initial Guard Timer	Enter the time limit, in seconds, for the initial TCP flow. Default: 300. Range: 0-4294967295.
   TCP Subsq Guard Timer	Enter the time limit, in seconds, for a subsequent TCP flow. Default: 300. Range: 0-4294967295.
   Hnt RTCP	Select to enable RTCP for hosted NAT traversal.
   ALGD Log Level	Select an ALGD log level from the drop-down list. Default: NOTICE.
   MBCDLog Level	Select an MBCD log level from the drop-down list. Default: NOTICE.
   Options	Add any optional parameters.
   Red Max Trans	Set the number of redundancy sync transactions to keep. Default: 10000. Range: 0-50000.
   Red Sync Start Time	Set the timeout for checking the transition from standby to active. Default: 5000. Range: 0-4294967295.
   Red Synch Comp Time	Set the timeout for subsequent synch requests after a redundancy synch occurred. Default: 1000. Range: 0-4294967295.
   Media Policing	Select to enable per session traffic rate policing in a media gateway. Default: Enabled.
   Max Untrusted Packet Rate	Enter the maximum untrusted signaling bandwidth allowed to the host path in bytes per second. Range: 20-200000.
   Max Trusted Packet Rate	Enter the maximum trusted signaling bandwidth allowed to the host path in bytes per second. Range 20 to 200000.
   Max ARP Packet Rate	Enter the maximum bandwidth that can be used by an ARP message. Default: 10. Range: 20 to 10000.
   Tolerance Window	Set the tolerance window size in seconds for measuring host access limits. Default: 30. Range: 0-4294967295.
   Trap on Demote to Deny	Select to generate a trap when the endpoint is demoted from untrusted to deny. Default: Disabled.
   Trap on Demote to Untrusted	Select to generate a trap when the endpoint is demoted from trusted to untrusted. Default: Disabled.
   Syslog on Demote to Deny	Select to generate Syslog when the endpoint is demoted from untrusted to deny. Default: Disabled.
   Syslog on Demote to Untrusted	Select to generate Syslog when the endpoint is demoted from trusted to untrusted. Default: Disabled.
   Anonymous SDP	Select to enable the Use Name and Session Name fields in Session Description Protocol (SDP). Default: Disabled.
   Translate Non rfc283 Event	Select to accept UII/INFO events for Inter-working Function (IWF), although RFC2833 is preferred. Default: Disabled.
   Syslog on Call Reject	Select to enable Syslog on SIP call rejection.

3. Click OK.
4. Save the configuration.

Use the Media Policy element to configure the Type of Service (TOS) and Differentiated Services (DiffServ) values that define a type or class of service. Apply the media policy to one or more realms.

1. Access the Media Policy configuration object: Configuration , Media Manager, Media Policy.
2. On the Media Policy page, click Add.
3. On the Add Media Policy page, do the following:

   Name	Enter a name for this media policy.
   TOS settings	Click Add.
   Add Media Policy / ToS Settings	Media Type—Enter any IANA-defined media type to use for this group of TOS settings. Range: 1-255 characters. Not case-sensitive. Media Sub Type—Enter any IANA-defined media sub-type for the media type. Range: 1-255 characters. Not case-sensitive. ToS value. Enter a list of TOS values for this policy. You can specify one or more audio media types and one or more video med a types. Use decimal (0.0) or hexadecimal number (0x00) format. Default is hexadecimal 0x00. Media Attributes—Click Add, and enter a list of one or more media attributes to match in the Session Description Protocol (SDP). Range: 1-255 characters. Case-sensitive. When entering more than one media attribute value, use a comma separator.

4. Click OK.
5. Save the configuration.

Use the Realm Config element to configure a realm for the Oracle® Enterprise Session Border Controller (E-SBC).

1. Access the Realm Config configuration object: Configuration, Media Manager, Realm Config, Add.
2. In the Realm Config object, do the following:

   Identifier	Enter the name of the realm.
   Description	Enter a description of this realm.
   Addr Prefix	Enter the IPv4 or IPv6 address and subnet mask combination to set the criteria the E-SBC uses to match packets sent or received on the network interface associated with this realm.
   Network Interfaces	Enter the physical and network interfaces through which this realm can be reached for ingress and egress traffic. Entries in this parameter take the form: (network-interface-ID):(subport). Only one network interface is allowed per realm-config object.
   Mm in Realm	Select to enable steering media through the E-SBC, when the communicating endpoints are located in the same realm.
   Mm in Network	Select to enable the E-SBC to trust media within realms with the same subnet mask as theE-SBC.
   Mm Same Ip	Select to enable media managing for endpoints behind the same IP address.
   QoS Enable	Select to enable the use of QoS in this realm.
   Max Bandwidth	Enter the maximum bandwidth for dynamic flows to and from this realm in kilobits per second.
   Max Priority Bandwidths	Enter the maximum priority bandwidth for dynamic flows to and from this realm in kilobits per second.
   Parent Realm	Enter the parent realm, if this is a nested realm.
   DNS Realm	Enter the name of the DNS realm for this realm.
   Media Policy	Select a default media-policy on a per-realm basis. This parameter must correspond to a valid name entry in a media policy element.
   Media Sec Policy	Enter the name of the default media security policy.
   RTCP Mux	Select to enable RTCP multiplexing negotiation. Default: disabled. Valid values disabled | enabled.
   ICE Profile	Specify an existing ICE profile. Default: none.
   SRTP MSM Passthrough	Select to enable the inclusion of information for multi-system SRTP passthrough.
   Class Profile	Enter the name of class-profile to use for this realm for ToS marking.
   InTtranslationid	Enter the name of a session-translation element. Only one is allowed.
   Out Translationid	Enter the name of a session-translation element. Only one is allowed.
   Average Rate Limit	Enter the average data rate limit in bytes per second.
   Access Control Trust Level	Select a trust level for the host within the realm.
   Invalid Signal Threshold	Enter the allowed invalid signalling message rate within the tolerance time period.
   Maximum Signal Threshold	Enter the allowed signalling message rate within the tolerance time period.
   Untrusted Signal Threshold	Enter the maximum number of untrusted signalling messages within the tolerance time period.
   NAT Trust Threshold	Enter the number of endpoints behind the NAT device that must be denied.
   Max Endpoints per NAT	Enter the maximum number of endpoints allowed behind a NAT device.
   NAT Invalid Message Threshold	Enter the allowed number of invalid messages from behind a NAT device.
   Wait Time for Invalid Register	Enter the time period, in seconds, for the E-SBC to wait before counting the absence of the REGISTER message as an invalid message.
   Deny Period	Enter the number, in seconds, for the time period to block denied dynamic entries.
   Untrust CAC Failure Threshold	Enter the maximum number of untrusted CAC failures in the time period.
   Subscription ID Type	Select a subscription ID type from the drop down list.
   Early Media Allow	Select the early media handling policy from the drop down list.
   Enforcement Profile	Select the enforcement profile from the drop down list.
   Additional Prefixes	Select or add an additional address prefix to use. Omit the number of bits for an exact match.
   Restricted Latching	Select a restricted latching mode.
   Options	Enter one or more optional features and parameters.
   SPL Options.	Enter one or more SPL options.
   Delay Media Update	Select to enable media update delay support for this realm.
   Refer Call Transfer	Select the refer call transfer mode for this realm.
   Hold Refer Reinvite	Select to enable the hold-refer-reinvite option. Default: Disabled.
   Refer Notify Provisional	Select the provisional mode for sending a NOTIFY message from the drop down list. Default: None. Valid values: None | Initial | All.
   Dyn Refer Term	Select to enable terminating refer call transfer for this realm. Default: Disabled.
   Codec Policy	Set the codec policy mode for this realm from the drop down list.
   Codec ManIP in Realm	Select to enable codec manipulation support for this realm. Default: Disabled.
   Codec ManIP in Network	Select to enable codec policy for this network. Default: Disabled.
   RTCP policy	Select the RTCP policy for this realm.
   Constraint Name	Select the name of a constraint for this realm from the drop down list.
   Call Recording Server ID	Enter the name of the call recording server.
   Session Recording Server	Select a recording server or recording server group.
   Session Recording Required	Select to enable session recording for this realm.
   QoS Constraint	Enter the name of a QoS constraint.
   TCP Media Profile	Select a TCP media profile for this realm.
   Monitoring Filters	Add a comma-separated list of monitoring filters for this realm. Use + to add the list. Use - to remove the list. Excluding + or -, replaces the list.
   Node Functionality	Select a node function from the drop down list.

3. Save the configuration.

Use the steering-pool element to define sets of ports used to steer media flows through the Oracle® Enterprise Session Border Controller to provide packet steering to ensure a level of quality or a routing path.

1. Access the Steering Pool configuration object: Configuration, Media Manager, Steering Pool.
2. On the Steering Pool page, do the following:

   IP Address	Enter the IP address of the generated pool.
   Start Port	Enter the port number that begins the range of ports available to this steering pool. Range:1-65535.
   End Port	Enter the port number that ends the range of ports available to this steering pool. Range:1-65535.
   Realm ID	Select the realm from the drop-down list from which media flows are allowed for this steering pool.
   Network Interface	Select the network interface from the drop-down list to which this steering pool directs media.

3. Save the configuration.

The TCP Media Profile defines media operations in a realm. You can create multiple TCP Media Profiles, for example, to assign to different realms.

1. Access the TCP Media Profile configuration object: Configuration, Media Manager, TCP Media Profile, Add.
2. On the Add TCP media profile page, enter a Name for this profile. Required before you can proceed.
3. Under Profile List, click Add.
4. On the Add TCP media profile / profile entry page, do the following:

   Media type	Set the media type subject to this profile. Default: message. Keep the default value for MSRP operations.
   Transport Protocol	Set the Transport Layer Protocol (TLS) that you want for this profile. Use either TCP/MSRP to specify unsecured TCP traffic or TCP/TLS/MSRP to specify secured and encrypted TLS traffic.
   Listen Port	Set the TCP port to use for incoming B2BUA MSRP connections. Range: 0-65535. Default: 0, which tells the B2BUA to choose the port from the steering pool of the realm associated with this profile.
   Preferred Setup Role	Set the value the B2BUA uses for the a=setup attribute when negotiating the setup role. Valid values: Active (Allows the B2BUA to create an outgoing connection.) | Passive. Default: Passive (Allows the B2BUA to accept an incoming connection.) Oracle recommends Passive.
   TLS Profile	If you set TCP/TLS/MSRP for transport-protocol, select a TLS profile that specifies cryptographic resources available to support TLS operations.
   Require Fingerprint	If you set TCP/TLS/MSRP for transport-protocol, enable TLS fingerprint for endpoint authentication using the certificate fingerprint methodology defined in RFC 4572 Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP).. Valid values: enabled | disabled. Default: disabled.
   MSRP CEMA Support	Specify whether or not the SBC negotiates support for the CEMA extension (RFC6714) for TCP or TLS connections to and from the realm associated with the current TCP media profile. Enable the CEMA extension to enable the SBC to exchange MSRP traffic through middleboxes that anchor the media, but do not touch the SDP a:path attribute. Valid values: enabled | disabled. Default: disabled.
   MSRP Sessmatch	Specify whether or not the SBC validates the MSRP To-Path header based only on the session-id field and MSRP transport type of the MSRP URI (and not also on the IP address and port number in the authority part of the MSRP URI). Sessmatch enables the SBC to exchange MSRP traffic through Middleboxes that anchor the media and also adjust the SDP a=path attribute. Valid values: enabled | disabled. Default: disabled.
   MSRP Message Size Enforce	Specify one element in a whitelist of allowed MSRP media types. Media types not included on the whitelist will be removed from the SDP a=accept-types attribute of the SDP offers. A "*" indicates that all MSRP media types are allowed. When left empty, it indicates that no media types filtering is performed. Valid value: MsrpMediaTypeList.
   MSRP Message Size	Specify the maximum size (in bytes) that MSRP is allowed to negotiate for the messages. It represents the maximum limit for the SDP a=max-size attribute, for the "size" token of the SDP a=file-selector attribute and MSRP Byte-range header. A value of 0 indicates that no maximum limit is enforced. Valid values: 0-4,000. Default: 0.
   MSRP Message Size File	Specify whether MSRP messages exceeding the negotiated size are rejected, respectively whether MRSP file transfers will be aborted when the negotiated size is exceeded. A value of 0 indicates that no maximum limit is enforced. Valid values: 0-4G. Default: 0.
   MSRP Types Whitelist	Specify a list of registered MSRP media types (RFC4975) supported for the ingress realm.

5. Click OK.
6. Click Back.
7. (Optional) Repeat the preceding steps to configure another tcp-media-profile.
8. Save the configuration.

The Oracle® Enterprise Session Border Controller (E-SBC) supports VoIP calls through the browser-based, real-time communication known as Advanced Media Termination. Using W3C and IETF standards, Advanced Media Termination supports cross-browser video calls and data transfers, such as browser-based VoIP telephony and video streaming. Advanced Media Termination allows users to make and receive calls from within a web browser, relieving the need to install a soft phone application. With Advanced Media Termination, the E-SBC can enable users to communicate concurrently with one or more peers through various browsers and devices to stream voice and data communications in real-time through a variety of web applications. Advanced Media Termination also supports communications through end-user clients such as mobile phones and SIP User Agents.

The Oracle® Enterprise Session Border Controller (E-SBC) can record user actions in audit logs by way of the Web GUI. The audit logs record the creation, modification, and deletion of all user-accessible configuration elements, as well as attempted access to critical security data such as public keys. For each logged event, the system provides the associated user-id, date, time, event type, and success or failure data.

You can configure the system to record audit log information in either verbose mode or brief mode. Verbose mode captures the system configuration after every change, and displays both the previous settings and the new settings in addition to the event details. Brief mode displays only the event details. Although you can specify the recording mode, you cannot specify which actions the system records. The following list describes the actions that the system records.

The system writes audit log events in Comma Separated Values (CSV) lists in the following format:

{TimeStamp,
src-user@address:port,Category,EventType,Result,Resource,Prev,
Detail}

The following list describes each value written to an audit log event.

As the E-SBC records audit log data, users with admin privileges can read, copy, and download that information from the Web GUI. No one can delete or edit the original log. You can View, Refresh, and Download audit logs by way of the System tab. Go to Audit Log under File Management.

The E-SBC transfers the audit logs to a designated directory on the target SFTP server. The audit log file is stored on the target SFTP server with a filename in the following format: audit<timestamp>. The timestamp is a 12-digit string the YYYYMMDDHHMM format.

The single instance SSH Config configuration element specifies SSH re-keying thresholds.

1. Access the SSH Config configuration object: Configuration, Security, Admin Security, SSH Config.
2. In SSH Config, do the following:

   Rekey Interval	Set the time in minutes after which the E-SBC re-keys an SSH or SFTP session. Default: 60. Range: 60-600.
   Rekey Byte Count	Set the number of bytes transmitted, in powers of 2, before re-keying an SSH or SFTP session. For example, entering a value of 24 sets this parameter to 2^24 (16777216) bytes. Default: 31. Range: 20-31.
   Proto Neg Time	Set the time in seconds to complete the SSH protocol negotiation, establishing the secure connection. Default: 60. Range: 30-60.
   Keep Alive Enable	Enable the TCP keepalive timer. Default: enabled. Valid Values: enabled | disabled.
   Keep Alive Idle Timer	Set the interval in seconds between the last data packet sent and the first keepalive probe. Default: 15. Range: 15-1800.
   Keep Alive Interval	Set the interval in seconds between two successful keepalive transmissions. Default: 15. Range: 15-120.
   Keep Alive Retries	Set the number of retransmission attempts before the E-SBC declares the remote end unavailable. Default: 2. Range: 2-10.

3. Save the configuration.

The Web GUI supports TACACS+ authentication.

TACACS+ provides access control for routers, network access servers, and other networked computing devices by way of one or more centralized servers. The Oracle® Enterprise Session Border Controller (E-SBC), supports TACACS+ authentication and limited accounting services. For accounting services support, the E-SBC supports only authentication success and failure. The E-SBC does not support TACACS+ authentication.

Security configuration from the web GUI consists of creating the building blocks used to establish TLS-secured paths for signaling traffic.

The Certificate Records and TLS Profile configurations are located under Security on the Configuration page. Apply TLS profiles to SIP interfaces in the SIP Interface configuration under Session Router.

You can perform the following certificate management tasks from the Web GUI in either Basic Mode or Advanced Mode. The process for configuring certificates on the Oracle® Enterprise Session Border Controller (E-SBC) includes the following steps:

1. Configure a Certificate Record on the E-SBC. See Add a Certificate Record.
2. Generate a Certificate request by the E-SBC. See Generate a Certificate Request.
3. Import a Certificate into the E-SBC. See Import a Certificate.
4. Reboot the system.

Use the SPL Config element to configure the parameters for integrating System Programming Language (SPL) plug-in extensions with the Oracle® Enterprise Session Border Controller (E-SBC).

1. Access the SPL Config configuration object: Configuration, System, SPL Config.
2. On the SPL Config page, do the following:

   SPL Options	Enter values for optional SPL parameters and features in a comma separated list enclosed in double quotation marks.
   Plugins	Click Add, and do the following: State. Select to enable the SPL plug-in on the E-SBC. Name. Specify the name of the SPL plug-in. Click OK.

3. Click OK.
4. Save the configuration.

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

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

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.

1. Access the H.323 Config configuration object:
   Configuration, Session Router, H323, H323 Config.
2. On the H323 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.

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

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

1. From the Web GUI, click Configuration, Session Router, IWF Config.
2. On the IWF Config page, do the following:

   State	Select to enable IWF to translate SIP and H.323 sessions. Default: Disabled.
   Media Profiles	Select the media profiles that you want to use for IWF translations. Valid values: An SDP codec or a telephone event if you want the SBC to support DTMF.
   Logging	Select to enable the SBC to log SIP messages related to the IWF. Default: Disabled.
   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	Enter an optional feature or parameter.
   Forward Source Call Address	Select to enable adding the H225SourceCallSignalAddress IP for IWF to egress SIP INVITEs.

3. Click OK.
4. Save the configuration.

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 Advanced mode to create and enable an LDAP configuration on the E-SBC.

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, 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 signaling.
   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 and local policy attributes for session routing based on the next hop parameter.

1. From the Web GUI, click Configuration, Session Router, Local Policy.
2. On the Local Policy page, do the following:

   From Address	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	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	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. Default: Enabled.
   Policy Priority	Select the policy priority for this local policy from the drop-down list. Default: None. Valid values: None | Normal | Non-urgent | Urgent | Emergency.
   Next Hop	Enter the signaling host IP address, SAG, hostname, or ENUM Config
   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. Default: None. Valid values: None | Replace URI | Redirect.
   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. Valid Values: 0-9999999.
   State	Select to enable.
   App Protocol	Select the application protocol for signaling the session agent from the drop-down list. Default: None. Valid values: Agent | SIP | H323 | MGCP | H248 | BGF | BFD | SCF | RTSP | DD | Diameter | IKE | None | " ".
   Methods	Enter a list of SIP methods to match with a SIP request method. Double quote the list with a comma between methods. Valid values: INFO | INVITE | MESSAGE | NOTIFY | OPTIONS | PRACK | PUBLISH | REFER | REGISTER | SUBSCRIBE.
   Lookup	Select an additional local policy lookup from the drop-down list. Default: Single. Valid values: Single | Multi.
   Next Key	Enter the next stage key for multi-stage local policy lookups.

3. Click OK.
4. Save the configuration.

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.

1. Access the Local Response Map configuration object: Configuration, Session Router, 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. Default: 0. Range: 100-699.
   Q850 Cause	Enter a Q850 cause code. Default: 0. 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. Default: 0. Range: 0-999999999.

3. Click OK.
4. Save the configuration.

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

• From the Web GUI, click Configuration, Session Router, Session Agent.
• On the session-agent page, click Add, and 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. Default: 5060. Range: 1025-65535. If you enter zero, the E-SBC cannot initiate communication with this agent (although it can accept calls). 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. Default: Enabled.
  App Protocol	Select the protocol to use to signal the session agent. Default: SIP. Valid values: SIP | H323.
  App Type	Select the type of application from the drop-down list. Valid values: " " | H323 -GW | H323-GK.
  Transport Method	Select the transport mode for connections to this agent. DTLS Dynamic TCP Dynamic TLS Static SCTP Static TCP Static TLS TLS+DTLS UDP - Default UDP+TCP
  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.
  Match Identifier	Click Add, and do the following: Identifier Rule—Specify the session agent identifier rule to use to identify this agent when not matching by IP address. Match Value—Enter the value to match in the SIP header field that identifies this session agent.
  Max Sessions	Enter the maximum number of sessions allowed for this constraint. Default: 0. Valid values: 0-999999999.
  Max Inbound Sessions	Enter the maximum number of inbound sessions allowed from this session agent. Default: 0. Valid values: 0-999999999.
  Max Outbound Sessions	Enter the maximum number of outbound sessions allowed for this constraint. Default: 0. Valid values: 0-999999999.
  Max Burst Rate	Enter the maximum number of invites allowed in a burst time period. Default: 0. Valid values: 0-999999999.
  Max Inbound Burst Rate	Enter the maximum inbound burst rate in INVITEs per second from this session agent. Default: 0.Valid values: 0-999999999.
  Mac Outbound Burst Rate	Enter the maximum outbound burst rate in INVITEs per second from this session agent. Default: 0. Valid values: 0-999999999.
  Max Sustain Rate	Enter the maximum rate of session invitations allowed within the current time period for this constraint. Default: 0. Valid values: 0-999999999.
  Max Inbound Sustain Rate	Enter the maximum inbound sustain rate of session invitations allowed within the current time period for this constraint. Default: 0. Valid values: 0-999999999.
  Max Outbound Sustain Rate	Enter the maximum outbound sustain rate of session invitations allowed within the current time period for this constraint. Default: 0. Valid values: 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. Default: 0. Valid values: 0-999999999
  In Service Period	Enter the number of seconds that this session agent is allowed to re-initialize before returning to in-service status. Default: 0. Valid values: 0-999999999
  Burst Rate Window	Enter the time period, in seconds, used to measure the burst rate. Default: 0. Valid values: 0-999999999.
  Sustain Rate Window	Enter the time period, in seconds, used to measure the sustained rate. Default: Valid values: 0. 0-999999999.
  Proxy Mode	Select a proxy mode for the E-SBC to use when a SIP request arrives from this agent Proxy—Forward requests. Redirect—Return redirect (3xx) responses. Proxy Record Route—Forward proxy requests with Record Route. (Stateless and transaction modes, only.)
  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 loose routing.
  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. Default: 0. Valid values: 0-4294967295.
  Ping Send Mode	Select the mode for pinging this session agent. Default: Keep alive. Continuous Keep alive
  Ping All Addresses	Select to ping all addresses from the DNS query.
  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.
  Trust Me	Select to trust this agent. Default: Disabled.
  Local Response Map	Select a local response map for this agent.
  In Manipulation ID	Select the in bound manipulation ID.
  Out Manipulation ID	Set the outbound manipulation 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 trunk group name and context to use as the default context to reach this agent. For example: tgname1:tgcontext1.
  Max Register Sustain Rate	Enter the maximum register sustain rate per second. Default: 0. Valid values: 0-999999999.
  Invalidate Registrations	Select to invalidate all registrations going to this session agent. Default: Disabled.
  RFC2833 Mode	Select the preferred mode for RFC2833. Default: None. Valid values: None | Transparent | Preferred | Dual.
  RFC2833 Payload	Enter a number for the payload used by the agent in Preferred RFC2833 mode. Default: 0. Valid values: 0-127.
  Codec Policy	Select the codec policy to apply to this session agent.
  Refer Call Transfer	Select the refer method for call transfer. Default: Disabled. Valid values: Disabled | Enabled | Dynamic.
  Refer Notify Provisional	Select the provisional mode for sending a NOTIFY message. Default: None. Valid values: 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. Default: None. Valid values: None | TCP | SCTP.
  TCP Keepalive	Select an option for the TCP keepalive function. Default: None. Valid values: None | Disabled | Enabled.
  TCP Reconn Interval	Enter the TCP/SCTP e-connection interval. Default: 0. Valid values: 0-300.
  Max Register Burst Rate	Enter the number of seconds allowed for the maximum register burst rate. Default: 0. Valid values: 0-999999999.
  KPML Interworking	Select a status for KPML Interworking inherit from the SIP interface. Default: Inherit. Valid values: Inherit | Disabled | Enabled.
  KMPL 2833 IWF on Hairpin	Select a status for KPML Interworking on a hairpin call. Default: Inherit. Valid values: Inherit | Disabled | Enabled.
  Precedence	Set the order of precedence for this agent among agents with the same IP address. Default: 0. Valid values: 0-4294967295.
  Monitoring Filters	Add one or more comma separated monitoring filters. Preface with the + character to add, the - character to remove, and the word exclude to replace.
  Auth Attribute	Click Add, and do the following: Auth Realm—Select an authentication realm. Username—Enter the user name for the selected realm. Password—Enter the password for the selected realm. In Dialog Methods—Add one or more in dialog methods to add authentication headers.
  Session Recording Server	Select a single session recording server <SRS-name> or a session recording group <SRS-group-name>.
  Session Recording Required	Select to enable calls upon successful set up and interaction with the Session Recording Server. Default: Disabled.
  Hold Refer Reinvite	Select to enable holding the re-INVITE. Default: Disabled.
  Send TCP Fin	Select to enable sending TCP FIN messages when the Session Agent stops responding. Default: Disabled.
  SIP Recursion Policy	Select a SIP recursion policy from the list.
  Sm ICSI Match for INVITE	Set the ICSI value to match for INVITE per RFC 6050.
  Sm ICSI Match for Message	Set the ICSI value to match for Message per RFC 6050..

• Click OK.
• Save the configuration.

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

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.

1. From the Web GUI, click Configuration, Ssession Router, Session Agent.
2. On the Session Agent page, select the agent and click Edit.
3. On the Session Agent page, select Hold Refer Invite.
4. Click OK.
5. Save the configuration.

Use the Session Group element to define a signaling 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 Add Session Group page, click Add, and 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—The system selects the session agent in list order. Least Busy—The 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—The system selects the session agent with the lowest sustained rate of session initiations and incitations. Prop Dist—The system uses the proportional distribution strategy to distribute traffic among all available session agent elements, based on session constraint limits. Round Robin—The 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.
   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.
   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.

3. Click OK.
4. Save the configuration.

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.

1. Access the Session Recording Group configuration object: Configuration, Session Router, Session Recording Group, Add.
2. In the 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	Enter the names of the session recording servers you want in this group. Use the + character to add a recording server to the existing list and the - character to remove one. Omit the + and - characters to replace the list. For example, +acme, -packet, or acme packet.
   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. Default: 0. Valid values: 1-10.

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

From the Configuration tab, define SIP Advanced Logging and Advanced Log Condition. The criteria that you configure re-maps the message logging and modifies the system configuration. You must save and activate these changes to the configuration.

1. From the Web GUI, go to Configuration, Session Router, SIP Advanced Logging, and click Add.
2. On the 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.

From the Configuration tab, clear the advanced logging settings.

1. From the Web GUI, go to Configuration, Session Router, SIP Advanced Logging.
2. On the SIP Advanced Logging page, clear all of the settings.
3. Save the configuration.

From the Configuration tab, define SIP Advanced Logging and Advanced Log Condition. The criteria that you configure re-maps the message logging and modifies the system configuration. You must save and activate these changes to the configuration.

1. From the Web GUI, go to Configuration, Session Router, SIP Advanced Logging, and click Add.
2. On the 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.

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

1. Access the SIP Config configuration object: 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. Default: 0. Range: 0-999999999.
   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. Default: 15. Range: 1-60. 0 = no delay.
   Transcoding Realm	Enter the name of the realm where transcoding agents reside.
   Transcoding Agents	Create a list of transcoding agents. For a single agent use <hostname>, <IPv4 | IPv6 | IPport>, or <SessionAgentName> plus the address. For example: somehostname 1 1.1.1.1. For multiple entries, list the agents and the address. For example, sa1 sa2 1.1.1.1. Use the + character to add an agent to the existing list and the - character to remove one.
   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. Valid values: BGCF | E-CSCF | IBCF | P-CSCF.
   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. Default: 0. : 0-4294967295.
   Cache Loc Info Expire	Enter the number of seconds for the SBC to rely on cached location information. The number must be higher than the transaction expiration time. Default: 32. Range: 1-4294967295.
   Msg Hold for Loc Info	Enter the number of seconds to hold MESSAGEs until hte SBC receives location information from PCRF. Default: 0. Range: 0-30.
   Npli Upon Register	Select to include the location provided by the network in REGISTER messages. Default: Disabled.

3. Click OK.
4. Save the configuration.

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.

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.

Use the SIP Interface object to define SIP signaling.

1. From the Web GUI, click Configuration, Session Router, SIP Interface.
2. On the SIP Interface page, click Add, and 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 Manipulation ID	Select an inbound SIP manipulation rule from the drop-down list.
   Out Manipulation ID	Select an outbound SIP manipulation rule from the drop-down list.
   Service Tag	Enter the service tag for this interface.

3. Click OK.
4. Save the configuration.

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.

1. From the Web GUI, click Configuration, Session Router, SIP Manipulation.
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.

You can configure Multi-Purpose Internet Mail Extensions (MIME) header rules and element rules on the Oracle® Enterprise Session Border Controller (E-SBC) from the "CfgRules" section of the "SIP Manipulations" page.

1. Access the SIP Manipulation configuration object.
   Configuration, System Administration, SIP Manipulation.
2. On the SIP Manipulation configuration page, do one of the following:
   1. Select and existing SIP manipulation configuration from the table, right-click, and click Edit. (Subsequent SIP manipulation pages use "Modify" in the title.)
   2. Click Add. (Subsequent SIP manipulation pages use "Add" in the title.)
3. On the Add or Modify SIP Manipulation page, do one of the following.
   1. If you chose Add, you must enter a name for this SIP Manipulation. (You can optionally complete the Description, Split Headers, and Join Headers parameters, at this time. See "Configure SIP Manipulation.") Proceed to the next step.
   2. If you chose to edit an existing configuration, proceed to the next step.
4. On the Add or Modify SIP Manipulation page under Cfg Rules, click Add and click mime-header-rule.
5. On the Add or Modify SIP Manipulation / Mime ISUP Rule page, do the following.

   Name	Enter a unique name for this rule set. Valid values: Alpha-numeric.
   Content Type	Enter the name of the header on which you want the E-SBC to use this HMR. Set this parameter to @status-line, where the at-sign (@)—not allowed in SIP header names—to prevent undesired matches with header having the name status-code. Default: Blank.
   Msg Type	Specify the message type this rule applies to. Default: Any. Valid Values: Any | Out of Dialog | Reply | Request | Out of Dialog.
   Methods	Enter the method type to use when this SIP HMR is used. Default: Blank. Valid values" ACK | CANCEL | INVITE. When you do not set the method, the E-SBC applies the rule to all SIP methods.
   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. Default: None. Valid values: Add | Delete | Find Replace All | Log | Manipulate | Monitor | None | Reject | SIP Manip | Store.
   Comparison Type	Specify how the E-SBC processes the match rules against the SIP header. Default: Refer Case Sensitive. Valid values: Boolean | Case Insensitive | Case Sensitive | Pattern Rule | Refer Case Insensitive | Refer Case Sensitive.
   Match Value	Enter the value to match against the header value in SIP packets; the E-SBC matches these against the entire SIP header value. This is where you can enter values to match using regular expression values. Your entries can contain Boolean operators. When you configure HMR (using SIP manipulation rules and elements rules, you can use escape characters in the match-value parameter to support escaping Boolean and string manipulation operators. You can also escape the escape character itself, so that it is used as a literal string. For example, the E-SBC treats the string \+1234 as +1234. The following are escape characters: +, -, +^, -^, &, |, \, (, ), ., $, ^, and “. You can also use the variables, $REMOTE_PORT and $LOCAL_PORT, which resolve respectively to the far-end and remote UDP or TCP port value.
   New Value	When you set the action parameter Add or to Manipulate, enter the new value that you want to substitute for the entire header value. This is where you can set stored regular expression values for the E-SBC to use when it adds or manipulates SIP headers. When you configure HMR (using SIP manipulation rules and elements rules, you can use escape characters in the match-value parameter to support escaping Boolean and string manipulation operators. You can also escape the escape character itself, so that it is used as a literal string. For example, the E-SBC treats the string \+1234 as +1234. The following are escape characters: +, -, +^, -^, &, |, \, (, ), ., $, ^, and “. You can also use the variables, $REMOTE_PORT and $LOCAL_PORT, which resolve respectively to the far-end and remote UDP or TCP port value.
   Cfg Rules (instructions for configuring MIME HeaderRule)	Click Add, MIME Header Rule, and do the following. Name—Enter a unique name for this header element rule. 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. (To clear the value, enter and empty string.) Match Value—Enter the match value to compare against the current object. (To clear the value, enter and empty string.) 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 following table cell. Finish the MIME ISUP rule configuration by completing steps 3-6.
   Cfg Rules (instructions for configuring ISUP Param Rule)	Click Add, isup-param-rule, 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. (To clear the value, enter and empty string.) Match Value—Enter the match value to compare against the current object. (To clear the value, enter and empty string.) 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. Finish the MIME ISUP Rule configuration by completing the following steps.

6. Click Back.
   The system displays the Add or Modify SIP Manipulation page.
7. Click Back.
   The system displays the SIP Manipulation page.
8. Save the configuration.

You can configure Multi-Purpose Internet Mail Extensions (MIME) header rules and element rules on the Oracle® Enterprise Session Border Controller (E-SBC) from the "CfgRules" section of the "SIP Manipulations" page.

1. Access the SIP Manipulation configuration object.
   Configuration, System Administration, SIP Manipulation.
2. On the SIP Manipulation configuration page, do one of the following:
   1. Select and existing SIP manipulation configuration from the table, right-click, and click Edit. (Subsequent SIP manipulation pages use "Modify" in the title.)
   2. Click Add. (Subsequent SIP manipulation pages use "Add" in the title.)
3. On the Add or Modify SIP Manipulation page, do one of the following.
   1. If you chose Add, you must enter a name for this SIP Manipulation. (You can optionally complete the Description, Split Headers, and Join Headers parameters, at this time. See "Configure SIP Manipulation.") Proceed to the next step.
   2. If you chose to edit an existing configuration, proceed to the next step.
4. On the Add or Modify SIP Manipulation page under Cfg Rules, click Add and click mime-sdp-rule.
5. In the Add or Modify SIP Manipulation / MIME SDP Rule page, do the following.

   Name	Enter a unique name for this rule set. Valid values: Alpha-numeric.
   Content Type	Enter the name of the header on which you want the E-SBC to use this HMR. Set this parameter to @status-line, where the at-sign (@)—not allowed in SIP header names—to prevent undesired matches with header having the name status-code. Default: Blank.
   Msg Type	Specify the message type this rule applies to. Default: Any. Valid Values: Any | Out of Dialog | Reply | Request | Out of Dialog.
   Methods	Enter the method type to use when this SIP HMR is used. Default: Blank. Valid values" ACK | CANCEL | INVITE. When you do not set the method, the E-SBC applies the rule to all SIP methods.
   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. Default: None. Valid values: Add | Delete | Find Replace All | Log | Manipulate | Monitor | None | Reject | SIP Manip | Store.
   Comparison Type	Specify how the E-SBC processes the match rules against the SIP header. Default: Refer Case Sensitive. Valid values: Boolean | Case Insensitive | Case Sensitive | Pattern Rule | Refer Case Insensitive | Refer Case Sensitive.
   Match Value	Enter the value to match against the header value in SIP packets; the E-SBC matches these against the entire SIP header value. This is where you can enter values to match using regular expression values. Your entries can contain Boolean operators. When you configure HMR (using SIP manipulation rules and elements rules, you can use escape characters in the match-value parameter to support escaping Boolean and string manipulation operators. You can also escape the escape character itself, so that it is used as a literal string. For example, the E-SBC treats the string \+1234 as +1234. The following are escape characters: +, -, +^, -^, &, |, \, (, ), ., $, ^, and “. You can also use the variables, $REMOTE_PORT and $LOCAL_PORT, which resolve respectively to the far-end and remote UDP or TCP port value.
   New Value	When you set the action parameter Add or to Manipulate, enter the new value that you want to substitute for the entire header value. This is where you can set stored regular expression values for the E-SBC to use when it adds or manipulates SIP headers. When you configure HMR (using SIP manipulation rules and elements rules, you can use escape characters in the match-value parameter to support escaping Boolean and string manipulation operators. You can also escape the escape character itself, so that it is used as a literal string. For example, the E-SBC treats the string \+1234 as +1234. The following are escape characters: +, -, +^, -^, &, |, \, (, ), ., $, ^, and “. You can also use the variables, $REMOTE_PORT and $LOCAL_PORT, which resolve respectively to the far-end and remote UDP or TCP port value.
   Cfg Rules (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 following table cells. Finish the MIME SDP rule configuration by completing steps 3-6.
   Cfg Rules (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 in this procedure. Finish the MIME SDP rule configuration by completing steps 3-6.
   Cfg Rules (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. (To clear the value, enter and empty string.) Match Value—Enter the match value to compare against the current object. (To clear the value, enter and empty string.) 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. Finish the MIME SDP rule configuration by completing the following steps.

6. Click Back.
   The system displays the Add or Modify SIP Manipulation page.
7. Click Back.
   The system displays the SIP Manipulation page.
8. Save the configuration.