Dispatcher "maxload" attribute

List overview All Threads
Download

newer

older

git:master: dispatcher:...

git:master: modules/registrar:...

Olle E. Johansson

11 Dec 2014 11 Dec '14

4:41 p.m.

Show replies by date

Daniel-Constantin Mierla

11 Dec 11 Dec

5:15 p.m.

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. 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

Olle E. Johansson

5:18 p.m.

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:

-- 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

Ovidiu Sas

5:29 p.m.

Also 'weight' attribute is not fully documented. There are missing examples and details about how it works. IIRC, the sum of all weights must be 100, otherwise strange things happens. 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:

_______________________________________________ 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

Olle E. Johansson

5:39 p.m.

On 11 Dec 2014, at 16:29, Ovidiu Sas <osas(a)voipembedded.com> wrote:

...

Also 'weight' attribute is not fully documented. There are missing examples and details about how it works. IIRC, the sum of all weights must be 100, otherwise strange things happens.

Is there a at least a warning message before we let the daemons out and the strange things start to happen? /O

...

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:

_______________________________________________ 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

Ovidiu Sas

6:31 p.m.

No :) On Thu, Dec 11, 2014 at 10:39 AM, Olle E. Johansson <oej(a)edvina.net> wrote:

...

On 11 Dec 2014, at 16:29, Ovidiu Sas <osas(a)voipembedded.com> wrote:

Also 'weight' attribute is not fully documented. There are missing examples and details about how it works. IIRC, the sum of all weights must be 100, otherwise strange things happens.

Is there a at least a warning message before we let the daemons out and the strange things start to happen? /O

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

Daniel-Constantin Mierla

12 Dec 12 Dec

11:49 a.m.

On 11/12/14 16:29, Ovidiu Sas wrote:

...

Also 'weight' attribute is not fully documented. There are missing examples and details about how it works. IIRC, the sum of all weights must be 100, otherwise strange things happens.

Can you give some examples of such strange things, because otherwise it is impossible to guess where to look for. Daniel

...

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:

_______________________________________________ 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

Ovidiu Sas

5:42 p.m.

Sorry, I should have been more specific. I used the feature a year ago and if my memory serves well, here are the issues that I encountered: - if the sum of all weights is less then 100, then the remaining weight is assigned to the first entry (if one entry has a weight of 10 and the second one a weight of 20, then the real weight will be 80% for the first entry and 20% for the second one) - if the sum of all weights is more then 100, then only the first 100 are taken into consideration (if first entry has a weight of 80 and the second one a weight of 80, then the real weight will be 80% for the first entry and 20% for the second one) Maybe, for now, it's enough to document this, if the behavior is still the same. I haven't tested the feature in a long time, this is what I remember. Hope this helps, Ovidiu On Fri, Dec 12, 2014 at 4:49 AM, Daniel-Constantin Mierla <miconda(a)gmail.com> wrote:

...

On 11/12/14 16:29, Ovidiu Sas wrote:

Also 'weight' attribute is not fully documented. There are missing examples and details about how it works. IIRC, the sum of all weights must be 100, otherwise strange things happens.

Can you give some examples of such strange things, because otherwise it is impossible to guess where to look for. Daniel

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

_______________________________________________ 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

-- VoIP Embedded, Inc. http://www.voipembedded.com

Olle E. Johansson

13 Dec 13 Dec

9:02 a.m.

On 12 Dec 2014, at 10:49, Daniel-Constantin Mierla <miconda(a)gmail.com> wrote:

...

On 11/12/14 16:29, Ovidiu Sas wrote:

Also 'weight' attribute is not fully documented. There are missing examples and details about how it works. IIRC, the sum of all weights must be 100, otherwise strange things happens.

Can you give some examples of such strange things, because otherwise it is impossible to guess where to look for.

THe weight option is really not documented well. Maybe we should start with documenting how it works. The source code has no comments and no explanations. It does some randomizing and other cool stuff to perform its magic - but can we please get an explanation? /O

...

Daniel

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

_______________________________________________ sr-dev mailing list sr-dev(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

Steve Murphy

14 Dec 14 Dec

7:03 a.m.

Uh, I'm just a bystander looking at this, and it seems that the code and explanation would be a lot simpler if the weights are just proportional. Given n weights (w), for i=1 to n: SUM w[i] = total weight proportional: Pw[i] = w[i] / total weight so, if you have two weights, 10 and 10, then Pw[1] = .5 and Pw[2] = .5 if they are 180 and 180, Pw[1] = .5 and Pw[2] = .5 Pw values vary from 0 to 1. They should always add up to 1. Multiply by 100 if you want. No conditionals, no special cases (as long as no w[i] == 0, everything should be OK). (or, as long as at least 1 w[i] != 0). Right? On Sat, Dec 13, 2014 at 12:02 AM, Olle E. Johansson <oej(a)edvina.net> wrote:

...

On 12 Dec 2014, at 10:49, Daniel-Constantin Mierla <miconda(a)gmail.com> wrote:

On 11/12/14 16:29, Ovidiu Sas wrote: > Also 'weight' attribute is not fully documented. There are missing > examples and details about how it works. > IIRC, the sum of all weights must be 100, otherwise strange things

happens.

Can you give some examples of such strange things, because otherwise it is impossible to guess where to look for.

Daniel > > 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.

>>> 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

_______________________________________________ sr-dev mailing list sr-dev(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

-- Steve Murphy ParseTree Corporation 57 Lane 17 Cody, WY 82414 ✉ murf at parsetree dot com ☎ 307-899-5535

Alekzander Spiridonov

11 Dec 11 Dec

5:35 p.m.

Just to be sure: what do you mean by "number of active calls" in terms of dispatcher functionality? Number of "hits" or new dependency will be introduced? 2014-12-11 18:18 GMT+03:00 Olle E. Johansson <oej(a)edvina.net>et>:

...

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

_______________________________________________ sr-dev mailing list sr-dev(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

-- Best regards, Alekzander Spiridonov

Olle E. Johansson

5:42 p.m.

On 11 Dec 2014, at 16:35, Alekzander Spiridonov <alekz(a)li.ru> wrote:

...

Just to be sure: what do you mean by "number of active calls" in terms of dispatcher functionality? Number of "hits" or new dependency will be introduced?

It's a dispatcher + dialog call load based system, so it's actually active calls as seen by dialog. /O

...

2014-12-11 18:18 GMT+03:00 Olle E. Johansson <oej(a)edvina.net>et>: 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:

_______________________________________________ sr-dev mailing list sr-dev(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev -- Best regards, Alekzander Spiridonov _______________________________________________ sr-dev mailing list sr-dev(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

Ovidiu Sas

6:46 p.m.

...

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:

_______________________________________________ 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

Federico Cabiddu

7:09 p.m.

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:

...

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

_______________________________________________ sr-dev mailing list sr-dev(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

Ovidiu Sas

7:13 p.m.

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:

...

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:

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

Federico Cabiddu

7:17 p.m.

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:

...

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:

> > 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.

> 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

_______________________________________________ sr-dev mailing list sr-dev(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

Ovidiu Sas

7: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:

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:

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

-- VoIP Embedded, Inc. http://www.voipembedded.com

3635

days inactive

3638

days old

sr-dev@lists.kamailio.org

Manage subscription

16 comments

6 participants

tags (0)

participants (6)

Alekzander Spiridonov
Daniel-Constantin Mierla
Federico Cabiddu
Olle E. Johansson
Ovidiu Sas
Steve Murphy