sr-users April 2005

sr-users@lists.kamailio.org

250 participants
697 discussions

[Serusers] Can some1 teach me how to add in Voice Mail into my Server....?
by Quek Eric 04 Apr '05

04 Apr '05

Hi all, I hav tried to understand SIP...im a totally new to sip, still a student learning. How do I enable my Voice Mail in my ser.cfg....or where can i learn to add voice mail? I had vry little understanding with my ser.cfg file due to the server was created by previous project student... here's ser.cfg # # $Id: ser.cfg,v 1.21.4.1 2003/11/10 15:35:15 andrei Exp $ # # simple quick-start config script # # ----------- global configuration parameters ------------------------ debug=3 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=yes # (cmd line: -E) /* Uncomment these lines to enter debugging mode debug=7 fork=no log_stderror=yes */ listen=172.16.221.38 listen=127.0.0.1 alias="sip.nyp.edu.sg" alias=172.16.221.38 alias=127.0.0.1 check_via=yes # (cmd. line: -v) dns=yes # (cmd. line: -r) rev_dns=no # (cmd. line: -R) port=5060 children=4 fifo="/tmp/ser_fifo" # ------------------ module loading ---------------------------------- loadmodule "/usr/lib/ser/modules/mysql.so" loadmodule "/usr/lib/ser/modules/sl.so" loadmodule "/usr/lib/ser/modules/tm.so" loadmodule "/usr/lib/ser/modules/rr.so" loadmodule "/usr/lib/ser/modules/maxfwd.so" loadmodule "/usr/lib/ser/modules/usrloc.so" loadmodule "/usr/lib/ser/modules/registrar.so" loadmodule "/usr/lib/ser/modules/auth.so" loadmodule "/usr/lib/ser/modules/auth_db.so" loadmodule "/usr/lib/ser/modules/acc.so" loadmodule "/usr/lib/ser/modules/exec.so" loadmodule "/usr/lib/ser/modules/group.so" loadmodule "/usr/lib/ser/modules/domain.so" loadmodule "/usr/lib/ser/modules/print.so" loadmodule "/usr/lib/ser/modules/textops.so" loadmodule "/usr/lib/ser/modules/uri.so" loadmodule "/usr/lib/ser/modules/msilo.so" loadmodule "/usr/lib/ser/modules/vm.so" # ----------------- setting module-specific parameters --------------- # -- tm parameters -- modparam("tm", "fr_timer", 12) modparam("tm", "fr_inv_timer", 24) # -- rr parameters -- #add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1) # -- usrloc parameters -- #2 enables write-back to persistent mysql storage for speed #disable=0, write-through=1 modparam("usrloc", "db_mode", 2) #minimize write back window - default is 60 seconds modparam("usrloc", "timer_interval", 120) #database location modparam("usrloc", "db_url", "sql://ser:heslo@localhost/ser") # -- auth parameters -- #database location modparam("auth_db", "db_url", "sql://ser:heslo@localhost/ser") #allows clear text password in the mysql database modparam("auth_db", "calculate_ha1", yes) #name of password column in mysql database modparam("auth_db", "password_column", "password") # -- acc parameters -- modparam("acc", "log_level", 1) modparam("acc", "log_flag", 1) modparam("acc", "log_missed_flag", 3) # -- msilo parameters -- modparam("msilo", "db_table", "silo") # -- msilo parameters -- #URL of the mysql database used to retrieve users. #modparam("vm", "db_url", "sql://username:password@localhost/ser") # ------------------------- request routing logic ------------------- # main routing logic route{ #checks messages with max_forwards==0 if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","too many hops"); break; }; #or excessively long requests if ( msg:len > max_len ) { sl_send_reply("513", "message is 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 if (loose_route()) { t_relay(); break; }; # labeled all transaction for accounting setflag(1); # record-route INVITES to make sure BYEs will visit our server too if (method=="INVITE") record_route(); # if the request is for other domain use UsrLoc # (in case, it does not work, use the following command # with proper names and addresses in it) if (uri==myself) { if (method=="REGISTER") { #make sure that users don't register infinite loops if (search("^(Contact|m):.*@(172\.16\.221\.38|(proxy\.)?sip\.nyp\.edu\.sg)")) { log(1, "LOG: alert: someone trying to set aor==contact\n"); sl_send_reply("476", "no server address in contacts allowed"); break; }; #Uncomment this if you want to use digest authentication # if (!www_authorize("sip.nyp.edu.sg", "subscriber")) # { # www_challenge("sip.nyp.edu.sg", "0"); # break; # }; save("aliases"); save("location"); log("REGISTER received -> dumping messages with MSILO\n"); #MSILO - dumping user's offline messages if (m_dump()) { log("MSILO: offline messages dumped - if they were\n"); } else { log("MSILO: no offline messages dumped\n"); }; break; }; #native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { if (! t_newtran()) { sl_reply_error(); break; }; if (!method=="MESSAGE") { if (!t_reply("404", "not found on LDAP or SER")) { sl_reply_error(); }; break; }; log("MESSAGE received -> storing using MSILO\n"); # MSILO - storing as offline message if (m_store("0")) { log("MSILO: offline message stored\n"); if (!t_reply("202", "accepted for later delivery")) { sl_reply_error(); }; } else { log("MSILO: offline message NOT stored\n"); if (!t_reply("503", "service unavailable")) { sl_reply_error(); }; }; break; sl_send_reply("404", "not found on LDAP or SER"); break; }; #if the downstream UA does not support MESSAGE requests #go to failure_route[1] t_on_failure("1"); t_relay(); break; #native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { if (!exec_dset("/etc/ser/sipldap")) { sl_send_reply("404", "not found on LDAP or SER"); break; } else { log(1, "sipldap call"); }; }; }; setflag(3); #forward to current uri now; use stateful forwarding; that #works reliably even if we forward from TCP to UDP if (!t_relay()) { sl_reply_error(); break; }; #does user wish redirection on no availability? #(is he in the voicemail (ser->grp) group? if (is_user_in("Request-URI", "voicemail")) { t_on_failure("4"); setflag(1); }; } failure_route[1] { #forwarding failed -- check if the request was a MESSAGE if (!method=="MESSAGE") { break; }; log(1,"MSILO: the downstream UA does not support MESSAGE requests ...\n"); #we have changed the R-URI with the contact address -- ignore it now if (m_store("1")) { log("MSILO: offline message stored\n"); t_reply("202", "accepted for later delivery"); } else { log("MSILO: offline message NOT stored\n"); t_reply("503", "service unavailable"); }; } failure_route[4] { append_branch("sip:80000@sip.nyp.edu.sg"); append_urihf("CC-Diversion: ", "\r\n"); append_hf("P-hint: OFFLINE-VOICEMAIL\r\n"); t_relay(); } rgds, Eric __________________________________ Do you Yahoo!? Make Yahoo! your home page http://www.yahoo.com/r/hs

2 1

Re: [Serusers] NAT NAT..and a little more NAT
by Greger V. Teigre 04 Apr '05

04 Apr '05

I suspect this is one of those questions where you know the answer ;-) Yes, you're of course right. You inject a direction=active in the failure_route, so that the GW will wait for the media before sending. However, I have had some issues with some clients that I haven't really figured completely out yet and I'm trying to be conservative. Do you have experiences where this work? If so, which GWs and clients do you have good experiences with? When we are first at it, there is another advanced case also: Where one SIP client is non-NATed and supports connection-oriented media, you don't have to use rtp proxy. The challenge is to know that a) the client is really public and does not appear to be public due to STUN usage b) it supports connection-oriented media (Honestly, I don't really know which clients do, AFAIK only GWs have implemented this so far, but there are probably exceptions) So, if you don't use STUN at all and know your clients well, you should be able to reduce the use of rtp proxy even more... g-) Juha Heinanen wrote: > Greger V. Teigre writes: > >> - PSTN-SIP when the SIP client is behind symmetric > > greger, > > why does pstn-sip require use of media/rtp proxy if sip client is > behind symmetric nat? can't media/rtp proxy send to the same ip/port > where media is coming from the client? > > -- juha

4 7

[Serusers] weird routing Asterisk -> ser
by Barry Murphy 04 Apr '05

04 Apr '05

Ok, So i'm trying to get ser to accept calls via asterisk (which I use for my voip termination). I dialed 85283363 from asterisk, however my SER receives the call and for some reason forwards the call to 64273040757 ########################################### # in extension.conf ########################################### exten => _8.,1,Dial(SIP/max.fast.co.nz/${EXTEN},60,t) exten => _8.,2,Hangup ########################################### # in ser.cfg (i'm guessing this accepts calls with the prefix 8 ########################################### if (method == "INVITE") { if (uri =~ "sip:8[0-9].@*"){ log(1, "Forwarding to Asterisk\n"); rewritehostport("202.150.105.150:5070"); t_relay(); break; } } The sip from shows call coming from 2206, which is correct, it sees it going to 82583363, the INVITE goes to 64273040757. caller_UUID callee_UUID sip_from sip_to sip_status sip_method i_uri o_uri from_uri to_uri sip_callid username domain fromtag totag time timestamp caller_deleted callee_deleted Barry <sip:2206@voip.fast.co.nz>;tag=2604881704 <sip:85283363@voip.fast.co.nz>;tag=0011219c488307c... 200 INVITE sip:85283363@voip.fast.co.nz sip:64273040757@voip.fast.co.nz sip:2206@voip.fast.co.nz sip:85283363@voip.fast.co.nz 5E6EFD0E-A920-412B-B760-C7F29E96E7AC(a)10.200.3.173 2206 voip.fast.co.nz 2604881704 0011219c488307ca4af6c9fb-0b9b8c1b 2005-04-04 01:13:59 20050404131359 0 0

