October 2003 - sr-users

[Serusers] compilation error of sources from cvs
by schweizer laurent 30 Oct '03

30 Oct '03

Hello, I try to compile the last version of ser( from the cvs) and i have some errors with rr module ... Thanks root@edu-pc134:~/ser/sip_router# make all Extra objs: gcc -Wl,-O2 -Wl,-E action.o crc.o data_lump.o data_lump_rpl.o dprint.o dset.o error.o fifo_server.o flags.o forward.o hash_func.o ip_addr.o main.o md5.o md5utils.o modparam.o msg_translator.o pass_fd.o proxy.o re.o receive.o resolve.o route.o route_struct.o script_cb.o socket_info.o sr_module.o stats.o tcp_main.o tcp_read.o timer.o udp_server.o mem/f_malloc.o mem/mem.o mem/memtest.o mem/q_malloc.o mem/shm_mem.o mem/vq_malloc.o parser/hf.o parser/msg_parser.o parser/parse_content.o parser/parse_cseq.o parser/parse_disposition.o parser/parse_event.o parser/parse_expires.o parser/parse_fline.o parser/parse_from.o parser/parse_hname2.o parser/parse_hostport.o parser/parse_nameaddr.o parser/parse_param.o parser/parse_rr.o parser/parse_to.o parser/parse_uri.o parser/parse_via.o parser/parser_f.o parser/digest/digest.o parser/digest/digest_parser.o parser/digest/param_parser.o parser/contact/contact.o parser/contact/parse_contact.o db/db.o db/db_fifo.o lex.yy.o cfg.tab.o -lfl -ldl -lresolv -o ser make[1]: Entering directory `/root/ser/sip_router/modules/acc' gcc -fPIC -DPIC -g -O9 -funroll-loops -Wcast-align -Wall -minline-all-str ingops -malign-double -falign-loops -mcpu=athlon -DNAME='"ser"' -DVERSI ON='"0.8.12dev-22-tcp_aliases"' -DARCH='"i386"' -DOS='"linux"' -DCOMPILER='" gcc 3.2"' -D__CPU_i386 -D__OS_linux -DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALL OC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP _HACK -DUSE_IPV6 -DUSE_TCP -DDISABLE_NAGLE -DDBG_QM_MALLOC -DFAST_LOCK -DHA VE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DSQL_ACC -DRAD_ACC -c acc.c -o acc.o acc.c:50:26: radiusclient.h: No such file or directory acc.c:61: `PW_CALLING_STATION_ID' undeclared here (not in a function) acc.c:61: initializer element is not constant acc.c:61: (near initialization for `rad_attr[0]') acc.c:61: `PW_CALLED_STATION_ID' undeclared here (not in a function) acc.c:61: initializer element is not constant acc.c:61: (near initialization for `rad_attr[1]') acc.c:62: `PW_ACCT_SESSION_ID' undeclared here (not in a function) acc.c:62: initializer element is not constant acc.c:62: (near initialization for `rad_attr[3]') acc.c:496: parse error before "phrase2code" acc.c:497: warning: return type defaults to `int' acc.c: In function `phrase2code': acc.c:498: `UINT4' undeclared (first use in this function) acc.c:498: (Each undeclared identifier is reported only once acc.c:498: for each function it appears in.) acc.c:498: parse error before "code" acc.c:502: `code' undeclared (first use in this function) acc.c: At top level: acc.c:511: parse error before "rad_status" acc.c:512: warning: return type defaults to `int' acc.c: In function `rad_status': acc.c:520: `PW_STATUS_START' undeclared (first use in this function) acc.c:523: `PW_STATUS_STOP' undeclared (first use in this function) acc.c: In function `acc_rad_request': acc.c:533: `VALUE_PAIR' undeclared (first use in this function) acc.c:534: `UINT4' undeclared (first use in this function) acc.c:534: parse error before "av_type" acc.c:548: invalid lvalue in assignment acc.c:559: `av_type' undeclared (first use in this function) acc.c:560: warning: implicit declaration of function `rc_avpair_add' acc.c:560: `PW_ACCT_STATUS_TYPE' undeclared (first use in this function) acc.c:565: `PW_SERVICE_TYPE' undeclared (first use in this function) acc.c:595: `PW_USER_NAME' undeclared (first use in this function) acc.c:657: warning: implicit declaration of function `rc_acct' acc.c:657: `OK_RC' undeclared (first use in this function) acc.c:661: warning: implicit declaration of function `rc_avpair_free' make[1]: *** [acc.o] Error 1 make[1]: Leaving directory `/root/ser/sip_router/modules/acc' make[1]: Entering directory `/root/ser/sip_router/modules/auth' make[1]: `auth.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/auth' make[1]: Entering directory `/root/ser/sip_router/modules/auth_db' make[1]: `auth_db.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/auth_db' make[1]: Entering directory `/root/ser/sip_router/modules/auth_diameter' make[1]: `auth_diameter.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/auth_diameter' make[1]: Entering directory `/root/ser/sip_router/modules/dbtext' make[1]: `dbtext.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/dbtext' make[1]: Entering directory `/root/ser/sip_router/modules/domain' make[1]: `domain.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/domain' make[1]: Entering directory `/root/ser/sip_router/modules/enum' make[1]: `enum.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/enum' make[1]: Entering directory `/root/ser/sip_router/modules/exec' make[1]: `exec.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/exec' make[1]: Entering directory `/root/ser/sip_router/modules/group' make[1]: `group.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/group' make[1]: Entering directory `/root/ser/sip_router/modules/maxfwd' make[1]: `maxfwd.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/maxfwd' make[1]: Entering directory `/root/ser/sip_router/modules/msilo' make[1]: `msilo.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/msilo' make[1]: Entering directory `/root/ser/sip_router/modules/nathelper' make[1]: `nathelper.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/nathelper' make[1]: Entering directory `/root/ser/sip_router/modules/options' make[1]: `options.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/options' make[1]: Entering directory `/root/ser/sip_router/modules/pa' make[1]: `pa.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/pa' make[1]: Entering directory `/root/ser/sip_router/modules/permissions' make[1]: `permissions.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/permissions' make[1]: Entering directory `/root/ser/sip_router/modules/pike' make[1]: `pike.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/pike' make[1]: Entering directory `/root/ser/sip_router/modules/print' make[1]: `print.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/print' make[1]: Entering directory `/root/ser/sip_router/modules/registrar' make[1]: `registrar.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/registrar' make[1]: Entering directory `/root/ser/sip_router/modules/rr' gcc -fPIC -DPIC -g -O9 -funroll-loops -Wcast-align -Wall -minline-all-str ingops -malign-double -falign-loops -mcpu=athlon -DNAME='"ser"' -DVERSI ON='"0.8.12dev-22-tcp_aliases"' -DARCH='"i386"' -DOS='"linux"' -DCOMPILER='" gcc 3.2"' -D__CPU_i386 -D__OS_linux -DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALL OC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP _HACK -DUSE_IPV6 -DUSE_TCP -DDISABLE_NAGLE -DDBG_QM_MALLOC -DFAST_LOCK -DHA VE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -c loose.c -o loose.o loose.c: In function `is_myself': loose.c:212: too few arguments to function `check_self' loose.c: In function `save_ruri': loose.c:374: warning: passing arg 1 of `anchor_lump' from incompatible pointer type loose.c: In function `handle_strict_router': loose.c:439: warning: passing arg 1 of `del_lump' from incompatible pointer type loose.c: In function `route_after_strict': loose.c:523: warning: passing arg 1 of `del_lump' from incompatible pointer type loose.c:571: warning: passing arg 1 of `del_lump' from incompatible pointer type loose.c:589: warning: passing arg 1 of `del_lump' from incompatible pointer type loose.c:622: warning: passing arg 1 of `del_lump' from incompatible pointer type loose.c: In function `route_after_loose': loose.c:665: warning: passing arg 1 of `del_lump' from incompatible pointer type loose.c:686: warning: passing arg 1 of `del_lump' from incompatible pointer type loose.c:733: warning: passing arg 1 of `del_lump' from incompatible pointer type make[1]: *** [loose.o] Error 1 make[1]: Leaving directory `/root/ser/sip_router/modules/rr' make[1]: Entering directory `/root/ser/sip_router/modules/sl' make[1]: `sl.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/sl' make[1]: Entering directory `/root/ser/sip_router/modules/sms' make[1]: `sms.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/sms' make[1]: Entering directory `/root/ser/sip_router/modules/textops' make[1]: `textops.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/textops' make[1]: Entering directory `/root/ser/sip_router/modules/tm' make[1]: `tm.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/tm' make[1]: Entering directory `/root/ser/sip_router/modules/uri' make[1]: `uri.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/uri' make[1]: Entering directory `/root/ser/sip_router/modules/usrloc' make[1]: `usrloc.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/usrloc' make[1]: Entering directory `/root/ser/sip_router/modules/vm' make[1]: `vm.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/vm' make[1]: Entering directory `/root/ser/sip_router/modules/xlog' make[1]: `xlog.so' is up to date. make[1]: Leaving directory `/root/ser/sip_router/modules/xlog'

