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-2381809.1
Update Date:2018-04-03
Keywords:

Solution Type  Technical Instruction Sure

Solution  2381809.1 :   Eagle: Is There Any Congestion Control Mechanism Enabled On Eagle STP  


Related Items
  • Oracle Communications EAGLE (Software)
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec Eagle 5
  •  




In this Document
Goal
Solution
References


Created from <SR 3-17117684853>

Applies to:

Oracle Communications EAGLE (Software) - Version EAGLE 44.x and later
Tekelec

Goal

To identify if there is any congestion control mechanism enabled on Eagle STP or if there are any specific features for this congestion control.
 

Solution

There is no specific feature for congestion control mechanism on the STP, rather the STP is implementing mechanisms according with the ITU standard, see Q.704 specification(paragraph 11.2.3).

For MTP routed traffic, TFC(Transfer Controlled) messages will be sent to all concerned message originators in order to throttle down the traffic reaching the STP. This TFC messages will be sent when a destination gets congested or when an outbound link towards a specific destination exceeds the provisioned TPS entering congestion state.

For GT/SCCP routed traffic, TFCs will not be sent, instead STP will send UDTS messages to the query OPC with Cause Code 6 - Network Congestion when the translated DPC gets congested. For this to happen, the "Return_on_error" bit has to be set in the originating MSU. Further, it depends on what congestion mechanisms are in place on the originating nodes and their behavior and actions when receiving UDTS with cause code 6 from the STP.

References

<NOTE:2277590.1> - SRDC - Data to Collect for Eagle STP Troubleshooting
<NOTE:838444.1> - Oracle Communications Industry Communities
<NOTE:2310006.1> - Oracle October 2017 Critical Patch Update for Tekelec HLR Router
<NOTE:1671775.1> - How to Create a Technical or Non-Technical Tekelec Service Request
<NOTE:1679525.1> - SRDC - How to Collect NSP Logs
<NOTE:1963058.1> - Where to Find Oracle Communications Documentation for Tekelec Products
<NOTE:739087.1> - Unable to Close a Service Request Without Closing Tasks First

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