Skip Headers
Oracle® WebLogic Communication Services Administrator's Guide
11g Release 1 (11.1.1)

Part Number E13806-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

E Supported Platforms, Protocols, RFCs and Standards

The following sections describe how Oracle WebLogic Communication Services complies with various specifications and RFCs:

E.1 Supported Configurations

Oracle WebLogic Communication Services is supported for production use on the operating system, hardware, and JVM combinations described shown in http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html.

Note:

Production deployment is supported only for Linux and UNIX platforms. Windows platforms are supported only for development purposes.

Oracle WebLogic Communication Services has similar requirements to Oracle WebLogic Server 10g Release 3. The following items are required in addition to the basic WebLogic Server requirements:

E.2 Supported SIP Clients

Oracle WebLogic Communication Services and the included sample applications support the following SIP softphone:

E.3 Supported Load Balancer

Oracle WebLogic Communication Services has been tested to run with F5 Networks, Inc. BIG-IP load balancer, versions 9.0.5 through 9.2.3 Build 34.3.

See the Oracle Technology Network (http://www.oracle.com/global/index.html) for information about support for other load balancer solutions.

E.4 Supported Databases

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):

E.5 Overview of Oracle WebLogic Communication Services Standards Alignment

Oracle WebLogic Communication Services 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, 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). 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.

E.6 Java Sun Recommendation (JSR) Standards Compliance

Oracle WebLogic Communication Services is compliant with Java EE version 5.0 and the corresponding Java EE component specifications.

Oracle WebLogic Communication Services is further enhanced by the addition of a SIP Servlet container defined by JSR 289: "SIP Servlet API."

Oracle WebLogic Communication Services has executed all related Test Compatibility Kits (TCKs) and has met the formal requirements established by Sun Microsystems for formal public statements of compliance.

E.7 IETF RFC Compliance

The following table lists the Oracle WebLogic Communication Services 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:

Table E-2 Oracle WebLogic Communication Services IETF Compliance

RFC or Specification Number Title Compliant? Additional Information

761

DoD Standard Transmission Control Protocol

Yes

See http://www.ietf.org/rfc/rfc761.txt

768

User Datagram Protocol

Yes

See http://www.ietf.org/rfc/rfc768.txt

1157

A Simple Network Management Protocol (SNMP)

Yes

Oracle WebLogic Communication Services supports SNMP V2c traps. See http://www.ietf.org/rfc/rfc1157.txt

1847

Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted

Yes (Platform)

Oracle WebLogic Communication Services supports applications that consume or generate signed or encrypted multipart MIME objects. See http://www.ietf.org/rfc/rfc1847.txt

1901

Introduction to Community-based SNMPv2

Yes

Oracle WebLogic Communication Services supports SNMP V2c traps. See http://www.ietf.org/rfc/rfc1901.txt

1905

Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)

Yes

Oracle WebLogic Communication Services supports SNMP V2c traps. See http://www.ietf.org/rfc/rfc1905.txt

1906

Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)

Yes

Oracle WebLogic Communication Services supports SNMP over both TCP and UDP. See http://www.ietf.org/rfc/rfc1906.txt

1907

Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)

Yes (Platform)

See http://www.ietf.org/rfc/rfc1907.txt

2183

Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc2183.txt

2246

The TLS Protocol Version 1.0

Yes

Oracle WebLogic Communication Services supports TLS. See http://www.ietf.org/rfc/rfc2246.txt

2327

SDP: Session Description Protocol

Yes

Oracle WebLogic Communication Services supports applications that consume or generate SDP. See http://www.ietf.org/rfc/rfc2327.txt

2460

Internet Protocol, Version 6 (IPv6) Specification

Yes

See http://www.ietf.org/rfc/rfc2460.txt

2543

SIP: Session Initiation Protocol (v1)

Yes

Oracle WebLogic Communication Services supports backward compatibility as described in this specification. See http://www.ietf.org/rfc/rfc2543.txt

2616

