[OpenSIPS-Users] Restrict Simultaneous-Use

[Bogdan-Andrei Iancu]

Hi Inaki,

This is an old, hot topic.

There are many services that are more appropriate via a B2BUA  (like 
acc, dialog stuff, security, etc) - last time the discussion started 
from the question if a proxy is the best place to do accounting.

In all the case is about compromising - how much you are willing to 
lose. You may loose time/resources to build and implement a platform 
were there is no way for bad thinks to happen (you deal with all corner 
cases) - and you end up with a huge platform, very complex, difficult to 
maintain, expensive to run, etc .

Or you can loose some corner cases and build a simpler and more 
efficient platform.

The whole idea is if it pays to spend 1 million $ to save one $ :)..

Regards,
Bogdan

Iñaki Baz Castillo wrote:
> 2009/3/5 Bogdan-Andrei Iancu <bogdan at voice-system.ro>:
>   
>> Hi Robert,
>>
>> You do not need Radius for this. OpenSIPS can do this by itself. See a
>> nice tutorial on this topic:
>>    http://www.opensips.org/index.php?n=Resources.DocsTutConcurrentCalls
>>     
>
> Hi, this is very interesting but I wonder how "dangerous" is a proxy
> trying to count the simultaneous calls.
>
> If for example alice calls to bob through OpenSIPs, how can OpenSIPS
> know if the call is really alive or not? imagine neither alice or bob
> are using SessionTimers.
>
> OpenSIPS cannot assume that it will receive an in-dialog request which
> would refresh the dialog expire time, so this time must be very long
> (hours). What about if alice and bob crash without sending a BYE? The
> call will remain "alive" in OpenSIPS until the dialog expires (various
> hours), so alice couldn't call bob again during this time.
>
>
>