I have deleted all the "modules" directories
from my system other
than /usr/local/lib/ser. However /usr/local/lib/ser doesnt contain
modules such as mysql.so, cpl-c.so etc. Is this normal?? If it is
then what how do I check these modules out cvs?. I have downloaded
the latest SER source code and made the SER binaries 2 more times
(according the onsip document) to make sure I running the most
up-to-date code.
I apologise for lack of linx knowledge and very much appreciate the
help I have been given so far.
Aisling.
---- Original Message ----
From: javarockx(a)gmail.com
To: ashling.odriscoll(a)cit.ie
Subject: Re: [Serusers] SER 0.8.14 to 0.9.0
Date: Tue, 29 Mar 2005 10:19:52 -0500
Again, this sounds like you've got more than
one version of ser on
your system.
I don't know where 0.8.14 kept it's modules but you can find other
ser
modules (and remove them).
to find them do this as root
find / -name mysql.so
you may find more than ser modules with this but it should spit out
the directory that 0.8.14 used.
ser-0.9 keeps its modules in /usr/local/lib/ser
Regards,
Paul
On Tue, 29 Mar 2005 15:53:56 +0100, Aisling O'Driscoll
<ashling.odriscoll(a)cit.ie> wrote:
> Yes that was it. Thanks. I promise I'm nearly there!I replaced the
> default script with the ser.cfg I was running with 0.8.14. I am
> getting two mismatch errors with the script though:
>
> ERROR: module version mismatch for
> /usr/local/lib/ser/modules/mysql.so; core: ser 0.9.1 (i386/linux);
> module ser 0.9.0 (i386/linux).
> Its the same for the cpl module.
>
> Can I run a command to update the modules only? Also I'm a bit
> confused if the mysql database that I was using with 0.8.14 is
still
> valid? Do I have create new tables
(ser_mysql.sh create etc)is the
> current database sufficient?
>
> Many thanks,
> Aisling.
>
> >
> >---- Original Message ----
> >From: greger(a)teigre.com
> >To: javarockx(a)gmail.com, ashling.odriscoll(a)cit.ie,
serusers(a)lists.iptel.org
> >Subject: Re: [Serusers] SER 0.8.14 to
0.9.0
> >Date: Tue, 29 Mar 2005 16:29:49 +0200
> >
> >>This is the default ser.cfg problem: Remove the
force_send_socket
> >line with
> >>reference to the smaug server.
> >>I thought this was changed in CVS (a test cfg file was committed
to
> >cvs in
> >>an error).
> >>g-)
> >>
> >>Java Rockx wrote:
> >>> your ser.cfg is in /usr/local/etc/ser
> >>>
> >>> I've not seen your ser.cfg file - so I can't really say.
> >>>
> >>> Regards,
> >>> Paul
> >>>
> >>>
> >>> On Tue, 29 Mar 2005 15:10:30 +0100, Aisling O'Driscoll
> >>> <ashling.odriscoll(a)cit.ie> wrote:
> >>>> Thanks,I've made that change. Any idea about why SER wont
start?
> >The
> >>>> following error is in /varlog/messages:
> >>>>
> >>>> /usr/local/sbin/ser[7966]: ERROR: fix_actions:
force_send_socket:
> >>>> could not resolvbe smaug.
> >>>>
> >>>> Also where is my new ser.cfg stored. My old one is in
etc/ser.
> >>>>
> >>>> Thanks,
> >>>> Aisling
> >>>>
> >>>> ---- Original Message ----
> >>>> From: javarockx(a)gmail.com
> >>>> To: ashling.odriscoll(a)cit.ie
> >>>> Subject: Re: [Serusers] SER 0.8.14 to 0.9.0
> >>>> Date: Tue, 29 Mar 2005 09:08:24 -0500
> >>>>
> >>>>> your PATH should actually be
> >>>>>
> >>>>> PATH=$PATH:/usr/local/sbin:.
> >>>>>
> >>>>> Regards,
> >>>>> Paul
> >>>>>
> >>>>>
> >>>>> On Tue, 29 Mar 2005 14:36:56 +0100, Aisling O'Driscoll
> >>>>> <ashling.odriscoll(a)cit.ie> wrote:
> >>>>>> Thanks for the replies so far - Everyone has been very
helpful.
> >I
> >>>>>> have one final question. I deleted the "ser"
directory from
> >>>>> /usr/sbin
> >>>>>> as suggested. I am using Suse Linux 9.0 so then I modified
the
> >>>>>> "profile"
file in the /etc directory with the following:
> >>>>>>
> >>>>>> PATH="$PATH:/usr/local/sbin/ser:."
> >>>>>>
> >>>>>> Then I carried out the cvs instructions from the iptel site
(as
> >>>>>> detailed at end of
this mail) to install SER 0.9.1. When I
run
> >"ser
> >>>>>> -V" I now see that SER has been updated. However when I
run
> >>>>>> /usr/local/sbin/serctl start to start SER. I get an error:
> >>>>>>
> >>>>>> Starting SER: PID file /var/run/ser.pid does not exist --
SER
> >start
> >>>>>> failed.
> >>>>>>
> >>>>>> I used to start SER using /etc/init.d/ser start. That also
> >doesn't
> >>>>>> work. What could be wrong? Also where is my new ser.cfg
file
> >>>>> stored?
> >>>>>> My old one is still in /etc/ser.
> >>>>>>
> >>>>>> Thanks again.
> >>>>>> Aisling.
> >>>>>>
> >>>>>> cd /usr/src
> >>>>>> export
CVSROOT=:pserver:anonymous@cvs.berlios.de:/cvsroot/ser
> >>>>>> cvs login
> >>>>>> [enter for password]
> >>>>>> "cvs co -r rel_0_9_0 sip_router" from onsip site.
> >>>>>> cd sip_router
> >>>>>> make all
> >>>>>> make install
> >>>>>>
> >>>>>>> ---- Original Message ----
> >>>>>>> From: javarockx(a)gmail.com
> >>>>>>> To: ashling.odriscoll(a)cit.ie
> >>>>>>> Subject: Re: [Serusers] SER 0.8.14 to 0.9.0
> >>>>>>> Date: Tue, 29 Mar 2005 08:07:35 -0500
> >>>>>>>
> >>>>>>>> Each linux user has an environment variable called
PATH.
You
> >can
> >>>>> set
> >>>>>>>> your path in the .bash_profile (assuming a redhat
linux
> >distro).
> >>>>>>>> Consult your linux distro for setting environment
variables.
> >>>>>>>>
> >>>>>>>> On most you can just do this:
> >>>>>>>>
> >>>>>>>> export PATH=$PATH:/usr/local/sbin/
> >>>>>>>>
> >>>>>>>> But this will only be for you current logged in
session.
When
> >you
> >>>>>>> exit
> >>>>>>>> the bash shell this setting will be lost.
> >>>>>>>>
> >>>>>>>> Regards,
> >>>>>>>> Paul
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Tue, 29 Mar 2005 13:50:18 +0100, Aisling
O'Driscoll
> >>>>>>>> <ashling.odriscoll(a)cit.ie> wrote:
> >>>>>>>>> Apologies if this is a ridculous question where
will I
find
> >the
> >>>>>>> $PATH
> >>>>>>>>> variable?
> >>>>>>>>>
> >>>>>>>>> Thanks,
> >>>>>>>>> Aisling
> >>>>>>>>>>
> >>>>>>>>>> ---- Original Message ----
> >>>>>>>>>> From: javarockx(a)gmail.com
> >>>>>>>>>> To: ashling.odriscoll(a)cit.ie,
serusers(a)lists.iptel.org
> >>>>>>>>>> Subject: Re: [Serusers] SER 0.8.14 to 0.9.0
> >>>>>>>>>> Date: Tue, 29 Mar 2005 07:49:44 -0500
> >>>>>>>>>>
> >>>>>>>>>>> it looks like you have two copies of ser
on your
machine.
> >>>>>>>>>>>
> >>>>>>>>>>> You should complete remove /usr/sbin/ser
and make sure
> >>>>>>>>>>> /usr/local/sbin/ser is in your $PATH.
> >>>>>>>>>>>
> >>>>>>>>>>> Regards,
> >>>>>>>>>>> Paul
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On Tue, 29 Mar 2005 13:43:56 +0100,
Aisling O'Driscoll
> >>>>>>>>>>> <ashling.odriscoll(a)cit.ie> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> When I type "which ser". I
get /usr/sbin/ser. How can
I
>
>>>>>>>>>>>> proceed from here?. Thank you for the
reply.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Aisling.
> >>>>>>>>>>>>
> >>>>>>>>>>>> ---- Original Message ----
> >>>>>>>>>>>> From: javarockx(a)gmail.com
> >>>>>>>>>>>> To: ashling.odriscoll(a)cit.ie
> >>>>>>>>>>>> Subject: Re: [Serusers] SER 0.8.14
to 0.9.0
> >>>>>>>>>>>> Date: Tue, 29 Mar 2005 06:46:20
-0500
> >>>>>>>>>>>>
> >>>>>>>>>>>>> Aisling,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> It seems like one of the
following is true:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> 1) you're somehow mixing
0.8.14 source code with
0.9.1
>
>>>>>>>>>>>>>
> >>>>>>>>>>>>> 2) you have more than one copy
of ser installed on
your
>
>>>>>>>>>>>>> system. If you
> >>>>>>>>>>>>> type "which ser" does
it point to
/usr/local/sbin/ser ??
>
>>>>>>>>>>>>>
> >>>>>>>>>>>>> Regards,
> >>>>>>>>>>>>> Paul
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Tue, 29 Mar 2005 09:55:06
+0100, Aisling
O'Driscoll
>
>>>>>>>>>>>>> <ashling.odriscoll(a)cit.ie>
wrote:
> >>>>>>>>>>>>>> Hello,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I am still trying to change
my SER version from
0.8.14
> >to
> >>>>>>>>>>>>>> 0.9.0. I have
> >>>>>>>>>>>>>> followed the instructions at
the following link and
> >also
> >>>>> on
> >>>>>>> the
> >>>>>>>>>>>>> onsip
> >>>>>>>>>>>>>> site.
> >>>>>>>>>>>>>>
http://www.iptel.org/ser/cvs/
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> However when I run ser -V, I
still see that I'm
running
>
>>>>>>>>>>>>>> 0.8.14. I've given an exact
detail of what i do
below
> >and
> >>>>>>>>>>>>>> can someone
> >>>>>>> PLEASE
> >>>>>>>>>>>>>> PLEASE point out the
mistake. Thank you.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> cd /usr/src
> >>>>>>>>>>>>>> export
> >>>>>>> CVSROOT=:pserver:anonymous@cvs.berlios.de:/cvsroot/ser
> >>>>>>>>>>>>>> cvs login
> >>>>>>>>>>>>>> [enter for password]
> >>>>>>>>>>>>>> Here I've tried both
"cvs co sip_router" for
unstable
>
>>>>>>>>>>>>>> version and "cvs co -r
rel_0_9_0 sip_router" from
onsip
>
>>>>>>>>>>>>>> site.
> >>>>>>>>>>>>>> cd sip_router
> >>>>>>>>>>>>>> make all
> >>>>>>>>>>>>>> make install
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> It says every file is
updated but I still run the
same
> >>>>>>> stable
> >>>>>>>>>>>>>> version. I've killed all
ser processes before
running
> >this
> >>>>>>>>>>>>>> command (killall ser)
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Please let me know what Im
doing wrong,
> >>>>>>>>>>>>>> Aisling.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> -------------------Legal
> >>>>>>>>>>>>>
Disclaimer---------------------------------------
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> The above electronic mail
transmission is
confidential
> >>>>> and
> >>>>>>>>>> intended
> >>>>>>>>>>>>> only for the person to whom it
is addressed. Its
> >contents
> >>>>>>>>>>>>> may be protected by legal and/or
professional
privilege.
>
>>>>>>>>>>>>> Should it be received by you in error
please contact
the
>
>>>>>>>>>>>>> sender at the
> >>>>>>> above
> >>>>>>>>>>>>> quoted email address. Any
unauthorised form of
> >>>>> reproduction
> >>>>>>> of
> >>>>>>>>>> this
> >>>>>>>>>>>>> message is strictly prohibited.
The Institute does
not
>
>>>>>>>>>>>>> guarantee the security of any
information
electronically
>
>>>>>>>>>>>>> transmitted and is not liable if the
information
> >contained
> >>>>>>>>>>>>> in this communication
> >>>>> is
> >>>>>>> not
> >>>>>>>>>> a
> >>>>>>>>>>>>> proper and complete record of
the message as
transmitted
> >by
> >>>>>>>>>>>>> the sender nor for any delay in
its receipt.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
_______________________________________________
> >>>>>>>>>>>>>> Serusers mailing list
> >>>>>>>>>>>>>> serusers(a)lists.iptel.org
> >>>>>>>>>>>>>>
http://lists.iptel.org/mailman/listinfo/serusers
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> -------------------Legal
> >>>>>>>>>>>>>
Disclaimer---------------------------------------
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> The above electronic mail
transmission is
confidential
> >and
> >>>>>>>>>> intended
> >>>>>>>>>>>>> only for the person to whom it
is addressed. Its
> >contents
> >>>>>>>>>>>>> may be protected by legal and/or
professional
privilege.
>
>>>>>>>>>>>>> Should it be received by you in error
please contact
the
>
>>>>>>>>>>>>> sender at the
> >>>>>>> above
> >>>>>>>>>>>>> quoted email address. Any
unauthorised form of
> >>>>> reproduction
> >>>>>>> of
> >>>>>>>>>> this
> >>>>>>>>>>>>> message is strictly prohibited.
The Institute does
not
>
>>>>>>>>>>>>> guarantee the security of any
information
electronically
>
>>>>>>>>>>>>> transmitted and is not liable if the
information
> >contained
> >>>>>>>>>>>>> in this communication
> >>>>> is
> >>>>>>> not
> >>>>>>>>>> a
> >>>>>>>>>>>>> proper and complete record of
the message as
transmitted
> >by
> >>>>>>>>>>>>> the sender nor for any delay in
its receipt.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> -------------------Legal
> >>>>>>>>>>
Disclaimer---------------------------------------
> >>>>>>>>>>>>
> >>>>>>>>>>>> The above electronic mail
transmission is
confidential
> >and
> >>>>>>>>>> intended only for the person to whom it is
addressed.
Its
> >>>>>>> contents
> >>>>>>>>>> may be protected by legal and/or
professional
privilege.
> >>>>>>>>>>
Should it be received by you in error please contact
the
> >>>>>>>>>>
sender at the
> >>>>> above
> >>>>>>>>>> quoted email address. Any unauthorised form
of
reproduction
> >of
> >>>>>>> this
> >>>>>>>>>> message is strictly prohibited. The
Institute does not
> >>>>>>>>>> guarantee the security of any information
electronically
> >>>>>>>>>>
transmitted and is
> >>>>> not
> >>>>>>>>>> liable if the information contained in this
communication
> >is
> >>>>>>>>>> not a proper and complete record of the
message as
> >transmitted
> >>>>>>>>>> by
> >>>>> the
> >>>>>>>>>> sender nor for any delay in its receipt.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> -------------------Legal
> >>>>>>>>>>
Disclaimer---------------------------------------
> >>>>>>>>>>>
> >>>>>>>>>>> The above electronic mail transmission
is confidential
and
> >>>>>>> intended
> >>>>>>>>>> only for the person to whom it is addressed.
Its
contents
> >may
> >>>>> be
> >>>>>>>>>> protected by legal and/or professional
privilege.
Should it
> >be
> >>>>>>>>>> received by you in error please contact the
sender at
the
> >>>>> above
> >>>>>>>>>> quoted email address. Any unauthorised form
of
reproduction
> >of
> >>>>>>> this
> >>>>>>>>>> message is strictly prohibited. The
Institute does not
> >>>>>>>>>> guarantee the security of any information
electronically
> >>>>>>>>>>
transmitted and is
> >>>>> not
> >>>>>>>>>> liable if the information contained in this
communication
> >is
> >>>>>>>>>> not a proper and complete record of the
message as
> >transmitted
> >>>>>>>>>> by
> >>>>> the
> >>>>>>>>>> sender nor for any delay in its receipt.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> -------------------Legal
> >>>>>>> Disclaimer---------------------------------------
> >>>>>>>>>
> >>>>>>>>> The above electronic mail transmission is
confidential
and
> >>>>>>> intended only
for the person to whom it is addressed. Its
> >contents
> >>>>>>> may be protected by legal and/or professional
privilege.
> >Should it
> >>>>> be
> >>>>>>> received by you in error please contact the sender at
the
> >above
> >>>>>>> quoted email address. Any unauthorised form of
reproduction of
> >>>>> this
> >>>>>>> message is strictly prohibited. The Institute does not
> >guarantee
> >>>>> the
> >>>>>>> security of any information electronically transmitted
and
is
> >not
> >>>>>>> liable if the information contained in this
communication
is
> >not a
> >>>>>>> proper and complete record of the message as transmitted
by
> >the
> >>>>>>> sender nor for any delay in its receipt.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> -------------------Legal
> >>>>>>> Disclaimer---------------------------------------
> >>>>>>>>
> >>>>>>>> The above electronic mail transmission is
confidential
and
> >>>>> intended
> >>>>>>> only for the person to whom it is addressed. Its
contents
may
> >be
> >>>>>>> protected by legal and/or professional privilege. Should
it be
> >>>>>>> received by you
in error please contact the sender at the
> >above
> >>>>>>> quoted email address. Any unauthorised form of
reproduction of
> >>>>> this
> >>>>>>> message is strictly prohibited. The Institute does not
> >guarantee
> >>>>> the
> >>>>>>> security of any information electronically transmitted
and
is
> >not
> >>>>>>> liable if the information contained in this
communication
is
> >not a
> >>>>>>> proper and complete record of the message as transmitted
by
> >the
> >>>>>>> sender nor for any delay in its receipt.
> >>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>> -------------------Legal
> >>>>> Disclaimer---------------------------------------
> >>>>>>
> >>>>>> The above electronic mail transmission is confidential and
> >intended
> >>>>> only for the person to whom it is addressed. Its contents
may be
> >>>>> protected by legal
and/or professional privilege. Should it
be
> >>>>> received by you in error
please contact the sender at the
above
> >>>>> quoted email address.
Any unauthorised form of reproduction
of
> >this
> >>>>> message is strictly prohibited. The Institute does not
guarantee
> >the
> >>>>> security of any information electronically transmitted and
is
> >not
> >>>>> liable if the information contained in this communication is
not
> >a
> >>>>> proper and complete record of the message as transmitted by
the
> >>>>> sender nor for any delay
in its receipt.
> >>>>>>
> >>>>>>
> >>>>>
> >>>>> -------------------Legal
> >>>>> Disclaimer---------------------------------------
> >>>>>
> >>>>> The above electronic mail transmission is confidential and
> >intended
> >>>>> only for the person to whom it is addressed. Its contents
may be
> >>>>> protected by legal
and/or professional privilege. Should it
be
> >>>>> received by you in error
please contact the sender at the
above
> >>>>> quoted email address.
Any unauthorised form of reproduction
of
> >this
> >>>>> message is strictly prohibited. The Institute does not
guarantee
> >the
> >>>>> security of any information electronically transmitted and
is
> >not
> >>>>> liable if the information contained in this communication is
not
> >a
> >>>>> proper and complete record of the message as transmitted by
the
> >>>>> sender nor for any delay
in its receipt.
> >>>>>
> >>>>
> >>>> -------------------Legal
> >>>> Disclaimer---------------------------------------
> >>>>
> >>>> The above electronic mail transmission is confidential and
> >intended
> >>>> only for the person to whom it is addressed. Its contents may
be
> >>>> protected by legal and/or
professional privilege. Should it
be
> >>>> received by you in error
please contact the sender at the
above
> >>>> quoted email address. Any
unauthorised form of reproduction
of
> >this
> >>>> message is strictly prohibited. The Institute does not
guarantee
> >the
> >>>> security of any information electronically transmitted and is
not
> >>>> liable if the information
contained in this communication is
not
> >a
> >>>> proper and complete record of the message as transmitted by
the
> >>>> sender nor for any delay in
its receipt.
> >>>>
> >>>>
> >>>
> >>> _______________________________________________
> >>> Serusers mailing list
> >>> serusers(a)lists.iptel.org
> >>>
http://lists.iptel.org/mailman/listinfo/serusers
> >>
> >>
> >>-------------------Legal
> >Disclaimer---------------------------------------
> >>
> >>The above electronic mail transmission is confidential and
intended
> >only for the person to whom it is
addressed. Its contents may be
> >protected by legal and/or professional privilege. Should it be
> >received by you in error please contact the sender at the above
> >quoted email address. Any unauthorised form of reproduction of
this
> >message is strictly prohibited. The
Institute does not guarantee
the
> >security of any information
electronically transmitted and is not
> >liable if the information contained in this communication is not
a
> >proper and complete record of the message
as transmitted by the
> >sender nor for any delay in its receipt.
> >>
> >>
>
> -------------------Legal
Disclaimer---------------------------------------
>
> The above electronic mail transmission is confidential and
intended only for
the person to whom it is addressed. Its contents
may be protected by legal and/or professional privilege. Should it be
received by you in error please contact the sender at the above
quoted email address. Any unauthorised form of reproduction of this
message is strictly prohibited. The Institute does not guarantee the
security of any information electronically transmitted and is not
liable if the information contained in this communication is not a
proper and complete record of the message as transmitted by the
sender nor for any delay in its receipt.
Disclaimer---------------------------------------
The above electronic mail transmission is confidential and intended
only for the
person to whom it is addressed. Its contents may be
protected by legal and/or professional privilege. Should it be
received by you in error please contact the sender at the above
quoted email address. Any unauthorised form of reproduction of this
message is strictly prohibited. The Institute does not guarantee the
security of any information electronically transmitted and is not
liable if the information contained in this communication is not a
proper and complete record of the message as transmitted by the
sender nor for any delay in its receipt.
>
>
-------------------Legal Disclaimer---------------------------------------
The above electronic mail transmission is confidential and intended only for the person
to whom it is addressed. Its contents may be protected by legal and/or professional
privilege. Should it be received by you in error please contact the sender at the above
quoted email address. Any unauthorised form of reproduction of this message is strictly
prohibited. The Institute does not guarantee the security of any information
electronically transmitted and is not liable if the information contained in this
communication is not a proper and complete record of the message as transmitted by the
sender nor for any delay in its receipt.