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

[<sa...@ER...>]

Hi ehernaez

ITSP <==> Peering OSBC <==> Access OSBC <==> sipX  This requires two (2)
opensbc's
UA <==> Access OSBC <==> sipX <==> Peering OSBC <==> 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 <==> Peering OSBC <==> Access OSBC <==> sipX

II

II
                                    UA <==> Access OSBC <==> sipX <==>
Peering OSBC <==> ITSP

or this

ITSP <==> Peering OSBC <==> Access OSBC <==> sipX <==> UA <==> Access OSBC
<==> sipX <==> Peering OSBC <==> 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.




----- Original Message ----- 
From: "ehernaez" <ope...@op...>
To: <ope...@li...>
Sent: Saturday, December 29, 2007 9:58 AM
Subject: Re: [OpenSIPStack] [OpenSBC] Two (2) OSBC on net segment


> Hi Warren,
>
> Here is the call flow that you can use to bridge the 2 OSBC instances:
> For an inbound call from PSTN:    ITSP -&gt; Peering OSBC -&gt;  Access
OSBC
> -&gt;  SIPXFor an outbound cal to the PSTN:  UA -&gt;  Access OSBC -&gt;
SIPX -&gt; Peering
> OSBC -&gt;  ITSP
> *inbound calls must be routed through the access OSBC in order to reach
> endpoints that are registered thru the access OSBC
> HTH
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>