Hypertext Transfer Protocol -- HTTP 1.1

Yes

See http://www.ietf.org/rfc/rfc2616.txt

2617

HTTP Authentication: Basic and Digest Access Authentication

Yes

See http://www.ietf.org/rfc/rfc2617.txt

2782

A DNS RR for specifying the location of services (DNS SRV)

Yes

See http://www.ietf.org/rfc/rfc2782.txt

2806

URLs for Telephone Calls

Yes

See http://www.ietf.org/rfc/rfc2806.txt

2848

The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call Services

Yes (Platform)

Note that implementing PINT services implies a pre-IMS architecture. Although Oracle 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 Oracle WebLogic Communication Services. See http://www.ietf.org/rfc/rfc2848.txt

2916

E.164 number and DNS

Yes

See http://www.ietf.org/rfc/rfc2916.txt

2960

Stream Control Transmission Protocol

Yes

SCTP supported only for Diameter traffic. See http://www.ietf.org/rfc/rfc2960.txt

2976

The SIP INFO Method

Yes

See http://www.ietf.org/rfc/rfc2976.txt

3204

MIME media types for ISUP and QSIG Objects

Yes (Platform)

Oracle WebLogic Communication Services 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

3261

SIP: Session Initiation Protocol

Yes

See http://www.ietf.org/rfc/rfc3261.txt

3262

Reliability of Provisional Responses in the Session Initiation Protocol (SIP)

Yes

See http://www.ietf.org/rfc/rfc3262.txt

3263

Session Initiation Protocol (SIP): Locating SIP Servers

Yes

See http://www.ietf.org/rfc/rfc3263.txt

3264

An Offer/Answer Model with Session Description Protocol (SDP)

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3264.txt

3265

Session Initiation Protocol (SIP)-Specific Event Notification

Yes

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3265.txt

3266

Support for IPv6 in Session Description Protocol (SDP)

Yes

See

http://www.ietf.org/rfc/rfc3266.txt

3268

Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security (TLS)

Yes (Platform)

Oracle WebLogic Communication Services 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

3311

The Session Initiation Protocol (SIP) UPDATE Method

Yes

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3311.txt

3312

Integration of Resource Management and Session Initiation Protocol (SIP).

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3312.txt

3313

Private Session Initiation Protocol (SIP) Extensions for Media Authorization

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3313.txt

3323

A Privacy Mechanism for the Session Initiation Protocol (SIP)

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3323.txt

3325

Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks

Yes

See http://www.ietf.org/rfc/rfc3325.txt

3326

The Reason Header Field for the Session Initiation Protocol (SIP)

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3326.txt

3327

Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts.

Yes (Platform)

See http://www.ietf.org/rfc/rfc3327.txt

3351

User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired Individuals

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3351.txt

3372

Session Initiation Protocol for Telephones (SIP-T): Context and Architectures

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3372.txt

3388

Grouping of Media Lines in the Session Description Protocol (SDP)

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3388.txt

3420

Internet Media Type message/sipfrag

 

See

http://www.ietf.org/rfc/rfc3420.txt

3428

Session Initiation Protocol (SIP) Extension for Instant Messaging

Yes

See http://www.ietf.org/rfc/rfc3428.txt

3455

Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3455.txt

3489

STUN-SimpleTraversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)

Yes

See http://www.ietf.org/rfc/rfc3489.txt

3515

The Session Initiation Protocol (SIP) Refer Method.

Yes

See http://www.ietf.org/rfc/rfc3515.txt

3524

Mapping of Media Streams to Resource Reservation Flows

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3524.txt

3556

Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3556.txt

3578

Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP)

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification, but it does not provide an ISUP interface. See http://www.ietf.org/rfc/rfc3578.txt

3581

An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing

Yes

See http://www.ietf.org/rfc/rfc3581.txt

3589

Diameter Command Codes for Third Generation Partnership Project (3GPP) Release 5

Yes

See http://www.ietf.org/rfc/rfc3589.txt

