Hi,
try to set log_stderr=yes and fork=no and debug=3 in sems.conf for testing, it
should produce a lot of debugging output on your console when starting up.
There are a lot of possible reasons for SEMS not starting, please post the
debugging output either from the commands above or from /var/log/syslog
(under redhat the file might be another one under /var/log/ ...)
You can also check is sems runs by calling in your shell:
ps ax | grep sems
Regards,
Uli.
P.S.: Please always CC to the list, others might answer quicker than me :-)
On Wednesday 07 April 2004 14:43, Shirley wrote:
> Hi,
>
> Thank you for your reply. How to make sure that the SEMS is running?
> I uses the /usr/local/sin/sems.redhat start- to start the sems service? Am
> I correct?
> My fifo name is same in both file that you mention. Please advice! Thanks
>
> Regards,
> Shirley
>
> > -----Original Message-----
> > From: Ulrich Abend [SMTP:ullstar@iptel.org]
> > Sent: Wednesday, April 07, 2004 8:00 PM
> > To: serusers(a)lists.iptel.org
> > Cc: Shirley
> > Subject: Re: [Serusers] Sems Error
> >
> > Hi,
> >
> > you should make shure, SEMS is running and uses the same fifo name (in
> > sems.conf) as SER (in ser.cfg).
> >
> > It is also important, that the fifo file (default: /tmp/am_fifo) has
> > write
> >
> > permissions for the user SER runs as. The easiest setup is to run SER and
> > SEMS as the same user.
> >
> > If you still experience problems, please post SER and SEMS debugging
> > output,
> > the config files, and the results of
> > ls -la /tmp/*fifo
> >
> > Regards,
> >
> > Uli.
> >
> > On Wednesday 07 April 2004 12:28, Shirley wrote:
> > > Hi all,
> > >
> > > Please Help!!! I am trying to install the sems when I try to start the
> >
> > sems
> >
> > > I encountered this problem as per below. I am running on Linux 9.0 and
> > > please also advice on how to check the fifo version....Thanks
> > >
> > > Mar 24 19:04:25 sipserver2 /usr/local/sbin/ser[12876]: ERROR:
> > > voicemail: ans_machine deamon is not running !
> > > Mar 24 19:04:25 sipserver2 /usr/local/sbin/ser[12876]: ERROR:
> > > voicemail:
> >
> > No
> >
> > > such device or address
> > > Mar 24 19:04:25 sipserver2 /usr/local/sbin/ser[12876]: ERROR: vm_start:
> > > write_to_fifo failed
> > > Mar 24 19:04:35 sipserver2 /usr/local/sbin/ser[12874]: ERROR:
> > > voicemail: ans_machine deamon is not running !
> > > Mar 24 19:04:35 sipserver2 /usr/local/sbin/ser[12874]: ERROR:
> > > voicemail:
> >
> > No
> >
> > > such device or address
> > > Mar 24 19:04:35 sipserver2 /usr/local/sbin/ser[12874]: ERROR: vm_start:
> > > write_to_fifo failed
> > >
> > > regards,
> > > shirley
> > >
> > > _______________________________________________
> > > Serusers mailing list
> > > serusers(a)lists.iptel.org
> > > http://lists.iptel.org/mailman/listinfo/serusers
Hi all,
Please Help!!! I am trying to install the sems when I try to start the sems
I encountered this problem as per below. I am running on Linux 9.0 and
please also advice on how to check the fifo version....Thanks
Mar 24 19:04:25 sipserver2 /usr/local/sbin/ser[12876]: ERROR: voicemail:
ans_machine deamon is not running !
Mar 24 19:04:25 sipserver2 /usr/local/sbin/ser[12876]: ERROR: voicemail: No
such device or address
Mar 24 19:04:25 sipserver2 /usr/local/sbin/ser[12876]: ERROR: vm_start:
write_to_fifo failed
Mar 24 19:04:35 sipserver2 /usr/local/sbin/ser[12874]: ERROR: voicemail:
ans_machine deamon is not running !
Mar 24 19:04:35 sipserver2 /usr/local/sbin/ser[12874]: ERROR: voicemail: No
such device or address
Mar 24 19:04:35 sipserver2 /usr/local/sbin/ser[12874]: ERROR: vm_start:
write_to_fifo failed
regards,
shirley
Hi friends,
I would like to set up ser for voicemail diverting only for some users
I know that "is_user_in" can be used to check for CALLER group
membership, how can I check if the DESTINATION user belongs to a
specific group?
tnx for any help !
--
Best regards,
Alessio mailto:afoc@interconnessioni.it
Is there any way for the proxy to reroute based on the 3xx response vs.
passing the 3xx response back to the originating GW? Can this be done via
the scripting or through a module? Is there any way for a module to trap a
response without sending it back to the originating GW?
Thanks
Mike
Hi,
I have dovnloaded and compiled the latest sources from the CVS. I use
digest authentication with mysql database. When I tried to start ser I
received the following error in the log:
0(0) auth_db module - initializing
0(0) find_mod_export: <db_use_table> in module sql not found
0(0) auth_db:mod_init(): Unable to bind database module
0(0) init_mod(): Error while initializing module auth_db
ERROR: error while initializing modules
mysql module was successfuly loaded before. It seems the problem is,
that auth_db looks up the function db_use_table in sql module and not in
mysql. The previous version of ser worked successfully with the same cfg
file.
Regards
Martin
Hi,
Following the radius howto i downloaded freeradius
which compiled ok and also radius client which compiled
ok too.
Compiling ser from sources produces the following at during
'make install'
module modules/acc/acc.so not compiled
auth_radius.so not compiled
group_radius.so not compiled
uri_radius.so not compiled
The main makefile and the makefile in modules/acc
have been modified as instructed.
Anyone got any idea where things could have gone wrong ?
This is a completely new installation (if it matters).
Regards,
Lambros
Running SER 0.8.12 on Solaris 8 -SPARC with MySQL installed.
The issue that I'm running into is that when the originating GW receives a
response and generates an ACK the SER doesn't seem to stop the timer for
resending the message. If you look in the log, you can see where the server
receives it, but the server resends the same response as if the ACK was
ignored. It the attached case a 503 response is sent back, but the same
situation occurs when other responses are sent.
Thanks, Mike
I am running into a problem where SER does not recognize a ua trying to
ACK a INVITE 200 OK response. It seems to be the result of pairing of
certain SIP ua Mfg. Not all UA's exhibit the problem.
1. Destination UA sends 200 OK to ser
2. SER forwards to origin UA
3. Origin ua sends ACK to SER
4. SER declares "sl_filter_ACK: to late to be a local ACK!"
5. destination UA resends 200 OK and does not open talk path, origin
device believes call is connected
The ACK seems to arrive just at the right time so I am not sure what the
"to late" debug means.
Greetings from the Interop+Networld SIP ilabs hotstage in Santa Clara
California. http://www.interop.com/lasvegas2004/interopnet/
- Dustin -
Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: SIP Request:
Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: method: <ACK>
Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: uri:
<sip:4991@45.210.3.91:5060>
Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: version: <SIP/2.0>
Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: parse_headers: flags=1
Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: Found param type 232,
<branch> = <z9hG4bK8872b9128>; state=16
Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: end of header reached,
state=5
Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: parse_headers: Via found,
flags=1
Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: parse_headers: this is
the first via
Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: After parse_msg...
Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: DEBUG : sl_filter_ACK: to
late to be a local ACK!
Origin UA 45.210.9.83
SER 45.210.9.21
Dest UA 45.210.3.91
No. Time Source Destination
Protocol Info
33 15.496582 45.210.9.83 45.210.9.21 SIP/SDP Request: INVITE
sip:4991@45.210.9.21:5060, with session description
34 15.513769 45.210.9.21 45.210.9.83 SIP Status: 100 trying
-- your call is important to us
35 15.515818 45.210.9.21 45.210.3.91 SIP/SDP Request: INVITE
sip:4991@45.210.3.91:5060, with session description
36 15.850049 45.210.9.21 45.210.3.91 SIP/SDP Request: INVITE
sip:4991@45.210.3.91:5060, with session description
37 16.108079 45.210.3.91 45.210.9.21 SIP Status: 100 Trying
38 16.108576 45.210.3.91 45.210.9.21 SIP Status: 180 Ringing
41 16.140632 45.210.9.21 45.210.9.83 SIP Status: 180 Ringing
48 19.346818 45.210.3.91 45.210.9.21 SIP/SDP Status: 200 OK,
with session description
49 19.355727 45.210.9.21 45.210.9.83 SIP/SDP Status: 200 OK,
with session description
50 19.377798 45.210.9.83 45.210.9.21 SIP Request: ACK
sip:4991@45.210.3.91:5060
51 19.843133 45.210.3.91 45.210.9.21 SIP/SDP Status: 200 OK,
with session description
52 19.855180 45.210.9.21 45.210.9.83 SIP/SDP Status: 200 OK,
with session description
53 19.867245 45.210.9.83 45.210.9.21 SIP Request: ACK
sip:4991@45.210.3.91:5060
56 20.844637 45.210.3.91 45.210.9.21 SIP/SDP Status: 200 OK,
with session description
57 20.855263 45.210.9.21 45.210.9.83 SIP/SDP Status: 200 OK,
with session description
58 20.867249 45.210.9.83 45.210.9.21 SIP Request: ACK
sip:4991@45.210.3.91:5060
63 22.843774 45.210.3.91 45.210.9.21 SIP/SDP Status: 200 OK,
with session description
64 22.855381 45.210.9.21 45.210.9.83 SIP/SDP Status: 200 OK,
with session description
69 25.012302 45.210.3.91 45.210.9.21 SIP Request: BYE
sip:4991@45.210.9.21:5060;ftag=1B1B70-179F;lr=on
70 25.026340 45.210.9.21 45.210.9.83 SIP Request: BYE
sip:45.210.9.83:5060
71 25.057274 45.210.9.83 45.210.9.21 SIP Status: 200 OK
72 25.067464 45.210.9.21 45.210.3.91 SIP Status: 200 OK
You're right; it seems that the site is down
Ralph
-----Original Message-----
From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On
Behalf Of Atle Samuelsen
Sent: Dienstag, 6. April 2004 16:04
To: serusers(a)lists.iptel.org
Subject: [Serusers] www.iptel.org
Uhm. Is it just me or is the iptel website not working now?
- Atle
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers