- sr-users - kamailio.org

[Serusers] red hat enterprise es 3
by finjurdata 30 Mar '05

30 Mar '05

Which package of ser/sip server workd with red hat enterprise es version 3

1 0

[Serusers] SER registration to a SIP Service
by Narcis GRATIANU 30 Mar '05

30 Mar '05

Hello ! My company currently uses SER to handle all internationl calls. Recently, we switched to another SIP VOIP service provider, that requires from us to authenticate using an username and password in order to send the calls to him. What configuration do i need to do in the sip.cfg file for that ? His sip address is: sip.voipcom.ro, username is "user" and password is "pass" (without the "). Thank you !

3 2

[Serusers] SER on different port & "myself"
by Timur Elzhov 30 Mar '05

30 Mar '05

Hello dear SER experts. I need to run SER on the different port in same reason. However, in this case `if (uri == myself)' is not true and the block after them is not proceed. When I run SER on the defaut 5060 port, all the OK and the above condition is true. Why? Now, to feed this condition instead of using "myself" I use regexp, i.e. if (uri =~ "(.+@)?(sip\.)?mydomain\.com([:;\?].*)?$") { ... } But, I will probably need to support different SER servers for several domains, and it would be more convinient for me to have the same config file for all of them. Thank you very much. -- Best regards, Timur V. Elzhov COO Warelex LLC

1 0

[Serusers] Can't make latest SIP-Version
by Tina 30 Mar '05

30 Mar '05

Hi Dirk, try to use gmake instead of make: gmake all; gmake install Tina __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

2 1

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

30 Mar '05

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.

3 2

[Serusers] Voicemail redirection
by Jack Damn 30 Mar '05

30 Mar '05

Hi, I am a new user to SER and here is what I would like it to do: Is it possible to have SER forward (or rewrite) the call to another destination (will be a voicemailbox in this scenario) after a certain timeout in 180 (ringing) ? If yes, can anyone give me a clue how to implement this ? Thank you, Jack

1 0

[Serusers] 477 response when registered with TCP
by mahesh 30 Mar '05

30 Mar '05

Hi all, I am using the following network configuration. HOST1---NAT---Internet---HOST2 HOST1 and HOST2 are windows XP machines with SJPhone softwares. The NAT box has SIP ALG(Application Level Gateway), which modifies the SIP packets to replace the Private IP address with the Public IP address. I am registering with iptel.org proxy server using TCP from both the machines. I am able to make a call from HOST1 to HOST2. But when i try to make a call from HOST2 to HOST1, i get an error which says, "477 Unfortunately error on sending to next hop occurred(477/TM)". When I register using UDP, then i do not see this problem. Could someone tell me what I am missing here. Thanks Mahesh

1 0

[Serusers] PA module problems/questions
by serusers＠jtoga.org 30 Mar '05

30 Mar '05

Looking for a sanity check... Starting to use the pa module and it seems like info may be missing in a notify - or not...;-/ Thanks in advance. User "joe" subscribes to "george" (who is online) SER responds with OK to subscribe SER sends NOTIFY to "joe" regarding "george" (ngrep below) There doesn't seem to be much in the body and the client doesn't see the presence as 'online'..... Is this a legitemate Notify, shouldn't it have 'status' info in the body?... xx.xx.xx.xx:5060 -> xx.xx.77.132:2341 NOTIFY sip:xx.xx.77.132:2341 SIP/2.0..Via: SIP/2.0/UDP 69.90.155.71;branch=z9hG4bKf53c.d25816d1.0..To: "joe" <s ip:joe@sip.acme.com>;epid=5b16759b5f;tag=6073e9d23fba4653ba872416ee788462..From: <sip:george@sip.acme.com>;tag=90131219488138b579c689b75333dc09-7a3d..CSeq: 142 NOTIFY..Call-ID: 77d5a344c9be47af8b4fb0cc2eb456b6@10 .1.1.162..Content-Length: 192..User-Agent: Sip EXpress router(0.9.0 (i386/linux))..Event: presence..Content-Typ e: application/xpidf+xml..Subscription-State: active;expires=3591....<?xml version="1.0"?>..<!DOCTYPE presence PU BLIC "//IETF//DTD RFCxxxx XPIDF 1.0//EN" "xpidf.dtd">..<presence>..<presentity uri="sip:george@sip.acme.com ;method=SUBSCRIBE"/>..</presence>.. -- Jim Toga COO, FWD/LibréTel FWD# 17670 (o) 631-961-8989 (m) 508-308-2913

1 0

[Serusers] Getting Started - Issue 03 covers NAT Support
by Simon Miles 29 Mar '05

29 Mar '05

Dear All, Paul, Greger and myself would like you to know that the next issue of 'Getting Started' is now available on the www.ONsip.org <http://www.onsip.org/> web site. This new version builds upon the last issue by adding NAT support. We have covered both mediaproxy AND rtpproxy and explain how to implement either. Example config files are explained and these can be downloaded from the web site as well. Many thanks for all the very supportive feedback we have received. We are doing this for the community and always welcome feedback on the document to make it more readable etc. Comments are welcome on the www.ONsip.org <http://www.onsip.org/> web site, goto Forums and select the Getting Started Feedback area. To download the document, go to the download section. We hope this is of benefit to the Community. Thanks Paul, Simon, Greger

2 1

[Serusers] Call Forwarding (No-Answer, Busy)
by reticent 29 Mar '05

29 Mar '05

I've been attempting to implement some call forwarding (noans, busy) logic into my SER script without any luck So far i've tried CPL (which doesn't seem to work at all for call forward busy and apparently doesn't work properly with no answer) (I must say, CPL seems like an excellent feature. Its really a shame that many of its useful functions aren't yet supported in SER) I've also tried setting the "fr_timer_avp" TM parameter from an AVP database and trying to forward the call once the timer expires, so far this has proven fruitless. I'm curious if anyone has found a solution to this problem, or if it possible.

2 2

[Serusers] SER Softphone and IM cleints
by Prameet Chhabra 29 Mar '05

29 Mar '05

Hello, I am new member of the alias. I have installed SER with MySQL and did some user provisioning. Where can I get SIP softphones or IM clients that are compatible with SER. Please adivice. Prameet Chhabra

5 6

[Serusers] Anonymization/uac-module questions
by Andreas Granig 29 Mar '05

29 Mar '05

Hi all, First of all two common anonymization questions: Is it save for anonymization to alter the Contact-Header in SER if record_route() is used to strip the username/IP? If not, how do you accomplish this correctly? And is there a way to modify the SDP body to change the o-Field to change/remove the IP of the owner/creator? Then an uac issue: The uac module (backported to ser-0.9 with "MANUAL RESTORE" mode) works well for me in this scenario: The group "clir" indicates anonymization, and the config looks like this: modparam("uac", "from_restore_mode", 2) route { # ... if(is_user_in("From", "clir")) { setflag(7); uac_replace_from("Anonymous", "sip:anonymous@my.domain"); } t_on_reply("1"); t_relay(); } onreply_route[1] { if(isflagset(7)) uac_restore_from(); } When A calls B and A is in group "clir", the From-Header sent to B is anonymized, and responses to A are restored correctly. But when B hangs up, the UAC of B (Cisco-ATA186 or Mediatrix 2102) changes From and To in the BYE message, so A receives the anonymized From-Header as To-Header. This is because uac_restore_from() only restores the From-Header (as the name of the function says ;o) ), not the To-Header if there is a vsf-Parameter available. This isn't correct behaviour, is it? Also the Cisco-ATA strips off the vsf-Parameter in the BYE-Message so it isn't available anyhow, but this seems to be a Cisco-Bug!? Any Comments/Ideas? Andy

6 19

RE: [Serusers] Forwarding to a LCS server
by Mimmus 29 Mar '05

29 Mar '05

> looks like the LCS doesn't find a matching entry in its > "routing table". mydomain.it is its native domain. All messages come in with user(a)mydomain.it. How is it possible? DV

1 0

[Serusers] parallel forking best practice?
by Jev 29 Mar '05

29 Mar '05

Hi All, For the 0_9_0 branch, what is the 'best practice' for implementing parallel forking? We used to be able to point one alias at several accounts, but that feature has regressed. Thanks, -Jev

6 8

[Serusers] Help me!!!
by Baudilio Zapata 29 Mar '05

29 Mar '05

Hello to all... I am nascent and I need aid because it corresponds to me to test with the SER and Linux, and do not have idea of as one settles and it forms, I believe that I did was to download the SER-0.8.14, but not like installing it, forming it and to make tests... If somebody knows help me please! NOTE: Excuse me, I don't speaking english... Atentamente... Baudilio O. Zapata G. Teléfono: 0414-1213474 e-mails: sistemasbozg(a)yahoo.es sistemasbozg(a)cantv.net baudilio25(a)hotmail.com ______________________________________________ Renovamos el Correo Yahoo!: ¡250 MB GRATIS! Nuevos servicios, más seguridad http://correo.yahoo.es

1 0

[Serusers] help me
by Baudilio Zapata 29 Mar '05

29 Mar '05

Hello to all... I am nascent and I need aid because it corresponds to me to test with the SER and Linux, and do not have idea of as one settles and it forms, I believe that I did was to download the SER-0.8.14, but not like installing it, forming it and to make tests... If somebody knows help me please! NOTE:I don't speaking spanish... Atentamente... Baudilio O. Zapata G. Teléfono: 0414-1213474 e-mails: sistemasbozg(a)yahoo.es sistemasbozg(a)cantv.net baudilio25(a)hotmail.com ______________________________________________ Renovamos el Correo Yahoo!: ¡250 MB GRATIS! Nuevos servicios, más seguridad http://correo.yahoo.es

1 0

[Serusers] help me
by Baudilio Zapata 29 Mar '05

29 Mar '05

Hello to all... I am nascent and I need aid because it corresponds to me to test with the SER and Linux, and do not have idea of as one settles and it forms, I believe that I did was to download the SER-0.8.14, but not like installing it, forming it and to make tests... If somebody knows help me please! NOTE:I don't speaking spanish... Atentamente... Baudilio O. Zapata G. Teléfono: 0414-1213474 e-mails: sistemasbozg(a)yahoo.es sistemasbozg(a)cantv.net baudilio25(a)hotmail.com ______________________________________________ Renovamos el Correo Yahoo!: ¡250 MB GRATIS! Nuevos servicios, más seguridad http://correo.yahoo.es

1 0

[Serusers] Forwarding to a LCS server
by Mimmus 29 Mar '05

29 Mar '05

Hi, I'm setting up SER to act as a proxy between Asterisk and Microsoft LCS (to enable TCP2UDP translation needed to speak with Microsoft LCS). I'd like to keep configuration the simplest as possible. Unfortunately, LCS refuses INVITE with a: <504: Server Timeout> as you can see in following output from 'ngrep' (some security sanityzing performed): ####### T xxx.yyy.64.118:32834 -> 10.99.1.9:5060 [AP] INVITE sip:myuser@mydomain.it SIP/2.0. Max-Forwards: 10. Record-Route: <sip:myuser@xxx.yyy.64.118;transport=tcp;r2=on;ftag=as12c76469;l r=on>. Record-Route: <sip:myuser@xxx.yyy.64.118;r2=on;ftag=as12c76469;lr=on>. Via: SIP/2.0/TCP xxx.yyy.64.118;branch=z9hG4bK1988.c780cdd1.0. Via: SIP/2.0/UDP xxx.yyy.64.118:5061;branch=z9hG4bK184e7f66. From: "01234564" <sip:01234564@xxx.yyy.64.118:5061>;tag=as12c76469. To: <sip:myuser@xxx.yyy.64.118>. Contact: <sip:01234564@xxx.yyy.64.118:5061>. Call-ID: 3b3a9d59133196ef4dfa27836e47cea9(a)xxx.yyy.64.118. CSeq: 102 INVITE. User-Agent: Asterisk PBX. Date: Tue, 29 Mar 2005 17:34:32 GMT. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER. Content-Type: application/sdp. Content-Length: 267. . v=0. o=root 14974 14974 IN IP4 xxx.yyy.64.118. s=session. c=IN IP4 xxx.yyy.64.118. t=0 0. m=audio 11980 RTP/AVP 8 3 0 101. a=rtpmap:8 PCMA/8000. a=rtpmap:3 GSM/8000. a=rtpmap:0 PCMU/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=silenceSupp:off - - - -. # T 10.99.1.9:5060 -> xxx.yyy.64.118:32834 [AP] SIP/2.0 100 Trying. Via: SIP/2.0/TCP xxx.yyy.64.118;branch=z9hG4bK1988.c780cdd1.0;ms-received-port=3 2834;ms-received-cid=1d00. Via: SIP/2.0/UDP xxx.yyy.64.118:5061;branch=z9hG4bK184e7f66. From: "01234564" <sip:01234564@xxx.yyy.64.118:5061>;tag=as12c76469. To: <sip:myuser@xxx.yyy.64.118>. Call-ID: 3b3a9d59133196ef4dfa27836e47cea9(a)xxx.yyy.64.118. CSeq: 102 INVITE. Content-Length: 0. . ## T 10.99.1.9:5060 -> xxx.yyy.64.118:32834 [AP] SIP/2.0 504 Server time-out. Via: SIP/2.0/TCP xxx.yyy.64.118;branch=z9hG4bK1988.c780cdd1.0;ms-received-port=3 2834;ms-received-cid=1d00. Via: SIP/2.0/UDP xxx.yyy.64.118:5061;branch=z9hG4bK184e7f66. From: "01234564" <sip:01234564@xxx.yyy.64.118:5061>;tag=as12c76469. To: <sip:myuser@xxx.yyy.64.118>;tag=9B5EAEFA3B5764273F459C938E732306. Call-ID: 3b3a9d59133196ef4dfa27836e47cea9(a)xxx.yyy.64.118. CSeq: 102 INVITE. Content-Length: 0. . ################################################################# Logs from LCS shows this message: Text: Unable to route the request Result-Code: 0xc3e91002 SIP-Start-Line: INVITE sip:myuser@mydomain.it SIP/2.0 SIP-Call-ID: 572410cc05c62bfe720cbc4c6cde6b0b(a)xxx.yyy.64.118 SIP-CSeq: 102 INVITE Data: Non-trusted source sent an FQDN/IP that doesn't match a routing table rule ################################################################## This is my ser.cfg: debug=9 # debug level (cmd line: -dddddddddd) log_stderror=yes # (cmd line: -E) check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) listen=xxx.yyy.64.118 alias="mydomain.it" alias="xxx.yyy.64.118" fifo="/tmp/ser_fifo" 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" modparam("usrloc", "db_mode", 0) modparam("rr", "enable_full_lr", 1) route{ # initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); break; }; if ( msg:len > 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 if (loose_route()) { t_relay(); break; }; # reject REGISTER attempts for now if (method=="REGISTER") { sl_send_reply( "503", "Registration Unavailable" ); break; }; # Forward to LCS if text usernames if (uri =~ "sip:[a-zA-Z\.\_]*@*") { log(1, "Forwarding to LCS\n"); rewritehostport("mydomain.it"); # forward to current uri now; use stateful forwarding; that # works reliably even if we forward from TCP to UDP if (!t_relay_to_tcp("eco.pitagora.it", "5060")) { sl_reply_error(); }; break; } # Forward to Asterisk if numerical username if (method == "INVITE") { if (uri =~ "sip:9[0-9]{10}@*") { log(1, "Forwarding to Asterisk\n"); rewriteport("5061"); # 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; } } sl_send_reply("404", "Not Found"); } ############################################################## Any help? Thanks in advance... Domenico Viggiani

2 1

[Serusers] Ayuda!!!!
by Baudilio Zapata 29 Mar '05

29 Mar '05

Hola a todos... soy principiante y necesito ayuda porque me corresponde hacer una prueba con el SER y Linux, y no tengo idea de como se instala y configura, lo unico que creo que hice fue bajar el SER-0.8.14, pero no se como instalarlo, configurarlo y realizar pruebas... Si alguien sabe por favor ayudenme!!! --- Simon Miles <simon(a)SystemsRM.co.uk> wrote: > Dear All, > > Paul, Greger and myself would like you to know that > the next issue of > 'Getting Started' is now available on the > www.ONsip.org > <http://www.onsip.org/> web site. > > This new version builds upon the last issue by > adding NAT support. > > We have covered both mediaproxy AND rtpproxy and > explain how to > implement either. Example config files are explained > and these can be > downloaded from the web site as well. > > Many thanks for all the very supportive feedback we > have received. We > are doing this for the community and always welcome > feedback on the > document to make it more readable etc. Comments are > welcome on the > www.ONsip.org <http://www.onsip.org/> web site, > goto Forums and select > the Getting Started Feedback area. > > To download the document, go to the download > section. > > We hope this is of benefit to the Community. > > > Thanks > > > Paul, Simon, Greger > > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers > Atentamente... Baudilio O. Zapata G. Teléfono: 0414-1213474 e-mails: sistemasbozg(a)yahoo.es sistemasbozg(a)cantv.net baudilio25(a)hotmail.com ______________________________________________ Renovamos el Correo Yahoo!: ¡250 MB GRATIS! Nuevos servicios, más seguridad http://correo.yahoo.es

1 0

[Serusers] X-Lite behind NAT + SER
by Timur Elzhov 29 Mar '05

29 Mar '05

Hello guys. I have X-Lite client on WinXP, which in installed on the Virtual Machine (VM), which in turn is installed under Linux host on the public host nf034.jinr.ru (IP 159.93.29.34). For sharing single network card between Linux host and Windows guest systems, VM uses the NAT technology. At first I run SER on Linux at nf034.jinr.ru:5060 and point them as a proxy for X-Lite in its configuration menu. I successfully logged X-Lite to the SER proxy server, and then looked at the X-Lite diagnostic (URI to which X-Lite is assigned is sip:test@nf034.jinr.ru): ====================== -- cut -- ====================== X-Lite release 1103m build stamp 14262 License key: 334EB1FDABF14B00BD22E1C2442210A4 Established SIP protocol listen on: 172.16.218.128:5060 Discovered Port Restricted Single Mapped Port Symmetric NAT Firewall SIP: 172.16.218.128:5060 RTP: 172.16.218.128:8000 NAT: 159.93.29.34 Discovering external SIP port on symmetric firewall... PROXY#0: 159.93.29.34:5060 SEND TIME: 29675015 SEND >> 159.93.29.34:5060 REGISTER sip:nf034.jinr.ru SIP/2.0 Via: SIP/2.0/UDP 159.93.29.34:5060;rport;branch=z9hG4bK2E70AA83DC6248CF85502BCD5E251FC7 From: Test User <sip:test@nf034.jinr.ru>;tag=1898047871 To: Test User <sip:test@nf034.jinr.ru> Contact: "Test User" <sip:test@159.93.29.34:5060> Call-ID: 3DE2CFB300024F7085AEB4169AF1E048(a)nf034.jinr.ru CSeq: 48982 REGISTER Expires: 1800 Max-Forwards: 70 User-Agent: X-Lite release 1103m Content-Length: 0 ====================== -- cut -- ====================== So, glance at the Contact field gives that X-Lite maps 172.16.218.128:5060 to the public IP 159.93.29.34 but with the *same* port 5060! The same we can see at the SER 'location' table in mysql/ser table: +----------+----------------------------+ | username | contact | +----------+----------------------------+ | test | sip:test@159.93.29.34:5060 | +----------+----------------------------+ But, I have SER running exactly at the 159.93.29.34:5060 that leads to the ports conflict. How can I resolve this situation? Thank you! -- Best regards, Timur V. Elzhov COO Warelex LLC

1 0

[Serusers] Callflow to monitor SIP messages
by Luis Leite 29 Mar '05

29 Mar '05

Hi, I'm trying to install a tool to monitor SIP messages between UA and SER. "Callflow" is a: callflow sequence diagram generator http://callflow.sourceforge.net/ Anyone succeded in installing this in Fedora 3 ?

4 5

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

29 Mar '05

I will try this and see how I get on....Thank you again for your patience and help. ---- 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 11:43:07 -0500 >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.

1 0

[Serusers] SER Performance
by ljzhang 29 Mar '05

29 Mar '05

Hi, I'm a novice here. Only yesterday I began to use SER. Now I tested its basic calling function, and found its rate of processing messages is very high. It's really fantastic. But furthermore, could you tell me whether there is memory leak in it, and it will crash after a few days' or a few hours' running? In order to keep its running normal, how should I configure my computer? Thanks a lot 　　　　　　　　jenny 　　　　　　　　xueyou38(a)163.com 　　　　　　　　　　2005-03-29

2 1

Re: [Serusers] Self registering tool for X-lite with SER
by Andr�s Parra L. 29 Mar '05

29 Mar '05

Ladislav: X-Ten calls that "hard coding" and the sell you licences. We contacted these guys last week and they say the minimun amount of X-Lites's that they sell are 27K units. So, if you are looking for GNU try using a sip stack such as oSIP to create your own app. Andres Parra __________________________________ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo

1 0

[Serusers] SIP 477 error when registered with TCP
by mahesh 29 Mar '05

29 Mar '05

Hi all, I am using the following network configuration. HOST1---NAT---Internet---HOST2 HOST1 and HOST2 are windows XP machines with SJPhone software. The NAT box has SIP ALG(Application Level Gateway), which modifies the SIP packets to replace the Private IP address with the Public IP address. I am registering with iptel.org proxy server using TCP from both the machines. I am able to make a call from HOST1 to HOST2. But when i try to make a call from HOST2 to HOST1, i get an error which says, "477 Unfortunately error on sending to next hop occurred(477/TM)". When I register using UDP, then i do not see this problem. Could someone tell me what I am missing here. Thanks Mahesh

2 1

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