[OpenSIPS-Users] Restrict Simultaneous-Use

[Brett Nemeroff]

Just chiming in here.. See, I'm having a problem with my provider who isn't
properly adhering to Record-Routing (see previous thread). And so sometimes
I don't get that BYE and it goes direct to my customer! So in that case, the
dialog gets left open permanently.
There is a notable danger in allowing a proxy to do this job. If everyone is
following the rules, it should be pretty good. I'd be interested in hearing
about other people's experiences with this..

BTW, I've spoken with my provider, who admitted it was a problem and fixed
it. so, yay. Thanks for the support everyone. :)
-Brett


On Thu, Mar 5, 2009 at 6:54 AM, Iñaki Baz Castillo <ibc at aliax.net> 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.
>
>
> --
> Iñaki Baz Castillo
> <ibc at aliax.net>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20090305/01e5ff67/attachment.htm