Re: [OpenSBC] [OpenSIPStack] Two (2) OSBC on net segment

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

It's definitely not necessary to have 4 OSBC instances.  The same OSBC instances can be used for inbound and outbound call scenarios.  You just need to be able to distinguish between inbound and outbound calls, which can be done by using a SIPX prefix for outbound calls. 

8&lt;----------------------------- 

Hi ehernaez

ITSP &lt;==&gt; Peering OSBC &lt;==&gt; Access OSBC &lt;==&gt; sipX  This requires two (2)
opensbc's
UA &lt;==&gt; Access OSBC &lt;==&gt; sipX &lt;==&gt; Peering OSBC &lt;==&gt; ITSP.  This requires
two (2) additional OSBC

For a grand total of four (4) OSBC's.  That's 5 servers altogether.

Another way of looking at this is using factoring:

ITSP &lt;==&gt; Peering OSBC &lt;==&gt; Access OSBC &lt;==&gt; sipX

II

II
UA &lt;==&gt; Access OSBC &lt;==&gt; sipX &lt;==&gt;
Peering OSBC &lt;==&gt; ITSP

or this

ITSP &lt;==&gt; Peering OSBC &lt;==&gt; Access OSBC &lt;==&gt; sipX &lt;==&gt; UA &lt;==&gt; Access OSBC
&lt;==&gt; sipX &lt;==&gt; Peering OSBC &lt;==&gt; ITSP

This is beginning to make me laugh out loud.  In other words there is no way
of using UPPerRegistration and Relay routes to eliminate 2 of the OSBC's

It's beginning to look like the sipX people should incorporate openSBC as a
SIP TRUNK Gateway for both Peering and Access Edge SBC's.  After all openSBC
is 100% RFC compliant.  My god 4 OSBC's servers...

Warrem Kreckler.