3 2

[Serusers] voicmail test
by Chen Youcheng 30 Oct '03

30 Oct '03

hello, i am testing voicemail mudule. But i want to use MySql database. So i change my ser.cfg: loadmodules "modules/mysql.so" loadmodules "modules/textops.so" loadmodules "modules/vm.so" modparam("voicemail","db_url","sql://ser:heslo@localhost/ser") I use the route logic of example in Admin's Guide. Ser seems to work. Pls. excuse the basic question, but in order to get started I would like to know: 1. Must i compile the voicemail application am first? 2. How can i invoke voiemail function. For example: use Windows Messenger Client. 3. Was does /modules/vm/test/vm_test.sh do? best regards dayong1973 __________________________________ Do you Yahoo!? Exclusive Video Premiere - Britney Spears http://launch.yahoo.com/promos/britneyspears/

2 1

Re[2]: [Serusers] Ser and Voicemail
by Jiri Kuthan 30 Oct '03

30 Oct '03

At 02:01 PM 10/30/2003, Alessio Focardi wrote: >JK> see the thread "standalone voicemail example" in our archive (copied bellow). > >JK> The mode we built is running SER at a separate place than voicemail, >JK> i.e., once SER as proxy, once SER as SEMS front-end, possibly at >JK> the same host but at different port-numbers. > >JK> One-SER-only is workable too for off-line users, but I'm not sure >JK> it is workable for failed called attemps (failur_routes in script). >JK> I promised to look at it as time allow -- that still holds, the time >JK> just has not allowed yet ;) > >Tnx for helping me, now I have 2 Ser servers configured, one for >normal processing and the other (on port 5090) for voicemail. > >Sems is running, now what I'm missing is the .cfg part of the "real >server" that will forward calls to the second one (voicemailer). > >I tried some "cut and paste" from examples, I guess that the part that >controls missed calls is this: > >if (!lookup("location")) { > > sl_send_reply("402", "Not Found"); > break; > }; > >But I havent found yet a directive for port rewriting .... Anyone can >help me figure out ? here it is, an example config file for the proxy server serving a separate voicemail server: http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/examples/vm_proxy.… -jiri

