<div dir="ltr"><br><br><div class="gmail_quote">On Mon, Sep 1, 2008 at 8:17 PM, <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;">
<div class="Ih2E3d">On Mon, Sep 01, 2008 at 01:28:16PM +0200, DanB wrote:<br>
> Is it? I would still consider B2BUA as a private case of SBC and it really<br>
> suits my scenario.<br>
<br>
</div>Thats a matter of "visualization" .. :)<br>
<div class="Ih2E3d"><br>
> That's a case of using Yate only for this purpose, but what about if you use<br>
> Yate for h323/sip conversion and receive calls from other parties as well.<br>
> Do u think they cannot set such of header? Do u want to give to the end user<br>
> the possibility of controlling your softswitch by setting different headers?<br>
<br>
</div>They can not, because H.323 does not allow "custom-headers" you could<br>
only use the "standar ones", H.323 it's a binary protocol, so no way<br>
to add customs headers and "magicatly" they appears on the UAS side.<br>
</blockquote><div><br>H323 example was given just to point out the need of having the proxy opened to the outside world and not only be behind openser/kamailio. The initial idea we started from was that there is no need of ip acl protection since Yate can sit behind a openser/kamailio. I said yes, but it can sit outside as well.<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>
In our scenarios (only SIP), everyone MUST pass throught our SBC's so<br>
.. we control all headers that goes to the MG's <br></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> 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<br>
<div class="Ih2E3d">
> users complaining about that till now). CDRTool initial operation was<br>
> developed with this policy in mind. You can also use the non-locking feature<br>
> introduced recently but it's just a matter of your policy, I will stick to<br>
> mine for the moment.<br>
<br>
</div>So, in your system you only allow a user to do ONE call?, what<br>
happers if one "user" configure his account on a IP-PBX? you only<br>
allow him to do ONE call? no been able to do more than one call<br>
simultaneous? ... that's a dessing misstake from my point of view.</blockquote><div><br>We are talking about openser prepaid here in a proxy scenario. I did not involve any IP-PBX inside because if I would do then what's the point of my prepaid system. Could be that I misunderstood your scenario, can u depict it a bit more? Where should your user configure his ip-pbx account and why?<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>
Best Regads<br>
<font color="#888888">--<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>