sr-users

sr-users@lists.kamailio.org

4 participants
37456 discussions

[Users] Simple xcap-emulator for OpenSER
by Adrian Georgescu 02 Apr '07

02 Apr '07

Hello, We wrote a simple xcap emulator to be able to manage the XCAP documents used by OpenSER presence agent, by using PHP scripts in combination with Apache web server. I have tested it against OpenSER with MySQL and Eyebeam for Apple. Klaus Darilion has tested it against Postgress and Eyebeam for Windows. The software can be downloaded from: http://download.dns-hosting.info/XCAP/xcap-0.5.tar.gz Regards, Adrian

2 3

[Serusers] How to disable RTP proxy connection in nathelper module
by tzieleniewski 02 Apr '07

02 Apr '07

Hi, I am using nathelper and because I have an CISCO router in front of the SER I don't need to use RTP Proxy. Whenever I start SER I get the following errors: Apr 2 09:13:33 sen ser[3442]: ERROR: send_rtpp_command: can't connect to RTP proxy Apr 2 09:13:33 sen ser[3442]: send_rtpp_command(): proxy <unix:/var/run/rtpproxy.sock> does not responding, disable it Apr 2 09:13:33 sen ser[3442]: WARNING: rtpp_test: can't get version of the RTP proxy Apr 2 09:13:33 sen ser[3442]: WARNING: rtpp_test: support for RTP proxy <unix:/var/run/rtpproxy.sock>has been disabled temporarily Apr 2 09:13:33 sen ser[3444]: ERROR: send_rtpp_command: can't connect to RTP proxy Is there a way to disable this trials through ser.cfg by nathelper mod parameter in order not to get those errors? Cheers Tomasz

2 1

[Users] WeSIP C2C and freeswitch
by Helmut Kuper 02 Apr '07

02 Apr '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I try to use WeSIP C2C with UACs registered to freeswitch. freeswitch never answeres the INVITEs for caller (that INVITE with no SDP and from=to=caller's sip address). So my question is, is it because freeswitch maybe doesn't support rfc 3725? If so, is there any C2C proven SIP-PBX I can use instead? Helmut -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF7s8L4tZeNddg3dwRArGjAKCRJ+Kqi4FqdE2J9S/Q6t8L3VEVzwCgncCc G2rxVs9s3fqs+XgUXnsefRs= =RqW7 -----END PGP SIGNATURE-----

4 9

[Users] How URI is parsed...
by Stuart Sheldon 02 Apr '07

02 Apr '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Newbe question: Can someone explain what causes a match when lookup() and does_uri_exist() is used? Does it look at the least significant characters is the URI? Does it drop certain leading numbers like '1'? Stu -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFGDs0BK69Y+xPZrWYRAg5XAJ9kL3FNuImfu6wasPZ9z32uDYmoGwCfWKhW 5al96b0dhkmFNYnwBzyHmoY= =mNnn -----END PGP SIGNATURE-----

2 2

[Users] use of AVPs in core functions
by Jens Carl 02 Apr '07

02 Apr '07

Hello List, is it possible to use AVPs in core function like rewritehost(), etc. Regards Jens

2 1

Re: [Users] Openser on Sun Ultrasparc T1 Processors - Mismatch architecture detection
by Henning Westerholt 02 Apr '07

02 Apr '07

On Tuesday 27 March 2007 17:41, you wrote: > Hi Henning. > > I tested the compilation and it does not detect the architecture. > > I think that maybe is because of uname -p outputs sparc, and uname -m > outputs sun4v. > [..] Hi Sergio, thank you for the testing. I add another check to the patch according your suggestions, could please try it another time? Cheers, Henning

3 2

re: [Users] postgres
by Mark Price 02 Apr '07

02 Apr '07

On 12/20/06, Klaus Darilion <klaus.mailinglists(a)pernau.at > wrote: > > Hi Mark! > > Postgres should work well - I use it since ser 0.8. Just make sure that > the hard disk does not get full, because this breaks the index inside > postgres and postgres is getting real slow (re-create the index if it > happens). > > Last time I tested openser_postgres.sh it worked fine. If you find a bug > please let us know. > > Please check to use the latest versions from CVS (for 1.1 use CVS > rel_1_1_0) The latest version from cvs doesn't work out of the box with openser build from the release tarball, because the release tarball doesn't included /usr/sbin/openser_gen_ha1 (although I could get past this by replacing it with the md5sum equivelant). However, the release tarball doesn't work because of this bug: https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1518732&group_… So, 1. is the cvs version of rel_1_1_0 considered safe for production use? 2. if so and there are important fixes such as this in CVS, would openser.org consider releasing a point release containing such changes? Thanks, Mark Price