1 0

[Serusers] Sometimes ser is not started correctly
by schweizer laurent 30 Oct '03

30 Oct '03

Hello, Sometimes, when I restart ser or when I reboot the server ser is not correctly started. When ser is started, the server indicate that it is ok, but when I try to stop ser I receive an error. I have tried to restart several times ser and I see that it is not each time. login as: root Sent username "root" root(a)10.192.72.169's password: [root@edu-pc134 root]# /etc/rc.d/init.d/ser restart Stopping ser: [FAILED] Starting ser: [ OK ] [root@edu-pc134 root]# /etc/rc.d/init.d/ser restart Stopping ser: [ OK ] Starting ser: [ OK ] [root@edu-pc134 root]# /etc/rc.d/init.d/ser restart Stopping ser: [ OK ] Starting ser: [ OK ] [root@edu-pc134 root]# /etc/rc.d/init.d/ser restart Stopping ser: [ OK ] Starting ser: [ OK ] [root@edu-pc134 root]# /etc/rc.d/init.d/ser restart Stopping ser: [ OK ] Starting ser: [ OK ] [root@edu-pc134 root]# /etc/rc.d/init.d/ser restart Stopping ser: [ OK ] Starting ser: [ OK ] [root@edu-pc134 root]# /etc/rc.d/init.d/ser restart Stopping ser: [FAILED] Starting ser: [ OK ] [root@edu-pc134 root]# /etc/rc.d/init.d/ser restart Stopping ser: [ OK ] Starting ser: [ OK ] [root@edu-pc134 root]# /etc/rc.d/init.d/ser restart Stopping ser: [ OK ] Starting ser: [ OK ] [root@edu-pc134 root]# /etc/rc.d/init.d/ser restart Stopping ser: [ OK ] Starting ser: [ OK ] [root@edu-pc134 root]# /etc/rc.d/init.d/ser restart Stopping ser: [ OK ] Starting ser: [ OK ] [root@edu-pc134 root]# /etc/rc.d/init.d/ser restart Stopping ser: [ OK ] Starting ser: [ OK ] [root@edu-pc134 root]# /etc/rc.d/init.d/ser restart Stopping ser: [ OK ] Starting ser: [ OK ] [root@edu-pc134 root]# /etc/rc.d/init.d/ser restart Stopping ser: [ OK ] Starting ser: [ OK ] [root@edu-pc134 root]# /etc/rc.d/init.d/ser restart Stopping ser: [FAILED] Starting ser: [ OK ] [root@edu-pc134 root]# Oct 28 13:20:02 edu-pc134 ser: ser shutdown succeeded Oct 28 13:20:02 edu-pc134 ser: Listening on Oct 28 13:20:02 edu-pc134 ser: 127.0.0.1 [127.0.0.1]:5060 Oct 28 13:20:02 edu-pc134 ser: 10.192.72.169 [10.192.72.169]:5060 Oct 28 13:20:02 edu-pc134 ser: Aliases: edu-pc134.tcom.eivd.ch:5060 edu-pc134:5060 localhost.localdomain:5060 localhost:5060 Oct 28 13:20:02 edu-pc134 ser: ser startup succeeded Oct 28 13:20:02 edu-pc134 ser: ser shutdown failed Oct 28 13:20:02 edu-pc134 /usr/sbin/ser[2059]: mod_init(): Database connection opened successfuly Oct 28 13:20:02 edu-pc134 /usr/sbin/ser[2059]: INFO: udp_init: SO_RCVBUF is initially 65535 Oct 28 13:20:02 edu-pc134 /usr/sbin/ser[2059]: INFO: udp_init: SO_RCVBUF is finally 131070 Oct 28 13:20:02 edu-pc134 /usr/sbin/ser[2059]: INFO: udp_init: SO_RCVBUF is initially 65535 Oct 28 13:20:02 edu-pc134 /usr/sbin/ser[2059]: INFO: udp_init: SO_RCVBUF is finally 131070 Oct 28 13:20:02 edu-pc134 ser: Listening on Oct 28 13:20:02 edu-pc134 ser: 127.0.0.1 [127.0.0.1]:5060 Oct 28 13:20:02 edu-pc134 ser: 10.192.72.169 [10.192.72.169]:5060 Oct 28 13:20:02 edu-pc134 ser: Aliases: edu-pc134.tcom.eivd.ch:5060 edu-pc134:5060 localhost.localdomain:5060 localhost:5060 Oct 28 13:20:02 edu-pc134 ser: Listening on Oct 28 13:20:02 edu-pc134 ser: 127.0.0.1 [127.0.0.1]:5060 Oct 28 13:20:02 edu-pc134 ser: 10.192.72.169 [10.192.72.169]:5060 Oct 28 13:20:02 edu-pc134 ser: Aliases: edu-pc134.tcom.eivd.ch:5060 edu-pc134:5060 localhost.localdomain:5060 localhost:5060 Oct 28 13:20:02 edu-pc134 ser: Listening on Oct 28 13:20:02 edu-pc134 ser: 127.0.0.1 [127.0.0.1]:5060 Oct 28 13:20:02 edu-pc134 ser: 10.192.72.169 [10.192.72.169]:5060 Oct 28 13:20:02 edu-pc134 ser: Aliases: edu-pc134.tcom.eivd.ch:5060 edu-pc134:5060 localhost.localdomain:5060 localhost:5060 Oct 28 13:20:02 edu-pc134 ser: ser startup succeeded

