sr-users

sr-users@lists.kamailio.org

19 participants
37571 discussions

Kamailio+IMS+WebSocket
by mohammed alyaseen 26 Apr '14

26 Apr '14

Hi folks, I am using Kamailio with IMS, I added the configuration of the WebSocket to the kamailio.cfg in the PCSCF to enable WebRTC clients like (JsSIP) to communicate with each other.. The registration works so far, however when I try to make peer-2-peer call between alice and bob, the caller gets a "403 error" "403 Forbidden Mohammed- Dialog not found on S-CSCF or Terminating user not suitable for unregistered services" from the S-CSCF.. I did trace on the PCSCF and I found a strange signaling behaviour. the invite is negotiated between the IMS components as follows: INVITE from PCSCF to SCSCF INVITE from PCSCF to PCSCF PCSCF responses itself with "403 Forbidden - You must register first with a S-CSCF" SCSCF sends the response "403 Forbidden Mohammed- Dialog not found on S-CSCF or Terminating user not suitable for unregistered services" to the PCSCF The private IP address of the PCSCF is 172.19.6.35 and of the SCSCF is 172.19.6.36. The PCSCF has a public IP "193.175.132.235" The IMS components don't run on the same machine, PCSCF and SCSCF are listening to the port 5060. the WebSocket port of the PCSCF is 8000 Can anyone help me get a solution for this problem Thanks in advance Best regards, Medo Mohammed Al-khameri Technical University Berlin TUB

1 0

Re: [SR-Users] cnxcc
by Andrzej Ciupek 26 Apr '14

26 Apr '14

Hello I’am using default config with options from an example. It looks like event route isn’t execuded after hangup. Apr 26 16:26:14 kamailio /usr/local/sbin/kamailio[4611]: INFO: <script>: 1000 has 1 call(s) Apr 26 16:26:15 kamailio /usr/local/sbin/kamailio[4611]: INFO: <script>: 1000 has 1 call(s) Apr 26 16:26:16 kamailio /usr/local/sbin/kamailio[4611]: INFO: <script>: 1000 has 1 call(s) Apr 26 16:26:17 kamailio /usr/local/sbin/kamailio[4611]: INFO: <script>: 1000 has 1 call(s) Apr 26 16:26:18 kamailio /usr/local/sbin/kamailio[4611]: INFO: <script>: 1000 has 1 call(s) Apr 26 16:26:19 kamailio /usr/local/sbin/kamailio[4611]: INFO: <script>: 1000 has 1 call(s) Apr 26 16:26:20 kamailio /usr/local/sbin/kamailio[4611]: INFO: <script>: 1000 has 1 call(s) Apr 26 16:26:20 kamailio /usr/local/sbin/kamailio[4604]: INFO: <script>: Setting up money based credit control Apr 26 16:26:20 kamailio /usr/local/sbin/kamailio[4604]: INFO: <script>: Setting up channel based credit control Apr 26 16:26:20 kamailio /usr/local/sbin/kamailio[4604]: INFO: <script>: CNXCC ROUTE: 1000 has 2 call(s) kamailio.cfg … … # ----- prepaid call controll ----- #!define DLG_FLAG 28 #!define CC_FLAG 29 loadmodule "dialog.so" modparam("dialog", "hash_size", 2048) modparam("dialog", "default_timeout", 3600) modparam("dialog", "db_mode", 0) modparam("dialog", "dlg_flag", DLG_FLAG) modparam("rtimer", "timer", "name=ta;interval=1;mode=1;") modparam("rtimer", "exec", "timer=ta;route=SHOW_CHANNEL_COUNT") loadmodule "cnxcc.so" modparam("cnxcc", "dlg_flag", CC_FLAG) modparam("cnxcc", "credit_check_period", 1) #check every 1 second … … … route { … … if (!allow_source_address("2") and !allow_source_address("1")){ route(CNXCC); route(PSTN); } … } route[CNXCC] { $var(client) = "1000"; xlog("L_INFO", "Setting up money based credit control"); $var(credit) = "10"; # 10$ of credit $var(cost_per_sec) = "1"; # 1$ per sec $var(i_pulse) = "1"; # 1$ to establish the call $var(f_pulse) = "1"; # 1$ per second # if only one call is established, that call should last 9 seconds. if (!cnxcc_set_max_credit("$var(client)", "$var(credit)", "$var(cost_per_sec)", "$var(i_pulse)", "$var(f_pulse)")) { xlog("Error setting up credit control"); return; } $var(count) = -1; if (!cnxcc_get_channel_count("$var(client)", "$var(count)")) { xlog("Error getting customer's channel count"); } xlog("L_INFO", "CNXCC ROUTE: $var(client) has $var(count) call(s)"); if ($var(retcode) < -1) { xlog("Too many channels for customer"); sl_send_reply(403, "Forbidden"); if (!cnxcc_terminate_all("$var(client)")) { xlog("Error terminating customer's calls"); } else { xlog("Terminating customer's call"); } exit; } } route[SHOW_CHANNEL_COUNT] { $var(count) = @cnxcc.channels["1000"].count; xlog("L_INFO", "1000 has $var(count) call(s)"); } event_route[dialog:failed] { xlog("dialog failed"); } event_route[cnxcc:call-shutdown] { xlog("L_INFO", "Shutting down channel by callcontroll"); xlog("L_INFO", "[$ci]: call killed"); $var(count) = $var(count)-1; if (!cnxcc_get_channel_count("$var(client)", "$var(count)")) { xlog("Error getting customer's channel count"); } xlog("L_INFO", "CNXCC ROUTE: $var(client) has $var(count) call(s)"); # perform some kind of notification, database update, email sending, etc } Greetings Andrzej Ciupek Od: Carlos Ruiz Díaz Wysłano: ‎sobota‎, ‎26‎ ‎kwietnia‎ ‎2014 ‎15‎:‎19 Do: Kamailio (SER) - Users Mailing List, Andrzej Ciupek Hi, sorry guys, I forgot about this. I will make my own tests and post the results. Andrzej, can you post the configuration file you are using? Regards, Carlos On Sat, Apr 26, 2014 at 4:15 AM, Kelvin Chua <kelchy(a)gmail.com> wrote: No, I have not yet found the solution for this issue on my setup. Maybe Carlos can help us out On Apr 26, 2014 5:10 PM, "Andrzej Ciupek" <andrzej.ciupek(a)hotmail.com> wrote: Hello Have You solved this issue ? I’am using Kamailio 4.1.3 and I’am getting the same results. Greetings Andrzej Ciupek _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Carlos http://caruizdiaz.com http://ngvoice.com +52 55 3048 3303

