Error Code 503

Associated Error Category: No Usable Keys In Binding Dependent Message

Description: No binding key in Binding Key Priority GUI can be matched or no key is included in the binding dependent message.

Associated P-DRA Alarm/Event: Event 22706 - Binding Key Not Found In Diameter Message (refer to the DSR Alarms and KPIs Reference for details about this event)

Associated Measurement: TxPdraAnswersGeneratedForDiameterErr

Associated Diameter Interface / Message Type:

Rx AAR
Gx-Prime CCR-I

GUI Configurable: Yes

Recovery:

Check AAR Processing in the Error Resolution appendix of the Policy DRA User Guide to investigate and understand the circumstances where the error occurs.
Go to Policy DRA NOAM GUI at Main Menu > Policy DRA > Configuration > Binding Key Priority to verify if the binding key priorities are expected (for instance IMSI and IPv56 Address are expected, but MSISDN and IPv4 are displayed instead).
If the binding key priorities are not expected, reset the binding key priority in this screen properly.
If the binding key priority are expected, check the validity of the received Request message as follows:
- AVP carrying the expected key is present in the message
- AVP carrying the expected key is correctly formed
- AVP carrying the expected key is using a supported format (e.g. Subscription-ID AVP only Subscription-ID-Type of END_USER_E164 for MSISDN key and END_USER_IMSI for IMSI key).
Check the Policy DRA SOAM GUI at Main Menu > Alarms & Events > View History to search for all relevant alarms/events. The alarm Display Filter may be set as Timestamp to verify all alarms generated at the same time when the error occurred.
Get the measurement report from Main Menu > Measurements > Report for, but not limited to, "SBR Binding Exception," "SBR Session Exception," and "Policy DRA Diameter Exception" Measurement Groups.