Change Request Number/BugDB ID
|
Description and Workaround or Solution
|
|
|
|
|
If you stop one AT server and one NT server in a multi-cluster domain and then restart only the AT server, application-initiated requests sent to that server may result in the following error with the message: “Failed to invoke end component <component name>”. In the reverse case, network-triggered requests may fail.
Dependent on Oracle WebLogic Server CR384639.
Make sure you start both servers.
Contact Oracle support for a patch on this issue.
|
|
|
|
|
If the credit control interceptor fails to connect to the Diameter server, the isConnected attribute will show the incorrect state.
Run traffic to check whether the interceptor is connected.
|
|
|
|
|
The Parlay X 2.1Short Messaging/SMPP plug-in does not support in-production upgrade after upgrading from 4.0.
Before you do a rolling upgrade to the servers, undeploy the EAR file for this communication service. After all upgrades are complete, redeploy the EAR.
This does not affect fresh installations of 4.1.
| Note: |
A mandatory patch will be released to correct this error. Please contact your Oracle service representative about acquiring this patch when it comes out. |
|
|
|
|
|
Due to an error in the data migration scripts, old SP SLAs are not changed.
Necessary script updates can be found in
“Upgrading Oracle Communications Services Gatekeeper” in Installation Guide, a separate document in this set.
|
|
|
|
|
PRM service provider users and operator users cannot be given access to a restricted set of JMX interfaces exposed by Oracle Communications Services Gatekeeper.
Dependent on Oracle WebLogic Server CR382906.
|
|
|
|
|
The SOAP to SOAP generation does not support all WSDLs.
The WSDL defining the application-facing interface must adhere to the following:
- Attribute name in <wsdl:service> must include the suffix Service.
- Attribute name in <wsdl:port> must be the same as the name attribute in <wsdl:service>, excluding the suffix Service.
Dependent on Oracle WebLogic Server CR384278.
|
|
|
|
|
The Native SMPP communication service does not actively disconnect applications if the SMSC connection is down.
The communication service sends an OK response to enquire link requests in this case.
|
|
|
|
|
When Services Gatekeeper is first used, the database is initialized. If two NT servers are started up at the same time, they may both try to initialize the database, causing a Service Deployment Exception and one server failing to start up.
Make sure the servers are started one at a time.
Restart the failed server.
|
|
|
|
|
Some Diameter requests may be dropped during patching, redeployment, or upgrade of the CDR to Diameter module.
Check the database for the time period during which the transition took place. All CDRs are stored in the database.
|
|
|
|
|
The Native SMPP Communication Service does not support hitless upgrades. Upgrades cannot be performed without traffic service interruption.
Perform a rolling upgrade instead.
|
|
|
|
|
The Plug-in Manager reports that plugin_sms_smpp state is connected even when it is not.
Use the ActiveStatus attribute of the SMPP MBean to check connection status.
|
|
|
|
|
When running the Legacy SMPP communication service, you may receive the following exception from your NT servers.
ERROR com.bea.wlcp.wlng.legacy.smpp.connector.SmppChannelProcessor - Could not find request for received response
This exception can be ignored.
|
|
|
|
|
Due to incompatible class changes to the stored blob data, old application data (notifications, etc.) in SIP call notification and presence plug-ins will NOT be usable after the upgrade. Exceptions will be thrown during the upgrade when the old application data is accessed.
Contact Oracle support for migration scripts.
|
|
|
|
|
The client cannot receive a delivery report that comes through a plug-in different from the one that sent the original request.
|
|
|
|
|
Services Gatekeeper does not detect when an application abnormally terminates, and therefore does not unbind the RX connection toward the SMSC.
|
|
|
|
|
Propagating the message ID in the short_message parameter of the deliver_sm operation is not supported for delivery receipts.
|
|
|
|
|
The sequence number and message ID are not included in SMS EDRs.
|
|
|
|
|
Support for windowing between Services Gatekeeper and the SMSC is not present.
|
|
|
|
|
Parlay X SMS does not function correctly because the SMPP plug-in does not send the enquire link to the SMSC.
|
|
|
|
|
The Parlay X 2.1 SMPP plug-in does not send a delivery report to the application if the message ID format in submitSm_response is different from the format in the delivery receipt (for example, hex format in one and decimal format in the other).
|
|
|
|
|
Applications are able to bind connections using connection types (for example, TX) that do not match the legacy plug-in connection type (for example, RX).
A new attribute, LooseBinding, has been added to control binds. For more information, see “Managing and Configuring Native SMPP Communication Services” in System Administrator’s Guide.
|
|
|
|
|
When multiple applications bind and unbind simultaneously, Services Gatekeeper opens more than the configured SMPP connection toward the SMSC.
|
|
|
|
|
Due to message IDs being case sensitive in the Oracle database, there are delivery report issues after applying bug patch 8238745.
Message IDs are now converted to lowercase.
|
|
|
|
|
If two application instances using same credentials bind to Services Gatekeeper and then one application unbinds, Services Gatekeeper closes all connections toward the SMSC, causing the other application to fail.
|
|
|
|
|
For terminal location calls, Services Gatekeeper sends a location-end notification to the application based on the call-duration parameter instead of the start and end time parameters, causing calls to be terminated at the wrong time.
|
|
|
|
|
The data types that Services Gatekeeper uses for the HOR_ACC and ALT_ACC elements of the Mobile Location Protocol (MLP) do not comply with the MLP standard.
|
|
|
|
|
Services Gatekeeper does not route delivery responses back to the SMSC.
|
|
|
|
|
The Parlay X 2.1 Presence/SIP commuication service does not support the OMA Presence attribute, overriding-willingness.
|
|
|
|
|
If the operation removeServiceProviderAccount is executed for a non-existent account, the Administration Console reports that the operation was successful instead of returning an error.
An exception is returned if the account does not exist.
|
|
|
|
|
The Administration Console allows management users to be added to a non-existent management user group without producing an error.
An exception is returned if the management user group does not exist.
|
|
|
|
|
The Parlay X 2.1 Presence/SIP communication service does not handle the P-Asserted-Identity header in the SIP subscribe message sent to the Presence server.
|
|
|
|
|
The Services Gatekeeper Parlay X 2.1 PresenceConsumer interface does not support the Expire parameter.
|
|
|
|
|
Services Gatekeeper does not support the TEL and SIP address schemes.
|
|
|
|
|
Services Gatekeeper does not support additional parameters in the SIP request URI.
Additional parameters are now supported. However, if subscription data is stored with the SIP URI, that data must be included when retrieving presence for the URI.
|
|
|
|
|
Workshop controls do not work correctly in session-based installations.
|
|
|
|
|
Services Gatekeeper does not handle empty SIP notifications sent from the Presence server.
|
|
|
|
|
Services Gatekeeper does not support the SMPP cancel_sm operation if the message ID is not provided.
|
|
|
|
|
Services Gatekeeper does not validate the input data for the startSmsNotification operation for the Parlay X SMS service.
|
|
|
|
|
The Administration Console will create management users even if the specified user type, level, or both are invalid.
|
|
|
|
|
Services Gatekeeper incorrectly handles remote exception that occurs during network tier node communication.
Cluster communication has been improved to consider server overload issues when a node is overloaded or is out of memory.
|
|
|
|
|
Extended short code service is required in Services Gatekeeper.
|
|
|
|
|
If the operation removeServiceProviderGroup is executed for a non-existent service provider group, the Administration Console reports that the operation was successful instead of returning an error.
An exception is returned if the service provider group does not exist.
|
|
|
|
|
The Administration Console allows short-code mapping with erroneous input values when executing the addShortCodeMapping operation.
|
|
|
|
|
If the operation removeApplicationAccount is executed for a non-existent account, the Administration Console reports that the operation was successful instead of returning an error.
An exception is returned if the account does not exist.
|
|
|
|
|
Newly created management users are not able to log in to the Administration Console in a cluster environment.
|
|
|
|
|
When executing the removeApplicationGroup operation in the Administration Console, it is possible to remove an existing application or service provider group that still has applications associated with it.
|
|
|
|
|
Services Gatekeeper does not validate the time set in the Parlay X Terminal Location StartGeographicalNotification interface.
|
|
|
|
|
Services Gatekeeper cannot receive SMPP submit_sm_resp messages that have no body.
|
|
|
|
|
It is possible to get zombie connections in a legacy SMPP plug-in if only some of the connections are successful during the bind.
|
|
|
|
|
The Terminal Location communication service requires the time zone to be entered in the format yyyy-MM-ddThh:mm:ss[+|-]HHMM instead of the format yyyy-MM-ddThh:mm:ss[+|-]HH:MM
|
|
|
|
|
The SMPP cancel_sm, query_sm, and replace_sm operations do not work properly with an Oracle database because the database queries are case sensitive.
|
|
|
|
|
Problem with validating the start time and stop time in Terminal Location startGeographicalNotification requests.
|
|
|
|
|
Null values are being sent in the start_time parameter to the Gateway Mobile Location Center (GMLC) during load tests.
|
|
|
|
|
The global node SLA is incorrectly applied if there is no reqLimitGuarantee element present in the Service Provider SLA.
|
|
|
|
|
The StatusText block is not included in the Status element in DeliverRsp and DeliveryReportRsp messages.
|
|
|
|
|
There are currently no originating and destination addresses for EDR and CDRs generated for mobile originating and MMS messages.
|
|
|
|
|
An exception is thrown when trying to generate an MIB file by using the generate-mib Ant task.
|
|
|
|
|
When executing the addApplicationInstance operation in the Administration Console, it is possible to create an application instance that has no instance name.
|
|
|
|
|
Services Gatekeeper does not validate the parameters for the startMessageNotification operation for Parlay X MMS.
|
|
|
|
|
When management users change passwords, Services Gatekeeper does not validate whether the new password is the same as the old password.
|
|
|
|
|
The SMPP cancel_sm operation fails when the service type is set to VMA, due to service types being case sensitive in the Oracle database.
|
|
|
|
|
Images arrive distorted when sending logos via SMS messages to mobile units.
|
|
|
|
|
Services Gatekeeper does not provide adequate validations while creating a Parlay X MMS plug-in instance.
|
|
|
|
|
When using the sendSmsRingtone operation, ring tones are not played at the mobile device.
|
|
|
|
|
The service name is missing from the mobile originating SMPP SMS CDR.
|
|
|
|
|
When a cancel_sm message is invoked and the message has no ID, the message is not routed to the correct plug-in instance.
|
|
|
|
|
An incorrect SQL query for processing cancel_sm requests causes a severe load on the server.
|
|
|
|
|
The Logica SMPP API used in Services Gatekeeper incorrectly parses responses that are grouped in a single TCP package.
|
|
|
|
|
Incorrect CDR generation points for mobile originating messages in Legacy SMPP communication service.
|
|
|
|
|
The cancel_sm_resp operation deletes the message data, preventing the delivery receipt with the final status from being processed and delivered to the application.
|
|
|
|
|
Need to be able to set independent TON and NPI values per plug-in for source and destination addresses at bind time for Parlay X SMPP.
|
|
|
|
|
Cannot create a shortcode if using the RESTful interface,
|
|
|
|
|
The Parlay X 2.1 SMPP plug-in returns NoMatchingOfflineNotificationException for concatenated SMS messages due to incorrect criteria evaluation.
|
|
|
|
|
When using the PTE to send an MT SMS message using legacy SMPP, the PTE generates multiple CDRs for one transaction.
|
|
|
|
|
The PTE returns DeliveryNotificationException when both REST SMS and REST binary SMS clients are used at the same time.
|
|
|
|
|
The Parlay X SMPP plug-in is not returning DeliverSm responses to the SMSC when the SMS messages are segmented.
|
|
|
|
|
No alarm is generated when an application tries to use an invalid log-in session.
|
|
|
|
|
More details are needed in alarms to assist with troubleshooting.
Additional details will be added to alarms where applicable, such as originating and destination addresses, sequence numbers, command status, and error descriptions.
|
|
|
|
|
Trace files do not include enough information to be able to debug and track failed messages and failed requests.
|
|
|
|
|
When a mobile originating request reaches a node that does not contain an application bind, Services Gatkeeper rejects the message with an exception. Too many such exceptions can cause a server to run out of memory and be shut down.
|
|
|
