sr-users

sr-users@lists.kamailio.org

1 participants
37563 discussions

[Kamailio-Users] TCP failover
by Gawith 21 Nov '08

21 Nov '08

Hi guys, is there a way to realize TCP fail over? With UDP, I check for 408s in the failure route and react accordingly. With TCP, the tm modules sends out a 477 without any chance for me to interfere. Regards.

3 4

[Kamailio-Users] Help!!!!! WARNING:tm:run_failure_handlers: no UAC or CANCEL support (1, 0)
by Krunal Patel 21 Nov '08

21 Nov '08

Hi, When I am sending high volume calls to openser , I am getting WARNING:tm:run_failure_handlers: no UAC or CANCEL support (1, 0). Please help me to find out the cause of it. I am using openser 1.2.3. Thanks Krunal Patel

3 6

[Kamailio-Users] about sip router project
by Daniel-Constantin Mierla 21 Nov '08

21 Nov '08

Hello, I want to reveal some details from the process of getting to sip-router.org project. Next statements are from my personal point of view -- warning: quite long message, probably boring... When all started, back in 2001/2002, it was research and SIP Express Router (SER). Over the time became more than that, the market demanded new features pushed beyond a SIP proxy/router definition, the place of this application was no longer in research, business side and telephony industry … [View More]forced to take actions. In that context I co-founded OpenSER in 2005, leaving SER to continue its way. Now after several years, the situation evolved as well, SIP is clear the today's technology for telecommunication, every Telco out there is deploying/replacing its infrastructure with SIP. However, SIP was designed for more than this, other companies develop innovative services and products using this protocol. I could identify couple of directions within our project: - old-style-fashion switch - mapped on SIP Router/Proxy, where speed and reliability is the main concern - call/dialog stateful proxy (back-to-back user agent) - for a larger set of security and service features - pbx-like features using SIP signaling only - call pickup, shared line appearance, etc... - new fashion functionalities - IM&Presence, gaming, integrated and convergent communication, application servers... To be able to sustain and keep high level quality, it is clear that we need more companies in, entities that are interested on different directions of the development, so they contribute there. I am interested in the first and last direction with higher priority, but I don't want to leave out the other two. Moveover, kamailio/openser is used now in many deployments, some serving millions of users and billions of minutes per month. We need to provide a reliable environment so more companies are confident the development and maintenance continue. The project shall prove the maturity that is not dependent on gringo-like actions, one company influence, forking out of nowhere, domain hijacking, etc... this is the first goal for myself, something I want to ensure before anything else. sip-router.org was not one minute/meeting decision (after a beer, dinner or one email, ...). Discussions started between different persons, coordinated or privately, several months ago, long before the latest fork. It was clear that SER and OpenSER made their points over the time, one satisfying better the need for stability, performance, the other better for innovation and flexibility. At a point in future, sooner or later, each project would have been switched some of its resources to the other direction. At the time of announcement, the sip-router.org site had comprehensive content about how this will work. It was the result of face-to-face meetings, phone and email conversations that took place a lot in the last months before the news. It was no decision until everyone deeply involved in each project acknowledged that there are mutual benefits for everybody (developers, users and businesses behind both projects) backed up by willingness to do it in a fair manner. I cannot talk about other projects in the x-SER eco-system, but with Kamailio/OpenSER never was the case/proposal of merging back to SER, all the time was about collaboration and joint effort. It will never happen to drop our goals for innovation and flexibility. Therefore we discussed and agreed the development mechanisms to ensure the need of each project: a stable layer (core + tm) and innovation by modules or libraries. Nothing was left out, every aspect, from licensing, contribution, ... to releasing and management, was approached. The meeting in Karsruhe came just to conclude that. All our community members were happy about announcement, and, as a matter of fact, there were no political-like discussions conducted between our members since sip-router.org announcement, the focus moved on the technical side and good progress was reached so far: http://lists.kamailio.org/pipermail/users/2008-November/020694.html Personally, I consulted people in open source and communication world, that are not particularly technical or in relation with x-SER projects. Getting to sip-router.org took more than half year since I realized a common layer between the x-SER projects should be beneficial for everybody. There are more things to say, but maybe not that relevant. I let them for the time we meet at SIP Router events. Now I hope several points are more clear: - it is not a merge back in SER, it is a joint project (this just because some tried to suggest it) - the entire collaboration process was carefully discussed and planned - it was conducted by the need of reliable, non-confusing environment -- that ensures sustainable development, innovation and rock-solid stability, it protects the interests of developers, users and businesses investing resources in the project. At the end, I want to thank to Kamailio and SER management team members, to the developers and many other people involved in both projects that helped with this process - they dedicated lot of time and resources. Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com [View Less]

