A Service record (SRV record) is a specification of data in the Domain Name System defining the location, i.e. the hostname and port number, of servers for specified services. It is defined in RFC , and its type code is . org. connection order as specified by RFC 5, in that all priorities and Presence Protocol (XMPP): Core >. The following are IETF Requests for Comments (RFC). (DNS NCACHE); RFC Domain Name System Security Extensions; RFC A.
|Published (Last):||2 November 2017|
|PDF File Size:||5.54 Mb|
|ePub File Size:||3.63 Mb|
|Price:||Free* [*Free Regsitration Required]|
Oracle WebLogic Communication Services is supported for production use on the operating system, hardware, and JVM combinations described shown in http: The following items are required in addition to the basic WebLogic Server requirements:. Gigabit Ethernet connections are required between engine and SIP data tier servers for most production deployments. Additional RAM is iett to support the throughput requirements of most production installations.
BIG-IP load balancer, versions 9. See the Oracle Technology Network http: Oracle WebLogic Communication Services has been tested to run with the following databases for storing long-lived session data and for replicating call state information across regional sites geographic persistence:.
Oracle Database 10 g 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, Oracle WebLogic Communication Services places priority on compliance with those specifications. In cases where specifications are part of a larger release plan, as with the 3GPP, Oracle prioritizes compliance with the latest ratified release in this case, Release 6.
DNS Standards Documents
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. The level of compliance is defined as follows:. Communicating Rf Information in Internet Messages: The Content-Disposition Header Field. Oracle WebLogic Communication Services supports applications that conform to this specification.
Oracle Jetf Communication Services supports backward compatibility as described in this specification. SCTP supported only for Diameter traffic. Oracle WebLogic Communication Services supports cryptographic services, but specific algorithms that are used are subject to local availability and export control.
Oracle WebLogic Communication Services supports applications that conform to this specification, but it does not provide a means of storing the ServiceRoute established during registration. This iehf can be implemented as part of the application.
Information on RFC » RFC Editor
Table E-3 summarizes the ability of Oracle WebLogic Communication Services to support implementation of rvc enablers or application functions identified by each applicable 3GPP Release 6 specification. Other than the exceptions noted, Oracle WebLogic Communication Services 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.
Oracle WebLogic Communication Services does not enforce the requirement that only one p-charging-function-address header per SIP request as described in sub-section 5. Oracle WebLogic Communication Services does enforce uniqueness. Oracle WebLogic Communication Services jetf not provide privacy support as described in sub-section 5.
Oracle WebLogic Communication Services supports the ‘X-3GPP-Asserted-Identity extension-header’ for use in applying access control and authorization constraints within the integrated security framework.
Windows platforms are ffc only for development purposes.
Oracle Communicator default client. The level of compliance is defined as follows: Session Initiation Protocol Yes See http: Yes Platform See http: Yes Platform Oracle WebLogic Communication Services supports applications that conform rf this specification, but it does not provide a means of storing the ServiceRoute established during registration.
Basic and Digest Access Authentication.
No support for partial document manipulation XPath.