2 1

Re: [Serusers] multiport hardware to be used with anonlue/digital pbx's mriadian
by Iqbal 04 Apr '05

04 Apr '05

Hi Multiport, I mean more than one port :-), basically the pbx with have a E1 coming into it, which is 30 lines. Now if theother end of the pbx is connected to 40 extensions in the office, I really want all 40 to be able to make a voip call, rather than getting engaged tone. The customer doesnt want to replace the existing pbx, hence would want to put something behind it, which connects to the IP world. hence by dialing *1 [or whatever prefix] the call would hit the pbx, it would then send that out via the IP device as a VoIP call. I dont really want to build a asterisk setup for them locally, but would just rather go for a out of the box solutions which already exists... Iqbal Shidan wrote: >Hi just wondering what you mean by multiport devices and what issues >you've had. We have integrated M1s and Norstars with Asterisk in a >hybrid voip/key system environment. > >On Apr 3, 2005 12:09 PM, Iqbal <iqbal(a)gigo.co.uk> wrote: > > >>Hi >> >>Has anyone used meridian pbx and connected that to a multiport voip box, >>or does anyone have any recommendations in general on multiport devices >>and PBX setups >> >>tks >> >>Iqbal >> >>_______________________________________________ >>Serusers mailing list >>serusers(a)lists.iptel.org >>http://lists.iptel.org/mailman/listinfo/serusers >> >> >> > >. > > >

1 0

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

04 Apr '05

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.

2 1

[Serusers] asterisk or ser
by T. Maron 04 Apr '05

04 Apr '05

Hello, I was playing with ser and asterisk for a few weeks but I couldn't make a decision what is better to use for medium voip network (more than 500 terminals in several locations, sepatate pstn gw, basic services - voice and voicebox). Asterisk looks like a very feature-rich voip application and ser more flexible. Can anyone share some experiences deploying either of the two voip systems? The maintenance effort is what weight more for us, we are looking for qualified support to install the platform once we are decided what to use. Many thanks in advance, TM PS. one can write me directly if the content of the mail is intended to be private. __________________________________ Do you Yahoo!? Make Yahoo! your home page http://www.yahoo.com/r/hs

1 0

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

04 Apr '05

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.

4 3

[Serusers] 'localhost' in the `serweb' login page
by Timur Elzhov 04 Apr '05

04 Apr '05

Dear SER experts, I unpacked 'serweb' (last CVS version) under www-trees on the two Linux machines. I modified 'config_path.php' only, just to change $config->root_path to "/serweb/html/" value, nothing else. However, on the first machine the 'localhost' word is appeared instead of right domain name. Moreover, this 'serweb' login form refuses any registered user to being logged in, with error "Bad username or password" (Of course, there is no problem with registering with `serctl' tool). The second machine shows the right domain name, and allows registered users to log in by the serweb form. Thank you for any help in advance. -- Best regards, Timur Elzhov Warelex LLC

2 1

[Serusers] t_replicate can't call to registered endpoint
by Raymond Chen 04 Apr '05

04 Apr '05

Dear all We have setup two SER servers which replicates endpoint registration info to the second server as follow: Server A: if (method=="REGISTER") { #if (src_ip=="xxx.xxx.xxx.xxx") { # save("location"); # break; #}; if (!www_authorize("", "subscriber")) { www_challenge("", "1"); break; }; if (!src_ip==xxx.xxx.xxx.xxx) { t_replicate("xxx.xxx.xxx.xxx", "5060"); }; save("location"); break; }; Server B: save_noreply("location"); registration process went fine. But when we use Server B to call the replicated endpoint, endpoint does not response to the INVITE message. Port and IP both are correct in the INVITE message. What could be the problem? Regards

2 1

[Serusers] avpops - how to fake a registration
by Java Rockx 04 Apr '05

04 Apr '05

Hi All. I'm using ser-0.9.1 with auth_db enabled for user registration stuff. I need to fake a REGISTRATION under certain circumstances. What I want to do is sl_send_reply("200", "OK") when I get a REGISTER message from user 697. I don't want to actually call the save("location") method because I do not want to store 697 in the database or in ser's cache. So how can I sl_send_reply() and include the <Contact> header which the save() function would normally insert in to the response? I'm thinking I could use AVPOPs somehow, but I'm not sure. Can this be done? Regards, Paul

2 6

← Newer
1
...
63
64
65
66
67
68
69
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