9 Nov
2003
9 Nov
'03
12:24 a.m.
Hi Kjell!
comments inline
On Sat, 08 Nov 2003 21:43:13 +0100, Kjell Mathiesen wrote
I downloaded the SIP Express Router on Nov. 6. I run
a VoIP course
(among others) and want a SIP application to show to my students and
I found yours interesting. However, I ran into an obstacle,
possibly a problem/bug. The details:
System: Red Hat 7.3 Personal on a 200 MHz Intel
'Ser' distr.: 0.8.11 RPM-package for RH 7.3
Clients using Windows Messenger
Ser.cfg: As distributed but with option <alias="matell5.no">
added
(in front of the 'check_via' option. Works fine. <km(a)matell5.no>
and others with the same domain can sign in, contact with other
clients established etc.
Then I add another domain to 'alias' as in <alias="matell5.no"
"f19-21.no">. 'ser' starts OK ('ser start' reports [OK] and
/var/log/messages says 'ser' is listening on all IP adresses and
both aliases are listed and "ser startup successful"). However,
attempted sign-in from clients (with the same domain name as earlier)
result in ICMP Destination Unreachable/Port Unreachable (port =
5060) and an attempt to stop 'ser' ('ser stop') reports [Failed] and
/var/log/messages says "ser shutdown unsuccessful".
ICMP unreachable means, that ser is not running. this may be caused by an
error in the config file or due to some other reason. watch the logging during
startup on another console, as root type:
tail -f /var/log/messages
I use the alias command just before the module loading and it works fine for
me, also with several domains, e.g:
fifo="/tmp/ser_fifo"
alias=obelix.ict.tuwien.ac.at
alias=xyz.ict.tuwien.ac.at
# ------------------ module loading ----------------------------------
I have also tried using two lines for the 'alias' parameters (<alias
"matell5.no" \n alias "f19-21.no"> with the same results.
Then I remove one 'alias' to return to the successful 'ser.cfg'
with only one 'alias', and I get the same IMCP message (Port
Unreachable).
Then I reboot the computer (no further changes to 'ser.cfg') and the
clients can sign in without a hitch.
sometimes ser does not start (reported several times on the mailinglist,
mostly at redhat systems). you can easy verify if ser is running by:
ps -A
Then you should see a lot of ser processes running.
regards,
klaus
The 'ser' Admin's Guide chapter 6.1
'Core Options' clearly indicates
that the 'alias' option can take several domain names. (It actually
says hostnames. I tried 'mytikas.matell5.no' which is name of the
machine 'ser' is running on but this caused the same erroneous
result as above. Changed it back to just the domain name and I
could sign in normally again.
If I am doing something wrong here (or not doing something I should
be doing) I would appreciate if you would tell me. I am relatively
new to Linux and Linux applications and sometimes find the
documentation difficult to understand.
If you want me to supply more information like logs etc. let me know
(if this really is a bug you probably will). I'll be happy to do
more testing/experimenting.
I am not running mysql. I'll try that next.
Thanks. (Hope I am sending this to the right place.)
Kjell Mathiesen
Matell Software AS
Fururabben 19
1361 Østerås, Norway
Tel. (+47) 6714 6509
Mob: (+47) 9073 2212
km(a)matell.no
www.matell.no
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
--