sr-users

sr-users@lists.kamailio.org

27 participants
37381 discussions

large dildo
by feigelwang＠uusextoy.com 26 Aug '23

26 Aug '23

Or, if you are good at Google search, I believe you can definitely find more ways to play the big dildo. All in all, huge dildos are the best sex toy for singles. For single women, it’s vaginal masturbation. For single men, it’s anal sex.https://www.hugedildo.com/

1 0

extreme dildoes
by feigelwang＠uusextoy.com 26 Aug '23

26 Aug '23

So, when you still are alone, buying a huge dildo is worth it. Enjoy sex with the huge realistic dildo anytime and anywhere. Not only that, the big dildo brings completely different sexual stimulation. Maybe you want to enjoy full sex, should try some other sex toys.https://www.hugedildo.com/

1 0

rtpengine large number used RTP ports
by marek 25 Aug '23

25 Aug '23

hi, i have open around ~8000 rtp ports for around ~200calls (in peak) with this statistic (current data, not from peak) rtpengine_closed_sessions_total{reason="rejected"} 0 rtpengine_closed_sessions_total{reason="timeout"} 237405 rtpengine_closed_sessions_total{reason="silent_timeout"} 103 rtpengine_closed_sessions_total{reason="final_timeout"} 0 rtpengine_closed_sessions_total{reason="offer_timeout"} 0 rtpengine_closed_sessions_total{reason="terminated"} 0 rtpengine_request_seconds_total{proxy="127.0.0.1",request="offer"} 539.270967 rtpengine_request_seconds_total{proxy="127.0.0.1",request="answer"} 367.237641 rtpengine_request_seconds_total{proxy="127.0.0.1",request="delete"} 0.000000 is it normal? (large number of timeouts, "zero" terminated) or i have missing rtpengine_manage (rtpengine_delete) somewhere? (os rocky 9.2, kamailio 5.6.4, rtpengine 11.3.1) thanks Marek

2 3

excessive CANCELs
by James Lipski 23 Aug '23

23 Aug '23

