The following table summarizes the issues that were resolved in WebLogic SIP Server 2.1.
WebLogic SIP Server sometimes threw a NullPointerException when running a User Agent Client (UAC) against a proxy servlet that proxied back to the same engine tier server instance. The problem caused the exception:
<Client timer task failed with fatal status java.lang.NullPointerException at com.bea.wcp.sip.engine.server.SipServletMessageImpl.getDialogId(SipServletMessageImpl.java:274) |
|
Configuration files used inconsistent naming conventions for the data tier and replicas within the data tier. The configuration file schema has changed to consistently use the term "data tier" to refer to the cluster of WebLogic SIP Server instances that manage call state data, "partition" to refer to a managed portion of the call state, and "replica" to refer to an individual WebLogic SIP Server instance within a partition. See
Configuring Data Tier Partitions and Replicas and
Data Tier Configuration Reference (datatier.xml).
|
|
The SNMP MIB for WebLogic SIP Server was previously available only from Managed Servers running in a domain. The code was modified to make WebLogic SIP Server MIB entries available from the Administration Server as well as Managed Servers. See
Configuring SNMP.
|
|
WebLogic SIP Server did not listen for UDP messages on a non-default network channel that specified IP_ANY/0.0.0.0 as the listen address. The code was modified so that the server listens for incoming UDP messages on any IP interface when you define a network channel with 0.0.0.0 as the listen address. See
Configuring Servers to Listen on Any IP Interface (0.0.0.0).
|
|
The previously deprecated XML configuration elements for defining trusted hosts have been replaced with new configuration elements. See
sip-security.
|
|
In a replicated environment, or in a single server environment with debugging turned on, adding sleep time at the end of a
doMessage() call could result in the error:
|
|
When waiting for over 60 minutes between an INVITE and a BYE message, a load testing proxy application would sent a 481 response even though the call should not be stateful. For example:
This problem was resolved by adding a new container configuration parameter,
default-behavior , which defines wether WebLogic SIP Server should act as a proxy or a user agent (UA) in the absence of an available, matching application. See
default-behavior.
|
|
Prior to version 2.2, a WebLogic SIP Server engine tier server would start up even if no SIP network channels were targeted to the server (for example, if a new engine tier server was configured manually and no channels were created).
|
|
The previous version of the
findme example application did not work in a domain having multiple engine tier servers in a cluster. The example code and documentation were modified to support a clustered environment. See
Build the Example.
|
|
The Administration Console allowed you to uncheck the Outbound Enabled attribute for a SIP or SIPS network channel, even though SIP and SIPS network channels can always originate outbound connections. In addition, the Console allowed you to select the HTTP Enabled for This Protocol attribute for SIP and SIPS channels even though HTTP and SIP/SIPS are not supported on the same port number. The Console code was modified to make these attributes read-only for SIP and SIPS network channels.
|
|
The WebLogic Server Administration Console had several problems that could affect the configuration of WebLogic SIP Server:
|
|