1 0

[Kamailio-Users] sip router project status
by Daniel-Constantin Mierla 21 Nov '08

21 Nov '08

Hello, just to let you know that yesterday evening first openser/kamailio modules run on the common core+tm provided by sip-router project. That was siputils (new module in Kamailio devel version). Soon after: - xlog module was ready too, with just an extra define in Makefile, marking the inclusion of pseudo-variable and transformation API in sip-router -- one can do color printing via xlog. Note that all pseudo-variables and transformations will be moved in PV module as discussed some … [View More]

1 0

[Kamailio-Users] kamailio devel team
by Daniel-Constantin Mierla 21 Nov '08

21 Nov '08

Hello, last month was very busy for myself, with lot of work and traveling for the sip-router.org, so apart of announcing few updates, I focused on getting things done rather than going in pointless discussions. I will send couple of other emails related to this subject. However, there was one person writing untrue statements and offending the developers of Kamailio/OpenSER on mailing lists, web and IRC channels. If he would have searched a bit on the net, have talked with our … [View More]developers, he would realize that people in our team are very rich in skills and experience, then probably he would refrain from statements like "no skills", "no knowledge". Until someone else than him, recognize him as the greatest, gets the Nobel prize, publishes world recognized books or standards, so I can take his opinion in consideration, the development of Kamailio/Project is ensured by people such as: - Juha Heinanen, doctor in computer science, former professor at Tampere University, author of many RFCs, and the list can continue ... from the web: http://occamnet.com/company/directors_and_advisors/jheinanen.cfm http://www.arkko.com/tools/rfcstats/juhaheinanen.html - Klaus Darilion, doctor in computer science at Technical University Vienna, involved in ENUM and security of VoIP/SIP, author/contributor to several open source applications and papers related to these domains http://www.ipcom.at/index.php?id=565 - Henning Westerholt, computer science engineer, in charge with the biggest VoIP deployment based on Kamailio/OpenSER I ever heard of: about 2 000 000 users, 5 000 000 phone numbers, 1 000 000 000 routed minutes per month. It is at least twice bigger than other deployments of openser/kamailio I am aware of. http://www.1und1.de I am stopping here, but all the other members of Kamailio/OpenSER devel team have broad knowledge in computer programming and VoIP technologies, authored or contributed to other open source applications -- just google the names. As co-founder of this project I felt is my duty to show the true. Therefore those statements are proofless and it is sad to see somebody can come up with such things. The development of Kamailio/OpenSER boosted since release 1.4, in summary: http://www.kamailio.org/dokuwiki/doku.php/features:new-in-1.5.x http://www.kamailio.org/dokuwiki/doku.php/roadmap:1.5.x and we are not ready yet with the new features for 1.5. Meanwhile, effort is directed to sip-router.org project as well -- I will post a status update soon. Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com [View Less]

1 0

Re: [Kamailio-Users] photos from Karlsruhe meeting
by luzango mfupe 20 Nov '08

20 Nov '08

Hi Daniel,Nice photos, but would you mind to put names of the participant in the photos??? i think that could be much better. Rgds, Lu. -- Luzango Mfupe TUUNE MOBILE Tel:0128440528/0123825710 Tshwane-RSA "...Ships are safe in harbor, but they were never meant to stay there......."

2 1

[Kamailio-Users] ACC module issue logging Reason: SIP header in missed_calls
by sergejf 20 Nov '08

20 Nov '08

2 3

[Kamailio-Users] openser - asterisk - methods field location table
by Matteo Piazza 20 Nov '08

20 Nov '08

Hi all, I'm using openser 1.3.3. And I found an issue between asterisk and openser. When an asterisk register himself to openser this is my opeserctl ul show: Contact:: sip:s@172.25.18.168 Q= Expires:: 116 Callid:: 76e873601b776e8a430237091a76a483(a)172.25.18.168 Cseq:: 103 User-agent:: Asterisk PBX 1.4 Test State:: CS_DIRTY Flags:: 0 Cflag:: 0 Socket:: udp:172.25.18.163:5060 Methods:: 4294967295 In to the postgres database into location table I have 2;"50001";"… [View More]

2 12

Re: [Kamailio-Users] [OpenSER-Users] Perl module and moduleFunction()
by Daniel-Constantin Mierla 20 Nov '08

