sr-users March 2005

sr-users@lists.kamailio.org

250 participants
627 discussions

[Serusers] HELP: mediaproxy re-INVITE NAT detection
by Java Rockx 30 Mar '05

30 Mar '05

Hi All. I'm using ser-0.9.1. Is there a way to determine if mediaproxy is in use for an existing SIP call so that re-INVITE messages can avoid losing audio when one or the other SIP UAs are NATed? We do not proxy RTP streams unless one or more SIP UAs are NATed. But on re-INVITE messages I cannot figure out how to test the destination of the re-INVITE for the UAs NAT status. I've scoured the archives and found a few related articles http://lists.iptel.org/pipermail/serdev/2004-March/001515.html http://lists.iptel.org/pipermail/serusers/2004-March/006806.html But nothing has led me to a solution. I cannot just use lookup("location") and test the nat_flag since that won't always work on re-INVITEs. A mediaproxy function for something like is_existing_session() would be awesome to lookup the Call-ID in the existing mediaproxy sessions. What am I missing? Regards, Paul

4 4

[Serusers] ser.cfg
by Bruno Oliveira 30 Mar '05

30 Mar '05

Hi ! I finished to install the server SER, more when it initiates syslog shows following msg: ser: "WARNING: could not rev. decides [IP of the server]" Anyone knows because?

1 0

[Serusers] ser+asterisk+voicemail
by hofi 30 Mar '05

30 Mar '05

hi all configuration: inalp gw (pstn) ------> ser ------> asterisk (only voicemail) the following problems occur: 1) ser forwards the call to asterisk (if the user is in the voicemail group) if the client does not answer after 30 sec. from sip to sip is working. but if a call comes from the pstn to a sip client, the client rings and hangs up after 30 sec. ser then forwards it to the asterisk, but the pstn call keeps on ringing and no voicemail is to hear. ser writes the following error Mar 29 13:24:39 sip /usr/local/sbin/ser[7017]: ++++++++++++INVITE****************** Mar 29 13:24:39 sip /usr/local/sbin/ser[7017]: ++++++++++++voicemail*********************** Mar 29 13:25:19 sip /usr/local/sbin/ser[7022]: ++++++++++++Failure Route****************** Mar 29 13:25:19 sip /usr/local/sbin/ser[7022]: ++++++++++++Failure Route****************** Mar 29 13:25:19 sip /usr/local/sbin/ser[7017]: ++++++++++++voicemail*********************** Mar 29 13:25:19 sip /usr/local/sbin/ser[7016]: ERROR: t_should_relay_response: status rewrite by UAS: stored: 408, received: 200 Mar 29 13:25:20 sip /usr/local/sbin/ser[7017]: ERROR: t_should_relay_response: status rewrite by UAS: stored: 408, received: 200 Mar 29 13:25:21 sip /usr/local/sbin/ser[7016]: ERROR: t_should_relay_response: status rewrite by UAS: stored: 408, received: 200 Mar 29 13:25:24 sip last message repeated 3 times Mar 29 13:25:28 sip /usr/local/sbin/ser[7015]: ++++++++++++Loose Route****************** Mar 29 13:25:28 sip /usr/local/sbin/ser[7014]: contact_parser(): Empty body Mar 29 13:25:28 sip /usr/local/sbin/ser[7014]: parse_contact(): Error while parsing Mar 29 13:25:28 sip /usr/local/sbin/ser[7014]: get_contact_uri: Error while parsing Contact body 2) if ua1 call ua2 (and ua2 is in the voicemail group) and ua1 hangs up ser forwards to asterisk and the voicemail is run in the background, but instead the call should be cancelled and not forwarded to the voicemail does anyone know about these problems? regards raid ser config snip: loadmodule "/usr/local/lib/ser/modules/sl.so" loadmodule "/usr/local/lib/ser/modules/tm.so" # ------------- tm parameters modparam("tm", "fr_timer", 30) modparam("tm", "fr_inv_timer", 25) modparam("tm", "wt_timer", 5) modparam("tm", "fr_inv_timer_avp", "inv_timeout") route { if (lookup("location") | lookup("aliases")) { if (is_user_in("Request-URI", "voicemail")) { log (1, "++++++++++++voicemail***********************"); t_on_failure("1"); avp_write("i:30", "inv_timeout"); t_relay(); route(2); break; } else { log (1, "++++++++++++no voicemail********************"); route(2); break; } } } route [2] { if (uri=~"[@:](192\.168\.|10\.|172\.(1[6-9]|2[0-9]|3[0-1])\.)" && !search("^Route:")){ sl_send_reply("479", "We don't forward to private IP addresses"); break; }; if (isflagset(2)) { force_rtp_proxy(); }; t_on_reply("1"); if (!t_relay()) { sl_reply_error(); }; } failure_route[1] { log (1, "++++++++++++Failure Route******************"); revert_uri(); rewritehostport("XXX.XXX.XXX.XXX:5060"); append_branch(); t_on_failure("1"); t_relay(); break(); }