4 5

Re: [Serusers] some trouble with ser 0.8.11 / 0.8.11pre29
by Daniel-Constantin Mierla 30 Oct '03

30 Oct '03

Hello, as Jiri suggested in another mail, if you haven't done it yet, is better to get the latest stable branch (rel_0_8_11) from CVS (see http://www.iptel.org/ser/cvs/) which is forked from v0.8.11 and has some updates and fixes. }Daniel On 10/30/2003 1:33 PM, schweizer laurent wrote: >Because ser 0.8.11 with redhat 9 is not always correctly started. >see http://lists.iptel.org/pipermail/serusers/2003-October/003352.html > >-----Original Message----- >From: Daniel-Constantin Mierla >[mailto:Daniel-Constantin.Mierla@fokus.fraunhofer.de] >Sent: jeudi, 30. octobre 2003 13:21 >To: schweizer laurent >Cc: serusers(a)lists.iptel.org >Subject: Re: [Serusers] some trouble with ser 0.8.11 / 0.8.11pre29 > > >Hello, >why do you need v0.8.11pre29? That version is an older prerelease and >there were some fixes for RH9.0 which are now included in v0.8.11. > >}Daniel > >On 10/30/2003 1:07 PM, schweizer laurent wrote: > > > >>Hello, >> >>I have some trouble with ser. >>First I have installed the 0.8.11 but I see that this version with red hat >> >> >9 > > >>is not always started correctly. >> >>Then I have installed the version 0.8.11pre29, this version start correctly >>but I see that after a few hours the server does not send any responses. >> >>Laurent >> >> >>_______________________________________________ >>Serusers mailing list >>serusers(a)lists.iptel.org >>http://lists.iptel.org/mailman/listinfo/serusers >> >> >> >> >> > > > > > >

1 0

[Serusers] some trouble with ser 0.8.11 / 0.8.11pre29
by schweizer laurent 30 Oct '03

30 Oct '03

Hello, I have some trouble with ser. First I have installed the 0.8.11 but I see that this version with red hat 9 is not always started correctly. Then I have installed the version 0.8.11pre29, this version start correctly but I see that after a few hours the server does not send any responses. Laurent

3 2

[Serusers] accounting
by Teppo Lunnas 30 Oct '03

30 Oct '03

Hello, Does anybody know how to get the serweb's accounting feature to work. I'm using Messenger 4.7 clients with SER 0.8.11 but in serweb's accounting tab there is only message "no calls" and the acc table in ser database is empty. So how to get the SER to make CDRs of the calls to the database? By the way I found that in serwebs config.php and accounting.php files the name of the acc table was false (=table_accounting).

2 1

[Serusers] Ser and Voicemail
by Alessio Focardi 30 Oct '03

30 Oct '03

Hi everyone ! First time here, SER newbie seeking for some help. We have a working SER installation that we would like to integrate with SER voicemail. What we would like to obtain is the possibility for someone calling an offline user to leave him a message. The message the should be notified to the destination user, dunno how by now ... First question is: can SER and SEMS coexist on the same server ? how can we archieve this "call redirection" ? Thank to everyone willing to help. -- Best regards, Alessio mailto:alessiof@interconnessioni.it

2 1

[Serusers] DNS client application
by Iizuka, Hirotaka, VF-JP 30 Oct '03

30 Oct '03

Hello, Does SER equip DNS client functionality? I want to know if SER needs DNS client soft to query DNS. Hiro

2 1

RE: [Serusers] Messenger5.0 481 Error continued
by Jiri Kuthan 30 Oct '03

30 Oct '03

I'm afraid I am then not aware of any way how to make Messenger work the way it should (except asking the vendor to fix it). given that interoperability in 5.0 is very questionable, and there are apparently some 5.0-to-5.0 issues [*], downgrading to 4.x may be a safer choice. (I'm serious.) -jiri [*] I have no slightest idea why the responding UA both agrees to have a session with 200 and terminates it with BYE. Did you apply the settings mentioned bellow on the recepient's side? Have you tried to turn modparam("rr", "enable_full_lr", ... on and off? (someone told me that 4.x love full_lr whereas 5.x hate it). If that does not help either, could you try turning record routing off (commenting the line with record_route() in SER config)? That's all just silly ideas how to make Messenger happy, the principal place to fix or replace with something else is Messenger. At 02:08 AM 10/30/2003, Rork, Joseph (J.P.) wrote: >There is no 4.7 involved. The problem exists on strickly a 5.0 to 5.0 basis. > >-----Original Message----- >From: Jiri Kuthan [mailto:jiri@iptel.org] >Sent: Wednesday, October 29, 2003 7:36 PM >To: Rork, Joseph (J.P.); 'serusers(a)lists.iptel.org' >Subject: Re: [Serusers] Messenger5.0 481 Error continued > > >That's a one-way trick to make 5.0 accept 4.7's instant messages. There is no way to make 4.7 or other standard-based implementation understand 5.0's proprietary messaing model (sending INVITEs to establish a messaging session). > >-jiri > >At 04:05 PM 10/28/2003, Rork, Joseph (J.P.) wrote: > >>I've followed the instructions: >>Attention: instant messaging model has changed from 4.7 to 5.0 dramatically and in a non-standard way. 5.0 takes session establishement using INVITE and drops out-of-dialog MESSAGEs on the floor, whereas sending "481 Call Leg/Transaction...". To permit them, apply the following registry setting: HighSecurityMode HKLM\Software\Policies\Microsoft\Messenger\Client\{83D4679F-B6D7-11D2-BF36-0 0C04FB90A03}\_Default\EnableSIPHighSecurityMode DWORD= 0 -- Low Security 1 -- High Security 2(Default, same as not set) --- Medium security You need set it to 0 in order to make peer-to-peer IM. Since WM4.7 client is not registered in the LCS server, I guess that WM5 treats it as peer-to-peer call. >> >>And I'm still getting the following error: >><<messenger5dump>> >> >>Any ideas? >> >>--joe >> >>_______________________________________________ >>Serusers mailing list >>serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers > >-- >Jiri Kuthan http://iptel.org/~jiri/ -- Jiri Kuthan http://iptel.org/~jiri/

