Hi!
I tried to test openser's call setup performance. Scenario: INVITE - 180 - 200
Server: 2 x P3 1266MHz
listen=UDP:... children=100
I used SIPP for testing.
1. Although the config is rather simple (no DNS, no DB, no lookup) I can't get more than 700 INVITE transactions per second. Shouldn't this be higher (AFAIK ser powers the whole bay area on a handheld PC)?
2. With children = 100, I can see more than 200 threads and lots of unix sockets opened, although no DB is used. Why?
3. openser core dumps when children=200
regards klaus
# # $Id: openser.cfg,v 1.5 2005/10/28 19:45:33 bogdan_iancu Exp $ # # simple quick-start config script #
# ----------- global configuration parameters ------------------------
debug=3 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=no # (cmd line: -E)
/* Uncomment these lines to enter debugging mode fork=no log_stderror=yes */
check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) port=5060 children=100 fifo="/tmp/openser_fifo"
listen=udp:83.136.32.132:5060 #listen=tcp:83.136.32.132:5060 #listen=tls:83.136.32.132:5061
# # uncomment the following lines for TLS support #disable_tls = 0 #tls_verify_client = 0 #tls_verify_server = 0 #tls_require_client_certificate = 0 #tls_method = TLSv1 #tls_certificate = "/etc/openser/tls/user/user-cert.pem" #tls_private_key = "/etc/openser/tls/user/user-privkey.pem" #tls_ca_list = "/etc/openser/tls/user/user-calist.pem"
# ------------------ module loading ----------------------------------
# Uncomment this if you want to use SQL database #loadmodule "/usr/lib/openser/modules/mysql.so"
loadmodule "/usr/lib/openser/modules/sl.so" loadmodule "/usr/lib/openser/modules/tm.so" loadmodule "/usr/lib/openser/modules/rr.so" loadmodule "/usr/lib/openser/modules/maxfwd.so" loadmodule "/usr/lib/openser/modules/usrloc.so" loadmodule "/usr/lib/openser/modules/registrar.so" loadmodule "/usr/lib/openser/modules/textops.so" loadmodule "/usr/lib/openser/modules/avpops.so" loadmodule "/usr/lib/openser/modules/xlog.so"
# Uncomment this if you want digest authentication # mysql.so must be loaded ! #loadmodule "/usr/lib/openser/modules/auth.so" #loadmodule "/usr/lib/openser/modules/auth_db.so"
# ----------------- setting module-specific parameters ---------------
# -- usrloc params --
modparam("usrloc", "db_mode", 0)
# Uncomment this if you want to use SQL database # for persistent storage and comment the previous line #modparam("usrloc", "db_mode", 2)
# -- auth params -- # Uncomment if you are using auth module # #modparam("auth_db", "calculate_ha1", yes) # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) # #modparam("auth_db", "password_column", "password")
# -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1)
# ------------------------- request routing logic -------------------
# main routing logic
route{
# initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; };
if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); exit; };
# we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol if (!method=="REGISTER")
record_route();
# subsequent messages withing a dialog should take the # path determined by record-routing if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); };
avp_printf("$avp(s:target)","sip:83.136.32.134;transport=udp"); avp_pushto("$ru","$avp(s:target)");
t_relay(); exit;
if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); # if you have some interdomain connections via TLS #if(uri=~"@tls_domain1.net") { # t_relay_to_tls("IP_domain1","port_domain1"); # exit; #} else if(uri=~"@tls_domain2.net") { # t_relay_to_tls("IP_domain2","port_domain2"); # exit; #} route(1); };
# if the request is for other domain use UsrLoc # (in case, it does not work, use the following command # with proper names and addresses in it) if (uri==myself) {
if (method=="REGISTER") {
# Uncomment this if you want to use digest authentication #if (!www_authorize("openser.org", "subscriber")) { # www_challenge("openser.org", "0"); # exit; #};
save("location"); exit; };
lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); exit; }; append_hf("P-hint: usrloc applied\r\n"); };
route(1); }
route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; exit; }
Another strange thing: When using TLS I get stable 670 cps whereas with TCP the results vary from 400 cps to 620 cps. Does someone knows a reason for this? Note: I do not know if this is caused by openser or sipp.
regards klaus
Klaus Darilion wrote:
Hi!
I tried to test openser's call setup performance. Scenario: INVITE - 180 - 200
Server: 2 x P3 1266MHz
listen=UDP:... children=100
I used SIPP for testing.
- Although the config is rather simple (no DNS, no DB, no lookup) I
can't get more than 700 INVITE transactions per second. Shouldn't this be higher (AFAIK ser powers the whole bay area on a handheld PC)?
- With children = 100, I can see more than 200 threads and lots of unix
sockets opened, although no DB is used. Why?
- openser core dumps when children=200
regards klaus
# # $Id: openser.cfg,v 1.5 2005/10/28 19:45:33 bogdan_iancu Exp $ # # simple quick-start config script #
# ----------- global configuration parameters ------------------------
debug=3 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=no # (cmd line: -E)
/* Uncomment these lines to enter debugging mode fork=no log_stderror=yes */
check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) port=5060 children=100 fifo="/tmp/openser_fifo"
listen=udp:83.136.32.132:5060 #listen=tcp:83.136.32.132:5060 #listen=tls:83.136.32.132:5061
# # uncomment the following lines for TLS support #disable_tls = 0 #tls_verify_client = 0 #tls_verify_server = 0 #tls_require_client_certificate = 0 #tls_method = TLSv1 #tls_certificate = "/etc/openser/tls/user/user-cert.pem" #tls_private_key = "/etc/openser/tls/user/user-privkey.pem" #tls_ca_list = "/etc/openser/tls/user/user-calist.pem"
# ------------------ module loading ----------------------------------
# Uncomment this if you want to use SQL database #loadmodule "/usr/lib/openser/modules/mysql.so"
loadmodule "/usr/lib/openser/modules/sl.so" loadmodule "/usr/lib/openser/modules/tm.so" loadmodule "/usr/lib/openser/modules/rr.so" loadmodule "/usr/lib/openser/modules/maxfwd.so" loadmodule "/usr/lib/openser/modules/usrloc.so" loadmodule "/usr/lib/openser/modules/registrar.so" loadmodule "/usr/lib/openser/modules/textops.so" loadmodule "/usr/lib/openser/modules/avpops.so" loadmodule "/usr/lib/openser/modules/xlog.so"
# Uncomment this if you want digest authentication # mysql.so must be loaded ! #loadmodule "/usr/lib/openser/modules/auth.so" #loadmodule "/usr/lib/openser/modules/auth_db.so"
# ----------------- setting module-specific parameters ---------------
# -- usrloc params --
modparam("usrloc", "db_mode", 0)
# Uncomment this if you want to use SQL database # for persistent storage and comment the previous line #modparam("usrloc", "db_mode", 2)
# -- auth params -- # Uncomment if you are using auth module # #modparam("auth_db", "calculate_ha1", yes) # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) # #modparam("auth_db", "password_column", "password")
# -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1)
# ------------------------- request routing logic -------------------
# main routing logic
route{
# initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); exit; }; # we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol if (!method=="REGISTER") record_route(); # subsequent messages withing a dialog should take the # path determined by record-routing if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); };
avp_printf("$avp(s:target)","sip:83.136.32.134;transport=udp"); avp_pushto("$ru","$avp(s:target)");
t_relay(); exit;
if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); # if you have some interdomain connections via TLS #if(uri=~"@tls_domain1.net") { # t_relay_to_tls("IP_domain1","port_domain1"); # exit; #} else if(uri=~"@tls_domain2.net") { # t_relay_to_tls("IP_domain2","port_domain2"); # exit; #} route(1); }; # if the request is for other domain use UsrLoc # (in case, it does not work, use the following command # with proper names and addresses in it) if (uri==myself) { if (method=="REGISTER") { # Uncomment this if you want to use digest
authentication #if (!www_authorize("openser.org", "subscriber")) { # www_challenge("openser.org", "0"); # exit; #};
save("location"); exit; }; lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); exit; }; append_hf("P-hint: usrloc applied\r\n"); }; route(1);
}
route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; exit; }
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi,
Just to get that cleared, did you run both openser and sipp on the same machine?
WL.
Klaus Darilion wrote:
Hi!
I tried to test openser's call setup performance. Scenario: INVITE - 180 - 200
Server: 2 x P3 1266MHz
listen=UDP:... children=100
I used SIPP for testing.
- Although the config is rather simple (no DNS, no DB, no lookup) I
can't get more than 700 INVITE transactions per second. Shouldn't this be higher (AFAIK ser powers the whole bay area on a handheld PC)?
- With children = 100, I can see more than 200 threads and lots of
unix sockets opened, although no DB is used. Why?
- openser core dumps when children=200
regards klaus
# # $Id: openser.cfg,v 1.5 2005/10/28 19:45:33 bogdan_iancu Exp $ # # simple quick-start config script #
# ----------- global configuration parameters ------------------------
debug=3 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=no # (cmd line: -E)
/* Uncomment these lines to enter debugging mode fork=no log_stderror=yes */
check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) port=5060 children=100 fifo="/tmp/openser_fifo"
listen=udp:83.136.32.132:5060 #listen=tcp:83.136.32.132:5060 #listen=tls:83.136.32.132:5061
# # uncomment the following lines for TLS support #disable_tls = 0 #tls_verify_client = 0 #tls_verify_server = 0 #tls_require_client_certificate = 0 #tls_method = TLSv1 #tls_certificate = "/etc/openser/tls/user/user-cert.pem" #tls_private_key = "/etc/openser/tls/user/user-privkey.pem" #tls_ca_list = "/etc/openser/tls/user/user-calist.pem"
# ------------------ module loading ----------------------------------
# Uncomment this if you want to use SQL database #loadmodule "/usr/lib/openser/modules/mysql.so"
loadmodule "/usr/lib/openser/modules/sl.so" loadmodule "/usr/lib/openser/modules/tm.so" loadmodule "/usr/lib/openser/modules/rr.so" loadmodule "/usr/lib/openser/modules/maxfwd.so" loadmodule "/usr/lib/openser/modules/usrloc.so" loadmodule "/usr/lib/openser/modules/registrar.so" loadmodule "/usr/lib/openser/modules/textops.so" loadmodule "/usr/lib/openser/modules/avpops.so" loadmodule "/usr/lib/openser/modules/xlog.so"
# Uncomment this if you want digest authentication # mysql.so must be loaded ! #loadmodule "/usr/lib/openser/modules/auth.so" #loadmodule "/usr/lib/openser/modules/auth_db.so"
# ----------------- setting module-specific parameters ---------------
# -- usrloc params --
modparam("usrloc", "db_mode", 0)
# Uncomment this if you want to use SQL database # for persistent storage and comment the previous line #modparam("usrloc", "db_mode", 2)
# -- auth params -- # Uncomment if you are using auth module # #modparam("auth_db", "calculate_ha1", yes) # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) # #modparam("auth_db", "password_column", "password")
# -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1)
# ------------------------- request routing logic -------------------
# main routing logic
route{
# initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); exit; }; # we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol if (!method=="REGISTER") record_route(); # subsequent messages withing a dialog should take the # path determined by record-routing if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); };
avp_printf("$avp(s:target)","sip:83.136.32.134;transport=udp"); avp_pushto("$ru","$avp(s:target)");
t_relay(); exit;
if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); # if you have some interdomain connections via TLS #if(uri=~"@tls_domain1.net") { # t_relay_to_tls("IP_domain1","port_domain1"); # exit; #} else if(uri=~"@tls_domain2.net") { # t_relay_to_tls("IP_domain2","port_domain2"); # exit; #} route(1); }; # if the request is for other domain use UsrLoc # (in case, it does not work, use the following command # with proper names and addresses in it) if (uri==myself) { if (method=="REGISTER") { # Uncomment this if you want to use digest
authentication #if (!www_authorize("openser.org", "subscriber")) { # www_challenge("openser.org", "0"); # exit; #};
save("location"); exit; }; lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); exit; }; append_hf("P-hint: usrloc applied\r\n"); }; route(1);
}
route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; exit; }
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hello,
On 07/24/06 14:39, Klaus Darilion wrote:
Hi!
I tried to test openser's call setup performance. Scenario: INVITE - 180 - 200
Server: 2 x P3 1266MHz
listen=UDP:... children=100
I used SIPP for testing.
I used sipp and the simplest openser config (just forward() ) and couldn't get very good. It seems that the limitation comes from sipp. You can try to use multiple sipp servers shooting at same openser to see if you see some differences. CPU used by openser was insignificant when the peak of cps was achieved.
- Although the config is rather simple (no DNS, no DB, no lookup) I
can't get more than 700 INVITE transactions per second. Shouldn't this be higher (AFAIK ser powers the whole bay area on a handheld PC)?
bay area is about 300 call setups per second, and indeed, this performance was achieved on a iPAQ, with 0.8.x about three years ago, using the basic config file with no database backend.
- With children = 100, I can see more than 200 threads and lots of
unix sockets opened, although no DB is used. Why?
the number of children is related to the number of interfaces openser listens to and the type of transport protocol enabled (UDP, TCP).
what is the name of the opened unixsock?
- openser core dumps when children=200
Any backtrace?
Cheers, Daniel
regards klaus
# # $Id: openser.cfg,v 1.5 2005/10/28 19:45:33 bogdan_iancu Exp $ # # simple quick-start config script #
# ----------- global configuration parameters ------------------------
debug=3 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=no # (cmd line: -E)
/* Uncomment these lines to enter debugging mode fork=no log_stderror=yes */
check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) port=5060 children=100 fifo="/tmp/openser_fifo"
listen=udp:83.136.32.132:5060 #listen=tcp:83.136.32.132:5060 #listen=tls:83.136.32.132:5061
# # uncomment the following lines for TLS support #disable_tls = 0 #tls_verify_client = 0 #tls_verify_server = 0 #tls_require_client_certificate = 0 #tls_method = TLSv1 #tls_certificate = "/etc/openser/tls/user/user-cert.pem" #tls_private_key = "/etc/openser/tls/user/user-privkey.pem" #tls_ca_list = "/etc/openser/tls/user/user-calist.pem"
# ------------------ module loading ----------------------------------
# Uncomment this if you want to use SQL database #loadmodule "/usr/lib/openser/modules/mysql.so"
loadmodule "/usr/lib/openser/modules/sl.so" loadmodule "/usr/lib/openser/modules/tm.so" loadmodule "/usr/lib/openser/modules/rr.so" loadmodule "/usr/lib/openser/modules/maxfwd.so" loadmodule "/usr/lib/openser/modules/usrloc.so" loadmodule "/usr/lib/openser/modules/registrar.so" loadmodule "/usr/lib/openser/modules/textops.so" loadmodule "/usr/lib/openser/modules/avpops.so" loadmodule "/usr/lib/openser/modules/xlog.so"
# Uncomment this if you want digest authentication # mysql.so must be loaded ! #loadmodule "/usr/lib/openser/modules/auth.so" #loadmodule "/usr/lib/openser/modules/auth_db.so"
# ----------------- setting module-specific parameters ---------------
# -- usrloc params --
modparam("usrloc", "db_mode", 0)
# Uncomment this if you want to use SQL database # for persistent storage and comment the previous line #modparam("usrloc", "db_mode", 2)
# -- auth params -- # Uncomment if you are using auth module # #modparam("auth_db", "calculate_ha1", yes) # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) # #modparam("auth_db", "password_column", "password")
# -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1)
# ------------------------- request routing logic -------------------
# main routing logic
route{
# initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); exit; }; # we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol if (!method=="REGISTER") record_route(); # subsequent messages withing a dialog should take the # path determined by record-routing if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); };
avp_printf("$avp(s:target)","sip:83.136.32.134;transport=udp"); avp_pushto("$ru","$avp(s:target)");
t_relay(); exit;
if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); # if you have some interdomain connections via TLS #if(uri=~"@tls_domain1.net") { # t_relay_to_tls("IP_domain1","port_domain1"); # exit; #} else if(uri=~"@tls_domain2.net") { # t_relay_to_tls("IP_domain2","port_domain2"); # exit; #} route(1); }; # if the request is for other domain use UsrLoc # (in case, it does not work, use the following command # with proper names and addresses in it) if (uri==myself) { if (method=="REGISTER") { # Uncomment this if you want to use digest
authentication #if (!www_authorize("openser.org", "subscriber")) { # www_challenge("openser.org", "0"); # exit; #};
save("location"); exit; }; lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); exit; }; append_hf("P-hint: usrloc applied\r\n"); }; route(1);
}
route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; exit; }
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
On Mon, July 24, 2006 22:11, Daniel-Constantin Mierla said:
Hello,
On 07/24/06 14:39, Klaus Darilion wrote:
Hi!
I tried to test openser's call setup performance. Scenario: INVITE - 180 - 200
Server: 2 x P3 1266MHz
listen=UDP:... children=100
I used SIPP for testing.
I used sipp and the simplest openser config (just forward() ) and couldn't get very good. It seems that the limitation comes from sipp. You can try to use multiple sipp servers shooting at same openser to see if you see some differences. CPU used by openser was insignificant when the peak of cps was achieved.
maybe I found some more severs for generating load :-) I also suspect SIPP to generate wrong messages sometimes and it crashes during high load when using multiple TLS connections.
- With children = 100, I can see more than 200 threads and lots of
unix sockets opened, although no DB is used. Why?
the number of children is related to the number of interfaces openser listens to and the type of transport protocol enabled (UDP, TCP).
only one UDP socket: no TCP, no TLS, no loopback-device. strange.
graham:/home/darilion# ps -Alf|grep openser.pid|wc 205 4504 29060
openser.cfg:
debug=3 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=no # (cmd line: -E)
check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) port=5060 children=100 fifo="/tmp/openser_fifo"
listen=udp:83.136.32.132:5060
disable_tls = 0 tls_verify_client = 0 tls_verify_server = 0 tls_require_client_certificate = 0 tls_method = TLSv1 tls_certificate = "/etc/openser/tls/user/user-cert.pem" tls_private_key = "/etc/openser/tls/user/user-privkey.pem" tls_ca_list = "/etc/openser/tls/user/user-calist.pem"
what is the name of the opened unixsock?
what is a name of a socket? I only see:
graham:/home/darilion# netstat -anp|grep openser udp 0 0 83.136.32.132:5060 0.0.0.0:* 3690/openser unix 3 [ ] STREAM CONNECTED 41582 3892/openser unix 3 [ ] STREAM CONNECTED 41581 3690/openser unix 3 [ ] STREAM CONNECTED 41580 3892/openser unix 3 [ ] STREAM CONNECTED 41579 3690/openser unix 3 [ ] STREAM CONNECTED 41576 3891/openser unix 3 [ ] STREAM CONNECTED 41575 3690/openser unix 3 [ ] STREAM CONNECTED 41574 3891/openser unix 3 [ ] STREAM CONNECTED 41573 3690/openser unix 3 [ ] STREAM CONNECTED 41572 3890/openser unix 3 [ ] STREAM CONNECTED 41571 3690/openser ...
- openser core dumps when children=200
Any backtrace?
I try to reproduce them.
regards klaus
Cheers, Daniel
regards klaus
# # $Id: openser.cfg,v 1.5 2005/10/28 19:45:33 bogdan_iancu Exp $ # # simple quick-start config script #
# ----------- global configuration parameters ------------------------
debug=3 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=no # (cmd line: -E)
/* Uncomment these lines to enter debugging mode fork=no log_stderror=yes */
check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) port=5060 children=100 fifo="/tmp/openser_fifo"
listen=udp:83.136.32.132:5060 #listen=tcp:83.136.32.132:5060 #listen=tls:83.136.32.132:5061
# # uncomment the following lines for TLS support #disable_tls = 0 #tls_verify_client = 0 #tls_verify_server = 0 #tls_require_client_certificate = 0 #tls_method = TLSv1 #tls_certificate = "/etc/openser/tls/user/user-cert.pem" #tls_private_key = "/etc/openser/tls/user/user-privkey.pem" #tls_ca_list = "/etc/openser/tls/user/user-calist.pem"
# ------------------ module loading ----------------------------------
# Uncomment this if you want to use SQL database #loadmodule "/usr/lib/openser/modules/mysql.so"
loadmodule "/usr/lib/openser/modules/sl.so" loadmodule "/usr/lib/openser/modules/tm.so" loadmodule "/usr/lib/openser/modules/rr.so" loadmodule "/usr/lib/openser/modules/maxfwd.so" loadmodule "/usr/lib/openser/modules/usrloc.so" loadmodule "/usr/lib/openser/modules/registrar.so" loadmodule "/usr/lib/openser/modules/textops.so" loadmodule "/usr/lib/openser/modules/avpops.so" loadmodule "/usr/lib/openser/modules/xlog.so"
# Uncomment this if you want digest authentication # mysql.so must be loaded ! #loadmodule "/usr/lib/openser/modules/auth.so" #loadmodule "/usr/lib/openser/modules/auth_db.so"
# ----------------- setting module-specific parameters ---------------
# -- usrloc params --
modparam("usrloc", "db_mode", 0)
# Uncomment this if you want to use SQL database # for persistent storage and comment the previous line #modparam("usrloc", "db_mode", 2)
# -- auth params -- # Uncomment if you are using auth module # #modparam("auth_db", "calculate_ha1", yes) # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) # #modparam("auth_db", "password_column", "password")
# -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1)
# ------------------------- request routing logic -------------------
# main routing logic
route{
# initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); exit; }; # we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol if (!method=="REGISTER") record_route(); # subsequent messages withing a dialog should take the # path determined by record-routing if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); };
avp_printf("$avp(s:target)","sip:83.136.32.134;transport=udp"); avp_pushto("$ru","$avp(s:target)");
t_relay(); exit;
if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); # if you have some interdomain connections via TLS #if(uri=~"@tls_domain1.net") { # t_relay_to_tls("IP_domain1","port_domain1"); # exit; #} else if(uri=~"@tls_domain2.net") { # t_relay_to_tls("IP_domain2","port_domain2"); # exit; #} route(1); }; # if the request is for other domain use UsrLoc # (in case, it does not work, use the following command # with proper names and addresses in it) if (uri==myself) { if (method=="REGISTER") { # Uncomment this if you want to use digest
authentication #if (!www_authorize("openser.org", "subscriber")) { # www_challenge("openser.org", "0"); # exit; #};
save("location"); exit; }; lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); }; # native SIP destinations are handled using our USRLOC
DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); exit; }; append_hf("P-hint: usrloc applied\r\n"); };
route(1);
}
route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; exit; }
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hello guys.
I've some trouble for compiling a module originallly written for SER (Works fine on SER 0.9.6). The lines below belongs to the code I'm talking about:
pre_auth_f pre_auth func = 0; post_auth_f post_auth_func = 0;
The problem is that I couldn't find the definition (neither gcc) of the post_auth_f and post_auth_f types. I've search in all the files of openser core sources and all the modules sources.
Have you any idea about where is they defined?
Thanks in advance.
Victoria
./modules/auth/api.h:63 says:
/* * Purpose of this function is to do post authentication steps like * marking authorized credentials and so on. */ typedef auth_result_t (*post_auth_f)(struct sip_msg* _m, struct hdr_field* _h, str* _rpid); <<
WL.
Hello guys.
I've some trouble for compiling a module originallly written for SER (Works fine on SER 0.9.6). The lines below belongs to the code I'm talking about:
pre_auth_f pre_auth func = 0; post_auth_f post_auth_func = 0;
The problem is that I couldn't find the definition (neither gcc) of the post_auth_f and post_auth_f types. I've search in all the files of openser core sources and all the modules sources.
Have you any idea about where is they defined?
Thanks in advance.
Victoria
_______________________________________________ Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Thanks, Weiter. Now I can see this clearly.
The lines you showed me has been taken from api.h, from the SER package. In OpenSER this lines are quite different. post_auth_f is not longer called post_auth_f. In OpenSER I can see the new names are post_auth_t and pre_auth_t.
Thanks a lot.
Victoria
----- Original Message ----- From: "Weiter Leiter" bp4mls@googlemail.com To: users@openser.org; openser@conexiongroup.com Sent: Monday, July 24, 2006 11:54 PM Subject: [Users] pre_auth_f and post_auth_f
./modules/auth/api.h:63 says:
/*
- Purpose of this function is to do post authentication steps like
- marking authorized credentials and so on.
*/ typedef auth_result_t (*post_auth_f)(struct sip_msg* _m, struct hdr_field* _h, str* _rpid); <<
WL.
Hello guys.
I've some trouble for compiling a module originallly written for SER (Works fine on SER 0.9.6). The lines below belongs to the code I'm talking about:
pre_auth_f pre_auth func = 0; post_auth_f post_auth_func = 0;
The problem is that I couldn't find the definition (neither gcc) of the post_auth_f and post_auth_f types. I've search in all the files of openser core sources and all the modules sources.
Have you any idea about where is they defined?
Thanks in advance.
Victoria
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users