4 6

[Serusers] Load mysql.so ERROR!!
by ljzhang 30 Mar '05

30 Mar '05

Hi, I uncomment the line of ser.cfg: loadmodule "/usr/lib/ser/modules/mysql.so" But when I start ser, I met the following error: ERROR: load_module: could not open module </usr/lib/ser/modules/mysql.so>: /usr/lib/libmysqlclient.so.10: symbol errno, version GLIBC_2.0 not defined in file libc.so.6 with link time reference? Can you tell me why? Note: libmysqlclient.so.10 is provided by MySQL-shared-3.23.54a-1.i386 MySQL version is 4.0.12 Thanks a lot. 　　　　　　　　jenny 　　　　　　　　xueyou38(a)163.com 　　　　　　　　　　2005-03-30

1 0

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

30 Mar '05

Hi Alex, Yes /var/run exists on the system. I got the following from "ls -l /var". I am logged in as root. drwxr-xr-x 12 root root 856 Mar 30 13:45 run Any other suggestions? Regards, Aisling. Aisling, Can you verify that directory /var/run actually exists on your system? also check the permissions: ls -l /var Are you logging in the system as root or some other user? The problem you may have is that you don't have permissions to access /var/run directory Alex ---- Original Message ---- From: ashling.odriscoll(a)cit.ie To: greger(a)teigre.com, ashling.odriscoll(a)cit.ie Subject: Re: [Serusers] SER 0.8.14 to 0.9.0 Date: Wed, 30 Mar 2005 13:39:26 +0100 >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.

1 0

[Serusers] PSTN Gateway Route Doesn't Work
by Ozan Blotter 30 Mar '05

30 Mar '05

I've created users beginning with 833 and 834 prefix, my aim is whenever a user needs to call numbers not beginning with 833 or 834 prefix the call will be directed to 212.154.32.154. It was working before but so many broken things and especially bad voice quality, now voice works great with below config and doing port forwarding for 5060 udp and tcp in UA's gateways a SIP2SIP call is possible without sucking SER's bandwidth, when i uncomment the lines ser does not work and don't know why. It was working before but since i've downloaded newer SER.CFG it doesn't work for me and i'm still a newbie. if (uri==myself) { if (method=="REGISTER") { # if (!(uri=~"sip:(833)|(834)")) { # t_relay_to_udp("212.154.32.154","5060"); save("location"); break; }; My complete SER.CFG as follows; # # $Id: ser.cfg,v 1.27 2005/03/10 14:16:25 andrei Exp $ # # simple quick-start config script # # ----------- global configuration parameters ------------------------ #debug=3 # debug level (cmd line: -dddddddddd) #fork=yes #log_stderror=no # (cmd line: -E) #memlog=5 # memory debug log level #log_facility=LOG_LOCAL0 # sets the facility used for logging (see syslog(3)) /* Uncomment these lines to enter debugging mode fork=no log_stderror=yes */ check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) #port=5060 #children=4 fifo="/tmp/ser_fifo" #user=ser #group=ser #fifo_user=ser # owner of the ser fifo #fifo_group=ser #fifo_mode=0660 # fifo's permissions #disable_core=yes #disables core dumping #open_fd_limit=1024 # sets the open file descriptors limit #mhomed=yes # usefull for multihomed hosts, small performance penalty #disable_tcp=yes #tcp_accept_aliases=yes # accepts the tcp alias via option (see NEWS) # # ------------------ module loading ---------------------------------- # Uncomment this if you want to use SQL database #loadmodule "/usr/local/lib/ser/modules/mysql.so" loadmodule "/usr/local/lib/ser/modules/sl.so" loadmodule "/usr/local/lib/ser/modules/tm.so" loadmodule "/usr/local/lib/ser/modules/rr.so" loadmodule "/usr/local/lib/ser/modules/maxfwd.so" loadmodule "/usr/local/lib/ser/modules/usrloc.so" loadmodule "/usr/local/lib/ser/modules/registrar.so" loadmodule "/usr/local/lib/ser/modules/textops.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! #loadmodule "/usr/local/lib/ser/modules/auth.so" #loadmodule "/usr/local/lib/ser/modules/auth_db.so" # ----------------- setting module-specific parameters --------------- # -- usrloc params -- modparam("usrloc", "db_mode", 0) # Uncomment this if you want to use SQL database # for persistent storage and comment the previous line #modparam("usrloc", "db_mode", 2) # -- auth params -- # Uncomment if you are using auth module # #modparam("auth_db", "calculate_ha1", yes) # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) # #modparam("auth_db", "password_column", "password") # -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1) # ------------------------- request routing logic ------------------- # main routing logic 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 if (!method=="REGISTER") record_route(); # subsequent messages withing a dialog should take the # path determined by record-routing if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); break; }; if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); route(1); break; }; # 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") { # if (!(uri=~"sip:(833)|(834)")) { # t_relay_to_udp("212.154.32.154","5060"); save("location"); break; }; lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); break; }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); break; }; }; append_hf("P-hint: usrloc applied\r\n"); route(1); } route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; }

