Send USSD Notification Feature Node does not Correctly End the Dialog after Sending the Notification (Doc ID 1487756.1)

Last updated on SEPTEMBER 06, 2016

Applies to:

Oracle Communications Network Charging and Control - Version 2.2.0 and later
Information in this document applies to any platform.

Symptoms

Whenever the Send USSD Notification (USSN fast key) feature node is used to send a notification to the HLR (Home Location Register), one of the following error messages is generated in the syslog (/var/adm/messages) on the SLC (Service Logic Controller):

TID = TCAP transaction ID (decimal)


Further diagnosis of the traffic, captured in a trace, will reveal that the HLR is sending an abort after some timeout period:


  SLC                                HLR
   |                                  | 
   |-----TCAP_BEGIN(USSD Notify)----->|
   |                                  |
   |<-TCAP_CONTINUE(returnResultLast)-|
   |                                  |

   ~                              [timeout]
   |                                  |
   |<-----------TCAP_ABORT------------|

 

Or that the SLC is sending the abort fairly quickly after the response from the HLR:
 

  SLC                                HLR
   |                                  | 
   |-----TCAP_BEGIN(USSD Notify)----->|
   |                                  |
   |<-TCAP_CONTINUE(returnResultLast)-|
   |                                  |
   |------------TCAP_ABORT----------->|

 

Changes

Adding the USSN feature node to control plans, or upgrading software to Network Charging and Control (NCC) 4.3.0 or higher.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms