[Serusers] Sems Error

Thu Apr 8 16:23:04 CEST 2004

Hi,

ok, you replaced the IP addresses ;-) Don't mind I wont post them...

You have the following setup, right?

SIP-UA(192...) -- NAT-FW -- SER (official IP)

You probably have a NAT problem here. The audio packets from SEMS are probably 
not forwarded through your NAT firewall.

Please check if you have audio packets inside your 192..-network by running a 
sniffer like tcpdump or ngrep on port 8000 (or whatever audio port your SIP 
UA chooses).

How do you traverse the NAT? Has your phone STUN support enabled (seems so)? 
What type of NAT-Firewall do you have (Linux, Router, ...)?

Please describe your setup in detail if you experience NAT problems, some 
really skilled people on this list will help you out (but probably not 
me ;-)!

Uli.

On Thursday 08 April 2004 16:02, Shirley wrote:
> Hi,
>
> Please take a look again.:)
>  <<logNoAudio.txt>>
> regards,
> shirley
>
> > -----Original Message-----
> > From:	Ulrich Abend [SMTP:ullstar at iptel.org]
> > Sent:	Thursday, April 08, 2004 10:02 PM
> > To:	Shirley
> > Cc:	serusers at lists.iptel.org
> > Subject:	Re: [Serusers] Sems Error
> >
> > Please review the settings in your IP phone, the address settings in the
> > SIP
> > messages look a bit strange to me (IP, dest_IP...)
> >
> > What are the IP addresses of you SIP phone and your server running
> > ser&sems?
> >
> > Regards,
> >
> > Uli.
> >
> > On Thursday 08 April 2004 15:46, Shirley wrote:
> > > Hi,
> > >
> > > Thank you for your reply. Now sems is running now...Thank you so much.
> > >
> > > When I try to do test call. It show "connected" on my UA but I hear no
> > > audio and the session ended. Please advice. Thanks again.
> > >  <<logNoAudio.txt>>
> > > Regards,
> > > Shirley
> > >
> > > > -----Original Message-----
> > > > From:	Ulrich Abend [SMTP:ullstar at iptel.org]
> > > > Sent:	Thursday, April 08, 2004 4:15 PM
> > > > To:	serusers at lists.iptel.org
> > > > Cc:	Shirley
> > > > Subject:	Re: [Serusers] Sems Error
> > > >
> > > > Hi,
> > > >
> > > > from your debugging:
> > > >
> > > > Apr  8 11:53:41 sipserver2 sems: (7785) DEBUG: loadAppPlugIn
> > > > (AmPlugIn.cpp:262): application 'number_reader' loaded.
> > > > Apr  8 11:53:41 sipserver2 sems: (7785) WARNING: reloadModuleConfig
> > > > (SemsConfiguration.cpp:66): no configuration found for module
> > > > number_reader,
> > > > maybe you want to specify config.number_reader in config file.
> > > > Apr  8 11:53:41 sipserver2 sems: (7785) ERROR: onLoad
> > > > (NumberReader.cpp:55):
> > > > required parameter number_path missing
> > > > Apr  8 11:53:41 sipserver2 sems: (7785) ERROR: load
> > > > (AmPlugIn.cpp:85): while
> > > > loading plug-in '/usr/local/lib/sems/plug-in/apps/number_reader.so'
> > > >
> > > > This says that number reader refuses to start and therefor SEMS
> >
> > refuses
> >
> > > > to
> > > >
> > > > start at all. You have two options now:
> > > >
> > > > 1. configure number_reader to start by supplying valid entries in the
> > > > following new section of your sems.conf (edit wav to your valid
> >
> > path!):
> > > > config.number_reader=inline
> > > > number_path=wav
> > > > prolog_file=wav/prolog.wav
> > > > epilog_file=wav/prolog.wav
> > > > config.number_reader=end
> > > >
> > > > 2. remove '/usr/local/lib/sems/plug-in/apps/number_reader.so', then
> >
> > sems
> >
> > > > should start. Be careful, if you do a "make install" again, the
> > > > module will
> > > > be regenerated, you might have to delete it again.
> > > >
> > > >
> > > > I call this a bug in SEMS, we will fix it someday. Modules should
> >
> > start
> >
> > > > without any configuration entries. By now, please use one of the
> >
> > options
> >
> > > > above.
> > > >
> > > > > I have also tested this ps ax | grep sems. I get this result:~
> > > > > [root at sipserver2 root]# ps ax | grep sems
> > > > >  5518 ?        S      1:25 gedit file:///etc/sems/sems.conf
> > > > >  7805 pts/0    S      0:00 grep sems
> > > >
> > > > This shows, that no SEMS is running, from all processes containing
> >
> > "sems"
> >
> > > > in
> > > > their command line, it's only your editor and the grep command
> > > > itself.
> > > >
> > > > Please always view the output of SEMS startup and review all lines
> > > > starting
> > > > with ERROR.
> > > >
> > > > Regards,
> > > >
> > > > Uli.
> > > >
> > > > On Thursday 08 April 2004 06:05, Shirley wrote:
> > > > > Hi,
> > > > >
> > > > > Thank you for your prompt reply.
> > > > > I have  tested :~ set log_stderr=yes and fork=no and debug=3 in
> > > >
> > > > sems.conf.
> > > >
> > > > > I have attached the log. Please help.
> > > > >
> > > > >  <<SemsError1.txt>>  <<sems.conf>>
> > > > > I have also tested this ps ax | grep sems. I get this result:~
> > > > > [root at sipserver2 root]# ps ax | grep sems
> > > > >  5518 ?        S      1:25 gedit file:///etc/sems/sems.conf
> > > > >  7805 pts/0    S      0:00 grep sems
> > > > >
> > > > > Regards,
> > > > > Shirley
> > > > >
> > > > > > -----Original Message-----
> > > > > > From:	Ulrich Abend [SMTP:ullstar at iptel.org
> > > > > > Sent:	Thursday, April 08, 2004 12:18 AM
> > > > > > To:	Shirley
> > > > > > Cc:	serusers at lists.iptel.org
> > > > > > Subject:	Re: [Serusers] Sems Error
> > > > > >
> > > > > > 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 at iptel.org]
> > > > > > > > Sent:	Wednesday, April 07, 2004 8:00 PM
> > > > > > > > To:	serusers at 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 at lists.iptel.org
> > > > > > > > > http://lists.iptel.org/mailman/listinfo/serusers