7.3.9.1 Additional Provisioning Rules

Basic input data validation is done using the DCA Framework’s Configuration Data Provisioning GUI. Apart from that, below additional validation is performed during DSA business logic script compilation. If validation fails, the compilation also fails, and Event #33309 is raised with appropriate error text. For script compilation, refer to the DCA Programmer’s Guide.

• If Specific AVP Screening (SpecAVPScr) countermeasure is provisioned in Security_Countermeasure_Config Table then this table cannot be empty. At least one entry needs be provisioned.
• An AVP Name can be configured only once for a given Application-ID, Command-Code, Message-Type and AVP Value combination. No Duplicate AVP Name is allowed.
• If an AVP-Name is configured with a given Application-ID, Command-Code and AVP Value combination with Message-Type as Both, then same combination cannot be configured again with Message_Type as Request or Answer.
• The allowable characters for an AVP Name are A–Z, a–z, 0–9, dash "–", underscore "_", parentheses "()", and dot "."
• The allowable separator for configuring Grouped AVP in AVP_Name is semicolon (;). For example:
  • Parent1AVPName;AVPName.
  • Parent1AVPName;Parent2AVPName;AVPName.
  • Parent1AVPName;Parent2AVPName;Parent3AVPName;Parent4AVPName;AVPName.
• A maximum of 5 level deep Grouped AVP is supported. I.e. a Grouped AVP can have at max four parents.
• The configured AVP Value should be in-line with the configured AVP data type. E.g. If the AVP_Value_Type is provisioned as OctetString then the value configured in AVP_Value must be of OctetString type.