[Serdev] SER's core design features(process model/parser/lumps/script) - was: So who/what is SER for, anyway?

[Dragos Vingarzan]

Greger V. Teigre wrote:
> Well, RADIUS in SER is as a client, I assume you have implemented a
> server. That's a big difference.
no, I did a peer (client & server).
> No, not the same thing. SER as a Diameter server does not make sense
> to me.
well, if you have an AAA, then you want to control things from there.
And what do you do when you decide to barre a user? You go to the
reigstrar manually and say "you're out"?

The idea would be to be able to also push event the other way around
(like the Registration Termination Request) so that you do not need to
do some crazy subscribe/notify mechanism on the other side.

So now with the Open IMS Core registrar, I am able to change the
expiration period from the global DB for any users, push service profile
changes, etc. And I can also do 1000 of them at a time, because I have a
nice architecture in SER too and it can take it and send SIP NOTIFYs
from the Diameter processes.

Also, I haven't read the online charging stuff, but I guess that it
makes more sense for example for the charging server to push the
"zero-credit" event to the session controllers than to continuously
monitor this.
> I've run RADIUS servers for years and I also know Diameter quite well.
> Creating a good Diameter server is NOT something you do inside SER.
> So, instead of having an excellent SIP proxy and and excellent
> Diameter server communicating with some dedicated, controlled way, you
> have two mediocre servers...
:) could I get some feedback on my CDiameterPeer module? I think that it
is pretty powerful (performance speaking).

http://svn.berlios.de/wsvn/openimscore/ser_ims/trunk/modules/cdp/?rev=0&sc=0

This is like my 3rd or 4th try at a Diameter integration... I don't see
much wrong with it (don't look for 100% RFC in there, yet - I for one
don't need it).

(I may be now in Amsterdam ;-), but this is getting off topic or what?)

-Dragos