2 1

Re: [SR-Users] cnxcc
by Kelvin Chua 26 Apr '14

26 Apr '14

No, I have not yet found the solution for this issue on my setup. Maybe Carlos can help us out On Apr 26, 2014 5:10 PM, "Andrzej Ciupek" <andrzej.ciupek(a)hotmail.com> wrote: > Hello > > Have You solved this issue ? > I’am using Kamailio 4.1.3 and I’am getting the same results. > > Greetings > Andrzej Ciupek >

2 1

Kamailio+IMS+WebSocket
by mohammed alyaseen 26 Apr '14

26 Apr '14

1 0

LCR from_uri help
by Geoffrey Mina 26 Apr '14

26 Apr '14

Greetings, I need a little help with the LCR module. I am running Kamailio 4.1.2. The LCR module is behaving in a way that is inconsistent with our old 1.5 versions. We have a customer that passes a certain caller-id. That from_uri should be routing over a specific trunk. Here are the relevant bits of the LCR data from kamcmd. I would expect gw_index: 7 to match before gw_index: 6 here, but that is not the case. Any help would be greatly appreciated. Please note, i Have stripped out a bunch of other routes that are not in play here... hence the reason gw_index starts at "6". kamcmd> lcr.dump_gws { lcr_id: 1 gw_id: 11 gw_index: 6 gw_name: Route A scheme: sip ip_addr: 1.2.3.4 hostname: port: 5060 params: transport: UDP strip: 0 prefix: tag: flags: 2 defunct_until: 0 } { lcr_id: 1 gw_id: 1 gw_index: 7 gw_name: Route P scheme: sip ip_addr: 4.3.2.1 hostname: port: 5060 params: transport: UDP strip: 0 prefix: DLR# tag: flags: 0 defunct_until: 0 } kamcmd> lcr.dump_rules { lcr_id: 1 rule_id: 31 prefix: +1 from_uri: 2089328663 request_uri: stopper: 0 } { gw_index: 6 priority: 1 weight: 1 } { lcr_id: 1 rule_id: 5 prefix: +1 from_uri: request_uri: stopper: 0 } { gw_index: 7 priority: 1 weight: 1 }

2 7

Kam 4.1 Crash: HELP PLZ!!!!
by Samuel Ware 26 Apr '14

26 Apr '14

Here are the logs from the first crash Apr 3 13:13:59 tel-vc-fs03 /usr/local/sbin/kamailio[7602]: ERROR: tm [../../forward.h:199]: msg_send(): msg_send: ERROR: udp_send failed Apr 3 13:13:59 tel-vc-fs03 /usr/local/sbin/kamailio[7602]: ERROR: tm [t_fwd.c:1609]: t_send_branch(): ERROR: t_send_branch: sending request on branch 0 failed Apr 3 13:13:59 tel-vc-fs03 /usr/local/sbin/kamailio[7602]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) Apr 3 13:14:05 tel-vc-fs03 /usr/local/sbin/kamailio[7579]: ERROR: <core> [udp_server.c:591]: udp_send(): ERROR: udp_send: sendto(sock,0x7feac6836310,65572,0,205.251.172.14:5060,16): Message too long(90) Apr 3 13:14:05 tel-vc-fs03 /usr/local/sbin/kamailio[7579]: ERROR: tm [../../forward.h:199]: msg_send(): msg_send: ERROR: udp_send failed Apr 3 13:14:05 tel-vc-fs03 /usr/local/sbin/kamailio[7579]: ERROR: tm [t_fwd.c:1609]: t_send_branch(): ERROR: t_send_branch: sending request on branch 0 failed Apr 3 13:14:05 tel-vc-fs03 /usr/local/sbin/kamailio[7579]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) Apr 3 13:14:20 tel-vc-fs03 /usr/local/sbin/kamailio[7594]: ERROR: <core> [udp_server.c:591]: udp_send(): ERROR: udp_send: sendto(sock,0x7feaace02c98,65533,0,205.251.172.14:5060,16): Message too long(90) Apr 3 13:14:20 tel-vc-fs03 /usr/local/sbin/kamailio[7594]: ERROR: tm [../../forward.h:199]: msg_send(): msg_send: ERROR: udp_send failed Apr 3 13:14:20 tel-vc-fs03 /usr/local/sbin/kamailio[7594]: ERROR: tm [t_fwd.c:1609]: t_send_branch(): ERROR: t_send_branch: sending request on branch 0 failed Apr 3 13:14:20 tel-vc-fs03 /usr/local/sbin/kamailio[7594]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) Apr 3 13:14:27 tel-vc-fs03 /usr/local/sbin/kamailio[7583]: ERROR: <core> [udp_server.c:591]: udp_send(): ERROR: udp_send: sendto(sock,0x7feac6836310,65569,0,205.251.172.14:5060,16): Message too long(90) Apr 3 13:14:27 tel-vc-fs03 /usr/local/sbin/kamailio[7583]: ERROR: tm [../../forward.h:199]: msg_send(): msg_send: ERROR: udp_send failed Apr 3 13:14:27 tel-vc-fs03 /usr/local/sbin/kamailio[7583]: ERROR: tm [t_fwd.c:1609]: t_send_branch(): ERROR: t_send_branch: sending request on branch 0 failed Apr 3 13:14:27 tel-vc-fs03 /usr/local/sbin/kamailio[7583]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) Apr 3 13:14:32 tel-vc-fs03 /usr/local/sbin/kamailio[7589]: : <core> [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0x7feaca6c9738), called from <core>: mem/shm_mem.c: sh_realloc(88), first free <core>: mem/shm_mem.c: sh_realloc(88) - aborting Apr 3 13:14:55 tel-vc-fs03 /usr/local/sbin/kamailio[7553]: ALERT: <core> [main.c:775]: handle_sigs(): child process 7589 exited by a signal 6 Apr 3 13:14:55 tel-vc-fs03 /usr/local/sbin/kamailio[7553]: ALERT: <core> [main.c:778]: handle_sigs(): core was generated Apr 3 13:14:55 tel-vc-fs03 /usr/local/sbin/kamailio[7553]: INFO: <core> [main.c:790]: handle_sigs(): INFO: terminating due to SIGCHLD Apr 3 13:14:55 tel-vc-fs03 /usr/local/sbin/kamailio[7604]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Apr 3 13:14:55 tel-vc-fs03 /usr/local/sbin/kamailio[7597]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Apr 3 13:14:55 tel-vc-fs03 /usr/local/sbin/kamailio[7579]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Apr 3 13:14:55 tel-vc-fs03 /usr/local/sbin/kamailio[7603]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Apr 3 13:14:55 tel-vc-fs03 /usr/local/sbin/kamailio[7601]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Logs from second crash Apr 3 14:38:42 tel-vc-fs03 /usr/local/sbin/kamailio[3979]: ERROR: <core> [udp_server.c:591]: udp_send(): ERROR: udp_send: sendto(sock,0x7f34ec4f6ed8,65569,0,205.251.172.14:5060,16): Message too long(90) Apr 3 14:38:42 tel-vc-fs03 /usr/local/sbin/kamailio[3979]: ERROR: tm [../../forward.h:199]: msg_send(): msg_send: ERROR: udp_send failed Apr 3 14:38:42 tel-vc-fs03 /usr/local/sbin/kamailio[3979]: ERROR: tm [t_fwd.c:1609]: t_send_branch(): ERROR: t_send_branch: sending request on branch 0 failed Apr 3 14:38:42 tel-vc-fs03 /usr/local/sbin/kamailio[3979]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) Apr 3 14:38:44 tel-vc-fs03 /usr/local/sbin/kamailio[3965]: ERROR: <core> [udp_server.c:591]: udp_send(): ERROR: udp_send: sendto(sock,0x7f35242e5d28,65535,0,205.251.172.14:5060,16): Message too long(90) Apr 3 14:38:44 tel-vc-fs03 /usr/local/sbin/kamailio[3965]: ERROR: tm [../../forward.h:199]: msg_send(): msg_send: ERROR: udp_send failed Apr 3 14:38:44 tel-vc-fs03 /usr/local/sbin/kamailio[3965]: ERROR: tm [t_fwd.c:1609]: t_send_branch(): ERROR: t_send_branch: sending request on branch 0 failed Apr 3 14:38:44 tel-vc-fs03 /usr/local/sbin/kamailio[3965]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) Apr 3 14:38:57 tel-vc-fs03 /usr/local/sbin/kamailio[3968]: ERROR: <core> [udp_server.c:591]: udp_send(): ERROR: udp_send: sendto(sock,0x7f3516fb6720,65578,0,205.251.172.14:5060,16): Message too long(90) Apr 3 14:38:57 tel-vc-fs03 /usr/local/sbin/kamailio[3968]: ERROR: tm [../../forward.h:199]: msg_send(): msg_send: ERROR: udp_send failed Apr 3 14:38:57 tel-vc-fs03 /usr/local/sbin/kamailio[3968]: ERROR: tm [t_fwd.c:1609]: t_send_branch(): ERROR: t_send_branch: sending request on branch 0 failed Apr 3 14:38:57 tel-vc-fs03 /usr/local/sbin/kamailio[3968]: ERROR: <core> [udp_server.c:591]: udp_send(): ERROR: udp_send: sendto(sock,0x7f37d8e91088,65522,0,205.251.172.14:5060,16): Message too long(90) Apr 3 14:38:57 tel-vc-fs03 /usr/local/sbin/kamailio[3968]: ERROR: sl [../../forward.h:199]: msg_send(): msg_send: ERROR: udp_send failed Apr 3 14:38:57 tel-vc-fs03 /usr/local/sbin/kamailio[3968]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) Apr 3 14:38:57 tel-vc-fs03 /usr/local/sbin/kamailio[3968]: ERROR: <core> [udp_server.c:591]: udp_send(): ERROR: udp_send: sendto(sock,0x7f37d8e91088,65522,0,205.251.172.14:5060,16): Message too long(90) Apr 3 14:38:57 tel-vc-fs03 /usr/local/sbin/kamailio[3968]: ERROR: tm [../../forward.h:199]: msg_send(): msg_send: ERROR: udp_send failed Apr 3 14:38:58 tel-vc-fs03 /usr/local/sbin/kamailio[3961]: ERROR: <core> [udp_server.c:591]: udp_send(): ERROR: udp_send: sendto(sock,0x7f37d81fa960,65522,0,205.251.172.14:5060,16): Message too long(90) Apr 3 14:38:58 tel-vc-fs03 /usr/local/sbin/kamailio[3961]: ERROR: tm [../../forward.h:199]: msg_send(): msg_send: ERROR: udp_send failed Apr 3 14:38:58 tel-vc-fs03 /usr/local/sbin/kamailio[3974]: : <core> [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0x7f34d7d6b720), called from <core>: mem/shm_mem.c: sh_realloc(88), first free <core>: mem/shm_mem.c: sh_realloc(88) - aborting Apr 3 14:39:20 tel-vc-fs03 /usr/local/sbin/kamailio[3935]: ALERT: <core> [main.c:775]: handle_sigs(): child process 3974 exited by a signal 6 Apr 3 14:39:20 tel-vc-fs03 /usr/local/sbin/kamailio[3935]: ALERT: <core> [main.c:778]: handle_sigs(): core was generated Apr 3 14:39:20 tel-vc-fs03 /usr/local/sbin/kamailio[3935]: INFO: <core> [main.c:790]: handle_sigs(): INFO: terminating due to SIGCHLD Apr 3 14:39:20 tel-vc-fs03 /usr/local/sbin/kamailio[3985]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Apr 3 14:39:20 tel-vc-fs03 /usr/local/sbin/kamailio[3983]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Apr 3 14:39:20 tel-vc-fs03 /usr/local/sbin/kamailio[3966]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Apr 3 14:39:20 tel-vc-fs03 /usr/local/sbin/kamailio[3988]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Apr 3 14:39:20 tel-vc-fs03 /usr/local/sbin/kamailio[3972]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Apr 3 14:39:20 tel-vc-fs03 /usr/local/sbin/kamailio[3984]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received

