Hi Peter,
I personally I'm quite happy with you suggestion and keen to improved
the integration with Radius.
regarding all the issues to mentioned in the following email, I will
come back to you in with more info.
Regards,
Bogdan
Peter Nixon wrote:
Hi Guys
I am new to the list so first a quick intro.
I have around 5 years experience with VoIP and many more with IP Networks and
Linux. I randomly poke at the code of many open source projects when the
need/fancy strikes. (A quick google search will find them) I am also one of
the core FreeRADIUS developers, and the founder of the openSUSE
server:telephony package group. (See
http://software.opensuse.org/download/server:/telephony/SUSE_Linux_10.1/repodata/
for an index). This means that I maintain the packages for SER, openSER and
mediaproxy as well as numerous other telephony related packages. I also have
some other networking, messaging and monitoring related projects but they are
not relevant here. (If you notice problems with any of my packages please let
me know so I can fix them)
Now for the question.
Why is it that neither SER nor OpenSer has submitted the SER radius dictionary
for inclusion in FreeRADIUS??? I notice all the documentation explains how to
copy it in, but the correct solution would be to have it as a vendor
dictionary and be done with it. Does anyone have anything against me
committing it to FreeRADIUS cvs? I also notice that it doesn't currently have
a vendor number from IANA at the top (has everyone just been too lazy to
apply for one?). The author of the radius module should apply for one, or
alternatively we can just use mine (26514)
We have a new stable FreeRADIUS release due out in the near future (days or
weeks at most) so a quick decision will allow for inclusion in what should be
the final release of the 1.1x branch.
Waiting for replies/flames before I do anything...
Cheers
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
