[prev in list] [next in list] [prev in thread] [next in thread]
List: freediameter-help
Subject: [Help] Legacy XML
From: sdecugis () freediameter ! net (Sebastien Decugis)
Date: 2012-09-09 19:11:28
Message-ID: 504CE9E0.7060903 () freediameter ! net
[Download RAW message or body]
Hi Patricio,
First I apologize, I had read too quickly the mail archive and I thought
it contained a grouped AVP, while it was actually a command definition.
Sorry about that.
Here is how to define the grouped AVP:
<avp name="Test-GroupedAVP" code="16777214" vendor-id="999999" mandatory="must">
<grouped>
<fixed>
<avprule name="Session-Id" minimum="1" maximum="1" />
</fixed>
<required>
<avprule name="Destination-Realm" minimum="1" maximum="1" />
<avprule name="Origin-Host" minimum="1" maximum="1" />
<avprule name="Origin-Realm" minimum="1" maximum="1" />
<avprule name="Test-AVP" minimum="1" maximum="1" />
</required>
<optional>
<avprule name="Destination-Host" minimum="1" maximum="1" />
</optional>
</grouped>
</avp>
Please let me know if you encounter any problem with this.
PS: I have fixed the example on the wiki, it contained erroneous tags
for the fixed, required and optional rules...
Best regards,
Sebastien.
Le 2012/09/07 13:50, Patricio Moreno a ?crit :
> Hi Sebastien,
> I've seen that XML file of the example, but I can't see how to
> implement grouped AVPs looking the example
> <http://www.freediameter.net/trac/wiki/dict_legacy_xml.fdx> (or the
> DTD file
> <http://www.freediameter.net/trac/browser/freeDiameter/contrib/dict_legacy/dictionary.dtd>).
> I'm looking at some OpenDiameter XML to see the correlation and try to
> generate a valid freeDiameter XML, as for my application it would be
> much better to have the possibility to change "dynamically" the AVP
> Dictionary (without having to recompile)
>
> Regards,
> -PATRICIO MORENO
>
>
> 2012/9/7 Sebastien Decugis <sdecugis at freediameter.net
> <mailto:sdecugis at freediameter.net>>
>
> Hi Patricio,
>
> There is an example of XML file defining a grouped AVP in the
> following archive:
> http://lists.freediameter.net/pipermail/dev/2012-August/000171.html
>
> I am not sure it is currently possible to load the same extension
> several times; I guess it would require not using any global /
> static variable in the code at all, but I am not sure what is the
> current situation. However, if your extension is meant to be
> loaded several times with different configurations, I think it is
> safer to design the extension initialization routine to accept
> several configuration files (either a file referencing all the
> others as for the dict_legacy_xml, or a list of configuration
> files directly in the string passed to the extension for example)
> and do the proper initialization (create several threads or
> register several handlers) according to these configuration files.
>
> Best regards,
> Sebastien.
>
> Le 2012/09/06 21:58, Patricio Moreno a ?crit :
>> Hi, I have a test client and a test server (separate fdx), with a
>> few modifications (irrelevant to the following questions, but
>> I've been playing with the code a littlebit). Now I'd like to use
>> the legacy XML extension to load a dictionary from an XML file
>> (obvious) but I don't know how to implement a dictionary
>> completely looking the DTD file. For example, how do I define a
>> grouped AVP? Also, is there a way to load several times the same
>> extension; example: I've said I have a client and a server, now I
>> want to load the server multiple times, with different
>> configurations; is this possible?
>>
>> Best regards,
>> -PATRICIO MORENO
>>
>>
>> _______________________________________________
>> Help mailing list
>> Help at freediameter.net <mailto:Help at freediameter.net>
>> http://lists.freediameter.net/cgi-bin/mailman/listinfo/help
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freediameter.net/pipermail/help/attachments/20120909/cf17da70/attachment.html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic