Re: [OpenSIPStack] [OpenSBC] OpenSBC 1.1.6, Summary of Feature Requests and Bug Reports

[Joegen E. B. <joe...@gm...>]

Dangi, Rajpal wrote:
> What about the feature to host OpenSBC behind NAT/firewall?
>   

I have tested OpenSBC in amazon EC2 cloud.  OpenSBC is installed in a 
virtual machine with a private IP address and Amazon exposes it through 
a public interface with one to one port binding.    I then set the 
static media address parameter  of OpenSBC to point to the public 
interface.   I was able to test this setup to be working.   The 
assumption here is that all traffic going to OpenSBC is coming from the 
public side of the network.   In this scenario, no feature request is 
needed to fulfill it.  It's already there.

The other scenario, which I think what you have in mind, is OpenSBC 
acting as a bridge between a private network and a public network while 
having itself bound by the same NAT firewall of the private network.   
Given that your NAT/Firewall is also a one to one setup, calls coming 
from the public space goinf to the public space would still work the way 
it worked in the amazon EC2 setup.  However the problem will arise if 
the call is coming from the public side towards the private network.  
OpenSBC would then need to determine when to rewrite the SDP using the 
static media address and not.   Given that we are able to do this, 
OpenSBC should be able to bridge the NAT properly.   This is always a 
tricky setup because no two systems behave similarly in such cases.    
There are also a lot of system specific behavior that are needed to be 
addressed not to mention screwed up routing tables.   Thus, this is into 
feature that would be solved with a snap of a finger.   I am sorry this 
cannot make it to the final release of 1.1.5 or even promise that 1.1.6 
will have this feature.    

If you have this kind of setup... then go for an NAT devices with a 
built-in ALG.

Joegen




> Rajpal
>
> -----Original Message-----
> From: ope...@li...
> [mailto:ope...@li...] On Behalf
> Of Joegen E. Baclor
> Sent: Tuesday, December 11, 2007 5:59 PM
> To: ope...@li...; listaopenSBC
> Subject: [OpenSBC] OpenSBC 1.1.6, Summary of Feature Requests and Bug
> Reports
>
> Hi Everyone,
>
> I am intending to finalize 1.1.5 release before the year ends so we have
>
> a clean slate for 1.1.6.  If you have feature requests or bug fixes 
> which you think should be part of this release, please document them and
>
> post them to the list ASAP.  We are going to implement  CVS branches 
> beginning 1.1.5 to allow bug fixes specific to a certain branch.   There
>
> will be some major architectural changes that will be implemented in 
> version 1.1.6 which might not be anymore compatible with the 1.1.5 
> branch.   I will enumerate the pending feature requests I summarized 
> from previous post.  Let me know if I missed smething
>
> Pending Feature Requests:
>
> 1.  Support for redirect in relay Routes - sam...@ve...
> 2.  Creation of folders (logs, registry, calea etc ) in places where 
> user has permission - H.Kropf
> 3.  Rewriting of From URI - Warren Kreckler
> 4.  Routing based on  Packet  Source - chr...@gm...
> 5.  Routing based on recipient NIC - Warren Kreckler
>
> If I  missed something feel free to reply inline.
>
> Planned Features for 1.1.6
>
> 1.  I have already announced the plan for a separate configuration 
> module on top of the current HTTP Admin.  
> 2.  We are also going to implement a separate  media proxy application 
> to allow HA/Load Balancing of streams on top of the internal media proxy
>
> implementation.  This change would allow an SBC to use multiple 
> instances of external media proxies giving way to a higher volume 
> deployment.  
> 3.  We are also going to extract the Media Server Trunk and promote it 
> as a fully featured VXML Media Server allowing PBX developers to create 
> PBX applications using the OpenSIPStack Framework. 
> 4.  The plan to implement Diameter as the AAA implementation in OpenSBC.
> 5.  Finally, the long awaited resurrection of the TCP and TLS
> transports.
>
> I have also Opened a  new development effort in SourceForge  called  
> Plugin++ (  http://sourceforge.net/projects/pluginpp ).  This new 
> project will be the entry point of a planned Plugin Framework/API for 
> OpenSBC and other OpenSIPStack applications.
>
> We are aiming for June 2008 as the ETC for the 1.1.6 release of 
> OpenSBC.  We will come up with milestone releases for each
> functionality.
>
>
> ------------------------------------------------------------------------
> -
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Opensipstack-osbcdevel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-osbcdevel
>
>
>