Custom AVPs, Commands, and Vendors

The user can add custom AVPs, commands and vendors through an XML configuration file called diameter dictionary file. The Diameter decoder component, which is responsible for diameter message/AVP decoding, will look at its start-up at the specific location (at the Application server itself) and if it finds the dictionary file there, it will use it to decode diameter messages.

If a change is made to this dictionary file, the application server must be restarted to pick-up the changes.

The custom diameter dictionary file must be valid XML file, which contains one single root element called dictionary. All other tags defining custom commands, vendors and AVP must be included inside of this tag.

AVP Example

<?xml version="1.0" encoding="UTF-8"?>
<dictionary>
        <vendor vendor-id="VF" code="12645" name="Vodafone" />
        <command code="316" short-name="UL" name="Update-Location" />
        <avp name="3GPP:3GPP-IMSI" display="3GPP-IMSI" code="1" vendor-id="3GPP" type="UTF8String"/>
        <avp name="Framed-Routing" display="Framed-Routing" code="10" type="Enumerated" >
                <enum code="0" name="None"/>
                <enum code="1" name="Broadcast"/>
                <enum code="2" name="Listen"/>
                <enum code="3" name="Broadcast-Listen"/>
        </avp>
        <avp name="3GPP:User-Identity" display="User-Identity" code="700" vendor-id="3GPP" type="Grouped">
                <avp ref="Public-Identity"/>
                <avp ref="3GPP:MSISDN"/>
                <avp ref="3GPP:Public-Identity"/>
        </avp>
</dictionary>