[SR-Users] sr-users Digest, Vol 83, Issue 77
Ali Wazni
ali.wazni at live.com
Fri Apr 20 09:47:55 CEST 2012
Chefta men chway.
Jaydeeeeee 7adret el consultant!!!!!
Ali Wazni
On 20 avr. 2012, at 08:41, sr-users-request at lists.sip-router.org wrote:
> Send sr-users mailing list submissions to
> sr-users at lists.sip-router.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
> or, via email, send a message with subject or body 'help' to
> sr-users-request at lists.sip-router.org
>
> You can reach the person managing the list at
> sr-users-owner at lists.sip-router.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of sr-users digest..."
>
>
> Today's Topics:
>
> 1. Kamailio v3.2.3 Released (Daniel-Constantin Mierla)
> 2. Re: [sr-dev] reminder - freezing development for next major
> release v3.3.0 (Peter Dunkley)
> 3. Stateless Proxy (Akan)
> 4. How does RLS work with kamailio. (Gnaneshwar Gatla)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 19 Apr 2012 19:15:29 +0200
> From: Daniel-Constantin Mierla <miconda at gmail.com>
> Subject: [SR-Users] Kamailio v3.2.3 Released
> To: "SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
> Users Mailing List" <sr-users at lists.sip-router.org>, sr-dev
> <sr-dev at lists.sip-router.org>, business at lists.kamailio.org
> Message-ID: <4F904831.1030503 at gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hello,
>
> Kamailio SIP Server v3.2.3 stable release is out.
>
> This is a maintenance release of the latest stable branch, 3.2, that
> includes fixes since release of v3.2.2. There is no change to database
> schema or configuration language structure that you have to do on
> installations of v3.2.0, v3.2.1 or v3.2.2. Deployments running previous
> v3.2.x versions are strongly recommended to be upgraded to v3.2.3.
>
> For more details about version 3.2.3 (including links and hints to
> download the tarball or from GIT repository), visit:
>
> * http://www.kamailio.org/w/2012/04/kamailio-v3-2-3-released/
>
> RPMs and Debian/Ubuntu packages will be available soon.
>
> Cheers,
> Daniel
>
> --
> Daniel-Constantin Mierla
> Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany
> http://www.asipto.com/index.php/kamailio-advanced-training/
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 19 Apr 2012 18:33:49 +0100
> From: Peter Dunkley <peter.dunkley at crocodile-rcs.com>
> Subject: Re: [SR-Users] [sr-dev] reminder - freezing development for
> next major release v3.3.0
> To: miconda at gmail.com, Development mailing list of the sip-router
> project <sr-dev at lists.sip-router.org>
> Cc: "SIP Router - Kamailio \(OpenSER\) and SIP Express Router \(SER\)
> - Users Mailing List" <sr-users at lists.sip-router.org>
> Message-ID: <1334856829.2795.29.camel at pd-laptop-linux>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> One of the developments I am currently working on is to add notifier
> processes to presence. I have already done this for RLS. This is
> needed not just for performance, but because there are race conditions
> (I see them under load) where you get multiple NOTIFY requests
> outstanding on the same dialog and, when in DB only mode, they often
> have the same CSeq (despite being different requests).
>
> Unfortunately, I don't believe I will get this finished by the end of
> Monday (April 23). I still expect to complete this development next
> week.
>
> As the CSeq issue is quite clearly a problem I would like to get this
> development into Kamailio 3.3. Will it be OK for me to put this
> development into master next week after the freeze?
>
> Thanks,
>
> Peter
>
> On Wed, 2012-04-11 at 11:34 +0200, Daniel-Constantin Mierla wrote:
>
>> Hello,
>>
>> a short reminder about freezing the development for next major release
>> v3.3.0. It is planned for April 23, less than two weeks away. If you
>> have new features to add for v3.3.0, commit them or send the patches
>> before the date.
>>
>> Cheers,
>> Daniel
>>
>
>
> --
> Peter Dunkley
> Technical Director
> Crocodile RCS Ltd
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20120419/f5498d34/attachment-0001.htm>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 19 Apr 2012 22:01:05 -0500
> From: Akan <forums at akan.net>
> Subject: [SR-Users] Stateless Proxy
> To: "SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
> Users Mailing List" <sr-users at lists.sip-router.org>
> Message-ID: <4F90D171.7030006 at akan.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hello,
>
> I am trying to setup a stateless proxy where certain requests are
> forwarded to another sip server that will handle those requests
> specifically. I have the request message forwarding to the other sip
> server but the reply is being sent back to the original sip server then
> to the client. When I look at the SIP request and reply, I see a new
> "Via" header line with the IP address of the original sip proxy server.
> What I am trying to setup is a stateless proxy which just forwards the
> original request to another sip server and then this second sip server
> will handle everything from there. Basically offloading the traffic to
> other servers. Currently i am rewriting the ruri host and port as done
> in the sample config and issuing the forward() function. I have tried
> t_relay() as also in the sample config but I get the same results. Is
> there something else that I need to do before forwarding to the other
> sip server? How can I get rid of the new "Via" line? I believe this is
> from record_route() but I am not issue this before I perform the relay.
>
> I have Kamailio 3.2.3 loaded and used the sample config as my base config.
>
>
> Thanks
>
> Nathaniel
>
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 19 Apr 2012 16:53:25 -0700
> From: Gnaneshwar Gatla <GGatla at InTouchHealth.com>
> Subject: [SR-Users] How does RLS work with kamailio.
> To: "SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
> Users Mailing List" <sr-users at lists.sip-router.org>
> Cc: Cody Herzog <CHerzog at IntouchHealth.com>
> Message-ID: <30FAD1AA513CBC40B3DC6ECDA160BDF6010746 at ITHMail.ith.local>
> Content-Type: text/plain; charset="us-ascii"
>
> Hello,
>
> I'm trying to implement RLS with integrated XCAP server. I have successfully run the Kamailio instance with the following snippet.
> Since I had no RLS clients available, I have tried to test this with SIPp. The attached pcap trace is the result.
>
> Test:
>
> 1. Send an XCAP signal over http to Kamailio.
>
> 2. Register and subscribe Kamailio.
>
> The test does store the xml received over http in the xcap table in the database. But rls module does not store the data neither in rls_presentity or rls_watcher.
> When I sent the Subscribe with sipp, the server throws error that subscription was not found in the database.
>
> I would like to know if I'm doing something wrong to implement this service. Is there any brief tutorial on how to implement this?
>
>
> Kamailio.cfg snippet:
>
> ##Presence
> modparam("presence", "server_address", PRESENCE_IP)
> modparam("presence", "clean_period", 65)
> modparam("presence", "db_update_period", 60)
> modparam("presence", "max_expires", 75)
> modparam("presence", "fallback2db", 1)
>
> modparam("presence_xml", "db_url", DBURL)
> modparam("presence_xml", "force_active", 0)
> modparam("presence_xml", "integrated_xcap_server", 1)
>
>
> ##rls modparams
> modparam("rls", "db_url", DBURL)
> modparam("rls", "waitn_time", 10)
> modparam("rls", "integrated_xcap_server", 1)
> modparam("rls", "max_notify_body_length", 32000)
> modparam("rls", "to_presence_code", 10)
> modparam("rls", "server_address", RLS_URI)
> modparam("rls", "outbound_proxy", PUA_OUTBOUND_PROXY)
> modparam("rls", "xcap_root", XCAP_ROOT)
>
>
> ##XCAP modparams
> modparam("xcap_server", "db_url", DBURL)
> modparam("xcap_client", "db_url", DBURL)
> modparam("xcap_client", "query_period", 50)
>
>
> route[PRESENCE]
> {
> if(!is_method("PUBLISH|SUBSCRIBE"))
> return;
>
> #!ifdef WITH_PRESENCE
> if (!t_newtran())
> {
> sl_reply_error();
> exit;
> };
>
> if(is_method("PUBLISH"))
> {
> handle_publish();
> t_release();
> }
> else
> if( is_method("SUBSCRIBE"))
> {
> $var(ret_code)= rls_handle_subscribe();
> xlog("Subscribe: $var(ret_code)");
> if($var(ret_code)== 10)
> handle_subscribe();
> t_release();
> }
> exit;
> #!endif
>
> # if presence enabled, this part will not be executed
> if (is_method("PUBLISH") || $rU==$null)
> {
> sl_send_reply("404", "Not here");
> exit;
> }
> return;
> }
>
> In the [xhttp:request]:
> switch($rm) {
> case "PUT":
> xcaps_put("$var(uri)", "$hu", "$rb");
> if($xcapuri(u=>auid)=~"pres-rules")
> {
> xlog("===== xhttp put: refreshing watchers for $var(uri)\n");
> pres_update_watchers("$var(uri)", "presence");
> pres_refresh_watchers("$var(uri)", "presence", 1);
> }
> else if ($xcapuri(u=>auid)=~"resource-lists"
> || $xcapuri(u=>auid)=~"rls-services")
> {
> xlog("==== xhttp put: refreshing rls watchers $var(uri)\n");
> rls_update_subs("$var(uri)", "presence");
> }
>
> exit;
> break;
>
>
>
> Gnaneshwar Gatla | InTouch Health | Software Developer
> 6330 Hollister Ave. Goleta CA, 93117 | P: 805.562.8686 ext: 199
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20120419/7e386944/attachment.htm>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: rls-test.pcap
> Type: application/octet-stream
> Size: 54993 bytes
> Desc: rls-test.pcap
> URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20120419/7e386944/attachment.obj>
>
> ------------------------------
>
> _______________________________________________
> sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
> End of sr-users Digest, Vol 83, Issue 77
> ****************************************
More information about the sr-users
mailing list