4 Apr
2006
4 Apr
'06
2:53 a.m.
Is there a way to restrict the number of simultaneous calls for a
particular sip client? For example, if I sell a service where each
line can have at most 4 simultaneous call voice paths and there are
two incoming calls and two separate outgoing calls, how can I make it
so that whenever a new calls comes in or a user tries to make another
call, they get fast busy or just busy?
Thanks,
Waldo
4 Apr
4 Apr
4:24 a.m.
I hear B2BUA is a good way to do this..
.
However, I've often tried to figure out why I can't just write a module
called "check_simult()" which increments a counter for simultanious call
count and checks to see if the result is over some maximum. This could be
placed in INVITEs. I've been told this doesn't work, but if I'm using
t_relay and record routing, I'm not sure why it wouldn't work.
Of course, it wouldn't be 100% accurate. It probably wouldn't persist
correctly across reboots and crashes, but personally, I don't need that
much accuracy (for example, if it can't limit the calls for a particular
subscriber for 15 minutes because I rebooted and now it doesn't realize
that a session is up, I really don't care).
So what does everyone think. I've wanted to write this module for some
time. I might work on it if there is any interest and if there isn't an
obvious reason this won't work IN STATEFULL MODE with RECORD ROUTING.
Of course there would be a function to decrement the counter for the BYEs
as well.
-Brett
On Mon, April 3, 2006 6:53 pm, Waldo Rubinstein wrote:
Is there a way to restrict the number of simultaneous
calls for a
particular sip client? For example, if I sell a service where each
line can have at most 4 simultaneous call voice paths and there are
two incoming calls and two separate outgoing calls, how can I make it
so that whenever a new calls comes in or a user tries to make another
call, they get fast busy or just busy?
Thanks,
Waldo
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
6:34 a.m.
Well, just from my previous inquiry, you have my vote to write it.
I'm also OK with your expectations about the module's accuracy. Maybe
there is a way to persist the counter on a DB and let SER clear the
counter(s) upon restart.
Thanks,
Waldo
On Apr 3, 2006, at 9:24 PM, Brett N wrote:
I hear B2BUA is a good way to do this..
.
However, I've often tried to figure out why I can't just write a
module
called "check_simult()" which increments a counter for simultanious
call
count and checks to see if the result is over some maximum. This
could be
placed in INVITEs. I've been told this doesn't work, but if I'm using
t_relay and record routing, I'm not sure why it wouldn't work.
Of course, it wouldn't be 100% accurate. It probably wouldn't persist
correctly across reboots and crashes, but personally, I don't need
that
much accuracy (for example, if it can't limit the calls for a
particular
subscriber for 15 minutes because I rebooted and now it doesn't
realize
that a session is up, I really don't care).
So what does everyone think. I've wanted to write this module for some
time. I might work on it if there is any interest and if there
isn't an
obvious reason this won't work IN STATEFULL MODE with RECORD ROUTING.
Of course there would be a function to decrement the counter for
the BYEs
as well.
-Brett
On Mon, April 3, 2006 6:53 pm, Waldo Rubinstein wrote:
Is there a way to restrict the number of
simultaneous calls for a
particular sip client? For example, if I sell a service where each
line can have at most 4 simultaneous call voice paths and there are
two incoming calls and two separate outgoing calls, how can I make it
so that whenever a new calls comes in or a user tries to make another
call, they get fast busy or just busy?
Thanks,
Waldo
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
4:03 p.m.
Why You don't simple make use of the Radius capability of calling external
procedures (scripts?) and let them make the checks? It's simpler and didn't
demand any line of code. At least not in new modules... ;)
Edson.
-----Original Message-----
From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On
Behalf Of Waldo Rubinstein
Sent: terça-feira, 4 de abril de 2006 00:34
To: brettlist(a)nemeroff.com
Cc: Mailing List SER User Mailing List
Subject: Re: [Serusers] Limiting number of calls
Well, just from my previous inquiry, you have my vote to write it.
I'm also OK with your expectations about the module's accuracy. Maybe
there is a way to persist the counter on a DB and let SER clear the
counter(s) upon restart.
Thanks,
Waldo
4:27 p.m.
It's also a good idea. I'm not that verse in Radius but I will
definitely look in that direction as well.
Thanks,
Waldo
On Apr 4, 2006, at 9:03 AM, Edson wrote:
Why You don't simple make use of the Radius
capability of calling
external
procedures (scripts?) and let them make the checks? It's simpler
and didn't
demand any line of code. At least not in new modules... ;)
Edson.
-----Original Message-----
From: serusers-bounces(a)lists.iptel.org [mailto:serusers-
bounces(a)iptel.org] On
Behalf Of Waldo Rubinstein
Sent: terça-feira, 4 de abril de 2006 00:34
To: brettlist(a)nemeroff.com
Cc: Mailing List SER User Mailing List
Subject: Re: [Serusers] Limiting number of calls
Well, just from my previous inquiry, you have my vote to write it.
I'm also OK with your expectations about the module's accuracy. Maybe
there is a way to persist the counter on a DB and let SER clear the
counter(s) upon restart.
Thanks,
Waldo
6807
days inactive
6808
days old
4 comments
3 participants
participants (3)
-
Brett N -
Edson -
Waldo Rubinstein