Thanx Duane for replying the mail ..<div><br></div><div>Let me explain you my scenario ...</div><div><br></div><div> I have 2 registered contact </div><div> 1 . 1234 (q value .9)</div><div> 2 5678 (q value .8)</div>
<div><br></div><div>On IIVITE after lookup() 1234 will be on top of list . So after lookup I just want to update contact 1234 with q value .7 in memory/data base .</div><div>So that for next call 5678 should come on top of the list for 2nd INVITE .</div>
<div><br></div><div>So I want make changes in memory/database so that 5678 should be picked up as first contact by very next INVITE .</div><div><br></div><div>Thanx,</div><div>Gomtesh</div><div><br></div><div><br></div><div>
<br></div><div><br></div><div><br></div><div><br><br><div class="gmail_quote">On Wed, Jan 30, 2013 at 1:50 AM, <span dir="ltr"><<a href="mailto:users-request@lists.opensips.org" target="_blank">users-request@lists.opensips.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Users mailing list submissions to<br>
<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:users-request@lists.opensips.org">users-request@lists.opensips.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:users-owner@lists.opensips.org">users-owner@lists.opensips.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Failover and dialog termination (microx)<br>
2. Re: Decrease the priority of contact (Duane Larson)<br>
3. Re: Carrierroute failure route enhancement (Samuel Muller)<br>
4. [RELEASE] OpenSIPS 1.9.0 - a new major release is out<br>
(Bogdan-Andrei Iancu)<br>
5. [RELEASES] Support and management of OpenSIPS release -<br>
IMPORTANT (Bogdan-Andrei Iancu)<br>
6. Re: [RELEASE] OpenSIPS 1.9.0 - a new major release is out (Bakko)<br>
7. Re: [OpenSIPS-Devel] [RELEASE] OpenSIPS 1.9.0 - a new major<br>
release is out (Sa?l Ibarra Corretg?)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 29 Jan 2013 06:12:46 -0800 (PST)<br>
From: microx <<a href="mailto:acmicrox@gmail.com">acmicrox@gmail.com</a>><br>
Subject: Re: [OpenSIPS-Users] Failover and dialog termination<br>
To: <a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br>
Message-ID: <<a href="mailto:1359468766526-7584255.post@n2.nabble.com">1359468766526-7584255.post@n2.nabble.com</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Hi Schneur,<br>
<br>
Yes, the two proxy servers PA and PB are using the same database. And the<br>
db_mode regarding dialog<br>
is set to 1 to make each dialog be written into memory as well as the<br>
database.<br>
<br>
What do you mean master/master replication? Can you specify your method?<br>
Thanks so much.<br>
<br>
Best wishes,<br>
Chen-Che<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://opensips-open-sip-server.1449251.n2.nabble.com/Failover-and-dialog-termination-tp7584192p7584255.html" target="_blank">http://opensips-open-sip-server.1449251.n2.nabble.com/Failover-and-dialog-termination-tp7584192p7584255.html</a><br>
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 29 Jan 2013 10:39:22 -0600<br>
From: Duane Larson <<a href="mailto:duane.larson@gmail.com">duane.larson@gmail.com</a>><br>
Subject: Re: [OpenSIPS-Users] Decrease the priority of contact<br>
To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
Message-ID:<br>
<<a href="mailto:CAFcM1EqZxr_FhVkJswpBNPK5wueE-9PvJPJFCof0nr4GHAtpDg@mail.gmail.com">CAFcM1EqZxr_FhVkJswpBNPK5wueE-9PvJPJFCof0nr4GHAtpDg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
I'm not 100% sure what you are trying to do. I needed to do some serial<br>
calling and here is what I did<br>
<br>
<a href="http://opensips-open-sip-server.1449251.n2.nabble.com/opensips-Bugs-3349030-Need-access-to-SIP-URI-Q-Value-td6554597.html" target="_blank">http://opensips-open-sip-server.1449251.n2.nabble.com/opensips-Bugs-3349030-Need-access-to-SIP-URI-Q-Value-td6554597.html</a><br>
<br>
<a href="http://www.opensips.org/Resources/DocsCoreVar19#toc75" target="_blank">http://www.opensips.org/Resources/DocsCoreVar19#toc75</a><br>
<br>
<br>
<br>
On Tue, Jan 29, 2013 at 2:02 AM, Gomtesh Jain <<a href="mailto:gomtesh@gmail.com">gomtesh@gmail.com</a>> wrote:<br>
<br>
> Hi ,<br>
> I want to decrease the priority (q value) of contact (in memory &<br>
> database)as soon as it comes on top of the list after lookup. So that next<br>
> call should not pick this contact (if other contacts are registered). As<br>
> soon as call finishes client will refresh its registration with original q<br>
> value.<br>
> How can I do this either in script after lookup() or in code in around<br>
> lookup.c ?<br>
><br>
> Can someone help me on this ?<br>
><br>
> Thanx,<br>
> Gomtesh<br>
><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
><br>
><br>
<br>
<br>
--<br>
--<br>
*--*--*--*--*--*<br>
Duane<br>
*--*--*--*--*--*<br>
--<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensips.org/pipermail/users/attachments/20130129/d66ee50b/attachment-0001.htm" target="_blank">http://lists.opensips.org/pipermail/users/attachments/20130129/d66ee50b/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 29 Jan 2013 18:21:30 +0100<br>
From: Samuel Muller <<a href="mailto:sml@l33.fr">sml@l33.fr</a>><br>
Subject: Re: [OpenSIPS-Users] Carrierroute failure route enhancement<br>
To: Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>><br>
Cc: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
Message-ID:<br>
<<a href="mailto:CAEhWu_ZOcx-p6r7exe6Lc0EY-pFyMMauFS5UyGUb9Lzgs8ad4g@mail.gmail.com">CAEhWu_ZOcx-p6r7exe6Lc0EY-pFyMMauFS5UyGUb9Lzgs8ad4g@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
it's working like a charm ...<br>
1 rule per number/group of numbers, each one with an AVP I can use to my wishes.<br>
<br>
thank you very much !<br>
<br>
<br>
Samuel MULLER<br>
<a href="mailto:sml@l33.fr">sml@l33.fr</a><br>
<a href="http://www.l33.fr" target="_blank">www.l33.fr</a><br>
<br>
<br>
On Tue, Jan 29, 2013 at 10:23 AM, Bogdan-Andrei Iancu<br>
<<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>> wrote:<br>
> Exactly ;)<br>
><br>
><br>
> Regards,<br>
><br>
> Bogdan-Andrei Iancu<br>
> OpenSIPS Founder and Developer<br>
> <a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a><br>
><br>
><br>
> On 01/28/2013 04:22 PM, Samuel Muller wrote:<br>
>><br>
>> Mmmh,<br>
>><br>
>> I just see the rule attribute column. I think I can use it for the<br>
>> stuff I need ?<br>
>><br>
>> Samuel MULLER<br>
>> <a href="mailto:sml@l33.fr">sml@l33.fr</a><br>
>> <a href="http://www.l33.fr" target="_blank">www.l33.fr</a><br>
>><br>
>><br>
>> On Mon, Jan 28, 2013 at 3:16 PM, Samuel Muller<<a href="mailto:sml@l33.fr">sml@l33.fr</a>> wrote:<br>
>>><br>
>>> Hello Bogdan,<br>
>>><br>
>>> Thanks for your reply, I understand a bit more the how-to.<br>
>>><br>
>>> This proxy (a stack of servers for fail-over and load-balancing, in<br>
>>> fact), where now DRouting is used, is some kind of pure class 4<br>
>>> switch.<br>
>>><br>
>>> I do a DID mapping to route calls to MGWs, SBCs, and almost 20 of<br>
>>> other virtualized opensips that take care of my customers (as a class<br>
>>> 5 level) - these have all the necessary infos with DB and Radius.<br>
>>> I would like to limit db accesses (and radius only for accounting),<br>
>>> and it's more efficient to get all infos that are not so many in that<br>
>>> case: who's requested, where to route, in one request.<br>
>>> I just need the "when it fails" - for that, I just need 1 column that<br>
>>> store an AVP with the new way of routing the requested number : to a<br>
>>> PSTN number, to a call-center, to an IVR, ...<br>
>>><br>
>>> I think I understood the system with the gateway attribute - I'm<br>
>>> afraid that if I've 100 000 numbers (or group of numbers) to take<br>
>>> care, I've to add a list of 100 000 gateways ...<br>
>>> Maybe the solution of the aliases table is good enough, but it's not<br>
>>> really clean (1 table to manage with almost the same request 2 times).<br>
>>><br>
>>> Again, it's something that should be really simple at this cl.4 level<br>
>>> - all the complex stuff is done by the cl.5 systems (parallel forks<br>
>>> that you helped me last month, ...).<br>
>>><br>
>>> Thank you for your help, I'm waiting for the tutorial !<br>
>>><br>
>>><br>
>>> Samuel MULLER<br>
>>> <a href="mailto:sml@l33.fr">sml@l33.fr</a><br>
>>> <a href="http://www.l33.fr" target="_blank">www.l33.fr</a><br>
>>><br>
>>><br>
>>> On Mon, Jan 28, 2013 at 11:16 AM, Bogdan-Andrei Iancu<br>
>>> <<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>> wrote:<br>
>>>><br>
>>>> Hi Samuel,<br>
>>>><br>
>>>> We will have a DR tutorial in place next week (after the release).<br>
>>>><br>
>>>> Now, reading your scenario, I see you have 2 ops here : (1) mapping the<br>
>>>> DID to your subscriber (what about using aliases here ?) and (2) doing call<br>
>>>> fwd on no-answer for your subscriber (serial forking)<br>
>>>><br>
>>>> Of course you can combine all this in CR / DR tool, or you can simply<br>
>>>> script everything (using aliases and AVPs with serial forking for fallback).<br>
>>>><br>
>>>> With DR, you need to set in dr_rules the DIDs and to point into<br>
>>>> dr_gateways (as IP of the proxy). Now, as attribute of the gateway you can<br>
>>>> define the mobile number -> if the call to GW failed, you can use the<br>
>>>> attribute and get the mobile number.<br>
>>>><br>
>>>> Regards,<br>
>>>><br>
>>>> Bogdan-Andrei Iancu<br>
>>>> OpenSIPS Founder and Developer<br>
>>>> <a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a><br>
>>>><br>
>>>><br>
>>>> On 01/18/2013 07:27 PM, Samuel Muller wrote:<br>
>>>><br>
>>>> Hello Bogdan,<br>
>>>><br>
>>>> it should be nice to get some tutorials, of course.<br>
>>>><br>
>>>> but I tried today to understand a bit more the drouting module, and it<br>
>>>> does not do what I need, as the carriermodule.<br>
>>>><br>
>>>> to explain briefly :<br>
>>>><br>
>>>> an incoming call from PSTN to one of my subscriber DID I've to take in<br>
>>>> charge.<br>
>>>> the carrierroute module find as prefix the R-URI username and tries to<br>
>>>> route the call to one of my other proxy.<br>
>>>> but, I get a 408 Time Out and I need to route in fallback to, i.e., the<br>
>>>> PSTN mobile phone of my subscriber.<br>
>>>> So, I've to rewrite to R-URI username and send the new request to my<br>
>>>> PSTN gateway.<br>
>>>><br>
>>>> In the drouting module or in the carrierroute, I've no way to find this<br>
>>>> new username to rewrite.<br>
>>>><br>
>>>> I think that I need to add a new column in the carrierfailureroute (or<br>
>>>> something equal in the drouting module) that contains the fallback r-uri<br>
>>>> username ...<br>
>>>><br>
>>>> If you have better idea, I take it !<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Samuel MULLER<br>
>>>> <a href="mailto:sml@l33.fr">sml@l33.fr</a><br>
>>>><br>
>>>><br>
>>>> On Wed, Jan 16, 2013 at 5:49 PM, Bogdan-Andrei<br>
>>>> Iancu<<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>> wrote:<br>
>>>>><br>
>>>>> Hi Samuel,<br>
>>>>><br>
>>>>> What is the kind of "complexity" you got stuck with DR ? You can use it<br>
>>>>> both in a simple or a complex way - maybe I can help with it.<br>
>>>>><br>
>>>>> Anyhow we plan to publish a tutorial for Dynamic Routing after the<br>
>>>>> 1.9.0 release.<br>
>>>>><br>
>>>>> Regards,<br>
>>>>><br>
>>>>> Bogdan-Andrei Iancu<br>
>>>>> OpenSIPS Founder and Developer<br>
>>>>> <a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a><br>
>>>>><br>
>>>>><br>
>>>>> On 01/16/2013 03:03 PM, Samuel Muller wrote:<br>
>>>>><br>
>>>>> Hey Bogdan,<br>
>>>>><br>
>>>>> I already tried the drouting module, I found that it was too complex<br>
>>>>> for my needs - and I was not agree in some way to take in charge the routing<br>
>>>>> (source routing is so weird in my case, regex are not working, and so on) -<br>
>>>>> so I turned back myself to the old LCR module I used once upon a time which<br>
>>>>> was really sufficient - to finally use carrierroute - that I thought it was<br>
>>>>> maintained yet.<br>
>>>>><br>
>>>>> I'll try again the drouting but I'm not really confident with this one<br>
>>>>> ...<br>
>>>>><br>
>>>>> Thanks a lot,<br>
>>>>><br>
>>>>><br>
>>>>> Samuel MULLER<br>
>>>>> <a href="mailto:sml@l33.fr">sml@l33.fr</a><br>
>>>>><br>
>>>>><br>
>>>>> On Wed, Jan 16, 2013 at 1:51 PM, Bogdan-Andrei<br>
>>>>> Iancu<<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>> wrote:<br>
>>>>>><br>
>>>>>> Hi Samuel,<br>
>>>>>><br>
>>>>>> I would suggest rather using the drouting module instead of<br>
>>>>>> carrierroute (this module is not maintained). With drouting module you have<br>
>>>>>> attributes per rules, per gateways and per carriers, and you use these<br>
>>>>>> attributes for whatever purposes (and they are available in script).<br>
>>>>>><br>
>>>>>> Regards,<br>
>>>>>><br>
>>>>>> Bogdan-Andrei Iancu<br>
>>>>>> OpenSIPS Founder and Developer<br>
>>>>>> <a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a><br>
>>>>>><br>
>>>>>><br>
>>>>>> On 01/16/2013 02:40 PM, Samuel Muller wrote:<br>
>>>>>><br>
>>>>>> Hello,<br>
>>>>>><br>
>>>>>> I've a single question about carrierroute module.<br>
>>>>>><br>
>>>>>> I would like to use the failure route to rewrite the user + domain to<br>
>>>>>> a new one as fallback (i.e. when 4xx catched after the main carrier route,<br>
>>>>>> redirect to another pstn number).<br>
>>>>>> Is there an easy way to do it - as adding a new column in the<br>
>>>>>> carrierfailureroute table ?<br>
>>>>>> I would like to save the db requests ...<br>
>>>>>><br>
>>>>>> thanks a lot,<br>
>>>>>><br>
>>>>>> Samuel MULLER<br>
>>>>>> <a href="mailto:sml@l33.fr">sml@l33.fr</a><br>
>>>>>><br>
>>>>>><br>
>>>>>> _______________________________________________<br>
>>>>>> Users mailing list<br>
>>>>>> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
>>>>>> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
>>>>><br>
>>>>><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 29 Jan 2013 21:11:03 +0200<br>
From: Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>><br>
Subject: [OpenSIPS-Users] [RELEASE] OpenSIPS 1.9.0 - a new major<br>
release is out<br>
To: "<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>" <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>>,<br>
"<a href="mailto:devel@lists.opensips.org">devel@lists.opensips.org</a>" <<a href="mailto:devel@lists.opensips.org">devel@lists.opensips.org</a>>,<br>
<a href="mailto:news@lists.opensips.org">news@lists.opensips.org</a>, <a href="mailto:business@lists.opensips.org">business@lists.opensips.org</a><br>
Message-ID: <<a href="mailto:51081EC7.1060609@opensips.org">51081EC7.1060609@opensips.org</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Hi all,<br>
<br>
One more major release is out - OpenSIPS 1.9.0 Release Candidate (beta)<br>
<br>
*OpenSIPS 1.9.0* comes with several major improvements (scripting,<br>
dialog support, TCP, Web Sockets, timers), but also with new<br>
functionalities like CacheDB Interface - CouchBase, MongoDB, Cache2SQL<br>
DNS caching, nice provisioning tool like PI_HTTP module or great helper<br>
on integration, the Event_Route module (combined with a rich set of new<br>
events from core and modules).<br>
<br>
One of the important goals of this release were scalability (geo and<br>
load), integration capabilities and controllability (debugging, tracing,<br>
monitoring).<br>
<br>
A complete compilation with all the additions and improvements for<br>
*OpenSIPS 1.9.0 *release is available under:<br>
<a href="http://www.opensips.org/Main/Ver190" target="_blank">http://www.opensips.org/Main/Ver190</a><br>
<br>
A comprehensive migration document is available also:<br>
<a href="http://www.opensips.org/Resources/DocsMigration180to190" target="_blank">http://www.opensips.org/Resources/DocsMigration180to190</a><br>
<br>
Many thanks to all the people who got involved in this release (and in<br>
the overall OpenSIPS project) and contributed with code, with testing<br>
and debugging, with patches or reports, with support on the lists, help<br>
with packaging and documentation. Here is the a fast compiled list:<br>
<br>
<a href="http://opensips.svn.sourceforge.net/viewvc/opensips/branches/1.9/CREDITS?revision=9708&view=markup" target="_blank">http://opensips.svn.sourceforge.net/viewvc/opensips/branches/1.9/CREDITS?revision=9708&view=markup</a><br>
If someone was missed, apologies in advance and let me know ASAP to fix<br>
it ;)<br>
<br>
I want to thanks you all for out great job and not in my behalf, but in<br>
the behalf of people who will find this piece of software a useful tool.<br>
<br>
The full Changelog is available here:<br>
<a href="http://opensips.org/pub/opensips/1.9.0/src/ChangeLog" target="_blank">http://opensips.org/pub/opensips/1.9.0/src/ChangeLog</a><br>
<br>
<br>
To get the *OpenSIPS 1.9.0* version, see :<br>
<br>
* website page: <a href="http://www.opensips.org/Resources/Downloads" target="_blank">http://www.opensips.org/Resources/Downloads</a><br>
<br>
* SF project:<br>
<a href="https://sourceforge.net/projects/opensips/files/OpenSIPS/1.9.0/" target="_blank">https://sourceforge.net/projects/opensips/files/OpenSIPS/1.9.0/</a><br>
<br>
<br>
Note that for the moment only the source tarballs are available. Also<br>
DEBs for Debian ans Ubuntu should be ready soon on the official repository.<br>
<br>
<br>
Enjoy it and best regards,<br>
Bogdan<br>
<br>
--<br>
Bogdan-Andrei Iancu<br>
OpenSIPS Founder and Developer<br>
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Tue, 29 Jan 2013 21:17:17 +0200<br>
From: Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>><br>
Subject: [OpenSIPS-Users] [RELEASES] Support and management of<br>
OpenSIPS release - IMPORTANT<br>
To: "<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>" <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>>,<br>
"<a href="mailto:devel@lists.opensips.org">devel@lists.opensips.org</a>" <<a href="mailto:devel@lists.opensips.org">devel@lists.opensips.org</a>>,<br>
<a href="mailto:news@lists.opensips.org">news@lists.opensips.org</a>, <a href="mailto:business@lists.opensips.org">business@lists.opensips.org</a><br>
Message-ID: <<a href="mailto:5108203D.7070009@opensips.org">5108203D.7070009@opensips.org</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Hi all,<br>
<br>
Following the new 1.9 RC release, according to the new release policy<br>
(see <a href="http://www.opensips.org/Development/Development" target="_blank">http://www.opensips.org/Development/Development</a>), here are the<br>
changes in what versions are to be supported or not and for how long:<br>
<br>
<br>
1) 1.7.x releases are no longer officially maintained.<br>
<br>
2) 1.8.x is an LTS release (Long Term Supported)<br>
<br>
3) 1.9.x is a STS release (Short Term Supported - up to the next major<br>
release).<br>
<br>
<br>
Most probably 1.10 will be an LTS .<br>
<br>
Please adjust your upgrading plans according to these changes !<br>
<br>
Thanks and Regards,<br>
<br>
--<br>
Bogdan-Andrei Iancu<br>
OpenSIPS Founder and Developer<br>
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Tue, 29 Jan 2013 14:25:44 -0500<br>
From: Bakko <<a href="mailto:asannucci@gmail.com">asannucci@gmail.com</a>><br>
Subject: Re: [OpenSIPS-Users] [RELEASE] OpenSIPS 1.9.0 - a new major<br>
release is out<br>
To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
Message-ID: <<a href="mailto:51082238.7000206@gmail.com">51082238.7000206@gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Very good news.<br>
<br>
Thank you<br>
<br>
<br>
El 29/01/2013 14:11, Bogdan-Andrei Iancu escribi?:<br>
> Hi all,<br>
><br>
> One more major release is out - OpenSIPS 1.9.0 Release Candidate (beta)<br>
><br>
> *OpenSIPS 1.9.0* comes with several major improvements (scripting,<br>
> dialog support, TCP, Web Sockets, timers), but also with new<br>
> functionalities like CacheDB Interface - CouchBase, MongoDB, Cache2SQL<br>
> DNS caching, nice provisioning tool like PI_HTTP module or great<br>
> helper on integration, the Event_Route module (combined with a rich<br>
> set of new events from core and modules).<br>
><br>
> One of the important goals of this release were scalability (geo and<br>
> load), integration capabilities and controllability (debugging,<br>
> tracing, monitoring).<br>
><br>
> A complete compilation with all the additions and improvements for<br>
> *OpenSIPS 1.9.0 *release is available under:<br>
> <a href="http://www.opensips.org/Main/Ver190" target="_blank">http://www.opensips.org/Main/Ver190</a><br>
><br>
> A comprehensive migration document is available also:<br>
> <a href="http://www.opensips.org/Resources/DocsMigration180to190" target="_blank">http://www.opensips.org/Resources/DocsMigration180to190</a><br>
><br>
> Many thanks to all the people who got involved in this release (and in<br>
> the overall OpenSIPS project) and contributed with code, with testing<br>
> and debugging, with patches or reports, with support on the lists,<br>
> help with packaging and documentation. Here is the a fast compiled list:<br>
> <a href="http://opensips.svn.sourceforge.net/viewvc/opensips/branches/1.9/CREDITS?revision=9708&view=markup" target="_blank">http://opensips.svn.sourceforge.net/viewvc/opensips/branches/1.9/CREDITS?revision=9708&view=markup</a><br>
> If someone was missed, apologies in advance and let me know ASAP to<br>
> fix it ;)<br>
><br>
> I want to thanks you all for out great job and not in my behalf, but<br>
> in the behalf of people who will find this piece of software a useful<br>
> tool.<br>
><br>
> The full Changelog is available here:<br>
> <a href="http://opensips.org/pub/opensips/1.9.0/src/ChangeLog" target="_blank">http://opensips.org/pub/opensips/1.9.0/src/ChangeLog</a><br>
><br>
><br>
> To get the *OpenSIPS 1.9.0* version, see :<br>
><br>
> * website page: <a href="http://www.opensips.org/Resources/Downloads" target="_blank">http://www.opensips.org/Resources/Downloads</a><br>
><br>
> * SF project:<br>
> <a href="https://sourceforge.net/projects/opensips/files/OpenSIPS/1.9.0/" target="_blank">https://sourceforge.net/projects/opensips/files/OpenSIPS/1.9.0/</a><br>
><br>
><br>
> Note that for the moment only the source tarballs are available. Also<br>
> DEBs for Debian ans Ubuntu should be ready soon on the official<br>
> repository.<br>
><br>
><br>
> Enjoy it and best regards,<br>
> Bogdan<br>
><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Tue, 29 Jan 2013 21:20:27 +0100<br>
From: Sa?l Ibarra Corretg? <<a href="mailto:saul@ag-projects.com">saul@ag-projects.com</a>><br>
Subject: Re: [OpenSIPS-Users] [OpenSIPS-Devel] [RELEASE] OpenSIPS<br>
1.9.0 - a new major release is out<br>
To: OpenSIPS devel mailling list <<a href="mailto:devel@lists.opensips.org">devel@lists.opensips.org</a>><br>
Cc: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
Message-ID: <<a href="mailto:460E8BA7-F825-4E6D-9CC5-045B6B2CF4EC@ag-projects.com">460E8BA7-F825-4E6D-9CC5-045B6B2CF4EC@ag-projects.com</a>><br>
Content-Type: text/plain; charset=iso-8859-1<br>
<br>
<br>
On Jan 29, 2013, at 8:11 PM, Bogdan-Andrei Iancu wrote:<br>
<br>
> Hi all,<br>
><br>
> One more major release is out - OpenSIPS 1.9.0 Release Candidate (beta)<br>
><br>
> *OpenSIPS 1.9.0* comes with several major improvements (scripting, dialog support, TCP, Web Sockets, timers), but also with new functionalities like CacheDB Interface - CouchBase, MongoDB, Cache2SQL DNS caching, nice provisioning tool like PI_HTTP module or great helper on integration, the Event_Route module (combined with a rich set of new events from core and modules).<br>
><br>
> One of the important goals of this release were scalability (geo and load), integration capabilities and controllability (debugging, tracing, monitoring).<br>
><br>
> A complete compilation with all the additions and improvements for *OpenSIPS 1.9.0 *release is available under:<br>
> <a href="http://www.opensips.org/Main/Ver190" target="_blank">http://www.opensips.org/Main/Ver190</a><br>
><br>
> A comprehensive migration document is available also:<br>
> <a href="http://www.opensips.org/Resources/DocsMigration180to190" target="_blank">http://www.opensips.org/Resources/DocsMigration180to190</a><br>
><br>
> Many thanks to all the people who got involved in this release (and in the overall OpenSIPS project) and contributed with code, with testing and debugging, with patches or reports, with support on the lists, help with packaging and documentation. Here is the a fast compiled list:<br>
> <a href="http://opensips.svn.sourceforge.net/viewvc/opensips/branches/1.9/CREDITS?revision=9708&view=markup" target="_blank">http://opensips.svn.sourceforge.net/viewvc/opensips/branches/1.9/CREDITS?revision=9708&view=markup</a><br>
> If someone was missed, apologies in advance and let me know ASAP to fix it ;)<br>
><br>
> I want to thanks you all for out great job and not in my behalf, but in the behalf of people who will find this piece of software a useful tool.<br>
><br>
> The full Changelog is available here:<br>
> <a href="http://opensips.org/pub/opensips/1.9.0/src/ChangeLog" target="_blank">http://opensips.org/pub/opensips/1.9.0/src/ChangeLog</a><br>
><br>
><br>
> To get the *OpenSIPS 1.9.0* version, see :<br>
><br>
> * website page: <a href="http://www.opensips.org/Resources/Downloads" target="_blank">http://www.opensips.org/Resources/Downloads</a><br>
><br>
> * SF project: <a href="https://sourceforge.net/projects/opensips/files/OpenSIPS/1.9.0/" target="_blank">https://sourceforge.net/projects/opensips/files/OpenSIPS/1.9.0/</a><br>
><br>
><br>
> Note that for the moment only the source tarballs are available. Also DEBs for Debian ans Ubuntu should be ready soon on the official repository.<br>
><br>
<br>
Congrats to the team! See (some of) you in Brussels!<br>
<br>
Also, FWIW, I've been running OpenSIPS straight from trunk for a while now without major problems, everyone go test!<br>
<br>
<br>
Cheers,<br>
<br>
--<br>
Sa?l Ibarra Corretg?<br>
AG Projects<br>
<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
<br>
End of Users Digest, Vol 54, Issue 71<br>
*************************************<br>
</blockquote></div><br></div>