Hello, I've already suppressed this via routing logic, however I was wondering if there is a dedicated parameter that handles this. I'm currently running version 5.6.4. Scenario: UA-1 registered towards kamailio, calls UA-2 which is registered towards a different platform (non kamailio); so there are 2 proxys involved. kamailio is set to fork the call to voicemail if there is either no response completely from the other end, or the call goes unanswered. So the initial leg is: UA-1 <-----> kamailio <-----> second proxy <-----> UA-2 Issue: I'm trying to catch a case where the second proxy does issue a "100 Trying" for the initial INVITE; and then timesout. The call does fork to voicemail; however 14000+ SIP packets are generated between kamailio and the second proxy of CANCEL and "100 Trying" (the 100 Trying has a CSeq for INVITE still). Is there a way to suppress the amount of CANCELs that is transmitted in this situation? I'm using the following as my "tm" parameters: modparam("tm", "failure_reply_mode", 3) modparam("tm", "fr_timer", 30000) modparam("tm", "fr_inv_timer", 300000) modparam("tm", "auto_inv_100_reason", "Trying") Thanks. Example SIP trace: (UA-1 --> kamailio) 72.255.255.255 --> 10.64.52.110 INVITE sip:131@sip-example.com SIP/2.0 v: SIP/2.0/UDP 10.0.0.102:51519;branch=z9hG4bK-xfelmyyjzne5;rport f: <sip:133@sip-example.com>;tag=i4mlq4jr0y t: <sip:131@sip-example.com> i: 95c3e4642670-rx28v46dte4p CSeq: 1 INVITE Max-Forwards: 70 User-Agent: snomD785/10.1.152.12 m: <sip:133@10.0.0.102:51519;line=6dv00d6r>;reg-id=1 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Supported: timer, replaces, from-change Session-Expires: 3600 Min-SE: 90 Proxy-Authorization: Digest username="133",realm="sip-example.com",nonce="ZOTEBGTkwtiM22ZE8IJsn/esiW3CZrt0"[,uri="sip:131@sip-example.com](mailto:,uri=)",response="fb44b4fe0f8fb17de13f043cf1248e14",algorithm=MD5 c: application/sdp l: 309 v=0 o=root 481174289 481174289 IN IP4 10.0.0.102 s=call c=IN IP4 10.0.0.102 t=0 0 m=audio 50864 RTP/AVP 9 0 8 18 101 a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv -------------------------------------------- (UA-1 <-- kamailio) 72.255.255.255 <-- 10.64.52.110 SIP/2.0 100 Trying v: SIP/2.0/UDP 10.0.0.102:51519;branch=z9hG4bK-xfelmyyjzne5;rport=51519;received=72.255.255.255 f: <sip:133@sip-example.com>;tag=i4mlq4jr0y t: <sip:131@sip-example.com> i: 95c3e4642670-rx28v46dte4p CSeq: 1 INVITE Content-Length: 0 -------------------------------------------- (kamailio --> second proxy) 10.64.52.110 --> 10.64.52.100 INVITE sip:second-proxy-example.com:5066;ua=43a58ecca39c9c8f37515e55b5b37ed7 SIP/2.0 Via: SIP/2.0/UDP 10.64.52.110:5060;branch=z9hG4bKecf9.6d10880e1353b8a7bbf0383d934a38a5.0 f: <sip:133@sip-example.com>;tag=i4mlq4jr0y t: <sip:131@sip-example.com?vm-ext%3D100%26ext-to%3D131%26ext-from%3D133> i: 95c3e4642670-rx28v46dte4p CSeq: 1 INVITE Max-Forwards: 15 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Supported: timer, replaces, from-change Session-Expires: 3600 Min-SE: 90 c: application/sdp l: 313 Contact: <sip:leg_1@sip-example.com;ccr=btpsh-64e387e0-ee528-2> v=0 o=root 481174289 481174289 IN IP4 10.64.52.111 s=call c=IN IP4 10.64.52.111 t=0 0 m=audio 34084 RTP/AVP 9 0 8 18 101 a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv -------------------------------------------- (kamailio <-- second proxy) 10.64.52.110 <-- 10.64.52.100 SIP/2.0 100 Trying v: SIP/2.0/UDP 10.64.52.110:5060;branch=z9hG4bKecf9.6d10880e1353b8a7bbf0383d934a38a5.0 f: <sip:133@sip-example.com>;tag=i4mlq4jr0y t: <sip:131@sip-example.com?vm-ext%3D100%26ext-to%3D131%26ext-from%3D133> i: 95c3e4642670-rx28v46dte4p CSeq: 1 INVITE l: 0 -------------------------------------------- After 10 seconds of no further response from second proxy, call is forked to voicemail (kamailio --> voicemail) 10.64.52.110 --> 10.64.56.10 INVITE sip:voicemail@voicemail-example.com SIP/2.0 Via: SIP/2.0/UDP 10.64.52.110:5060;branch=z9hG4bKecf9.6d10880e1353b8a7bbf0383d934a38a5.1 f: <sip:133@sip-example.com>;tag=i4mlq4jr0y t: <sip:131@sip-example.com?vm-ext%3D100%26ext-to%3D131%26ext-from%3D133> i: 95c3e4642670-rx28v46dte4p CSeq: 1 INVITE Max-Forwards: 15 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Supported: timer, replaces, from-change Session-Expires: 3600 Min-SE: 90 c: application/sdp l: 313 Contact: <sip:leg_1@sip-example.com;ccr=btpsh-64e387e0-ee533-3> v=0 o=root 481174289 481174289 IN IP4 10.64.52.111 s=call c=IN IP4 10.64.52.111 t=0 0 m=audio 38722 RTP/AVP 9 0 8 18 101 a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv -------------------------------------------- At roughly the same time, CANCEL is issued towards the second proxy (kamailio --> second proxy) 10.64.52.110 --> 10.64.52.100 CANCEL sip:second-proxy-example.com:5066;ua=43a58ecca39c9c8f37515e55b5b37ed7 SIP/2.0 Via: SIP/2.0/UDP 10.64.52.110:5060;branch=z9hG4bKecf9.6d10880e1353b8a7bbf0383d934a38a5.0 f: <sip:133@sip-example.com>;tag=i4mlq4jr0y t: <sip:131@sip-example.com> i: 95c3e4642670-rx28v46dte4p CSeq: 1 CANCEL Max-Forwards: 15 l: 0 -------------------------------------------- (kamailio <-- voicemail) 10.64.52.110 <-- 10.64.56.10 SIP/2.0 200 Ok Via: SIP/2.0/UDP 10.64.52.110:5060;branch=z9hG4bKecf9.6d10880e1353b8a7bbf0383d934a38a5.1 From: <sip:133@sip-example.com>;tag=i4mlq4jr0y To: <sip:131@sip-example.com?vm-ext%3D100%26ext-to%3D131%26ext-from%3D133>;tag=vzx5x3mlbd Call-ID: 95c3e4642670-rx28v46dte4p CSeq: 1 INVITE Contact: <sip:voicemail@10.64.56.10:5078> Require: timer Session-Expires: 3600;refresher=uac Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO Supported: timer, 100rel, replaces Content-Type: application/sdp Content-Length: 264 v=0 o=root 1084843702 1084843703 IN IP4 10.64.56.10 s=call c=IN IP4 10.64.56.10 t=0 0 m=audio 31908 RTP/AVP 0 101 a=rtpmap:0 pcmu/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=alt:1 0.9 : user 9kksj== 10.64.56.10 31908 a=sendrecv -------------------------------------------- (UA-1 <-- kamailio) 72.255.255.255 <-- 10.64.52.110 SIP/2.0 200 Ok From: <sip:133@sip-example.com>;tag=i4mlq4jr0y To: <sip:131@sip-example.com?vm-ext%3D100%26ext-to%3D131%26ext-from%3D133>;tag=vzx5x3mlbd Call-ID: 95c3e4642670-rx28v46dte4p CSeq: 1 INVITE Require: timer Session-Expires: 3600;refresher=uac Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO Supported: timer, 100rel, replaces Content-Type: application/sdp Content-Length: 270 Via: SIP/2.0/UDP 10.0.0.102:51519;received=72.255.255.255;branch=z9hG4bK-xfelmyyjzne5;rport=51519 Contact: <sip:leg_2@sip-example.com;ccr=atpsh-64e387e0-ee533-3> v=0 o=root 1084843702 1084843703 IN IP4 10.64.52.110 s=call c=IN IP4 10.64.52.110 t=0 0 m=audio 33552 RTP/AVP 0 101 a=rtpmap:0 pcmu/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=alt:1 0.9 : user 9kksj== 10.64.56.10 31908 a=sendrecv =============================================== These next 2 SIP packets repeat, generating 14000+ CANCEL <--> 100 Trying transactions between kamailio, and the second proxy. (kamailio --> second proxy) 10.64.52.110 --> 10.64.52.100 CANCEL sip:second-proxy-example.com:5066;ua=43a58ecca39c9c8f37515e55b5b37ed7 SIP/2.0 Via: SIP/2.0/UDP 10.64.52.110:5060;branch=z9hG4bKecf9.6d10880e1353b8a7bbf0383d934a38a5.0 f: <sip:133@sip-example.com>;tag=i4mlq4jr0y t: <sip:131@sip-example.com> i: 95c3e4642670-rx28v46dte4p CSeq: 1 CANCEL Max-Forwards: 15 l: 0 -------------------------------------------- (kamailio <-- second proxy) 10.64.52.110 <-- 10.64.52.100 SIP/2.0 100 Trying v: SIP/2.0/UDP 10.64.52.110:5060;branch=z9hG4bKecf9.6d10880e1353b8a7bbf0383d934a38a5.0 f: <sip:133@sip-example.com>;tag=i4mlq4jr0y t: <sip:131@sip-example.com?vm-ext%3D100%26ext-to%3D131%26ext-from%3D133> i: 95c3e4642670-rx28v46dte4p CSeq: 1 INVITE l: 0

2 2

Force communications for I-CSCF and S-CSCF to be TCP only
by hvanhelmondt＠peratonlabs.com 23 Aug '23

23 Aug '23

Hi, I would like to force the transport protocol between the I-CSCF and S-CSCF to be TCP only. How would I do that exactly? I'm using an older Kamailio release 5.0.8. Regards,

2 2

use_dns_failover default value
by Silvan Nagl 23 Aug '23

23 Aug '23

Hi, I would like to know the reason for having "off" as default value for use_dns_failover. https://github.com/kamailio/kamailio/issues/3547 Greetings, Silvan

5 4

Kamailio 5.5.4 pua module memory leak
by Vladyslav Korniiaka 20 Aug '23

20 Aug '23

Hello! We are facing a Kamailio memory leak with the pua module, pua module consumes about 2GBs: kamcmd mod.stats all shm Module: pua { add_pua_event(72): 648 init_pua_evlist(36): 56 new_htable(79): 8192 init_puacb_list(35): 16 new_htable(64): 8 publ_cback_func(409): 12451504 publ_cback_func(363): 1658482848 update_htable(203): 210590960 new_htable(93): 131512 Total: 1881665744 } Module: pua_dialoginfo { get_str_list(463): 344 get_dialog_data(500): 1744 Total: 2088 } PUA Module parameters: loadmodule "pua.so" loadmodule "pua_dialoginfo" # ----- pua params ----- modparam("pua", "db_url", DBURL) modparam("pua", "db_mode", 0) modparam("pua", "outbound_proxy", PUA_PROXY) modparam("pua", "db_table_lock_write", 0) modparam("pua", "update_period", 0) modparam("pua", "dlginfo_increase_version", 0) modparam("pua", "reginfo_increase_version", 0) modparam("pua", "check_remote_contact", 0) modparam("pua", "fetch_rows", 1000) modparam("pua", "default_expires", 30) # ----- pua_dialoginfo params ----- modparam("pua_dialoginfo", "include_callid", 1) modparam("pua_dialoginfo", "send_publish_flag", FLT_PUBLISH) modparam("pua_dialoginfo", "caller_confirmed", 1) modparam("pua_dialoginfo", "include_tags", 1) modparam("pua_dialoginfo", "include_localremote", 0) modparam("pua_dialoginfo", "use_pubruri_avps", 1) modparam("pua_dialoginfo", "pubruri_caller_avp", "$avp(s:puburis_caller)") modparam("pua_dialoginfo", "pubruri_callee_avp", "$avp(s:puburis_callee)") *- Kamailio 5.5.4 (x86_64/linux), installed from .deb packages:* kamailio --version version: kamailio 5.5.4 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 8.3.0 *- Kamailio is runned in Docker:* docker --version Docker version 20.10.21, build baeda1f *- With “Debian GNU/Linux 10” docker image:* cat /etc/issue Debian GNU/Linux 10 \n \l *- Host OS is “Ubuntu 18.04.6 LTS”:* cat /etc/issue Ubuntu 18.04.6 LTS \n \l *- Server is AWS EC2 with CPU:* lscpu: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 46 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 85 Model name: Intel(R) Xeon(R) Platinum 8275CL CPU @ 3.00GHz Stepping: 7 CPU MHz: 3599.769 BogoMIPS: 5999.98 Hypervisor vendor: KVM Virtualization type: full L1d cache: 32K L1i cache: 32K L2 cache: 1024K L3 cache: 36608K NUMA node0 CPU(s): 0-7 Please tell me if you need any additional information about this issue. Thanks for helping me with this! -- Regards, Vladyslav Korniiaka vladyslav.korniiaka(a)net2phone.com

2 1

Kamailio 5.5.4 pua module memory leak
by vladyslav.korniiaka＠idt.net 20 Aug '23

20 Aug '23

Hello! We are facing a Kamailio memory leak with the pua module, pua module consumes about 2GBs: kamcmd mod.stats all shm Module: pua { add_pua_event(72): 648 init_pua_evlist(36): 56 new_htable(79): 8192 init_puacb_list(35): 16 new_htable(64): 8 publ_cback_func(409): 12451504 publ_cback_func(363): 1658482848 update_htable(203): 210590960 new_htable(93): 131512 Total: 1881665744 } Module: pua_dialoginfo { get_str_list(463): 344 get_dialog_data(500): 1744 Total: 2088 } PUA Module parameters: loadmodule "pua.so" loadmodule "pua_dialoginfo" # ----- pua params ----- modparam("pua", "db_url", DBURL) modparam("pua", "db_mode", 0) modparam("pua", "outbound_proxy", PUA_PROXY) modparam("pua", "db_table_lock_write", 0) modparam("pua", "update_period", 0) modparam("pua", "dlginfo_increase_version", 0) modparam("pua", "reginfo_increase_version", 0) modparam("pua", "check_remote_contact", 0) modparam("pua", "fetch_rows", 1000) modparam("pua", "default_expires", 30) # ----- pua_dialoginfo params ----- modparam("pua_dialoginfo", "include_callid", 1) modparam("pua_dialoginfo", "send_publish_flag", FLT_PUBLISH) modparam("pua_dialoginfo", "caller_confirmed", 1) modparam("pua_dialoginfo", "include_tags", 1) modparam("pua_dialoginfo", "include_localremote", 0) modparam("pua_dialoginfo", "use_pubruri_avps", 1) modparam("pua_dialoginfo", "pubruri_caller_avp", "$avp(s:puburis_caller)") modparam("pua_dialoginfo", "pubruri_callee_avp", "$avp(s:puburis_callee)") - Kamailio 5.5.4 (x86_64/linux), installed from .deb packages: - Kamailio 5.5.4 (x86_64/linux), installed from .deb packages: kamailio --version version: kamailio 5.5.4 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 8.3.0 - Kamailio is runned in Docker: docker --version Docker version 20.10.21, build baeda1f - With “Debian GNU/Linux 10” docker image: cat /etc/issue Debian GNU/Linux 10 \n \l - Host OS is “Ubuntu 18.04.6 LTS”: cat /etc/issue Ubuntu 18.04.6 LTS \n \l - Server is AWS EC2 with CPU: lscpu: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 46 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 85 Model name: Intel(R) Xeon(R) Platinum 8275CL CPU @ 3.00GHz Stepping: 7 CPU MHz: 3599.769 BogoMIPS: 5999.98 Hypervisor vendor: KVM Virtualization type: full L1d cache: 32K L1i cache: 32K L2 cache: 1024K L3 cache: 36608K NUMA node0 CPU(s): 0-7 Please tell me if you need any additional information about this issue. Thanks for helping me with this! -- Regards, Vladyslav Korniiaka vladyslav.korniiaka(a)net2phone.com

1 0

Check refer-to number
by David Cunningham 17 Aug '23

17 Aug '23

Hello, We want to check if the number in a REFER's Refer-To header begins with 011, and if so reject the request as not allowed. What would be the most effective way to do that? Thanks in advance, -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

4 4

Unable to get avp value in response
by peter＠alienzombie.co.uk 17 Aug '23

17 Aug '23

I am trying to set a value to an avp on the request route, but when I try to read the avp on the reply route I always get nil. On the route I have this: KSR.xlog.xinfo("invite_request: ********** Setting avp test\n") KSR.pv.seti("$avp(test)", 1) KSR.xlog.xinfo("invite_request: **** " .. tostring(KSR.pv.get("$avp(test)")).."\n") On the reply route I have this: KSR.xlog.xinfo("response_invite: **** " .. tostring(KSR.pv.get("$avp(test)")).."\n") In the logs I see on the INVITE: Aug 8 13:49:15 test /usr/sbin/kamailio[1927947]: INFO: [a0748d39-3f17-4080-b5ed-0a6b7019cb95 INVITE 1]invite_request: ********** Setting avp test Aug 8 13:49:15 test /usr/sbin/kamailio[1927947]: INFO: [a0748d39-3f17-4080-b5ed-0a6b7019cb95 INVITE 1]invite_request: **** 1 ... ... Aug 8 13:49:15 test /usr/sbin/kamailio[1927968]: INFO: [a0748d39-3f17-4080-b5ed-0a6b7019cb95 INVITE 2]response_invite: **** nil Do avp not cover the transaction?

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users