THanks for that Andrei, all sorted.
One last thing, getting a call from the PSTN to go to a soft phone
registered with ser. I have tried a few route clauses like if
method==invite lookup location etc but it doesn't seem to be working. Is
there a simple thing I am missing here?
Thanks
Stephen
Andrei Pelinescu-Onciul wrote:
> On Oct 29, 2003 at 17:55, Stephen Miles <smiles(a)callplus.co.nz> wrote:
>
>>Hi Andrei,
>>
>>I have grabbed the latest cvs version and have compiled it and seems to
>>be running ok. I now get an error 5(3681) ERROR: extract_mediaip: no
>>`c=' in SDP when I try to place a call from a soft phone on my laptop
>>through the ser proxy running on the proxy box. Any ideas?
>
>
>
> The 'c=' in SDP specifies the IP address you use for receiving media.
> It shouldn't be missing (see RFC 2327 "SDP: Session Description Protocol").
>
>
>>Also is there a way to get ser to forward/relay registers to another server?
>>We have a SIP server (broadsoft) setup and I need all the register and
>>call info, and calls to be routed from ser to the broadsoft server.
>
>
> Yes, you can do this stateless or statefull.
>
> stateless:
> forward("server", port);
>
> statefull:
> make sure the tm module is loaded:
>
> t_relay_to_udp("server", port);
>
>>Is it possible to set ser up as just a proxy where it takes the client
>>request and then proxies it to our other sip server?
>
>
> Yes, see above and set ser+nathelper box as outbound proxy for you ua.
>
> You should also record route everything, to make sure all the
> subsequent requests in the dialogs pass through your proxy (if you are
> using it for nat traversal you want this).
> For a record routing example see the default ser.cfg (on cvs sources in
> etc/ser.cfg) and copy the loose_route & record_route stuff.
>
>
> More info about configuring ser: http://www.iptel.org/ser/admin.html
> (a little bit outdated)
>
>
> Andrei
-----------------------------------------------------------------------------------------------
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.
4.6 and 4.7 are mostly ok, but 5 breaks the specification quite violently.
kphone seems quite ok today for linux.
I'm not aware of a solid IM SIP UA for Windows other than elderly Messenger
versions.
There are some conversations about building a reasonable client, but they
are still in very early stage.
-jiri
At 11:44 AM 10/28/2003, dhiraj.2.bhuyan(a)bt.com wrote:
>Hello List,
>
>Can anyone recommend some SIP Instant Messaging UA (linux and windows) that follows the specification word by word?
>I tried MSN Messenger 4.6 and 5 - both appears to have some problems (version 5 tries to send a MESSAGE with the INVITE method and gets back a BYE in response!!!!!!!!!!!!!).
>
>Thanks in advance,
>
>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/
At 07:49 PM 10/30/2003, Vo, Tony wrote:
>Workaround is change the DIR=... lines in serctl to path to ser.
>>>Tony>> I've tried this and no luck.....
well, then try something else. perhaps watching the serctl execution
could help (replace leading line #!/bin/sh with #!/bin/sh -x)
-jiri
Hi Jiri,
Please read my comments to your questions below.....
-----Original Message-----
From: Jiri Kuthan [mailto:jiri@iptel.org]
Sent: Wednesday, October 29, 2003 7:03 PM
To: Vo, Tony; serusers(a)lists.iptel.org
Subject: Re: [Serusers] SER does not start with MySQL
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?
>>Tony>> /usr/sbin
Which distribution are you using?
>>Tony>> I installed version 8.11 for RedHat 8.0 (ser-0.8.11-0.i386.rpm). SER works fine without loading mysql module. Problem only occurs when trying to load the mysql module.
Workaround is change the DIR=... lines in serctl to path to ser.
>>Tony>> I've tried this and no luck.....
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/
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'
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/
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
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
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
>>
>>
>>
>>
>>
>
>
>
>
>
>
