I would like to see more feature for security/stability:
- do not block during establishing new TCP/TLS connections
- do not try to establish TCP/TLS to clients behind NAT
- possibility to drop final response if there is no matching transaction
- do not block during DNS lookup
I also thought how to make openser more responsive during high
load/blocking - e.g. openser blocks because of DNS or DB problems. Then
we get retransmissions, the input queues get full and openser collapses.
I first idea would be a dedicated worked thread which handles this
overload traffic - and only this overload traffic using a dedicated
route, e.g.
overload_route {
append_to_reply("Retry-After: 300");
sl_send_reply("500","Server busy");
exit;
}
If all the worker threads are blocked for some time (e.g. >100 ms), then
the scheduler start giving the incoming requests to the overload thread
until the worker threads become idle again.
Any comments?
regards
klaus
Henning Westerholt wrote:
Hello all,
i've combined the discussed roadmap items from friday. On the roadmap to 1.2
there were also some not finished "nice to have" items, i added them and some
things from the list too for discussion. :-)
From friday:
1) tighter integration of xmpp into OpenSER, get rid of two levels of
addressing
2) dialog enhancements
- Bogdan
3) better diameter support
- Ovidiu Sas
4) SIPS url support
- get rid of hard coded "sip" in modules
- enhance parser
5) replace OpenSSL with GnuTLS
- performance issues, GnuTLS seems two times slower then OpenSSL
- but GnuTLS supports more features
- Julien Blache announced that he wants to work on this
6) replace integrated assembler code with system provided assembler functions
- Bogdan
- needs performance evaluation
7) RTPProxy enhancements
- collaboration with existing project, or rewrite
- Adam Linford announced that he can perhaps provide funding for an rewrite
8) Build system change
- not decided yet
- cmake vs. autotools
- Sebastien Tricaud announced that he wants to work in this
9) OpenSER lib
- would probably easier with better build system and isolation of memory
management
- Sebastien Tricaud announced that he wants to work on this
From the 1.2 roadmap:
10) OpenSER Core
[o] memory defragmentation
[o] OpenSER command line interface (terminal)
[o] pass socket information through fifo/unixsock
[o] interpret ICMP error messages
[o] SIP identity
- in patch tracker
11) OpenSER Modules
[[avpops]]
[o] local avps - avps to be stored locally, specific per script, not per
transaction
[[cpl-c]]
[o] replace support
[o] reload support
[[dispatcher]]
[o] database support
[[uac]]
[o] qop authentication support
[o] proper CSeq value after authentication challenge
[[usrloc]]
[o] possibility to attach to a contact a set of values (similar to log_extra
in acc)
[[xmpp]]
[o] support for presence and voice
I would like to add:
12) OpenSER config reload
- use a new configuration without an server restart
13) Database interface enhancements
- application level clustering, especially for location data
- needs to be discussed
- I would like to work on this
Cheers,
Henning
_______________________________________________
Devel mailing list
Devel@openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel@openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