2 1

RE: [Serusers] DNS client application
by Iizuka, Hirotaka, VF-JP 30 Oct '03

30 Oct '03

I'm sorry but how do you mean by that? -----Original Message----- From: Jiri Kuthan [mailto:jiri@iptel.org] Sent: Thursday, October 30, 2003 2:25 PM To: Iizuka, Hirotaka, VF-JP; serusers(a)lists.iptel.org Subject: Re: [Serusers] DNS client application ser does support DNS. At 06:17 AM 10/30/2003, Iizuka, Hirotaka, VF-JP wrote: >Content-Class: urn:content-classes:message >Content-Type: multipart/alternative; > boundary="----_=_NextPart_001_01C39EA5.251C914C" > >Hello, > >Does SER equip DNS client functionality? I want to know if SER needs >DNS client soft to query DNS. > >Hiro >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

1 0

Re: [Serusers] DNS client application
by Jiri Kuthan 30 Oct '03

30 Oct '03

ser does support DNS. At 06:17 AM 10/30/2003, Iizuka, Hirotaka, VF-JP wrote: >Content-Class: urn:content-classes:message >Content-Type: multipart/alternative; > boundary="----_=_NextPart_001_01C39EA5.251C914C" > >Hello, > >Does SER equip DNS client functionality? I want to know if SER needs DNS client soft to query DNS. > >Hiro >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

1 0

Re: [Serusers] SER does not start with MySQL
by Jiri Kuthan 30 Oct '03

30 Oct '03

I suppose ser would not start without mysql either. The reason is presumably serctl's way to find SER executable. It tries to use the same directory for SER as where serctl lives, certainly a problem with compiled versions and possibly a problem in some distributions. Where is your 'ser' and 'serctl' installed? Which distribution are you using? Workaround is change the DIR=... lines in serctl to path to ser. I introduced (hopefuly) more helpful error output to serctl. Thanks for reporting, -jiri At 03:20 AM 10/30/2003, Vo, Tony wrote: >content-class: urn:content-classes:message >Content-Type: multipart/alternative; > boundary="----_=_NextPart_001_01C39E8C.7267B729" > >Hi, >SER will not start if I am to configure SER to run using MySQL module. I followed the instructions in the HowTo guides. I currently have MySQL version 4.0.16 installed and is running. The mysql.so module is in the correct directory as specified in the config file. When I run the 'serctl start' script, I would get only this response; > >[root@localhost modules]# serctl start > >Starting SER : cat: /var/run/ser.pid: No such file or directory >started pid() > >Here's an excerpt from my config file (ser.cfg). Thanks for your advice(s); > ># ># ># $Id: ser.cfg,v 1.21.2.1 2003/07/30 16:46:18 andrei 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 >debug=7 >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=4 >fifo="/tmp/ser_fifo" > ># ------------------ module loading ---------------------------------- > ># Uncomment this if you want to use SQL database >loadmodule "/usr/lib/ser/modules/mysql.so" > >loadmodule "/usr/lib/ser/modules/sl.so" >loadmodule "/usr/lib/ser/modules/tm.so" >loadmodule "/usr/lib/ser/modules/rr.so" >loadmodule "/usr/lib/ser/modules/maxfwd.so" >loadmodule "/usr/lib/ser/modules/usrloc.so" >loadmodule "/usr/lib/ser/modules/registrar.so" > ># Uncomment this if you want digest authentication ># mysql.so must be loaded ! >loadmodule "/usr/lib/ser/modules/auth.so" >loadmodule "/usr/lib/ser/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) >modparam("usrloc", "db_url", "sql://ser:spirent@localhost/ser") > ># -- auth params -- ># Uncomment if you are using auth module ># >modparam("auth_db", "calculate_ha1", 1) ># ># If you set "calculate_ha1" parameter to yes (which true in this config), ># uncomment also the following parameter) ># >modparam("auth_db", "password_column", "password") > >#database location for auth module >modparam("auth_db", "db_url", "sql://serro:spirent@localhost/ser") > ># -- rr params -- ># add value to ;lr param to make some broken UAs happy ># modparam("rr", "enable_full_lr", 1) > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

1 0

[Serusers] SER does not start with MySQL
by Vo, Tony 30 Oct '03

30 Oct '03

