Good ideas, Samuel, but I think too far ahead. Let's start with a base
level SER system first and get that up and working with the basic core
level apps. Once that's done, we can see what can easily be added
(presence will be a big one, I'm sure, and TLS will have interest as well).
N.
samuel wrote:
Just thinking loud...may be not feasible... but....
it would be great that the base would enable easily interconnecting to
other already running systems coming from the base via TLS so it would
create kind of "trusted" SER nodes. This way newcomers to
"SIP providers world" would have an added value installing the base...I think
that
just installing the right
certificates in the base would make things easier.
This made me think about how many features would the base include?
*TLS
*auth_identity
*presence...
For all of them to work we need different instances of SER due to the
ssl library incompatibility. How big are we gonna make the base?
Case we can deploy several TLS+auth_identiy running nodes it would be
"easy" to add SPIT methods....
Maybe too far,
Samuel.
2008/2/28, Mike Trest - Personal <Mike(a)trest.com
<mailto:Mike@trest.com>>:
At 11:11 AM 2/28/2008, SIP wrote:
Tools:
All tools (ser_ctl, sipsak, tcpdump/ngrep, wireshark/tshark, sipp,
sip_scenario, spyagent+sipspy
I will install & maintain wireshark, tcpdump and any other standard
linux packages.
Anyone with specific version needs, just let me know.
I will need to lookup sipp, sip_scenario, spyagent,sipspy as I am not
familiar with them.
Anyone want to suggest a specifc version or URL for these?
..mike..
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org <mailto:Serusers@lists.iptel.org>
http://lists.iptel.org/mailman/listinfo/serusers