| Oracle® Communications Services Gatekeeper Release Notes Release 5.0 Part Number E18543-02 |
|
|
View PDF |
| Oracle® Communications Services Gatekeeper Release Notes Release 5.0 Part Number E18543-02 |
|
|
View PDF |
Release Notes
Release 5.0
E18543-02
April 2011
These release notes list the new and enhanced features, and the resolved and known issues, in Oracle Communications Services Gatekeeper, Release 5.0.
This section describes new features and feature enhancements in Services Gatekeeper Release 5.0.
A new standalone, customizable SDK provides an easy-to-use application test environment (ATE) for application developers. See SDK User's Guide.
The Platform Development Environment (PTE) Graphical User Interface has been rearranged to include the new Services Gatekeeper features. The PTE now includes a network simulation map that you populate with network nodes and use to test your network services.
For more information see Platform Test Environment Guide.
Services Gatekeeper is newly certified to be deployed with the following databases:
Oracle 11g RAC
Oracle 11g
MySQL 5.1
Services Gatekeeper no longer includes IONA Orbacus.
If you are using a communication service that requires an ORB, install the ORB after installing Services Gatekeeper. See the "Install Orbacus" section of the "Completing Post-Installation" chapter in Installation Guide.
It is now possible to define an SLA over a combination of communication services. See the “Defining Composed Service Contracts” chapter in Accounts and SLAs Guide.
Services Gatekeeper supports the Coherence storage provider. See the “Configuring Coherence” chapter in System Administrator's Guide.
Services Gatekeeper allows the addition and modification of Diameter attribute/value pairs (AVPs) through configuration or a run-time access API. This feature is supported for standard Diameter commands commands271, 272) and payment plug-in/credit control interceptor-specific AVPs. See the “Customizing Diameter AVPs” chapter in Platform Development Studio Developer's Guide.
Services Gatekeeper has added a new SMPP Server Service that provides connection services and some other protocol-related features, such as windowing. The Parlay X 2.1 Short Messaging, Extended Web Services Binary SMS, and Native SMPP communication services all use this SMPP Server Service.
Some configuration options that used to be in the plug-in MBeans are now configured in the SMPP Server Service. See the “Managing and Configuring Native SMPP Communication Services” chapter in System Administrator's Guide for a description of the SMPP Server Service and Native SMPP plug-in options. See the “Managing and Configuring Short Messaging Communication Services” chapter in System Administrator's Guide to see which options are configured in the Parlay X 2.1 Short Messaging and Extended Web Services Binary SMS plug-ins.
The Services Gatekeeper SOA facades are now based on the OSB version 11g. They also support the new Services Gatekeeper communication services introduced in Release 5.0.
Services Gatekeeper supports Internet Protocol version 6 (IPV6) in the following communication services: Parlay X 2.1 SMS/SMPP, Native SMPP, Parlay X 2.1 MMS, and Parlay X2.1 Terminal Location.
Services Gatekeeper provides the new communication services listed below.
See the appropriate chapters in the System Administrator's Guide, Communication Service Reference, Application Developer's Guide and RESTful Application Developer's Guide for details about these services.
Services Gatekeeper provides a Parlay X 2.1 Audio Call communication service that supports the SIP network protocol.
This communication service supports:
Sending an audio file to a terminal.
Retrieving the status for a Parlay X 2.1 Audio call (played, playing, pending, or error).
Explicitly ending an audio call.
The Audio Call/SIP plug-in is usable only with high availability systems if the media server supports clustering. See your media server documentation to find out whether the media server supports clustering.
For more information, see "Parlay X 2.1 Audio Call Communication Service" in Communication Service Reference.
Services Gatekeeper provides a Parlay X 3.0 Device Capabilities communication service that supports the LDAP protocol.
The Device Capabilities communication service sends requests to any LDAPv3-compliant directory server with a device's address and in return receives one of the following device identifiers:
The device's unique device ID, device/model name, and a link to the User Agent Profile XML file.
The device's equipment identifier (for example, its IMEI).
For more information, see "Parlay X 3.0 Device Capabilities and Configuration Communication Service" in Communication Service Reference.
Services Gatekeeper provides a Native UCP-UCP(5.0 ""EMI-UCP Interface) communication service. See "Native UCP Communication Service" in Communication Service Reference.
Services Gatekeeper now provides Parlay X3.0 /REST Terminal Status communication service notification interfaces that support the MAP network protocol. Using this communication service you can:
Obtain the status (reachable, unreachable, or busy) of a single terminal or group of terminals as often as you specify, within a time period you specify.
Return the status of a terminal or group of terminals if the status changes. The terminal statuses are checked as frequently as you specify, for a time period you specify.
For more information see "Parlay X 2.1 Terminal Status Communication Service" in Communication Service Reference.
Services Gatekeeper has enhanced the following communication services.
See the appropriate chapters in the System Administrator's Guide, Communication Service Reference, Application Developer's Guide and RESTful Application Developer's Guide for details about these services.
The Parlay X 2.1 MultiMedia Messaging/MM7 communication service has been upgraded to support version 6.8.0.
Services Gatekeeper supports ChargedParty and ChargedParty ID in the Parlay X2.1 MM7 plug-in through context attributes. See the “Parlay X 2.1 Multimedia Messaging Communication Service” chapter in Communication Service Reference.
Services Gatekeeper supports the standard XSD version REL-5-MM7-1-0 for the Parlay X 2.1 MM7 communication service.
Services Gatekeeper supports tunneling USSD (3G TS 23.090 version 3.0.0) messages through the SMPP protocol. This uses SMPP as the transport mechanism and supports both MO and MT traffic and additional TLV required for submit_sm and deliver_sm operations. See the ussd_service_operation parameter in the “Parlay X 2.1 Short Messaging Communication Service” and “Native SMPP Communication Service” chapters in Communication Service Reference.
Services Gatekeeper supports all standard character encodings for the short messaging communication service.
This communication service uses the new SMPP Server Service for connection services with the Small Message Service Center (SMSC).
In previous releases, there were three attributes:
TransceiverProxyLocalAddressAndPort
TransceiverProxyLocalAddressAndPort
ReceiverProxyLocalAddressAndPort
In the current release these are replaced by the LocalAddress and LocalPort attributes. The bind type is set in the BindType attribute. For valid values, see "Managing and Configuring Short Messaging Communication Service" in System Administrator's Guide.
If the BindType was 0 (Transmitter and Receiver) in 4.1.x, after the upgrade to 5.0, the LocalPort is set to the value that the port was in the TransmitterProxyLocalAddressAndPort attribute from 4.1.x.
This section describes known issues from the previous release that are resolved in this release.
| Bug ID /SR ID | Description |
|---|---|
|
9969772 / SR:3-1970677821 |
Some delivery reports were being lost, because deliveryReport was trying to read mappingInfo from storage before it was written to storage. The fix is to retry the read from storage no more than 5 times before sending a negative response to the SMSC. This can be done by setting a system property such as:
|
|
9826654 / SR:3-185228719 |
When an invalid service provider identifier is entered for the Set Application Account group operation in Application Groups, the correct exception message for a Service Provider account is displayed. |
|
9780794 / SR:3-1817170291 |
A periodic counter checker has been introduced for both the SMPP connector and plug-in. In the connector, the periodic counter checker keeps the application counter accurate. In the plug-in, it ensures that southbound connections are closed properly when there are no northbound connections. |
|
9723289 / SR:3-1624820911 |
Multiple SOAP ports contained in one service are now supported. The way package name is created for north and south classes has changed from using the port name to service name instead. |
|
9462801 / SR:3-151384274 |
Credit control and custom SLAs are now deleted after the associated Service Provider and Application accounts are deleted. |
|
8678848 / SR 7682744.99 |
Multiple plug-in instances, having different serviceIds, can no longer be created with the same name. |
|
8800106 / SR 7735432.992 |
Alarms relating to Parlay X 2.1 Short Messaging (SMS) and Parlay X 2.1 Multimedia Messaging (MMS) communication services now have originatingParty and destinationParty attributes. |
|
8905239 / SR 7555846.993 |
RESTful binary SMS communication service now passes the correct DCS value. |
|
8726273 / SR 7607208.994 |
Services Gatekeeper no longer modifies the headers on SOAP attachments when there are multiple attachments. This issue previously affected MMSs containing Chinese characters. |
|
8840897 / SR 2-5949543 |
A listOnlineBinaryNotificationInfo method has been added to the Parlay X 2.1 Short Messaging/SMPP plug-in MBean. This enables the display of online notifications for binary SMSs. |
|
8855146 / SR 7517297.994 |
Duplicate of 8905239/SR 7555846.993 |
|
8574992 / SR7517297.994 |
Account service no longer permits creation of an empty (all spaces) application group account. Duplicate of 857909. |
|
8438615 / SR 7456902.993 |
Attribute values entered at the administration console are validated for type mismatches. If the input value is invalid, an error message is displayed at the console, and the attribute is not changed. |
|
8981602 / SR 7787001.992 |
The native SMPP plug-in has been enhanced so that if all plug-ins matching the bind type of a northbound connection are lost (connection to SMSC is dropped), the northbound connection is unbound. The UNBIND also considers loose/strict binding. The MBean method The The The It is no longer possible to change the bindtype of a plug-in when the plug-in is connected to an SMSC. Validation added to |
|
8943911 / SR 7634236.994 |
Alarms involving policy evaluation in the native MM7 plug-in now include the |
|
9024388 / SR 2-5991566 |
The sequence number is now correctly incremented for each unbind request. Previously all unbind requests sent from Services Gatekeeper to the application used sequence number 1. |
|
8848266 |
A bind counter was added to the native SMPP plug-in to track the number of applications bound to a connection. This tracking ability reduces the occurrences of memory leaks because plug-ins monitoring the counter know when to close connections to the SMSC. |
|
9049012 / SR 7762885.994 |
The native SMPP plug-in has been updated to correctly use the In addition, if a plug-in fails to bind to the SMSC the first time a connection is established, the heartbeat is started anyway. If all plug-ins fail to bind, the application bind also fails and the plug-ins do not try to re-connect. |
|
9061526 / SR 7835001.992 |
A timeout of five seconds is enforced for opening a socket from the native SMPP plug-in. This prevents hanging threads from blocking other threads, eventually causing a system overload. |
|
9055760 / SR 7834656.992 |
If the native SMPP plug-in cannot find an Previously, it sent the This situation can occur when a long period of time has elapsed between when the message was submitted and the delivery report sent. |
|
9006708 / SR 7814592.992 |
In the native SMPP communication service, the application session is automatically refreshed:
The refresh is transparent to the application, which is able to continue sending requests until it performs an |
|
8613248 / SR 7814592.992 |
Service provider accounts can not be created in which the |
|
8609069 / SR 7604625.992 |
A check is added so a management user and a traffic user can not be created with identical credentials. |
|
9071295 / SR 7837808.992 |
Statistics service is updated to update transaction counters for statistics atomically. |
|
9077470 / SR 7842809.992 |
Generation of SOAP to SOAP communication services using the Platform Development Studio has been updated to refer to the correct version of com.bea.wlcp.wlng.heartbeater_version.jar. |
|
9147072 / SR 3-1090122581 |
Parlay X 2.1 Short Messaging/SMPP has been updated handle empty criteria for notifications, that is, application-initiated online notifications as well as offline and online notifications started by management operations. Empty criteria can overlap other criteria for a certain activation number and will be treated as default. For example, if three notifications are started for tel:1234, one with criteria asdf, one with criteria 1234, and one with empty criteria, messages that start with 'asdf' or 1234 are handled by the notification with empty criteria. |
|
9164920 / SR 3-1139923971 and 9278174 |
Parlay X 3.0 Payment/Diameter has been updated with an MBean attribute that defines the Service-Context Id AVP. If not specified, The new MBean methods are: /** * Service-Context-Id AVP's domain. */ public String domain = "oracle.com"; public void setDomain(String value) throws ManagementException; public String getDomain() throws ManagementException; |
|
9064216 / SR 7588302.994 |
Logging has been improved by adding MMS request/response information for all failed and success requests based on priority logging for the following Parlay X MM7 operations:
|
|
8899647 / SR 2-5875340 |
Partner Relationship Management implementation has been updated to look up and retry MBean invocations. There was a problem accessing certain MBeans after a restart of the administration server. |
|
9185625 / SR 3-1096187521 |
The Parlay X 2.1 MultiMedia Messaging/MM7 plug-in has been updated to respond to a malformed request from an MMSC according to the MM7 specification. |
|
8866684 / SR 7668405.992 |
The Parlay X 2.1 Short Messaging/SMPP plug-in has been updated to send a configurable error code to the SMSC if a delivery notification or mobile-originated message could not be delivered to the requesting application and there is no matching offline notification. The configuration attribute is DeliverSmRespCommandStatus. |
|
8866684 / SR 3-1132029711 |
The Parlay X 2.1 Short Messaging/SMPP plug-in has been updated to allow applications to define whether they want delivery reports and to specify the message priority. Applications specify whether delivery reports will be requested using the tunneled parameter (xparam) com.bea.wlcp.wlng.plugin.sms.RequestDeliveryReportFlag. Setting it to true requests a delivery report. The priority order is:
Applications specify the message priority using the tunneled parameter (xparam) com.bea.wlcp.wlng.plugin.sms.Priority. Valid values (case sensitive) are HIGH and LOW. |
|
9192234 / SR 3-1131773221 |
Statistics service updated to generate statistics of type TRANSACTION_TYPE_MESSAGING_RECEIVE when mobile-originated messages are received by Parlay X 2.1 Short Messaging/SMPP and Binary SMS/SMPP. |
|
9294040 / SR 3-1305642511 |
The Parlay X 2.1 MultiMedia Messaging/MM7 plug-in has been updated to support the service code parameter according to the MM7 specification. The service code is configured in the ServiceCode management attribute. If this value is null, no service code is used. |
|
9307594 / SR 3-1334865211 |
The Parlay X 2.1 MultiMedia Messaging/MM7 plug-in has been updated. It now routes MO MM7 messages to applications as indicated below, based on criteria that may have been provided when the notifications were created. The behavior for matching criteria is:
|
|
9315124 / SR 3-1244353221 |
The Parlay X 2.1 MultiMedia Messaging/MM7 plug-in has been updated to handle malformed message content from the MMSC. If the If the This check can be disabled by setting the |
|
9359887 / SR:3-1364115371 |
The Parlay X 2.1 Short Messaging/SMPP plug-in has been updated to allow applications to define the SMPP sub-unit field Applications specify this parameter using the tunneled parameter (xparam) |
|
9321567 / SR 3-1244130326 |
See description of bug 8866684. |
|
8977936 / SR-8977936 |
The Parlay X 2.1 MultiMedia Messaging/MM7 plug-in has been updated to create CDRs correctly. The default wlng-edr.xml file has been updated to filter EDRs for mobile-terminated MMSs correctly. |
|
9390474 / SR 3-1442552291 |
The SOAP2SOAP communication service now correctly reports undeclared SOAP2SOAP fault messages (without namespaces in the URI). They are now passed back to the application that caused them. |
|
9314292 / SR 3-1244130311 |
The Parlay X 2.1 MultiMedia Messaging/MM7 plug-in no longer treats date and time values as mandatory parameters. MM7 messages are now processed correctly regardless of whether the contain correct data and time values. |
|
9410852 / SR 3-1442552291 |
The SOAP2SOAP communication services now correctly return SOAP faults to their originating application. Note that the -Dweblogic.wsee.soap.81CustomException=true flag must be set in order to push the soap faults defined in WSDL as-is. This fix replaces the fixes to 8149902 and 9406223. |
|
9178281 / SR 2-6029605 |
The The text in the payload of the short message is used to determine which application receives the notification. The text is matched in two steps: 1. The entire string is compared against the incoming short message for an exact match. 2. If no match is found, the plug-in matches the short message one word at a time against the criteria string, up to the value set in the |
|
9338436 / SR 3-1332612277 |
The Parlay X 2.1 Short Messaging/SMPP plug-in The If the link has been silent since the last schedule time limit, the plug-in sends an If there are outstanding requests that stop the Duplicate of 9238223. |
|
9338223 / SR:3-1332740944 |
In the Parlay X 2.1 Short Messaging/SMPP plug-in, the
Duplicate of 9338436. |
|
9020004 / SR 2-5831656 |
The Parlay X 2.1 MultiMedia Messaging/MM7 plug-in now routes mobile-originated MMS messages with empty subject lines to the correct application. If there is a subject, it is used as filter criteria. If there is no subject, the first word of the first text attachment is used as filter criteria. If there is no subject and no text attachment, the message can not be delivered. Duplicate of 9307594. |
|
9214390 / SR 3-1193433921 |
The Parlay X 2.1 MultiMedia Messaging/MM7 plug-in now supports the XSD Version REL-5-MM7-1-0 for MM7 messages specification. |
|
9461690 / SR 3-1430848691 |
The Parlay X 2.1 Short Messaging/SMPP plug-in now includes a boolean Previously only segmented messages such as ringtones, logos, and long SMSs could be carried as an optional message_payload. |
|
9383651 / SR 3-1355119241 |
Two new EDRs have been added to the Parlay X 2.1 Short Messaging/SMPP plug-in: EDR #7016 is triggered when a mobile-originated SMS (binary or text) is successfully delivered to application endpoint. EDR #7017 is triggered when a mobile-originated SMS (binary or text) is stored to database. |
|
9475202 / SR 3-1329676931 |
The Parlay X 2.1 Short Messaging/SMPP plug-in now captures the This plug-in also now handles expired messages with null destination addresses correctly. |
|
9504688 / SR 3-1575887181 |
The SOAP2SOAP communication services now allow |
|
9508148 / SR 3-1522413101 |
Extended Web Services WAP Push/PAP has been updated with the |
|
9374912 / SR 3-1391133611 |
The Partner Relationship Management operation |
|
9004013 / SR 7723606.994 |
Parlay X 2.1 Short Messaging plug-in CDRs now include the session ID. The message ID has been added as the session id in EdrConstants.FIELD_CDR_SESSION_ID. |
|
8664305 / SR 2-6003112 |
Before a Submit_mm7 SOAP request is submitted, an element named "TransactionID" is added to the SOAP header and This fixes a problem in which a MustUnderstand error was thrown by the SOAP processor, causing the native MM7 facade to fail when delivery notification was enabled. |
|
9352917 / SR:3-1404378141 |
A new attribute has been added to the Terminal Location plug-in: |
|
9555507 / SR 3-1575887181 |
In the Platform Development Studio, callbacks ((CallbackPortTypeImpl.cg) have been updated. The correct port name now appears in the WLHttpTransport annotation.Names of passed-in parameters are no longer hard coded. Support has been added for one-way operations. |
|
9628891 / SR:3-1493022241 |
The Parlay X 2.1 Short Messaging/SMPP plug-in now permits empty mobile-originated messages. |
|
9582620 / SR:3-1662481611 |
In the Platform Development Studio, the previously-missing |
|
9664039 / SR:3-1708743341 |
That native SMPP plug-in handles all PDUs read from a single channel (TCP connection) in serial rather than parallel. This corrects the problem of messages being received out of order. |
|
9667564 / SR:3-1719632531 |
Instead of all Parlay X 2.2/SMPP plug-ins sending The plug-ins must be configured correctly to support this behavior:
|
|
9321890 / SR:3-1363049451 |
In the Parlay X 2.1 Short Messaging/SMPP plug-in, segments in split SMSs are correctly concatenated with other segments in the same message. This also resolves 9019838 / SR 7815146.992. |
This section describes known problems in Services Gatekeeper 5.0.
Table 2 Known Problems in this Release
| Bug ID | Description |
|---|---|
|
10160804 |
The Tieto Enator (TE) library is not included in the installer. Customers using the Terminal Status communication service must add the TE library manually and provision their licenses before creating a Terminal Status plug-in. To add and activate the TE library, do the following commands:
After running these commands, either restart the Services Gatekeeper server or redeploy wlng_nt_terminal_status_px21.ear. Then create and provision the Terminal Status plug-in. |
|
10155554 |
After a hitless upgrade to Services Gatekeeper 5.0 , the listClientConnections and closeClientConnection Native SMPP operations do not always work properly. The workaround is to set the following values to greater than zero:
These attributes must be set to non-zero in both the NativeSMPP and ParlayX 2.1 Short Messaging/SMPP plugins. These values are set one of two ways: either as parameters to the Native SMPP ApplicationSpecificSettings operation or as attributes in the Administration console. |
|
10147497 |
PasswordDigest authentication is not functioning properly. |
|
9831623 |
When a segmented message is sent through the native UCP communication service, all message segments are not always sent on the same socket channel. |
|
9781397 |
The Native UCP communication service does not stop processing, as it should, after sending a NACK on multiple open sesssion PDUs. The client should not send multiple open session PDUs, but if this does occur, Services Gatekeeper should handle it correctly. The workaround is to use the MBean interface to close any additional client-side connections resulting from multiple open session requests. |
|
8192972 |
The Parlay X SMS/SMPP plug-in handles correlators, such as the ones used in start/stopSmsNotification operations, to check for security violations. These checks should instead be handled the the normal security framework in a plug-in agnostic way. |
|
8179671 |
In the SOAP facade of the Extended Web Services WAP Push/PAP communication service, the value of deliverBeforeTimestamp property set in the SendPushMessage operation cannot be set into a later timestamp. |
|
8177019 |
In the SOAP facade of the Extended Web Services WAP Push/PAP communication service, if the pap.bear-required or pap.network-required property is set in the sendPushMessage operation, the pap.bearer property must be set also. |
|
8176540 |
In the SOAP facade of the Extended Web Services WAP Push/PAP communication service, the error checking of the destination address is faulty. It accepts some poorly-formatted addresses and rejects some valid ones. |
|
10151710 |
SMPP bind and unbind operations in quick succession result in connection errors. The workaround is to sleep for five seconds between bind and unbind operations. |
|
8172929 |
A CDR DB write retry can cause the EDR queue to reach maximum capacity without raising an alarm. In this case, alarm 111103 should be raised. This would alert the operator that CDRs may have been lost. |
|
8823412 |
Services Gatekeeper does not return an appropriate error message to the application when the SMSC does not respond before timeout. This issue was identified in release 4.1.1. |
We have made the following changes to the Services Gatekeeper documentation.
The information about the supported communication services that was previously documented in the Communication Service Reference and in chapters 21 through 35 of the System Administrator's Guide has been combined into a single Communication Service Guide. This new guide presents both general information and OAM properties, operations and attributes per communication service, with one chapter for each service.
The Communication Service Reference has been retired.
Chapters that described OAM for the communication services have been removed from the System Administrator's Guide.
We are publishing for general availability a guide that presents a high-level view of the different deployment strategies for Services Gatekeeper.
We are publishing the Javadoc for Services Gatekeeper OAM and Extensions.
We have reformatted the RESTful Application Developer's Guide to use a more conventional API reference format.
We have added a comprehensive sample SLA in an appendix to the Accounts and SLAs Guide.
We have added a section to the <serviceContract> description in Chapter 7, "Defining Service Provider Group and Application Group SLAs" to address what happens when conflicting enforcements for in <serviceContract> and <serviceTypeContract> are defined in the same SLA.
We have reorganized the information in Chapter 7, "Defining Service Provider Group and Application Group SLAs", and Chapter 8, "Defining Global Node and Service Provider Group Node SLAs", to eliminate redundancy and make the elements easier to find.
We have incorporated the information that was previously in Chapter 9, Defining Composed Service Contracts, into Chapter 8. We have removed Chapter 9.
We have added information about maintaining the database underlying the Services Gatekeeper installation. See "Database Maintenance" in the "Operation and Maintenance" chapter and "Storage Data Expiration" in the "Managing and Configuring the Storage Service" of the System Administrator's Guide.
We have provided more information about the request context as it applies to communication services. See the "Request Context Data Used to Handle Request Flow" section in the "Service Interceptors" chapter in the Platform Development Studio Developer's Guide.
We have added information about requirements for deploying a custom interceptor. See the "Custom Interceptors" section in the "Service Interceptors" chapter in the Platform Development Studio Developer's Guide.
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.
Oracle Communications Services Gatekeeper Release Notes, Release 5.0
E18543-02
Copyright © 2010, 2011, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
|
 Copyright © 2010, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