2 1

[Serusers] Freeradius Authentication Problem
by Nimal Ratnayake 30 Mar '05

30 Mar '05

Hi, I am using ser 0.8.14 and FreeRadius 1.0.2 on a FreeBSD 5.3 system. When I try to authenticate using the auth_radius module, ser debug log reports failure, although freeradius debug says that an Access-Accept packet has been sent. Excerpts from both logs are appended. I am able to authenticate the same user using radclient. What could be wrong? Any help for solving this will be much appreciated. Nimal Ratnayake ser debug log ============= 0(43510) check_nonce(): comparing [424a8e7ce5e7651fa1c028c28d08e33d603fe2da] and [424a8e7ce5e7651fa1c028c28d08e33d603fe2da] 0(43510) res: -2 0(43510) radius_authorize_sterman(): Failure freeradius debug log ==================== auth: type "digest" Processing the authenticate section of radiusd.conf modcall: entering group authenticate for request 0 A1 = nimalr:pdn.ac.lk:xxxxxxx <- password changed by me A2 = REGISTER:sip:pdn.ac.lk KD = c054dd23cd7bcd4c70b75b4f447906cd:424a8e7ce5e7651fa1c028c28d08e33d603fe2da:4ea8a5db028bb11e4698dcaef8f4c6d9 modcall[authenticate]: module "digest" returns ok for request 0 modcall: group authenticate returns ok for request 0 Sending Access-Accept of id 253 to 127.0.0.1:60346

1 0

[Serusers] cvs
by finjurdata 30 Mar '05

30 Mar '05

How do I create my own sip/ser package is there a step by step guide on how to do this?? have not done this so far. please advise

1 0

[Serusers] Arbitrarily altering the "Contact:" field
by reticent 30 Mar '05

30 Mar '05

I've got a situation where i need to replicate registrations to an outside proxy, a simple replicate wont work because i need the registration on the outside proxy to reference the SER proxy and not the client directly. The one requirement is that i know (in a scripting context) what the username of the registration is so i can construct a Contact that contains it. The only function i've found that could do this is the subst(///) function in the textops.so module, however its acting very strangely. Ex. subst('/^Contact:.*sip:([0-9]+)@.*$/Contact: <sip:\1@!OUTSIDE_PROXY!>/'); Seems to match properly, but inspecting the packet as its routed out (using ngrep) shows the following contact field "<sip:200010001000@!OUTSIDE_PROXY!>sip:200010001000@!ORIGINAL_IP!:5070." My understanding is that "sip:200010001000@!ORIGINAL_IP!:5070" should have been replaced with <sip:200010001000@!OUTSIDE_PROXY!> instead of being prepended. Perhaps there is a module that provides a function that would allow me to manipulate the contact more easily (i'm aware that the regex in the subst in inadequate and would not match the full range of RFC3261 valid Contact strings, i'm just testing right now) Would anyone be able to offer any advice? tavis

3 4

[Serusers] ser and buddy list
by ePonkFiria 30 Mar '05

30 Mar '05

Hi, Anybody knows how implement buddy list in SER with SIP phone? Best Regards --------------------------------- Do you Yahoo!? Yahoo! Small Business - Try our new resources site!

1 0

← Newer
1
...
4
5
6
7
8
9
10
...
63
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 March 2005