6 8

RE: [Users] out of memory
by Papadopoulos Georgios 02 Apr '07

02 Apr '07

Hi Bogdan, I increased PKG_MEM_POOL_SIZE to 2MB and of course it took much longer to run out of memory. Usually it happens once every day, this time it ran for 3 days before running out of memory. If you don't mind, I will send the memory dump by personal email since I don't have easy access to an ftp server. Can you explain what you mean by 1.1.x? The version I am using is openser-1.1.1-notls_src.tar.gz, downloaded from your site under 1.1.1/. I am guessing that to get the fix I should use whatever is under latest-1.1.x/ Is this right? thank you George > -----Original Message----- > From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] > Sent: Friday, March 30, 2007 3:33 PM > To: Papadopoulos Georgios > Cc: users(a)openser.org > Subject: Re: [Users] out of memory > > Papadopoulos Georgios wrote: > > > > Hi Bogdan, > > > > I found the following thread in the list > > http://www.openser.org/pipermail/users/2006-June/005339.html > > I suspect that I have the same issue. If I assume that our DNS is > > strange, then my 1.1.1-notls version will be affected, > right? Is there > > a patch to fix this? Eventually I want to go to 1.2 but I > have to do a > > lot of testing before I can put it in production. So for > the moment I > > need a fix for 1.1.1. > > > that fix is present in 1.1.x also. > > Also back in December I sent this to the list > > http://www.openser.org/pipermail/users/2006-December/008205.html > > >From the start, we had the issue of openser stopping to process any > > incoming requests. On December I thought it was DNS related. I am > > still in the dark about this. Lately I added logging and I > discovered > > the "out of memory" error. I am guessing that the error was > there from > > the start, I just did not know about it. Do all of these make any > > sense to you? And is there a way to test our DNS to > determine whether it is buggy? > > > I;m afraid not :) > > In the meantime I will follow the instructions on the wiki > to get the > > memory dump. > > > yes - that will be the most relevant info. > > regards, > bogdan > > thank you > > > > George > > > > > > > > > >> -----Original Message----- > >> From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] > >> Sent: Wednesday, March 28, 2007 11:54 AM > >> To: Papadopoulos Georgios > >> Cc: users(a)openser.org > >> Subject: Re: [Users] out of memory > >> > >> Hi Papadopoulos, > >> > >> the error you get complains about the lack of private memory (per > >> process) - the statistics show info about the shared memory. See: > >> http://www.openser.org/dokuwiki/doku.php/troubleshooting:memory > >> > >> but look for pkg instead of shm..... > >> > >> regards, > >> bogdan > >> > >> Papadopoulos Georgios wrote: > >> > >>> Hello, > >>> > >>> Lately our OpenSER 1.1.1 is running out of memory and I get the > >>> following message > >>> 4(25190) get_hdr_field: out of memory The result is that > it stops > >>> processing any incoming request. This is a production > system and of > >>> course it causes a great deal of frustration. > >>> > >>> The last time this happened I got the following statistics before > >>> restarting > >>> > >>>> ./openserctl fifo get_statistics > >>>> > >>> Total statistics = 37 > >>> Total modules = 5 > >>> Module name = core; statistics=8 > >>> core:rcv_requests = 3259334 > >>> core:rcv_replies = 8816 > >>> core:fwd_requests = 736 > >>> core:fwd_replies = 137 > >>> core:drop_requests = 743 > >>> core:drop_replies = 0 > >>> core:err_requests = 0 > >>> core:err_replies = 43 > >>> Module name = shmem; statistics=6 > >>> shmem:total_size = 268435456 > >>> shmem:used_size = 1675864 > >>> shmem:real_used_size = 1835104 > >>> shmem:max_used_size = 4399048 > >>> shmem:free_size = 266600352 > >>> shmem:fragments = 17710 > >>> Module name = sl; statistics=9 > >>> sl:1xx_replies = 0 > >>> sl:2xx_replies = 1690410 > >>> sl:3xx_replies = 43 > >>> sl:4xx_replies = 334827 > >>> sl:5xx_replies = 1185629 > >>> sl:6xx_replies = 0 > >>> sl:sent_replies = 3210909 > >>> sl:sent_err_replies = 0 > >>> sl:received_ACKs = 743 > >>> Module name = tm; statistics=11 > >>> tm:received_replies = 8636 > >>> tm:relayed_replies = 7096 > >>> tm:local_replies = 1718 > >>> tm:UAS_transactions = 7003 > >>> tm:UAC_transactions = 94 > >>> tm:2xx_transactions = 1528 > >>> tm:3xx_transactions = 3 > >>> tm:4xx_transactions = 5129 > >>> tm:5xx_transactions = 468 > >>> tm:6xx_transactions = 0 > >>> tm:inuse_transactions = 0 > >>> Module name = usrloc; statistics=3 > >>> usrloc:location-users = 0 > >>> usrloc:location-contacts = 0 > >>> usrloc:location-expires = 7282 > >>> > >>> I am not sure how to read these numbers but I see a big > "free_size" > >>> and still OpenSER is out of memory. Any suggestions? > >>> > >>> thank you > >>> > >>> George > >>> > >>> > >>> > >>> > >>> > >>> > >>> Disclaimer > >>> > >>> The information in this e-mail and any attachments is > >>> > >> confidential. It > >> > >>> is intended solely for the attention and use of the named > >>> addressee(s). If you are not the intended recipient, or person > >>> responsible for delivering this information to the intended > >>> > >> recipient, > >> > >>> please notify the sender immediately. Unless you are the intended > >>> recipient or his/her representative you are not > authorized to, and > >>> must not, read, copy, distribute, use or retain this > message or any > >>> part of it. E-mail transmission cannot be guaranteed to be > >>> > >> secure or > >> > >>> error-free as information could be intercepted, corrupted, lost, > >>> destroyed, arrive late or incomplete, or contain viruses. > >>> > >>> > >>> > >> > --------------------------------------------------------------------- > >> - > >> > >>> -- > >>> > >>> _______________________________________________ > >>> Users mailing list > >>> Users(a)openser.org > >>> http://openser.org/cgi-bin/mailman/listinfo/users > >>> > >>> > >> > > > > > >