3588

Diameter Base Protocol

Yes

See http://www.ietf.org/rfc/rfc3588.txt

3605

Real Time Control Protocol (RTCP) attribute in Session Description Protocol ((SDP)

 

See http://www.ietf.org/rfc/rfc3605.txt

3608

Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration.

Yes (Platform)

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 functionality can be implemented as part of the application. See http://www.ietf.org/rfc/rfc3608.txt

3665

Session Initiation Protocol (SIP) Basic Call Flow Examples.

Yes

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3665.txt

3666

Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call Flows

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3666.txt

3680

A Session Initiation Protocol (SIP) Event Package for Registrations

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3680.txt

3689

General Requirements for Emergency Telecommunication Service (ETS)

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3689.txt

3690

IP Telephony Requirements for Emergency Telecommunication Service (ETS)

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3690.txt

3702

Authentication, Authorization, and Accounting Requirements for the Session Initiation Protocol (SIP)

Yes

Oracle WebLogic Communication Services version supports JDBC and LDAP. See http://www.ietf.org/rfc/rfc3702.txt

3725

Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)

Yes

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3725.txt

3761

The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)

Yes

See http://www.ietf.org/rfc/rfc3761.txt

3764

Enumservice Registration for Session Initiation Protocol (SIP) Addresses-of-Record

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3764.txt

3824

Using E.164 numbers with the Session Initiation Protocol (SIP)

Yes

See http://www.ietf.org/rfc/rfc3824.txt

3840

Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3840.txt

3841

Caller Preferences for the Session Initiation Protocol (SIP)

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3841.txt

3853

S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP)

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3853.txt

3856

Presence Event Package for the Session Initiation Protocol (SIP)

Yes

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3856.txt

3857

Watcher Information Event Template-Package for the Session Initiation Protocol (SIP)

Yes

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3857.txt

3858

Extensible Markup Language (XML) Based Format for Watcher Information

Yes

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3858.txt

3863

Presence Information Data Format (PIDF)

Yes

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3863.txt

3891

The Session Initiation Protocol (SIP) 'Replaces' Header

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3891.txt

3892

The Session Initiation Protocol (SIP) Referred-By Mechanism

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3892.txt

3893

Session Initiation Protocol (SIP) Authenticated Identity Body (AIB) Format

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3893.txt

3903

Session Initiation Protocol (SIP) Extension for Event State Publication

Yes

See http://www.ietf.org/rfc/rfc3903.txt

3911

The Session Initiation Protocol (SIP) "Join" Header

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3911.txt

3959

The Early Session Disposition Type for the Session Initiation Protocol (SIP)

 

See http://www.ietf.org/rfc/rfc3959.txt

3960

Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP)

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc3960.txt

3966

The tel URI for Telephone Numbers

Yes

See http://www.ietf.org/rfc/rfc3966.txt

4028

Session Timers in the Session Initiation Protocol (SIP)

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc4028.txt

4032

Update to the Session Initiation Protocol (SIP) Preconditions Framework

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc4032.txt

4244

An Extension to the Session Initiation Protocol (SIP) for Request History Information

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc4244.txt

4320

Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction

 

See http://www.ietf.org/rfc/rfc4320.txt

4321

Problems Identified Associated with the Session Initiation Protocol's (SIP) Non_INVITE Transaction

 

See http://www.ietf.org/rfc/rfc4321.txt

4474

Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)

Yes

See http://www.ietf.org/rfc/rfc4474.txt.

4479

Data Model for Presence

Yes

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc4479.txt.

4480

RPID: Rich Presence Extensions to the Presence Information Data Format

Implicitly Supported

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc4480.txt.

4481

Timed Presence Extensions to the Presence Information Data Format (PIDF) to Indicate Status Information for Past and Future Time Intervals

Implicitly Supported

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc4481.txt.

4483

A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See http://www.ietf.org/rfc/rfc4483.txt.

4825

The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)

Partially Supported

No support for partial document manipulation (XPath)

