Contents

Release Notes

• New Features
  • Netra 6000 High Availability Manager
  • New IM-PSX Module
  • New R-IM-OCF Module
  • Degraded SDR Mode
  • Support for a New ForceB2B iFC Element
  • Enabling Orchestration of All Types of SIP Requests
  • Support for CAP Phase 4 Releases 6.5.0 and 7.5.0
  • Play Token According to RFC 4240
  • Improved IN Media Resource Support
  • New Administration Console
  • New Oracle Universal Installer
  • Improved Overload Protection Mechanism
  • Streamlined Interworking Module and Supplementary Module Upgrades
  • Improved Interworking Module and Supplementary Module Management
  • Multiple Point Codes for Service Broker Deployment
  • Global Title Addressing
  • Improved SCCP Inbound Routing
  • Routing Through a Default IM-ASF Module
  • IM's Individual Global Title Address
  • Dispatching Incoming Diameter Traffic to IMs
  • SSL Support
  • Using Oracle Coherence
  • OSGi-based Implementation
  • Enabling Multiple Processing Domains Deployments
• Fixes in This Release
• Known Problems
  • Service Broker Supports Only SIP B2BUA and RDS Application Servers
  • Signaling Traffic Discarded When Signaling Servers Start before Processing Servers
  • JVM Arguments Need to Be Set for Improving Performance
  • Mandatory Domain Configuration Is Not Available in the Administration Console
  • SIP URIs Cannot Be Used if DNS Resolution Is Not Set Up in The Network
  • Service Broker Does Not Respond to SIP OPTION Requests
  • SNMP Support is Not Available
  • Stand-Alone Administration Console is Not Supported on Solaris Sparc 64-bit with 64 bit JVM
  • Servers Need Redundant Network Interfaces to Avoid Manual Restarts in Case of Network Outages
  • Missing Solaris SUNWuiu8 Package Issue During Installation
  • Directory Permissions on Solaris During Installation
  • Administration Console Does Not Show Correct State of Secondary Bootstrap Blade
  • SUN_NetraCard MBean Is Not Updated When a Powered On Blade Is Removed from Chassis
  • Concurrent Configuration Updates May Cause Server Startup Failure
  • Internet Explorer not Supported
  • A Set of Hardware MBeans that are Displayed are not Supported
  • Error Text in Statistics Tab Does not Indicate an Error
  • Warning Message During Blade Boot
  • First Server Added to the Default Route of a Diameter Node Is Not Effective
  • Incorrect Prcosses State is Displayed in the Administration Console after Automatic Restart of eMA on Worker Blades
• Documentation Updates