14 Nov
2004
14 Nov
'04
3:53 p.m.
Hi there
thanks for answering
Jan Janak wrote:
I've heard and read that using a B2BUA is the only
way to impose a call duration limit with SER.
unfortunately it doesn't scale well (asterisk
is processor power hungry and NAT unfriendly,
being compared to SER)
is there any other idea being worked on or even
on hold on imposing such a limit using SER alone
(patched, of course)?
as the nathelper/mediaproxy calls have to pass
fully onto the SER box, it sounded reasonable
to me to do this control there. I'd appreciate
some comments (pros/cons) on this topic :-)
thank you for the great work made on SER.
Cheers
!3runo
would sound
reasonable to get (i.e. from RADIUS) a
call duration limit (i.e. time_t time + duration),
save it together with the nathelper call setup (possibly
while nathelper first asks rtpproxy for the call ports),
and modify rtpproxy to check if the time limit was
reached, ending/blocking the call in this case and
avoiding the need of a B2BUA for this particular
situation?
No, I do not think that this is a good idea.
Jan.