The WebLogic SIP Server 2.0.1 Release Notes includes the following sections:
WebLogic SIP Server 2.0.1 uses two separate license files to provide basic functionality:
All default installations of WebLogic SIP Server 2.0.1 include an evaluation license for both WebLogic Server 8.1 SP4 and the SIP container.
You can purchase a production upgrade license for WebLogic SIP Server 2.0.1, which includes a production-enabled sip-liense.xml file and requires that you own or purchase a separate BEA WebLogic Server 8.1 production license. To use the production version of WebLogic SIP Server, follow these steps to update and use an existing BEA WebLogic Server 8.1 production license and to install the purchased WebLogic SIP Server license:
cd c:\beawls copy license.bea license.bea.backup copy sip-license.xml sip-license.xml.backup
http://elicense.bea.com to change the IP address.copy c:\bea814\license.bea c:\beawls
copy c:\downloads\sip-license.xml c:\beawls
SIP Servlet Engine uses the following products:
For license information for these products, see the following files and URL:
WebLogic SIP Server 2.0.1 is a restricted release of a BEA product and is subject to change in future releases. The following features are specifically called out as being deprecated in WebLogic SIP Server 2.0.1:
The WEB-INF subdirectory of a SIP application must contain both a web.xml and sip.xml descriptor, even if your are deploying a pure SIP application. The web.xml descriptor must define a standard listener class used to manage the lifecycle of HTTP and SIP Servlet contexts. See Interaction between Servlet Contexts for more information.
WebLogic SIP Server 2.0.1 does not support the following functions described in the "SIP Servlet API (Version 1.0):"
The 100rel extension defined in RFC3262 does not operate. If the following information is specified in a message header,
Require: 100rel
A 420 error message is returned to this request.
TLS does not operate as an SIP transport protocol, and the only available transport protocols are TCP and UDP. Because of this, the <transport-guarantee> which is a child element of the <user-data-constraint> element is not supported. If any value other than NONE is specified in <transport-guarantee>, WebLogic SIP Server throws an exception.
This release does not support the <ejb-link> which is a child of the <ejb-ref> and <ejb-local-ref> elements. If the <ejb-link> is specified, the setting is ignored.
This release does not support the send-by parameter in the Via header defined in RFC3261. If the send-by parameter is specified, the setting is ignored.
This release does not support the SUBSCRIBE requests forked at proxies defined in RFC3265. SIP sessions are not generated properly for the SUBSCRIBE requests forked at proxies.
This release does not support virtual hosting. Use SIP applications on only one virtual host. When an SIP servlet is used on multiple virtual hosts, SIP messages may not be delivered properly to the servlet.
WebLogic SIP Server does not open the port for receiving SIP messages until the J2EE container has completely started. Therefore, if SIP servlets are simultaneously generated and initialized with <load-on-startup> in sip.xml, the following limitations apply to the Servlet.init():
public syncronized init() {
...
SipFactory factory = getFactory();
SipServletRequest req = factory.createRequest(...);
wait();
...
}
public synchronized doSuccessResponse(SipServletResponse res) {
notifyAll();
}
WebLogic Server startup applications may perform the following processes:
Therefore, the third limitation on Servlet.init() also applies to Servlet.destroy(). In this case, the init() affected by limitation 3 above sends only the request which the SipServletRequest.send() has attempted to send after WebLogic Server has started. The request which the SipServletRequest.send() has attempted to send in the init() affected by the limitation 1 is destroyed by the destroy() affected by limitation 3.
On Windows platforms, communication via TCP does not operate properly. Use only UDP as a transport protocol.