SIP Option Response Configuration

You can configure the ping-in-service-response-codes parameter in the session agent configuration to refine how the OECB monitors agent status. You define one or more response codes that keep a session agent in service when sent as response to the OECB’s ping request in this parameter. The OECB takes the session agent out of service if the session agent sends a response code that is not on this list. The exception to this is a 200 OK response, which, by default, always keeps the agent in-service. This behavior applies to both single and multi-hop pings.

See the OECB Essentials Guide for a full explanation of this feature.

Managing the ECB with SDM

You can perform configuration and fault management on the Oracle Enterprise Communications Broker (OECB) and OECB groups using Oracle's Session Delivery Manager (SDM) management system. Fault management by SDM includes the handling of SNMP traps and logs. Configuration management is based on software version, with each version able to specify which elements you can configure with SDM. The use of SDM for OECB also provides you with the ability to establish consistent configuration management across multiple OECB deployments.

As of this release, you can configure the following using Session Deliver Manager:

• access-control
• account-config
• additional-target-group
• allowed-elements-profile
• audit-logging
• authentication
• certificate-record
• dialing-context
• enum-config
• filter-config
• host-route
• ldap-config
• ldap-group
• local-subscriber-table
• network-interface
• ntp-config
• policy
• realm-config
• redundancy-config
• routing-entry
• session-agent
• session-group
• sip-authentication-profile
• sip-config
• sip-interface
• sip-manipulation
• sip-monitoring
• sip-registrar
• snmp-community
• spl-config
• sync-agent
• sync-config
• system-config
• tls-profile
• trap-receiver
• user-number
• http-server
• http-client

Dynamic ACLs

The OECB DoS protection functionality protects softswitches and gateways with overload protection, dynamic and static access control, and trusted device classification and separation at Layers 3-5. The OECB itself is protected from signaling and media overload, but more importantly the feature allows legitimate, trusted devices to continue receiving service even during an attack.

See the OECB Essentials Guide for a full explanation of this feature.

DNS Enhancements

When configured, the OECB performs DNS client functions per RFC1034 and RFC1035. The user can define one primary DNS server and two backup DNS servers for the OECB to query a domain for SRV (FQDN), AAAA (IPv6), and A (IP address) information. A common example of the OECB using DNS is to locate a SIP server via server location discovery, as described in RFC 3263. An applicable context is identifying a callee so the OECB can place a call.

See the OECB Essentials Guide for a full explanation of this feature.

Dynamic REFER Support

In the simplest scenarios, the Oracle Enterprise Communications Broker (OECB) supports Dynamic REFER either by proxying the REFER to the other User Agent in the dialog, or by terminating the received REFER and issuing a new INVITE to the referred party. In addition, the OECB provides dynamic refer support, which determines on a call-by-call basis whether to proxy the REFER to the next hop, or terminate the REFER and issue an INVITE. You configure these operational modes on realms and session agents.

See the OECB Essentials Guide for a full explanation of this feature.

Source Routing Enhancements

The OECB supports source routing based on agent hostname. You configure these routes by adding the hostname to the source agent portion of your route. When the OECB sees this hostname in the FROM URI, it uses your source route to direct the traffic. You can also configure the OECB to perform source routing on calling numbers that have a FROM header with a R-URI that contains an IP address or an FQDN. For this, the OECB attempts to determine the hostname by searching for the address or FQDN in the UserDB. If it finds the entry, the OECB inserts the hostname into the FROM and performs a route lookup.

See the OECB Essentials Guide for a full explanation of this feature.

Web GUI Display and Behavioral Changes

The GUI offered with PCZ3.3.0 presents major changes the previous GUI. See "Web GUI Changes" in the Release Notes for a centralized description of the changes, and the Oracle Enterprise Communications Broker Administrator's Guide and User's Guide for updated documentation on these changes.

Web GUI display and behavior changes do not change the behavior of service operation or any other system features.

Review the GUI Limitations section for a summary of changes to expect.

Configuration to Establish Authentication by TACACS Only

You can configure the OECB to restrict access authentication to the TACACS function, thereby enhancing system security.

This support is available in software versions P-Cz3.3.0p1 and above. See the Oracle Enterprise Communications Broker Administrator's Guide and User's Guide for extended documentation on this feature.

TCP Timers

The OECB includes timing capabilities for inbound connections that the remote peer initiated, meaning that the remote peer sent the first SYN message. You can configure timers that define timing surrounding TCP connections, including maximum idle time for a connection before the system consider the connection inactive.

This support is available in software versions P-Cz3.3.0p1 and above. See the Oracle Enterprise Communications Broker Administrator's Guide and User's Guide for extended documentation on this feature.

Global SIP Timers

The OECB includes SIP timers that define the transaction expiration times, retransmission intervals when UDP is used as a transport, and the lifetime of dynamic TCP connections. These retransmission and expiration timers correspond to timers defined in RFC 3261.

This support is available in software versions P-Cz3.3.0p1 and above. See the Oracle Enterprise Communications Broker Administrator's Guide and User's Guide for extended documentation on this feature.