<div dir="ltr">Hi Raul,<br><br><div class="gmail_quote">On Mon, Sep 1, 2008 at 12:59 PM, Raúl Alexis Betancor Santana <span dir="ltr"><<a href="mailto:rabs@dimension-virtual.com">rabs@dimension-virtual.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">El Monday 01 September 2008 11:12:49 DanB escribió:<br>
<div class="Ih2E3d">> Hi Matteo,<br>
><br>
> I was in the same position like you are now, months back.<br>
><br>
> At least in OpenSER (please note that 1.4 is no longer tagged as OpenSER,<br>
> but Kamailio) it was hard to do call-control since SER like was not<br>
> initially developed to be dialog aware server. Dialog module is coming<br>
> slowly to be there but I have the feeling it will take a bit time more to<br>
> have a mature product out.<br>
><br>
> In the mean time I decided to go with an easier approach, so have installed<br>
> Yate ( I am sure Asterisk or Freeswitch can do the same job as well, but it<br>
> is just about having yate on hands on that time). In my case Yate will take<br>
> the timeout value from Private SIP Header and process it as global timer of<br>
> the call (Yate acts as SBC or B2BUA).<br>
<br>
</div>In that scenario Yate is working as B2BUA not as SBC.</blockquote><div> </div><div>Is it? I would still consider B2BUA as a private case of SBC and it really suits my scenario.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<div class="Ih2E3d"><br>
> If the call does finish before the<br>
> timer is hit, Yate will do the job and disconnect both legs of the call<br>
> (inbound and outbound) by sending BYE to both parties, therefore reaching<br>
> the scenario wanted. However, this is considered like a security whole in<br>
> Yate since anyone could achieve call disconnects by using the right private<br>
> header, so u must set also an ip acl inside yate for the calls where u<br>
> process the private-timer header.<br>
<br>
</div>In you put a Kamailio in front of Yate you could ensure taht private-timer<br>
headers are only there because Kamailio put them, so no security hole<br>
possible.</blockquote><div><br>That's a case of using Yate only for this purpose, but what about if you use Yate for h323/sip conversion and receive calls from other parties as well. Do u think they cannot set such of header? Do u want to give to the end user the possibility of controlling your softswitch by setting different headers?<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<div class="Ih2E3d"><br>
> I am at your disposal if you need further help with freeradius-cdrtool<br>
> connector (planning to release out a new version soon, just hope that the<br>
> time will stay still to give me that opportunity ;-) ).<br>
<br>
</div>In your solution, you have not considered the situation of two simultaneous<br>
calls from the same user.</blockquote><div><br>We provide free accounts to our users, and each account is individual, so each user will call at one moment in time from one account only (did not get users complaining about that till now). CDRTool initial operation was developed with this policy in mind. You can also use the non-locking feature introduced recently but it's just a matter of your policy, I will stick to mine for the moment.<br>
<br>Cheers,<br>DanB<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<font color="#888888"><br>
--<br>
Raúl Alexis Betancor Santana<br>
Dimensión Virtual S.L.<br>
</font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.kamailio.org">Users@lists.kamailio.org</a><br>
<a href="http://lists.kamailio.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.kamailio.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div>