11 Dec
2014
11 Dec
'14
6:21 p.m.
I didn't check the code. I see it in trunk now, all good.
We can say that my initial statement is true for the stable version of
kamailio ;)
-ovidiu
On Thu, Dec 11, 2014 at 12:17 PM, Federico Cabiddu
<federico.cabiddu(a)gmail.com> wrote:
It is, unless there is a bug ;-)
Regards,
Federico
On Thu, Dec 11, 2014 at 6:13 PM, Ovidiu Sas <osas(a)voipembedded.com> wrote:
--
VoIP Embedded, Inc.
http://www.voipembedded.com
Yeah, that was added recently. It could/should be listed under the
RPC attrs node.
It's a quick way to verify that the special attrs are properly defined
by admin and recognised by kamailio.
-ovidiu
On Thu, Dec 11, 2014 at 12:09 PM, Federico Cabiddu
<federico.cabiddu(a)gmail.com> wrote:
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
There is a fourth one, 'socket', to set
the socket used to send pings
and
requests.
Regards,
Federico
On 11 Dec 2014 17:46, "Ovidiu Sas" <osas(a)voipembedded.com> wrote:
--
VoIP Embedded, Inc.
http://www.voipembedded.com
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
BTW, all 'special' attributes are listed in the RPC 'dispatcher.list'
command.
So far, there are three reserved attributes:
- duid
- maxload
- weight
On Thu, Dec 11, 2014 at 10:18 AM, Olle E. Johansson <oej(a)edvina.net>
wrote:
>
> On 11 Dec 2014, at 16:15, Daniel-Constantin Mierla
> <miconda(a)gmail.com>
> wrote:
>
>> Hello,
>>
>> it is supposed to be the upper limit for call load distribution --
>> if
>> number of active calls gets to it, no new call should be sent there.
>> If
>> not implemented, then I forgot about it.
> I think there's a risc that your latest statement is true. If so,
> this
> is a gentle
> reminder ;-)
>
> /O
>>
>> Cheers,
>> Daniel
>>
>> On 11/12/14 15:41, Olle E. Johansson wrote:
>>> Hi!
>>>
>>> In the source code for dispatcher there is parsing of a predefined
>>> attribute called "maxload".
>>>
>>> It's not documented and I don't see it used anywhere in the source
>>> code. Only in output of
>>> attributes and debug code.
>>>
>>> Anyone that knows more? Can we remove this unused attribute or is
>>> it
>>> planned for future glory?
>>>
>>> /O
>>> _______________________________________________
>>> sr-dev mailing list
>>> sr-dev(a)lists.sip-router.org
>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>>
>> --
>> Daniel-Constantin Mierla
>> http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
>>
>>
>> _______________________________________________
>> sr-dev mailing list
>> sr-dev(a)lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>
>
> _______________________________________________
> sr-dev mailing list
> sr-dev(a)lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
VoIP Embedded, Inc.
http://www.voipembedded.com
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev