| Asset ID: |
1-72-1956764.1 |
| Update Date: | 2017-06-30 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1956764.1
:
RBAR not being encountered on DSR
| 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
Created from <SR 3-10039990325>
Applies to:
Oracle Communications Diameter Signaling Router (DSR) - Version DSR 4.0 and later
Information in this document applies to any platform.
Symptoms
Error Message 3002202: No peer routing rule found or message otherwise not routed as expected. Further investigation reveals that RBAR application is not encountered although routing is setup to send message to RBAR. Message contains AVP 2468.
Cause
The present of avp 2468 prevents RBAR from being encountered on an Oracle DSR
Solution
The presence of the tekelec-specific avp (DSR-Application-Invoked, avp 2468) containing a value that points to RBAR (i.e., 3) in a request message would by design prevent the RBAR application from being invoked at a subsequent Oracle DSR because the AVP indicates that RBAR has already been invoked. Removing this AVP can be done by mediation at the receiving DSR or by an appropriate setting of the "Allow Subsequent RBAR Invocation" option at the sending DSR. The later option can be set on a system-wide basis or on a per destination basis.
For the system-wide approach RBAR-> Configuration-> System Options : Allow Subsequent RBAR Invocation would be set to "yes" i.e., checked. When this is checked the per destination settings would be ignored and the tekelec-specific avp containing the RBAR application id would not be included in request messages. If this value is set to "no" i.e., unchecked, then the per destination values take precedence.
The per destination values are set under RBAR-> Configuration-> Destinations: Allow Subsequent RBAR Invocation. For each destination where the value is set to "yes" i.e., checked, the system would not include the tekelec-specific avp when sending messages to that destination. If the per destination value is set to "no" i.e., unchecked, then the tekelec-specific avp would be included in messages going to that destination. The per destination option provides flexibility such that it can be set to "no" for internal destinations and can be set to "yes" for external destination if desired.
Attachments
This solution has no attachment