Hi, SER will not start if I am to configure SER to run using MySQL module. I followed the instructions in the HowTo guides. I currently have MySQL version 4.0.16 installed and is running. The mysql.so module is in the correct directory as specified in the config file. When I run the 'serctl start' script, I would get only this response; [root@localhost modules]# serctl start Starting SER : cat: /var/run/ser.pid: No such file or directory started pid() Here's an excerpt from my config file (ser.cfg). Thanks for your advice(s); # # # $Id: ser.cfg,v 1.21.2.1 2003/07/30 16:46:18 andrei 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 debug=7 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=4 fifo="/tmp/ser_fifo" # ------------------ module loading ---------------------------------- # Uncomment this if you want to use SQL database loadmodule "/usr/lib/ser/modules/mysql.so" loadmodule "/usr/lib/ser/modules/sl.so" loadmodule "/usr/lib/ser/modules/tm.so" loadmodule "/usr/lib/ser/modules/rr.so" loadmodule "/usr/lib/ser/modules/maxfwd.so" loadmodule "/usr/lib/ser/modules/usrloc.so" loadmodule "/usr/lib/ser/modules/registrar.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! loadmodule "/usr/lib/ser/modules/auth.so" loadmodule "/usr/lib/ser/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) modparam("usrloc", "db_url", "sql://ser:spirent@localhost/ser") # -- auth params -- # Uncomment if you are using auth module # modparam("auth_db", "calculate_ha1", 1) # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) # modparam("auth_db", "password_column", "password") #database location for auth module modparam("auth_db", "db_url", "sql://serro:spirent@localhost/ser") # -- rr params -- # add value to ;lr param to make some broken UAs happy # modparam("rr", "enable_full_lr", 1)

1 0

RE: [Serusers] Messenger5.0 481 Error continued
by Rork, Joseph (J.P.) 30 Oct '03

30 Oct '03

There is no 4.7 involved. The problem exists on strickly a 5.0 to 5.0 basis. -----Original Message----- From: Jiri Kuthan [mailto:jiri@iptel.org] Sent: Wednesday, October 29, 2003 7:36 PM To: Rork, Joseph (J.P.); 'serusers(a)lists.iptel.org' Subject: Re: [Serusers] Messenger5.0 481 Error continued That's a one-way trick to make 5.0 accept 4.7's instant messages. There is no way to make 4.7 or other standard-based implementation understand 5.0's proprietary messaing model (sending INVITEs to establish a messaging session). -jiri At 04:05 PM 10/28/2003, Rork, Joseph (J.P.) wrote: >I've followed the instructions: >Attention: instant messaging model has changed from 4.7 to 5.0 dramatically and in a non-standard way. 5.0 takes session establishement using INVITE and drops out-of-dialog MESSAGEs on the floor, whereas sending "481 Call Leg/Transaction...". To permit them, apply the following registry setting: HighSecurityMode HKLM\Software\Policies\Microsoft\Messenger\Client\{83D4679F-B6D7-11D2-BF36-0 0C04FB90A03}\_Default\EnableSIPHighSecurityMode DWORD= 0 -- Low Security 1 -- High Security 2(Default, same as not set) --- Medium security You need set it to 0 in order to make peer-to-peer IM. Since WM4.7 client is not registered in the LCS server, I guess that WM5 treats it as peer-to-peer call. > >And I'm still getting the following error: ><<messenger5dump>> > >Any ideas? > >--joe > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

1 0

Re: [Serusers] Messenger5.0 481 Error continued
by Jiri Kuthan 30 Oct '03

30 Oct '03

That's a one-way trick to make 5.0 accept 4.7's instant messages. There is no way to make 4.7 or other standard-based implementation understand 5.0's proprietary messaing model (sending INVITEs to establish a messaging session). -jiri At 04:05 PM 10/28/2003, Rork, Joseph (J.P.) wrote: >I've followed the instructions: >Attention: instant messaging model has changed from 4.7 to 5.0 dramatically and in a non-standard way. 5.0 takes session establishement using INVITE and drops out-of-dialog MESSAGEs on the floor, whereas sending "481 Call Leg/Transaction...". To permit them, apply the following registry setting: HighSecurityMode HKLM\Software\Policies\Microsoft\Messenger\Client\{83D4679F-B6D7-11D2-BF36-0 0C04FB90A03}\_Default\EnableSIPHighSecurityMode DWORD= 0 -- Low Security 1 -- High Security 2(Default, same as not set) --- Medium security You need set it to 0 in order to make peer-to-peer IM. Since WM4.7 client is not registered in the LCS server, I guess that WM5 treats it as peer-to-peer call. > >And I'm still getting the following error: ><<messenger5dump>> > >Any ideas? > >--joe > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

1 0

[Serusers] Please.... suggestion about SER
by Ivan Dario Salazar 29 Oct '03

29 Oct '03

HI, my name is Ivan Dario First of all, congratulations for iptel.org , I'm a student and i'm really interested about SER and what i can do with it. I was reading SER description when a friend of mine told me about JTAPI, a java telephony API I would be gratefuled if you explain me if this is for telephony ip and how is SER relationed with it I'm also worried about wath kind of development can i do Being based on SER, and one last thing I only have a computer with 16MB on ram, 2GB on Hard Disk and pentium 120 MHZ, what could i do in order to install SER on it, i mean what version and all that.. Please.. any be your answer, send me a mail Thanks a lot IVAN DARIO _________________________________________________________ http://www.latinmail.com. Gratuito, latino y en espa�ol.

2 1

[Serusers] cisco phone domain
by Daniel Medina 29 Oct '03

29 Oct '03

