Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2309202.1
Update Date:2017-09-19
Keywords:

Solution Type  Technical Instruction Sure

Solution  2309202.1 :   Interface-suspect Binding Removal Rule In Account Exceed Using External Result  


Related Items
  • Oracle Communications Diameter Signaling Router (DSR)
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
  •  




In this Document
Goal
Solution


Created from <SR 3-15688985651>

Applies to:

Oracle Communications Diameter Signaling Router (DSR) - Version DSR 7.3.0 and later
Information in this document applies to any platform.

Goal

This test will demonstrate DSR behavior when:
• PCRF returns Result-Code 3002 to requests with previously bound IMSI.
• PCRF is down when PCEF initiates request with existing binding until Suspect Binding Removal Events Threshold is exceeded

Expected result was not met. Instead the result was:

After 2nd CCA-I with 3002 error code, PDSR doesn't generate an RAR: "session-release- casue". As a result binding still exist for the given IMSI.

Solution

Based on the description of the test case we want to focus on the transactions related to Result Code 3002. In the pcap file provided I see two such complete transactions.

We also see in the NOAM configuration provided that your "Suspect Binding Removal Events Threshold" is set to 2.

Based on this configuration I expect that you would need more than 2 transactions/events to exceed the threshold.

Number of CCA-I with 3002 error code sent should exceed value in "Suspect Binding Removal Events Threshold".


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback