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.
Appserver: /usr/TKLC/xIH/diameter/custom-avps.xml
If a change is made to this dictionary file, the application server must be restarted in order 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.