4827

Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document Contents

Yes

Replaces draft-ietf-simple-xcap-pidf-manipulation-usage-02

draft-levy-sip-diversion-08

Diversion Indication in SIP

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See https://datatracker.ietf.org/public/idindex.cgi?command=id_detail&id=6002

draft-donovan-mmusic-183-00

SIP 183 Session Progress Message Draft

Yes (Platform)

Oracle WebLogic Communication Services supports applications that conform to this specification. See https://datatracker.ietf.org/public/idindex.cgi?command=id_detail&id=4308

draft-ietf-sip-gruu-15

Obtaining and Using Globally Routable User Agent (UA) URIs (GRUU) in the Session Initiation Protocol (SIP)

Yes

See http://www.ietf.org/internet-drafts/draft-ietf-sip-gruu-15.txt

Presence Authorization Rules

draft-ietf-simple-presence-rules-04

Yes

http://tools.ietf.org/html/draft-ietf-simple-presence-rules-10

OMA extensions to the presence data model

OMA-TS-Presence_SIMPLE-V1_0-20051122-C

Yes

 

OMA extensions to geopriv common policy

OMA-TS-XDM_Core-V1_0-20051122-C

Yes

 

OMA extensions to presence rules

OMA-TS-Presence_SIMPLE_XDM-V1_0-20051122-C

Yes

 

E.8 3GPP R6 Specification Conformance

Table E-3 summarizes the ability of Oracle WebLogic Communication Services to support implementation of the 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. The default behavior of the Oracle WebLogic Communication Services Sip Servlet Container is to pass unrecognized headers, request methods and payloads to SIP Servlets using normal SIP Servlet API procedures.

Table E-3 3GPP R6 Specification Conformance

Specification Comments

3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2 (Release 6)"

  • No comments.

3GPP TS 24.229: "IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (Release 6)"

  • 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.7.1.2. Oracle WebLogic Communication Services does enforce uniqueness.

  • Oracle WebLogic Communication Services does not provide privacy support as described in sub-section 5.7.3.

3GPP TS 23.141: "Presence Service; Architecture and Functional description (Release 6)"

  • Oracle WebLogic Communication Services does not natively support the Ph (MAP), Pl (LIF-MLP), Px (DIAMETER Cx/Dx), Pg (phase 4, 3GPP Release 5),Pc (CAMEL phase 4, 3GPP Release 5) or Pr, Pk and Pp (RADIUS) reference points.

  • Oracle WebLogic Communication Services does not support IPv6 as required for the Presence User Agent (Peu) reference point as required in sub-section 4.3.1.

3GPP TS 23.218: "IP Multimedia (IM) session handling; IM call model; Stage 2 (Release 6)"

  • No comments.

3GPP TS 24.247 "Messaging using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 (Release 6)"

  • Oracle WebLogic Communication Services does not provide support for the Message Session Relay Protocol (MSRP), although it is presumed that an MSRP relay will typically be implemented as a Media Resource Function in the IMS architecture.

3GPP TS 24.841: "Presence service based on Session Initiation Protocol (SIP); Functional models, information flows and protocol details (Release 6)"

  • Oracle WebLogic Communication Services does not provide support for IETF RFC 3310: "Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)".

3GPP TS 24.109: "Bootstrapping interface (Ub) and Network application function interface (Ua); Protocol details (Release 6)"

  • Oracle WebLogic Communication Services does not provide support for IETF RFC 3310: "Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)".

  • 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.

3GPP TS 29.328: "IP Multimedia Subsystem (IMS) Sh interface; Signalling flows and message contents"

  • No comments.

3GPP TS 29.329: "Sh interface based on the Diameter protocol; Protocol details"

  • No comments.

3GPP TS 32.299: "Telecommunication management; Charging management; Diameter charging applications"

  • No comments.

3GPP TS 33.222: "Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS) (Release 6)"

  • Oracle WebLogic Communication Services supports the Application Server role in the GAA.