Most of the tasks used to send request or answer messages, takes an AVP parameter list. This parameter is used to specify (Optional) AVPs to be included in the message to be sent.
AVPs is specified in a list, using the name, value and vendor id of each AVP. Example:
AVP name and values is specified using text and converted to values when executed. All AVPs as specified in Supported Diameter Protocols are supported.
AVP of different types are converted from string values to the expected type automatically. In most cases the conversion is straightforward, but the following are notes for a few types.
Enumerated values can be specified using a number as well as a symbolica name. For example the enumerated AVP "Framed-Protocol" can be set as follows:
Which will give the same result.
AVP values of type Date are specified in one of the following formats:
A special case is grouped AVPs which value is specified by using the syntax:
<AVP-group> : <AVP-Value>
For example to specify Subscription-Id that includes Subscription-Id-Type and Subscription-Id-Data, the folllowing can be used:
This will give you the following result:
Subscription-Id: <Grouped> Subscription-Id-Type: END_USER_SIP_URI Subscription-Id-Data: <sip:bob@ims.test>
If you need multiple instance of same grouped AVP, you can force to use a new AVP using * at the end of the name. For example:
This will give you the following result:
Supported-Features: <Grouped> Vendor-Id: 10415 Feature-List-ID: 1 Feature-List: 2 Supported-Features: <Grouped> Vendor-Id: 10415 Feature-List-ID: 2 Feature-List: 3