sr-users April 2005

sr-users@lists.kamailio.org

250 participants
697 discussions

[Serusers] force_tcp_alias
by Cesc Santasusana 05 Apr '05

05 Apr '05

Hi everybody, i dont seem to be able to get the force_tcp_alias to work ... or i am using it for the wrong thing. I want ser to reuse tcp sockets. My config is: phoneA ---UDP---- SER_A ---- TCP ---- SER_B ---- UDP ---- phoneB Now, if phoneA sends the INV to phoneB, no problem. If phoneA hangs up, SER_A reuses the tcp socket to send to SER_B. But, if it were phoneB to hangup, SER_B does not reuse the tcp socket it already has with SER_A. I've tried calling force_tcp_alias on top of the config file ... but no luck. Any ideas? Cesc Unclassified

1 0

[Serusers] onsip.org ser.cfg NAT issues.
by Dipole Moment 05 Apr '05

05 Apr '05

Hi all, Has anyone tried to implement SER using the getting started document on onsip.org? I tried it but calling NAT users wasn't possible until I replaced fix_nated_register() with fix_nated_contact(), since otherwise, SER would store RFC1918 IP of the end user in location table. Another issue is that when a user behind NAT tries to call someone with public IP address, only first few seconds of the conversation is heard by the caller, later on, although callee can hear the caller's voice the reverse isn't working. I'm using SER with rtpproxy again from the onsip.org site. Thanks in advance for any help.

4 6

[Serusers] append_branch Question
by Glenn Dalgliesh 05 Apr '05

05 Apr '05

I must be missing something; This seems like it should be so simple. I am trying to have ser 0.9. parallel fork using append_branch which I can get to work with the following append_branch("sip:voicemail@xxx.xxx.83.5:5060"); t_relay(); it Invites the original uri and then new one spec'd in append branch but what I need is to have the the original invited and the append branch keep the original user portion and change the host and port portion but I don't seem to be it seem to be able to find a way to accomplish this. What am I missing! Example: Ua1 and Ua2 are both registered with SER and Ua1@ser calls Ua2@ser then ser needs to Invite ua2@usrloc and ua2@asterisk Thanks

1 0

Re: [Serusers] SER 0.8.14 to 0.9.0
by Aisling O'Driscoll 05 Apr '05

05 Apr '05

