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

[Stefan Sayer]

Hi Martin,

Martin Hoffmann wrote:
> 
>> SER is no longer "just a SIP proxy".
> 
> But it is just that. I don't really like all the attempts to make it
> more than that (which is the main reason why I don't use SEMS). SER is a
> proxy and a registrar. Everything more fancy shall be done somewhere
> else.
SEMS uses SER only as SIP stack, on transaction layer. This performs 
quite well, assures standards compliance etc. Everything fancy (dialogs, 
media, b2b, ...) is done somewhere else - in SEMS.
I am using virtually the same ser-sems.cfg for all the different things 
I do with SEMS (I only adapt the data which should be passed to SEMS, 
which is more a performance optimization).

Regards
Stefan


-- 
Stefan Sayer
Media Services Development

iptego GmbH
Am Borsigturm 40
13507 Berlin
Germany

stefan.sayer at iptego.de
www.iptego.de