...
- Linux machine
- SER version 2.0rc or higher. Se also SER 2rc1
- Server certificate and private key in PEM fomrat
- CA list - list of trusted authorities in PEM format
- TLS enabled client - i.e. EyeBeam or new CMC
If you use binary package, see if it supports TLS. command ser -V should show something like
...
and tls module (tls.so) has to located in module directory (depends on distribution and package i.e. /usr/local/lib/ser/modules)Otherwise you have to recompile SER from source. Download daily snaphot from iptel.org or from CVS.package i.e. /usr/local/lib/ser/modules)
Otherwise you have to recompile SER from source. Download daily snaphot from iptel.org or from CVS.
Ser 2rc daily snaphost
Ser 2.0 cvs branch
| No Format |
|---|
export CVSROOT=:pserver:anonymous@cvs.berlios.de:/cvsroot/ser
cvs co -r rel_2_0_0 sip_router
|
Ser head cvs branch
| No Format |
|---|
export CVSROOT=:pserver:anonymous@cvs.berlios.de:/cvsroot/ser
cvs co sip_router
|
Compiling of source
Make everything
| No Format |
|---|
make group_include="standard" include_modules="tls" all |
...
- Invalid TLS version: though TLS 1.0 should be used according to the SIP RFC, SSL 2/3
- certificate verification. CA list often doesn't include the necessary certs.
- Common name of the server certificate does not match DNS name of the server
...