5 10

Kamailio+IMS+WebSocket
by mohammed alyaseen 25 Apr '14

25 Apr '14

1 0

Re: [SR-Users] Minimalist Kamilio configuration example using dynamic routing module
by Gary Wallis 25 Apr '14

25 Apr '14

Hi, We are moving away from OpenSIPS and would like to start testing Kamailio. I really liked how Kamailio complies so clean and is configured easily in comparison with OpenSIPS monstrosity. So to not waste time can anybody provide some practical info for... Kamailio complilation and config examples (w/MySQL) to route Carrier SIP (DID incoming and outgoing PSTN termination) traffic to and from Asterisk PBXs. Example current OpenSIPS setup using dynamic routing module: 1-. dr_rules have the complete DID for PBXs (for incoming traffic from Carriers to be proxied to the correct PBX). 2-. dr_rules have the partial DID for Carrier gateways (for example based on internatinal, state, etc. routing of outgoing traffic from PBXs to Carriers). 3-. dr_gateways have the IP numbers for PBXs. 4-. dr_gateways have the IP numbers for Carriers. Any info and pointers appreciated. Best regards, Gary

2 2

Re: [SR-Users] Caller ID fields incorrect on Polycom 650s
by J Lee 25 Apr '14

25 Apr '14

Thanks for your response Daniel! I think I omitted a key piece of information in my original question! We are using the SCA module. Hope that sheds some more light on the situation. -jl > Date: Thu, 24 Apr 2014 23:06:28 +0200 > From: Daniel-Constantin Mierla <miconda(a)gmail.com> > To: "Kamailio (SER) - Users Mailing List" > <sr-users(a)lists.sip-router.org> > Subject: Re: [SR-Users] Caller ID fields incorrect on Polycom 650s > Message-ID: <53597CD4.8030106(a)gmail.com> > Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" > > Hello, > > kamailio is not touching from/to headers by default. If there are > incorrect, then could be somewhere else. You ahve tos end a sip trace > (ngrep for example) with incoming and outgoing sip packets on kamailio > server. > > Cheers, > Daniel > > On 24/04/14 21:58, J Lee wrote: >> Hi there. >> >> I have a situation where the caller id information on my phone appear >> incorrectly. >> When I have ext 1 dial ext 2, on the caller's phone, instead of saying >> "To: 2", it says "From: 2". >> >> I'm using kamailio version 4.0.4. I'm just new to everything kamailio >> and VoIP so I apologize in advance for any remedial questions. >> >> So far, I've done a SIP trace to and checked all packets line by line >> to see if I could spot where the To address was erroneously changed to >> FROM. In particular, I was checking the call-info fields for caller >> id data or any other data what would appear on the LED of the phone. >> >> Now I'm wondering, who's job (aka which module) is it to set the >> caller id information for both phones? >> I'm thinking of digging inside the code for the right module just to >> see if I can follow what's going on >> >> In addition to answering the question above, if you have any >> suggestions on what else I can check or try, I'd appreciate it. >> >> Thanks List! >> >> >> >> >> >> _______________________________________________ >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >> sr-users(a)lists.sip-router.org >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > -- > Daniel-Constantin Mierla - http://www.asipto.com > http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Kamailio v4.1.3 Released
by Daniel-Constantin Mierla 25 Apr '14

25 Apr '14

Hello, Kamailio SIP Server v4.1.3 stable release is out. This is a maintenance release of the latest stable branch, 4.1, that includes fixes since release of v4.1.2. There is no change to database schema or configuration language structure that you have to do on installations of v4.1.x. Deployments running previous v4.x.x versions are strongly recommended to be upgraded to v4.1.3. For more details about version 4.1.3 (including links and guidelines to download the tarball or from GIT repository), visit: * http://www.kamailio.org/w/2014/04/kamailio-v4-1-3-released/ RPM, Debian/Ubuntu packages will be available soon as well. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

3 3

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