Hi greger, That didn't work unfortunately and there are no error messages in var log. I typed "which ser" and saw /usr/local/sbin/ser. I realise this is not correct so in /etc/profile I changed this to : PATH="$PATH:/opt/ser/sbin:." However that didn't make much of a difference. I did rm ser.pid again from the var/run directory and now repeatedly get the error: Starting SER : PID file /var/run/ser.pid does not exist -- SER start failed. Do you think this is again something got to do with other versions? Thanks Aisling. > >---- Original Message ---- >From: greger(a)teigre.com >To: ashling.odriscoll(a)cit.ie >Subject: Re: [Serusers] SER 0.8.14 to 0.9.0 >Date: Tue, 5 Apr 2005 14:16:05 +0200 > >>Deleting /var/run/ser.pid is quite ok when ser is not running. >Maybe you >>have a leftover ser process. kill it (kill -9 if it still persists). > Then >>start ser: serctl start. >>Check /var/log/messages for error messages. >>g-) >> >>Aisling O'Driscoll wrote: >>> Greger, >>> >>> I followed the instructions in your previous emails and everything >>> worked like a charm for the first few times. However now when I >>> attempt to start SER (/opt/ser/sbin/serctl start). I get the >followng >>> error: >>> >>> Starting SER : PID file exists! (/var/run/ser.pid) already >running? >>> >>> I had already killed all ser processes (killall ser)before I >executed >>> this command so I dont understand why this happened. I then >removed >>> ser.pid i.e. cd /var/run, rm ser.pid. When I restarted again it >said >>> ser had restarted but when i typed pstree, I could only see one >ser >>> process (theres normally 27) and when i ran netstat -tunap I >couldnt >>> see ser listening on any port. >>> >>> Regards, >>> Aisling. >>>> >>>> ---- Original Message ---- >>>> From: greger(a)teigre.com >>>> To: ashling.odriscoll(a)cit.ie >>>> Subject: Re: [Serusers] SER 0.8.14 to 0.9.0 >>>> Date: Mon, 4 Apr 2005 13:01:48 +0200 >>>> >>>>> Well, difficult to know what's wrong. If you use the ONsip.org >>>> package and >>>>> follow the description I wrote in my last email, cpl-c.so should >be >>>>> installed correctly. >>>>> g-) >>>>> >>>>> Aisling O'Driscoll wrote: >>>>>> Thanks for that Greger. I have SER working now anyway (at last >;)) >>>>>> and when I run ser -V I can see that 0.9.1 is running. I have >to >>>>>> start ser using "ser -d -E". Now I want to get cpl-c.so >working. I >>>> am >>>>>> trying to follow the "SER CPL Howto" document but that seems to >>>>>> assume that cpl-c.so will be in /usr/local/lib/ser/modules and >>>> just >>>>>> needs to be patched. However there is no cpl-c.so module in >that >>>>>> directory. I have edited the makefile so the module isnt >excluded >>>> but >>>>>> that has made a difference. >>>>>> >>>>>> Any ideas? >>>>>> Thanks very much for your help so far. >>>>>> Aisling. >>>>>>> >>>>>>> ---- Original Message ---- >>>>>>> From: greger(a)teigre.com >>>>>>> To: ashling.odriscoll(a)cit.ie >>>>>>> Subject: Re: [Serusers] SER 0.8.14 to 0.9.0 >>>>>>> Date: Mon, 4 Apr 2005 10:48:59 +0200 >>>>>>> >>>>>>>> Aisling, >>>>>>>> Sorry, I overlooked this post. >>>>>>>> >>>>>>>> For installation from scratch, do the following as root: >>>>>>>> Make sure /opt exists, if not: mkdir /opt >>>>>>>> Delete your mysql ser database: mysqladmin -u root >[-ppassword] >>>>>>>> drop ser (I assume you don't need data in the old) >>>>>>>> unzip the source file to /tmp >>>>>>>> cd /tmp/ser-0.9.0 >>>>>>>> Run: ./make_and_install sql /opt/ser >>>>>>>> Ser will be installed to /opt/ser. >>>>>>>> Copy the config file to /opt/ser/etc/ser/ >>>>>>>> Create tables with /opt/ser/sbin/ser_mysql.sh create >>>>>>>> Verify that you have the correct ser: /opt/ser/sbin/ser -V >>>>>>>> >>>>>>>> Start ser with /opt/ser/sbin/serctl start >>>>>>>> >>>>>>>> Verify that ser is running: ps -ax | grep ser >>>>>>>> and check /var/log/messages >>>>>>>> >>>>>>>> If you still have problems, start ser this way: >>>>>>>> /opt/ser/sbin/ser -d -d -d -d -d -d -d -E -D >>>>>>>> >>>>>>>> Post the output. >>>>>>>> >>>>>>>> g-) >>>>>>>> >>>>>>>> Aisling O'Driscoll wrote: >>>>>>>>> I installed the following from the onsip site. I did "tar >-zxvf >>>>>>>>> ser-0.9.etcetc" in the /usr/local directory and then ran the >>>>>>> scripts. >>>>>>>>> Do I start ser now by doing /usr/local/sbin/serctl start. I >am >>>>>>> still >>>>>>>>> getting the error /var/run/ser.pid does not exist when I do >>>> that. >>>>>>>>> >>>>>>>>> Could someone let me know a command how to delete all ser >files >>>>>>> from >>>>>>>>> my computer and then confirm that I should unzip the ser >0.9.0 >>>>>>> source >>>>>>>>> file in the /usr/local directory. >>>>>>>>> >>>>>>>>> Thanks a million, >>>>>>>>> Aisling. >>>>>>>>> >>>>>>>>>> ---- Original Message ---- >>>>>>>>>> From: greger(a)teigre.com >>>>>>>>>> To: ashling.odriscoll(a)cit.ie >>>>>>>>>> Subject: Re: [Serusers] SER 0.8.14 to 0.9.0 >>>>>>>>>> Date: Wed, 30 Mar 2005 07:46:06 +0200 >>>>>>>>>> >>>>>>>>>>> Aisling, >>>>>>>>>>> >>>>>>>>>>> We have now also posted a complete 0.9.0 source package on >>>>>>>>>>> http://www.onsip.org/. It comes with a simple script that >>>>>>>>>>> will compile and install most of the modules (including >cpl) >>>>>>>>>>> either to the default directory /usr/local/*/ser or to a >>>>>>>>>>> directory of your choice. The package was created as a >part >>>>>>>>>>> of the "Getting Started" effort to support speedy upstart >of >>>>>>>>>>> a full SER installation. >>>>>>>>>>> >>>>>>>>>>> Regards, >>>>>>>>>>> Greger >>>>>>>>>>> >>>>>>>>>>> Java Rockx wrote: >>>>>>>>>>>> Great. Now you need to compile the mysql support module. >>>>>>>>>>>> >>>>>>>>>>>> You can get a full how-to at http://www.onsip.org >>>>>>>>>>>> >>>>>>>>>>>> Just register and download the "Getting Started" >document. >>>>>>>>>>>> This should be enough to get your using the mysql module. >>>>>>>>>>>> >>>>>>>>>>>> As for cpl but I suspect that it simply isn't complied by >>>>>>> default. >>>>>>>>>>>> >>>>>>>>>>>> You can compile it by changing to your ser source >directory >>>>>>>>>>>> and doing this: >>>>>>>>>>>> >>>>>>>>>>>> make exclude_modules="" modules >>>>>>>>>>>> >>>>>>>>>>>> Then copy the <ser-source>/modules/cpl-c/*.so to >>>>>>>>>>>> /usr/loca/lib/ser/modules >>>>>>>>>>>> >>>>>>>>>>>> Regards, >>>>>>>>>>>> Paul >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Tue, 29 Mar 2005 17:34:38 +0100, Aisling O'Driscoll >>>>>>>>>>>> <ashling.odriscoll(a)cit.ie> wrote: >>>>>>>>>>>>> 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)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)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)iptel.org >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>> http://mail.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)iptel.org >>>>>>>>>>>>>>>>>>> http://mail.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. >>>>> >>>>> >>>>> -------------------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.

1 0

Re [Serusers] Contact Header and SDP not rewritten
by Vivienne Curran 05 Apr '05

05 Apr '05

Thank you for that Greger. I have altered my script so that it exactly mimics the one in the onsip document besides the has_totag and fix_nated register. All is good when I ring from a private phone to a public phone i.e. the audio is very clear and the following messages are in /var/log. ERROR: extract_body: message body has length zero ERROR: force_rtp_proxy2: cant extract body from the message. I assume this is because of the 200 OK to a register message where theres no sdp?? Is this correct? However when I try to phone from public into private I get: ERROR: send_rtpp_command: cant read reply from a RTP Proxy. I find this confusing because I know the rtpproxy is working. BR Vivienne. "Greger V. Teigre" <greger(a)teigre.com> wrote: Yes, you can use fix_nated_contact instead. It is not entirely RFC-compliant, but that's what you have in 0.8.14. The has_totag() only tests to see if the INVITE has a To header, which means that it is in-dialog and thus is a re-INVITE. An INVITE will normally not have loose routing unless you have another SIP proxy forwarding an INVITE to you (in which case you should assume that the other proxy handles NAT and thus not trigger NAT-related code). You can safely remove the has_totag() if you use force_rtp_proxy("l") g-) ---- Original Message ---- From: Vivienne Curran To: Greger V. Teigre ; serusers(a)lists.iptel.org Sent: Tuesday, April 05, 2005 02:25 PM Subject: Re: [Serusers] Contact Header and SDP not rewritten > Greger, > > Since fix_nated_register does not exist with 0.8.14, will > fix_nated_contact do instead? Also if I am leaving out the > has_totag() at the start of the script, will this greatly effect its > functionality? > > Thank you, > Vivienne > > "Greger V. Teigre" <greger(a)teigre.com> wrote: > Vivienne, > > This is the first INVITE going from SER to your public phone. I have > prefixed my comments with *==> > > U 84.203.148.146:5060 -> 157.190.74.151:5060 > INVITE sip:2092@157.190.74.151 SIP/2.0..Via: SIP/2.0/UDP > 84.203.148.146;branch=z9hG4bK77bc.b54ca216.0.. > Via: SIP/2.0/UDP > 172.16.3.31;rport=5060;received=84.203.148.14;branch=z9hG4bK1a48edc121f5bc1f.. > From: "2093" <sip:2093@84.203.148.146>;tag=2dc376dcd4655094.. > To: <sip:2092@84.203.148.146>.. > Contact: <sip:2093@84.203.148.14:5060>.. > *==> Correctly changed to the public address and port of 2093 > Supported: replaces..Call-ID: 44e1ae63c476fbff@172.16.3.31..CSeq: > 10327 INVITE.. > User-Agent: Grandstream BT100 1.0.5.18.. > Max-Forwards: 69..Allow: > INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE.. > Content-Type: application/sdp.. > Content-Length: 443....v=0.. > o=2093 8000 0 IN IP4 172.16.3.31.. > s=SIP Call.. > c=IN IP4 84.203.148.1484.203.148.146.. > *==> Here it seems that first fix_nated_sdp("3") is called (replace > private IP with public IP), then force_rtp_proxy() (replace with > proxy IP). You must only call one of them (fix_nated_sdp("1") is ok) > t=0 0.. > m=audio 35006 RTP/AVP 0 8 4 18 2 15 99 9.. > a=sendrecv.. > a=rtpmap:0 PCMU/8000/3.. > a=rtpmap:8 PCMA/8000/3.. > a=rtpmap:4 G723/8000/3..a=rtpmap:18 G729/8000/3.. > a=rtpmap:2 G726-32/8000/3.. > a=rtpmap:15 G728/8000/3.. > a=rtpmap:99 iLBC/8000/3.. > a=fmtp:99 mode=20.. > a=rtpmap:9 G722/8000/3.. > a=ptime:20.. > a=direction:active.. > *==> Added by fix_nated_sdp("1") (and "3") > a=oldmediaip:172.16.3.31.. > *==> Added by fix_nated_sdp("3") > a=nortpproxy:yes.. > *==> Added by force_rtp_proxy() > > So, your call is proxied. Try using fix_nated_sdp("1"). It should > make the INVITE correct. You have not posted the OK, so I don't know > what is happening there. If you have followed the rtpproxy ONsip.org > example in your onreply_route, you should be fine. > > Good luck! > g-) > > ---- Original Message ---- > From: Vivienne Curran > To: serusers(a)lists.iptel.org > Sent: Tuesday, April 05, 2005 01:23 PM > Subject: [Serusers] Contact Header and SDP not rewritten > >> Hello, >> >> I have a problem whereby when a private client rings a public client >> only the public user can hear voice and when the public user rings >> the private user, no audio is transmitted. After looking at the >> messages I have have determined that the contact header and sdp part >> of the invite contains the private address of the natted client. This >> would lead me to believe that the registration process is incorrect. >> My problem is that I believe my script should handle the registration >> process correctly and I suspect that the following code is being >> skipped: I tried changing it to nat_uac_test("19") and >> fix_nated_sdp("3") but that didnt help. >>> if (nat_uac_test("3")){ >> if (method == "REGISTER" || ! search("^Record-Route:")){ >> log("Log: Someone trying to register from private >> IP,rewriting\n"); fix_nated_contact(); #Rewrite contact with >> source IP if (method == "INVITE"){ >> fix_nated_sdp("1"); #Add direction=active to SDP >> force_rtp_proxy(); >> }; >> force_rport(); # Add rport parameter to topmost Via >> setflag(6); # Mark as Nated >> }; >> }; >> >> I have included the log message below and my ser.cfg as an >> attachment. Please let me know where I could be going wrong. >> >> Thank you, >> Vivienne. Send instant messages to your online friends http://uk.messenger.yahoo.com

1 0

[Serusers] problem with sems and ser
by voip technocrat 05 Apr '05

05 Apr '05

Dear friends, iam trying to use the sems and ser ser is of version 0.8.12 and sems is of 0.1.0 from berlios.de i used the er-0.8.14 version also now when make a call in debug mode of the sems iam getting like this (8313) DEBUG: run (AmServer.cpp:185): version= <0.2> (8313) ERROR: run (AmServer.cpp:249): ## Wrong FIFO Interface version ## this is the ser.cfg iam useing # $Id: ser.cfg,v 1.11 2003/07/03 12:17:56 rco Exp $ # # iptel's voicemail config script # # ----------- global configuration parameters ------------------------ #debug=7 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=yes # (cmd line: -E) 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 ---------------------------------- loadmodule "/usr/local/lib/ser/modules/sl.so" loadmodule "/usr/local/lib/ser/modules/tm.so" loadmodule "/usr/local/lib/ser/modules/maxfwd.so" loadmodule "/usr/local/lib/ser/modules/rr.so" loadmodule "/usr/local/lib/ser/modules/textops.so" loadmodule "/usr/local/lib/ser/modules/vm.so" loadmodule "/usr/local/lib/ser/modules/dbtext.so" loadmodule "/usr/local/lib/ser/modules/usrloc.so" loadmodule "/usr/local/lib/ser/modules/registrar.so" # ----------------- setting module-specific parameters --------------- modparam("usrloc", "db_mode", 0) modparam("voicemail", "db_url","/root/ser/ser-0.8.12/modules/vm/db") modparam("rr", "enable_full_lr", 1) # ------------------------- request routing logic ------------------- # main routing logic route{ # initial sanity checks -- messages with # max_forwars==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); break; }; # if (len_gt( max_len )) { # sl_send_reply("513", "Message too big"); # break; # }; # we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol record_route(); # loose-route processing loose_route(); # Make MSN Messenger happy... if (method=="REGISTER") { log (0, "Regiseter Packet"); sl_send_reply("200","ok"); break; }; if (uri == myself) { # Voicemail specific configuration - begin if(method=="ACK" || method=="INVITE" || method=="BYE" || method=="REFER"){ if(t_newtran()){ t_reply("100","Trying -- just wait a minute !"); if(method=="INVITE" || method=="REFER"){ log("**************** vm start - begin ******************\n"); if( uri =~ "conference" ){ if(!vm("/tmp/am_fifo","conference")){ log("could not contact conference server\n"); t_reply("500","could not contact conference server"); }; } else if( uri =~ "echo" ){ if(!vm("/tmp/am_fifo","echo")){ log("could not contact echo\n"); t_reply("500","could not contact echo"); }; } else { if(!vm("/tmp/am_fifo","voicemail")){ log("could not contact voicemail\n"); t_reply("500","could not contact voicemail"); }; }; log("**************** vm start - end ******************\n"); break; }; if(method=="BYE"){ log("**************** vm end/refer - begin ******************\n"); if(!vm("/tmp/am_fifo","bye")){ log("could not contact the media server\n"); t_reply("500","could not contact the media server"); }; log("**************** vm end/refer - end ********************\n"); break; }; } else { log("could not create new transaction\n"); sl_send_reply("500","could not create new transaction"); }; }; # Voicemail specific configuration - end } else { if (!t_relay()) { sl_reply_error(); }; }; } this is my sems.conf --------------------- # $Id: sems.conf.sample,v 1.1.2.1 2003/08/28 19:13:25 rco Exp $ # # sems.conf.sample # # Sip Express Media Server (sems) # # sample configuration file # # # whitespaces (spaces and tabs) are ignored # comments start with a "#" and may be used inline # # example: option=value1, value2 # i like this option # ################################## # global parameters # ################################## # optional parameter: fork={yes|no} # # - specifies if sems should run in daemon mode (background) fork=yes # optional parameter: stderr={yes|no} # # - debug mode: do not fork and log to stderr stderr=no # optional parameter: loglevel={0|1|2|3} # # - sets log level (error=0, warning=1, info=2, debug=3) loglevel=1 # optional parameter: fifo_name=<filename> # # - path and file name of our fifo file fifo_name=/tmp/am_fifo # optional parameter: ser_fifo_name=<filename> # # - path and file name of Ser's fifo file ser_fifo_name=/tmp/ser_fifo # optional parameter: plugin_path=<path> # # - sets the path to the plug-ins # - may be absolute or relative to CWD plugin_path=/usr/local/lib/sems/plug-in/ ################################## # voicemail specific parameters # ################################## # optional parameter: announce_path=<path> # # - sets the path where announce files are searched for announce_path=/usr/local/lib/sems/audio/ # optional parameter: default_announce=<filename> # # - sets the name of the default announce WAV file default_announce=default_en.wav # optional parameter: max_record=<seconds> # # - maximum record time max_record=30 # optional parameter: smtp_server=<hostname> # # - sets address of smtp server smtp_server=localhost # optional parameter: smtp_port=<port> # # - sets port of smtp server smtp_port=25 ################################## # module specific parameters # ################################## # add more module configurations here (inline or external): # # config.mymodule=<filename> # or # config.mymodule=inline # ... with regards ________________________________________________________________________ Yahoo! India Matrimony: Find your life partner online Go to: http://yahoo.shaadi.com/india-matrimony

1 0

[Serusers] [Seruser] 483 too many hoops?
by Erdem HAKI 05 Apr '05

05 Apr '05

Hello again, When i want to send IM, I get this error "483 too many hoops" . Klaus said "probably you loop the messages in ser!Use ethereal on the loopback device and watch for looped messages.". How can i resolve it? I mean what kind of changes sould i do and in which files? Thanks.

3 5

[Serusers] why would a client behave differently for nat on outbound as opposed to inbound
by Iqbal 05 Apr '05

05 Apr '05

Couldnt think of a better subject, basically I have a handytone (HT) , and a xlite behind the same router, which is natting. SER is external Now when I call HT to xlite I hear absolutely nothing in either direction, and nuthing except for a request from xlite hits the mediaproxy...but when xlite calls HT, mediaproxy lights up like a xmas tree, and all is well. What I can see is that if the router is the same one, then surely something in the HT settings (I have no NAT traversal set in HT) causing this, or something in xlite telling it what to do, I just cant see what. Oh xlite/HT to pstn works fine, and inbound from pstn to HT/xlite is also fine voice both ways. Iqbal

2 7

RE: [Serusers] still no help - usrloc synchronization
by Matt Schulte 05 Apr '05

05 Apr '05

I'm starting to lean this direction, using t_replicate and all. I could never get usrloc (db mode) to function properly.. t_replicate is a dirty but very effective workaround. -----Original Message----- From: Greger V. Teigre [mailto:greger@teigre.com] Sent: Saturday, April 02, 2005 1:33 AM To: kramarv(a)yahoo.com Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] still no help - usrloc synchronization Have a look at this thread: http://lists.iptel.org/pipermail/serusers/2005-January/014669.html g-) Java Rockx wrote: > Tina, > > I thought I saw you post the other day that you did not want to use > t_replicate(), however, this is probably your best bet to getting this > to work, IMHO. > > Regards, > Paul > > On Apr 1, 2005 4:08 PM, Tina <kramarv(a)yahoo.com> wrote: >> >> Hi, please help me, I'm stuck with it!!!!! >> I am trying to set up several sers with a shared MySQL database for >> location service. >> >> I set in each ser.cfg: >> >> modparam("usrloc", "db_mode", 2) >> modparam("usrloc", >> "db_url","sql://ser:heslo@192.168.25.163/ser") >> >> and the servers are not synchronized. >> The I set >> modparam("usrloc", "db_mode", 2) >> >> >> made UAC (Xlite) register to one of the servers. >> I see it via usrloc, but there is no record in "location" mySQL >> table....So others do not see the client and I'm unable to make >> calls.... >> >> >> Please help how to work with usrloc and mySQL... >> >> Tina, >> software engineer >> >> ________________________________ >> Do you Yahoo!? >> Better first dates. More second dates. Yahoo! Personals >> >> >> _______________________________________________ >> Serusers mailing list >> serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers >> >> >> > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

2 1

Re: [Serusers] SER 0.8.14 to 0.9.0
by Aisling O'Driscoll 05 Apr '05

05 Apr '05

Greger, I followed the instructions in your previous emails and everything worked like a charm for the first few times. However now when I attempt to start SER (/opt/ser/sbin/serctl start). I get the followng error: Starting SER : PID file exists! (/var/run/ser.pid) already running? I had already killed all ser processes (killall ser)before I executed this command so I dont understand why this happened. I then removed ser.pid i.e. cd /var/run, rm ser.pid. When I restarted again it said ser had restarted but when i typed pstree, I could only see one ser process (theres normally 27) and when i ran netstat -tunap I couldnt see ser listening on any port. Regards, Aisling. > >---- Original Message ---- >From: greger(a)teigre.com >To: ashling.odriscoll(a)cit.ie >Subject: Re: [Serusers] SER 0.8.14 to 0.9.0 >Date: Mon, 4 Apr 2005 13:01:48 +0200 > >>Well, difficult to know what's wrong. If you use the ONsip.org >package and >>follow the description I wrote in my last email, cpl-c.so should be >>installed correctly. >>g-) >> >>Aisling O'Driscoll wrote: >>> Thanks for that Greger. I have SER working now anyway (at last ;)) >>> and when I run ser -V I can see that 0.9.1 is running. I have to >>> start ser using "ser -d -E". Now I want to get cpl-c.so working. I >am >>> trying to follow the "SER CPL Howto" document but that seems to >>> assume that cpl-c.so will be in /usr/local/lib/ser/modules and >just >>> needs to be patched. However there is no cpl-c.so module in that >>> directory. I have edited the makefile so the module isnt excluded >but >>> that has made a difference. >>> >>> Any ideas? >>> Thanks very much for your help so far. >>> Aisling. >>>> >>>> ---- Original Message ---- >>>> From: greger(a)teigre.com >>>> To: ashling.odriscoll(a)cit.ie >>>> Subject: Re: [Serusers] SER 0.8.14 to 0.9.0 >>>> Date: Mon, 4 Apr 2005 10:48:59 +0200 >>>> >>>>> Aisling, >>>>> Sorry, I overlooked this post. >>>>> >>>>> For installation from scratch, do the following as root: >>>>> Make sure /opt exists, if not: mkdir /opt >>>>> Delete your mysql ser database: mysqladmin -u root [-ppassword] >drop >>>> ser (I >>>>> assume you don't need data in the old) >>>>> unzip the source file to /tmp >>>>> cd /tmp/ser-0.9.0 >>>>> Run: ./make_and_install sql /opt/ser >>>>> Ser will be installed to /opt/ser. >>>>> Copy the config file to /opt/ser/etc/ser/ >>>>> Create tables with /opt/ser/sbin/ser_mysql.sh create >>>>> Verify that you have the correct ser: /opt/ser/sbin/ser -V >>>>> >>>>> Start ser with /opt/ser/sbin/serctl start >>>>> >>>>> Verify that ser is running: ps -ax | grep ser >>>>> and check /var/log/messages >>>>> >>>>> If you still have problems, start ser this way: >>>>> /opt/ser/sbin/ser -d -d -d -d -d -d -d -E -D >>>>> >>>>> Post the output. >>>>> >>>>> g-) >>>>> >>>>> Aisling O'Driscoll wrote: >>>>>> I installed the following from the onsip site. I did "tar -zxvf >>>>>> ser-0.9.etcetc" in the /usr/local directory and then ran the >>>> scripts. >>>>>> Do I start ser now by doing /usr/local/sbin/serctl start. I am >>>> still >>>>>> getting the error /var/run/ser.pid does not exist when I do >that. >>>>>> >>>>>> Could someone let me know a command how to delete all ser files >>>> from >>>>>> my computer and then confirm that I should unzip the ser 0.9.0 >>>> source >>>>>> file in the /usr/local directory. >>>>>> >>>>>> Thanks a million, >>>>>> Aisling. >>>>>> >>>>>>> ---- Original Message ---- >>>>>>> From: greger(a)teigre.com >>>>>>> To: ashling.odriscoll(a)cit.ie >>>>>>> Subject: Re: [Serusers] SER 0.8.14 to 0.9.0 >>>>>>> Date: Wed, 30 Mar 2005 07:46:06 +0200 >>>>>>> >>>>>>>> Aisling, >>>>>>>> >>>>>>>> We have now also posted a complete 0.9.0 source package on >>>>>>>> http://www.onsip.org/. It comes with a simple script that >will >>>>>>> compile and >>>>>>>> install most of the modules (including cpl) either to the >>>>>>>> default directory /usr/local/*/ser or to a directory of your >>>>>>>> choice. The package was created as a part of the "Getting >>>>>>>> Started" effort to support speedy upstart of a full SER >>>>>>>> installation. >>>>>>>> >>>>>>>> Regards, >>>>>>>> Greger >>>>>>>> >>>>>>>> Java Rockx wrote: >>>>>>>>> Great. Now you need to compile the mysql support module. >>>>>>>>> >>>>>>>>> You can get a full how-to at http://www.onsip.org >>>>>>>>> >>>>>>>>> Just register and download the "Getting Started" document. >This >>>>>>> should >>>>>>>>> be enough to get your using the mysql module. >>>>>>>>> >>>>>>>>> As for cpl but I suspect that it simply isn't complied by >>>> default. >>>>>>>>> >>>>>>>>> You can compile it by changing to your ser source directory >and >>>>>>> doing >>>>>>>>> this: >>>>>>>>> >>>>>>>>> make exclude_modules="" modules >>>>>>>>> >>>>>>>>> Then copy the <ser-source>/modules/cpl-c/*.so to >>>>>>>>> /usr/loca/lib/ser/modules >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> Paul >>>>>>>>> >>>>>>>>> >>>>>>>>> On Tue, 29 Mar 2005 17:34:38 +0100, Aisling O'Driscoll >>>>>>>>> <ashling.odriscoll(a)cit.ie> wrote: >>>>>>>>>> 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)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)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)iptel.org >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> http://mail.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)iptel.org >>>>>>>>>>>>>>>> http://mail.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. >> >> >>-------------------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.

2 1

← Newer
1
...
59
60
61
62
63
64
65
...
70
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users April 2005