![]() ![]() ![]() ![]() ![]() ![]() |
The following sections describe how WebLogic SIP Server 2.2 complies with various specifications and RFCs:
WebLogic SIP Server is developed with special attention to Internet Engineering Task Force and 3rd Generation Partnership Project specifications. Feature development is prioritized according to general market trends, both observed and predicted. In cases where certain specifications are obsolete or where Internet drafts are formalized as `Request For Comments' standards, WebLogic SIP Server places priority on compliance with those specifications. In cases where specifications are part of a larger release plan, as with the 3GPP, BEA prioritizes compliance with the latest ratified release (in this case, Release 6). This should not be presumed to mean that the product is not compliant with subsequent versions of component specifications, although this document does not summarize compliance with those specifications.
WebLogic SIP Server 2.2 is compliant with the JSR 58: Java 2 Platform, Enterprise Edition 1.3 Specification and all of its component specifications, and is enhanced by the addition of a SIP Servlet container defined by JSR 116: "SIP Servlet API."
WebLogic SIP Server 2.2 has executed all related Test Compatibility Kits (TCKs) and has met the formal requirements established by Sun Microsystems for formal public statements of compliance.
The following table lists the WebLogic SIP Server level of compliance to common Internet Engineering Task Force (IETF) Requests for Comment (RFCs) and Internet drafts. The level of compliance is defined as follows:
WebLogic SIP Server supports applications that consume or generate signed or encrypted multipart MIME objects. See
http://www.ietf.org/rfc/rfc1847.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www.ietf.org/rfc/rfc2183.txt
|
|||
WebLogic SIP Server supports TLS. See
http://www.ietf.org/rfc/rfc2246.txt
|
|||
WebLogic SIP Server supports applications that consume or generate SDP. See
http://www.ietf.org/rfc/rfc2327.txt
|
|||
WebLogic SIP Server supports backward compatibility as described in this specification. See
http://www.ietf.org/rfc/rfc2543.txt
|
|||
Note that implementing PINT services implies a pre-IMS architecture. Although BEA favors the 3GPP/TISPAN architecture and approach to class 4/5 Service Emulation and does not advocate PINT, it is possible to implement PINT service elements using WebLogic SIP Server. See
http://www.ietf.org/rfc/rfc2848.txt
|
|||
WebLogic SIP Server does not directly consume or generate ISUP and QSIG objects, but it supports applications that consume or generate these objects. See
http://www.ietf.org/rfc/rfc3204.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www.ietf.org/rfc/rfc3264.txt
|
|||
WebLogic SIP Server supports cryptographic services, but specific algorithms that are used are subject to local availability and export control. See
http://www.ietf.org/rfc/rfc3268.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www.ietf.org/rfc/rfc3311.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www.ietf.org/rfc/rfc3312.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www.ietf.org/rfc/rfc3323.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www.ietf.org/rfc/rfc3326.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www.ietf.org/rfc/rfc3351.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www.ietf.org/rfc/rfc3372.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www.ietf.org/rfc/rfc3455.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification, but it does not provide an ISUP interface. See
http://www.ietf.org/rfc/rfc3578.txt
|
|||
WebLogic SIP Server does not expose the Diameter base protocol to developers, but uses the base protocol as a means of managing profile data with network functions such as Home Subscriber Servers (HSS) via the Sh interface.See
http://www.ietf.org/rfc/rfc3588.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification, but it does not provide a means of storing the ServiceRoute established during registration. This functionality can be implemented as part of the application. See
http://www.ietf.org/rfc/rfc3608.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www.ietf.org/rfc/rfc3665.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www.ietf.org/rfc/rfc3666.txt
|
|||
WebLogic SIP Server version 2.2 supports JDBC and LDAP. See
http://www.ietf.org/rfc/rfc3702.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www.ietf.org/rfc/rfc3725.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www.ietf.org/rfc/rfc3764.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www.ietf.org/rfc/rfc3853.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www.ietf.org/rfc/rfc3892.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www.ietf.org/rfc/rfc3893.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www.ietf.org/rfc/rfc3911.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www.ietf.org/rfc/rfc4244.txt
|
|||
WebLogic SIP Server supports SNMP V2c traps. See
http://www.ietf.org/rfc/rfc1157.txt
|
|||
WebLogic SIP Server supports SNMP V2c traps. See
http://www.ietf.org/rfc/rfc1901.txt
|
|||
WebLogic SIP Server supports SNMP V2c traps. See
http://www.ietf.org/rfc/rfc1905.txt
|
|||
WebLogic SIP Server supports SNMP over both TCP and UDP. See
http://www.ietf.org/rfc/rfc1906.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
https://datatracker.ietf.org/public/idindex.cgi?command=id_detail&id=6002
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
https://datatracker.ietf.org/public/idindex.cgi?command=id_detail&id=4308
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www.ietf.org/internet-drafts/draft-ietf-sip-content-indirect-mech-05.txt
|
|||
WebLogic SIP Server supports applications that conform to this specification. See
http://www3.ietf.org/proceedings/05nov/IDs/draft-ietf-simple-xcap-08.txt
|
Table 5-2, 3GPP R6 Specification Conformance, on page 5-10 summarizes the ability of the WebLogic SIP Server 2.2 release to support implementation of the enablers or application functions identified by each applicable 3GPP Release 6 specification.
Other than the exceptions noted, WebLogic SIP Server 2.2 does not impose any restrictions on implementing applications or functions that are compliant with those associated with the Application Server entity described in the specification. In some cases, applications must implement support for SIP methods or headers. The default behavior of the WebLogic SIP Server Sip Servlet Container is to pass unrecognized headers, request methods and payloads to SIP Servlets using normal SIP Servlet API procedures.
![]() ![]() ![]() |