Hi, We've just installed ser we've noticed that when placing a call from a Cisco IP phone the "From:" is set to "username(a)serserver.domain.com" rather than the expected "username(a)domain.com". Other SIP clients (we've tested with MS Messenger) don't exhibit this problem. At first we thought ser was re-writing this, but ngrep revealed that to not be the case (the phone was actually sending this information). Inserting "rewritehost("domain.com")" into the config didn't seem to alter this any. The phone is configured with the hostname serserver.domain.com as the SIP server. Any idea why this is happening? (Apologies for the skimpiness of the details; I can follow up with config information, models, etc, but I was hoping someone had seen this before and had an idea). -- Dan

2 3

Re: [Serusers] SIP and NAT Traversal | How To
by Jiri Kuthan 29 Oct '03

29 Oct '03

I think there is a more appealing case, which is getting clients of a public SIP service behind any NATs. an internal SER version does exactly that along with rtpproxy -- feel free to try it out with our public SIP service. It will certainly show up in stable release some day. -jiri At 03:12 PM 10/29/2003, dhiraj.2.bhuyan(a)bt.com wrote: >Hello List, > >SIP and NAT - this issue has been raised on numerous occassions. I finally got a small working demo for SIP Instant Messaging through a NAT gateway (next on the list is to try it with some RTP traffic). I am using "siproxd" http://sourceforge.net/projects/siproxd on the NAT gateway. Siproxd is an proxy/masquerading daemon for the SIP protocol. It allows SIP clients to work behind an IP masquerading firewall or router. > >Demo setup - > >[UA1] <------> [siproxd/NAT Gateway]<------->[SER]<------->[UA2] > >where UA1 is behind a NAT gateway, siproxd is running on the NAT gateway and UA2 is on the public side. Both UA1 and UA2 uses SER as the registration server in this demo (siproxd is also capable of working as a registration server). UA1 is configured to use siproxd as its outgoing proxy. All SIP packets going through siproxd are re-written to address the NAT traversal issues (so the SIP packets appear to be coming from the NAT gateway). I used Siemens SIP client for this demo. > >siproxd is also capable of proxying RTP traffic - although I am yet to test this feature. > >Many of us are looking for "siproxd" like utility that addressed the NAT traversal problems. And I think it will be a great idea to add such a capability to SER. In the meantime, it will be great if more people tests and contributes to siproxd. > >Thoughts anyone? > >Dhiraj Bhuyan >Security Research Engineer >BT Exact > >Tel: +44 1473 643932 >Mob: +44 7962 012145 >Email: dhiraj.2.bhuyan(a)bt.com > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

1 0

[Serusers] Nathelper & rtpproxy
by Glenn Dalgliesh 29 Oct '03

29 Oct '03

I am seeing 2 problems with nathelper and rtpproxy. One I have seen mentioned on the list but no solution or explainations that I can find. 1. I am seeing the following in my messages file Oct 29 11:01:34 serv1 ser[9229]: ERROR: extract_mediaip: no `c=' in SDP Oct 29 11:01:35 serv1 ser[9229]: ERROR: extract_mediaip: no `c=' in SDP Oct 29 11:01:36 serv1 ser[9227]: ERROR: extract_mediaip: no `c=' in SDP 2. In some situations the BYE messages don't hangup the call I am using yesterday unstable CVS tree. Client I am using in the test lab are Budgetone and x-lite softphones and hear is my ser.cfg Thanks # # $Id: ser.cfg,v 1.21 2003/06/04 13:47:36 jiri Exp $ # # simple quick-start config script # # ----------- global configuration parameters ------------------------ /* Uncomment these lines to enter debugging mode debug=3 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=no # (cmd line: -E) */ # /* Uncomment these lines to enter debugging mode debug=10 fork=yes log_stderror=no # */ check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) port=5060 children=4 fifo="/tmp/ser_fifo" alias=mydomain.dyndns.org # ------------------ module loading ---------------------------------- # Uncomment this if you want to use SQL database #loadmodule "/usr/local/lib/ser/modules/mysql.so" loadmodule "/usr/local/lib/ser/modules/nathelper.so" loadmodule "/usr/local/lib/ser/modules/textops.so" loadmodule "/usr/local/lib/ser/modules/sl.so" loadmodule "/usr/local/lib/ser/modules/tm.so" loadmodule "/usr/local/lib/ser/modules/rr.so" loadmodule "/usr/local/lib/ser/modules/maxfwd.so" loadmodule "/usr/local/lib/ser/modules/usrloc.so" loadmodule "/usr/local/lib/ser/modules/registrar.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! #loadmodule "/usr/local/lib/ser/modules/auth.so" #loadmodule "/usr/local/lib/ser/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"); break; }; if (msg:len >= max_len ) { sl_send_reply("513", "Message too big"); break; }; # 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 record_route(); # loose-route processing if (loose_route()) { t_relay(); break; }; # 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") { force_rport(); fix_nated_contact(); save("location"); # Uncomment this if you want to use digest authentication # if (!www_authorize("iptel.org", "subscriber")) { # www_challenge("iptel.org", "0"); # break; # }; save("location"); break; }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); break; }; }; #inserted by klaus if (method=="INVITE") { record_route(); force_rtp_proxy(); /* set up reply processing */ t_on_reply("1"); }; # forward to current uri now; use stateful forwarding; that # works reliably even if we forward from TCP to UDP if (!t_relay()) { sl_reply_error(); }; } #inserted by klaus # all incoming replies for t_onrepli-ed transactions enter here onreply_route[1] { if (status=~"2[0-9][0-9]") force_rtp_proxy(); }

2 1

[Serusers] reuse of existing tcp connection
by Juha Heinanen 29 Oct '03

29 Oct '03

i'm behind gprs service that doesn't allow any incoming udp packets or establishment of inbound tcp connections. when i register, a tcp connection is established between my sip ua and ser. if there is an existing tcp connection open between sip ua and ser, is ser supposed to reuse it for all incoming sip traffic, such as subscribes and notifies? -- juha

6 23

[Serusers] SIP and NAT Traversal | How To
by dhiraj.2.bhuyan＠bt.com 29 Oct '03

29 Oct '03

Hello List, SIP and NAT - this issue has been raised on numerous occassions. I finally got a small working demo for SIP Instant Messaging through a NAT gateway (next on the list is to try it with some RTP traffic). I am using "siproxd" http://sourceforge.net/projects/siproxd on the NAT gateway. Siproxd is an proxy/masquerading daemon for the SIP protocol. It allows SIP clients to work behind an IP masquerading firewall or router. Demo setup - [UA1] <------> [siproxd/NAT Gateway]<------->[SER]<------->[UA2] where UA1 is behind a NAT gateway, siproxd is running on the NAT gateway and UA2 is on the public side. Both UA1 and UA2 uses SER as the registration server in this demo (siproxd is also capable of working as a registration server). UA1 is configured to use siproxd as its outgoing proxy. All SIP packets going through siproxd are re-written to address the NAT traversal issues (so the SIP packets appear to be coming from the NAT gateway). I used Siemens SIP client for this demo. siproxd is also capable of proxying RTP traffic - although I am yet to test this feature. Many of us are looking for "siproxd" like utility that addressed the NAT traversal problems. And I think it will be a great idea to add such a capability to SER. In the meantime, it will be great if more people tests and contributes to siproxd. Thoughts anyone? Dhiraj Bhuyan Security Research Engineer BT Exact Tel: +44 1473 643932 Mob: +44 7962 012145 Email: dhiraj.2.bhuyan(a)bt.com

1 0

[Serusers] RTP Proxy and SER
by Stephen Miles 29 Oct '03

29 Oct '03

Hi all, I'm new to the list so sorry if this question has already been answered. I have has a search through all the posts and all the info at iptel.org but alas am still having a problem with my ser. What I am trying to do is set ser up as an off net solution for our current VOIP/SIP systems. I have most of it nailed and have thus far found ser very easy to work with the help great. I have now hit a bit of a road block. I am trying to get the rtpproxy working with ser so that ALL rtp streams go through the ser proxy and not from the off net phone directly to the called phone. I have the rtpproxy and it runs fine (so far as I can tell) but when trying to get ser to use it I keep getting an error in the logs about loadmodule and unknown module, the error is: unknown command, missing loadmodule? This is being trigered by the line in the ser.cfg file force_rtp_proxy. I used the example from the voip-info.org so am a little unsure of what I have done wrong. Is there something else I need to do? There is little documentation about rtpproxy... I am running Debian on a 2.4.21 kernel and have used the ser .deb packeges for the ser install. Any help would be great. Thanks, Stephen ----------------------------------------------------------------------------------------------- This message and any attachments contain privileged and confidential information. If you are not the intended recipient of this message, you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately via email and then destroy this message and any attachments.

3 5

Re: [Serusers] listen=0.0.0.0 with Windows Messenger
by Jiri Kuthan 28 Oct '03

28 Oct '03

listen=0.0.0.0 is not advicable -- it prints 0.0.0.0 in Via, which makes many UASs unable to respond to it. -jiri At 10:48 PM 10/28/2003, David Quenzler wrote: >SER Team, > >Working with two Windows Messenger clients that don not show as 'online' to >each other using 'listen=0.0.0.0' > >On a two node cluster, I have SER running with listen=0.0.0.0 and the mysql >module. One node has the clientIP, the other node is on warm standby. >Clients connect to a movable IP, which SER picks up as needed > >Client wants to talk to his buddy >+========================+ >Client sends a SUBSCRIBE notice to the SER server via the movable IP >A different, valid, non-movable SER server IP sends the SUBSCRIBE to the >buddy >- the header record-route notes sip:user@0.0.0.0 and Via: 0.0.0.0 > >How to ensure Windows Messenger clients show valid info re: their contact >lists? > >Thanks, > >- Dave > >BluePages: >http://bluepages.ibm.com/cgi-bin/bluepages.pl?Selection=Name&selectOn=quenz… > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

1 0

[Serusers] listen=0.0.0.0 with Windows Messenger
by David Quenzler 28 Oct '03

28 Oct '03

SER Team, Working with two Windows Messenger clients that don not show as 'online' to each other using 'listen=0.0.0.0' On a two node cluster, I have SER running with listen=0.0.0.0 and the mysql module. One node has the clientIP, the other node is on warm standby. Clients connect to a movable IP, which SER picks up as needed Client wants to talk to his buddy +========================+ Client sends a SUBSCRIBE notice to the SER server via the movable IP A different, valid, non-movable SER server IP sends the SUBSCRIBE to the buddy - the header record-route notes sip:user@0.0.0.0 and Via: 0.0.0.0 How to ensure Windows Messenger clients show valid info re: their contact lists? Thanks, - Dave BluePages: http://bluepages.ibm.com/cgi-bin/bluepages.pl?Selection=Name&selectOn=quenz…

1 0

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 October 2003