[SR-Users] Fwd: sr-users Digest, Vol 102, Issue 53
santosh satapathy
santosh.satapathy at gmail.com
Sat Nov 16 01:24:51 CET 2013
---------- Forwarded message ----------
From: santosh satapathy <santosh.satapathy at gmail.com>
Date: Fri, Nov 15, 2013 at 4:23 PM
Subject: Fwd: sr-users Digest, Vol 102, Issue 53
To: Daniel-Constantin Mierla <miconda at gmail.com>
Appreciate for the input Daniel.
I was looking here little different scenario where in weights are dynamic.
Load distribution should happen in such a way that first it round robins
among the nodes with weight 3 until they are equal with other sets of nodes
with weight 2. Once this stage is reached where in all the nodes in both
the sets are equally weighted, then LB should round robin among all the
nodes uniformly.
This means that dynamically nodes with higher weights will get more calls
until their weight difference is substantiated and after that all nodes are
treated as equal.
Is it possible to configure script for the above scenario?
Thanks ,
Santosh
---------- Forwarded message ----------
From: <sr-users-request at lists.sip-router.org>
Date: Thu, Nov 14, 2013 at 2:26 AM
Subject: sr-users Digest, Vol 102, Issue 53
To: sr-users at lists.sip-router.org
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. Re: Kamailio/Radius problem (Daniel-Constantin Mierla)
2. Re: Variables in event_route[sl:local-response]
(Daniel-Constantin Mierla)
3. Re: Query regd the dispatcher algorithm support
(Daniel-Constantin Mierla)
4. WORDS_BIGENDIAN error in auth_diameter.h (Sotas Development)
----------------------------------------------------------------------
Message: 1
Date: Thu, 14 Nov 2013 10:06:20 +0100
From: Daniel-Constantin Mierla <miconda at gmail.com>
To: "Kamailio (SER) - Users Mailing List"
<sr-users at lists.sip-router.org>
Subject: Re: [SR-Users] Kamailio/Radius problem
Message-ID: <5284928C.9080300 at gmail.com>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
On 11/14/13 10:02 AM, Daniel-Constantin Mierla wrote:
> Hello,
>
> On 11/14/13 4:31 AM, jonathan augenstine wrote:
>> I am working on the configuration to enable RADIUS in Kamailio 4.0.
>> The basic install worked successfully and the daemon started without
>> problems. I then install radiusclient-ng and configured RADIUS in
>> the Kamailio build/configuration. All seemed OK until the Kamailio
>> restart and I encountered the following error during the restart:
>>
>> Nov 13 06:52:23 lax-vproxy2-a kernel: [ 348.808624] kamailio[5346]:
>> segfault at 0 ip 00007f375d249a5d sp 00007fff4d42eed0 error 4 in
>> libradiusclient-ng.so.2.0.0[7f375d243000+c000]
>> Nov 13 06:52:23 lax-vproxy2-a kamailio: ERROR: <core>
>> [daemonize.c:307]: daemonize(): Main process exited before writing to
>> pipe
>>
>> After some research it seemed that others encountered a similar error
>> and traced it to the dictionary. I have gone through the dictionary
>> configuration and all seems to be correct. Any guidance on what
>> might be the issue or some troubleshooting steps?
> did you get a core dump? Looking at the backtrace may show where is
> the problem in libradiusclient-ng.
Just found this one that seems to be similar:
- http://sip-router.org/tracker/index.php?do=details&task_id=310&project=1
It mentions that acctserver was not set in radius config.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Nov 25-28
- more details about Kamailio trainings at http://www.asipto.com -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.sip-router.org/pipermail/sr-users/attachments/20131114/e6432ceb/attachment-0001.html
>
------------------------------
Message: 2
Date: Thu, 14 Nov 2013 10:15:48 +0100
From: Daniel-Constantin Mierla <miconda at gmail.com>
To: "Kamailio (SER) - Users Mailing List"
<sr-users at lists.sip-router.org>
Subject: Re: [SR-Users] Variables in event_route[sl:local-response]
Message-ID: <528494C4.80604 at gmail.com>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Hello,
for sl:local-response, the attributes of remote address are available
via $sndto(...) variables, see the cookbook from the wiki.
For dialog, current sip message under processing is given (so all pvs
should refgect it), but sometime there is no such message (at the dialog
timeout event). However, the attributes of the dialog should be visible
via $dlg(...) variables.
Cheers,
Daniel
On 11/14/13 9:17 AM, Kelvin Chua wrote:
> well as far as i know, $rU comes up NULL on event_route[dialog:XXXX]
> how do we pass pseudo-variables to event_route properly?
>
> Kelvin Chua
>
>
> On Thu, Jun 20, 2013 at 2:58 AM, Sergey Okhapkin
> <sos at sokhapkin.dyndns.org <mailto:sos at sokhapkin.dyndns.org>> wrote:
>
> Which variables I can use in event_route[sl:local-response] route
> to xlog proto:ip:port to which the response will be sent?
>
> event_route[sl:local-response] {
>
> xlog("L_INFO","Local response to $??\n$mb\n");
>
> }
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
> list
> sr-users at lists.sip-router.org <mailto:sr-users at lists.sip-router.org>
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Nov 25-28
- more details about Kamailio trainings at http://www.asipto.com -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.sip-router.org/pipermail/sr-users/attachments/20131114/36955a1b/attachment-0001.html
>
------------------------------
Message: 3
Date: Thu, 14 Nov 2013 10:21:14 +0100
From: Daniel-Constantin Mierla <miconda at gmail.com>
To: "Kamailio (SER) - Users Mailing List"
<sr-users at lists.sip-router.org>
Subject: Re: [SR-Users] Query regd the dispatcher algorithm support
Message-ID: <5284960A.5040004 at gmail.com>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Hello,
there is no such algorithm done internally. But you can get it via
configuration:
- use two set ids, first with the 3 nodes and then the second with the
other 2 nodes
- first to ds_select_*(setid1, 4) and ds_next_*() utill you consume all
of them
- if no answer yet and no more addresses with setid1, then call
ds_select_*(setid2, 4) and ds_next_*()
You can also look to see if weight based distribution fits your needs,
so you can have the 3 good nodes with high weight and the other with
something lower. But it won't try first the 3 good ones, it will
distribute across all of them based on their weight.
Cheers,
Daniel
On 11/14/13 2:54 AM, santosh satapathy wrote:
> Hi,
>
> Any input for the below query is highly appreciated.
>
> *Question:*
>
> Does the dispatcher module allow combination like "weighted round
> robin" algorithm. Or Do we have any similar algorithm ?
>
> Example:
>
> 3 of 5 nodes are in better condition so I set them as weight 1 and the
> other two as weight 2.
>
> Then the dispatcher will round robin between the 3 nodes with weight 1
> until all 5 are with the same weight.
>
> That also means that the weight should be dynamic and updated as
> conditions of the node changes.
>
>
> --
> Thanks
>
> Santosh
>
>
>
> --
> Thanks
>
> Santosh
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Nov 25-28
- more details about Kamailio trainings at http://www.asipto.com -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.sip-router.org/pipermail/sr-users/attachments/20131114/9e883f02/attachment-0001.html
>
------------------------------
Message: 4
Date: Thu, 14 Nov 2013 11:25:59 +0100
From: Sotas Development <sotasdev at gmail.com>
To: "SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
Users Mailing List" <sr-users at lists.sip-router.org>
Subject: [SR-Users] WORDS_BIGENDIAN error in auth_diameter.h
Message-ID:
<CAM0BVXxpUxXdAHMeZ3uL4i7V3T=wF-MDZOv=g3_f4ORw2Z_0AA at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hello All,
We are currently cross compiling Kamailio for powerpc and are encountering
an "issue", of which we want to know whether or not it is intentional. In
the modules/auth_diameter/diameter_msg.h of Kamailio 4.0.4 (latest) we
found the following line:
72: #error BIG endian detected!!
But it looks like if all the code is in place to make big endian function
as desired. Is this a leftover debug message? The reason we are asking is
because we previously encountered another error with a similar check for
WORDS_BIGENDIAN, in MD5.h.
It appears as the check is built in on multiple places for this
preprocessor directive, however it is not set anywhere. Are we missing a
necessary build step somewhere?
We have solved the issue for now by patching the diameter_msg.h to remove
the #error statement, and start the makefile using:
CC_EXTRA_OPTS = "-DWORDS_BIGENDIAN"
This seems to solve our initial issue, which was an md5 mismatch on
authentication, however we are still unsure if this is a proper workaround,
or if we are missing something else. It would be very nice if someone could
shed some light on this.
Thanks in advance,
Sotas Team
(Pascal, Yuri).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.sip-router.org/pipermail/sr-users/attachments/20131114/81938b76/attachment.html
>
------------------------------
_______________________________________________
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 102, Issue 53
*****************************************
--
Thanks
Santosh
--
Thanks
Santosh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20131115/8e286178/attachment-0001.html>
More information about the sr-users
mailing list