20 Nov '08

please cc always to mailing lists... On 11/18/08 18:30, Sebastian sastre wrote: > Daniel, > > Thanks a lot for the info. I was playing with the scripts yesterday to > find a workaround. > > When I call my perl script with perl_exec() if I rewrite the headers > with > > $m->rewrite_ruri("sip:A@B"); > > They never get overwritten. > rewrite_uri should set a new request URI, not headers. What do you expect to be overwritten? Daniel > Is there a … [View More]

2 2

[Kamailio-Users] [Fwd: [Kamailio-Devel] Karlsruhe meeting minutes]
by Daniel-Constantin Mierla 20 Nov '08

20 Nov '08

-------- Original Message -------- Subject: [Kamailio-Devel] Karlsruhe meeting minutes Date: Thu, 20 Nov 2008 01:35:25 +0100 From: Andrei Pelinescu-Onciul <andrei(a)iptel.org> To: sr-dev(a)lists.sip-router.org, devel(a)lists.kamailio.org, serdev(a)iptel.org Hi, I've attached a very brief version of the Karlsruhe meeting minutes. It contains input mostly from me and Daniel (so that you know who to blame :-)). Sorry for the long delay. Hope we haven't missed anything and if we did … [View More]feel free to reply to this thread. Thanks a lot to 1&1 for hosting the meeting and to everyone who was able to come on such a short notice. Andrei - move forward, sip-router.org repo should be up next week - end of January we should have a runable core+tm with support for the most used features from both kamailo and ser (100% support might be a little delayed) - kamailo next-next release (probably after spring next year) will be based on sip-router core+tm - next or next-next ser release will be based on sip-router (ser might make another 2.1 release from the current cvs, since the code is ready - to be discussed) - future releases will most likely be common and will unify all or most of the modules (depending on everything up to that point working ok) - copyright: patches that are not accompanied by (c) claims will not add to the (c). We should put this on a web page and when in doubt we can ask the patch author for confirmation. While it's likely this has no or very limited legal value (especially in Europe), it will server at least as a gentleman agreement. We need this because: 1. we need the agreement of all (c) holders for the GPL code to add licensing exemptions (e.g. we need to add an openssl linking exemption) and it's easy if we have a known "small" set of (c) holders 2. people might not like having multiple (c) notices on files they created, just because someone did send a trivial or not so significant patch (note: "trivial" and "significant" are very relative) On problems, probably the board will decide, if nobody gives up the claim we'll fork the module (worst case, to be avoided as hard as possible). - forking modules: highly discouraged, but allowed - unmantained and rarely used modules: removed after a grace period - board: for now we continue to have 2 boards, ser and kamailo at least until we have something runable. In the meantime we should think/discuss how the common board will look like: how it will be elected and for how long, "composition" (how many devels, how many from the user community, testers a.s.o) - testing: very important, Jerome proposed having beta-tester groups and stressed out the importance of dynamic tested. Everybody seems to agree, but there are doubts about finding beta-testers volunteers. - release management: we need a release manager for each release - documentation: kamailo uses a wiki for core, and docbook .xml for modules ser use NEWS (txt file) for core and docbook for modules, but it's in the process of migrating to a more man page friendly format (still .xml) More discussion is needed, between the main doc writers from both sided. sip-router.org: - repo should be up next week - sr-dev should be used for technical dicussions related to merging the cores - new features mails should be cc'ed to sr-dev too (very important especially when core or tm is involved). - todo: find easy to remember short name related projects: - some modules may be on separate repos for a while (e.g., openimscore), maintaned by their devs for using them out of the box with sip-router - stand-alone application servers (Voztelecom/WeSIP, Iptego/SASI) may merge the communication interface specs in the future. - it is a need for a place where to collect basic info about related projects further steps: - new meeting, to be organized somewhere end of winter/beginning of spring 2009 (topics: celebrate first integrated working version, discuss further development of sip-router) - setup of adjacent tools that help developing code and documentation (e.g., wiki, tracker) general opinions: - there are x-ser platforms running milions of users, sip-router must provide a rock-solid SIP server, esure trust and project reliability - while having a strong focus on above item, innovation shall not be stopped, new features to be added as module to avoid effects to core and main modules - very important modules (e.g., usrloc, registrar, ...) should be protected as much as possible, patches and new features to be carefully reviewed not to affect stability and interoperability - improvements to most important parts to be discussed on sr-dev mailing list _______________________________________________ Devel mailing list Devel(a)lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/devel [View Less]

1 0

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