3 2

[Users] OpenSER v1.2.0 released
by Daniel-Constantin Mierla 02 Apr '07

02 Apr '07

Hello, version 1.2.0 of OpenSER has been released. It is major release, which means that you get along a lot of new features and improvements to existing ones in old versions. The configuration file and database structure suffered some changers, please read careful release notes to learn how to update. Just to list few of the new features: - SIMPLE Presence support (http://openser.org/dokuwiki/doku.php/presence:presence-module) - SNMP (http://openser.org/docs/modules/devel/snmpstats.html) - PERL API (http://openser.org/docs/modules/devel/perl.html) - JAVA SIP Servlet Application Server (http://wesip.eu) - script variables and transformations (http://openser.org/dokuwiki/doku.php/transformations:devel) - DNS failover - IP blacklists - XMPP IM gateway - XMLRPC - SIP session timers - secure federation peering - retransmission timer accuracy - usrloc refurbished for better performances - automatic error handling - AVPs in reply routes Read full release notes at: http://www.openser.org/mos/view/OpenSER-v1.2.x-Release-Notes/ Source tarball can be downloaded from: http://www.openser.org/pub/openser/latest/src/ Or SourceForge: http://sourceforge.net/project/showfiles.php?group_id=139143&package_id=224… This is the first release coming out o SVN. Old CVS repository was migrated to SVN, and with these, a few changes apply to get sources from repository. Please read instructions from download page: http://www.openser.org/mos/view/Download/ Migration instructions (although not complete, I'm sure) are available at: http://openser.org/dokuwiki/doku.php/install:1.1.x-to-1.2.x The documentation for modules is posted at: http://openser.org/docs/modules/1.2.x/ We would like to thank to all developers and contributors for their work with coding and testing for this new release. Cheers, Daniel

9 20

[Serusers] Header Selects
by Andrey Kuprianov 02 Apr '07

02 Apr '07

Hi, @msg.event or @msg.supported, or even @msg.["header-name"] is not implemented yet? im using latest ser from CVS.. btw, is it ok to use latest SER 2.0 for presence instead of the suggested snapshot v.4? I've noticed xcap-root and auth_xcap_root params were removed from rls and pa modules, so i've set xcap_root param in xcap module instead.

3 6

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