Re: [OpenSBC] Peering Edge or Access Edge SBC's

[eric h. <er...@so...>]

Warren,

Yes, you are correct in concluding that you would need two OSBC 
instances in the scenario you laid out.  The instance that you use for 
SIP trunking to face your ITSP should not be the same instance that you 
are using for NAT traversal of  SIP UAs using upper registration to SIPX.

In fact, it may even be necessary for you to have 3 instances of OSBC if 
you need to support DID providers that do not comply with SIP REFER.   
As you may know, calls transferred from the SIPX auto-attendant are 
referred to the relevant UA.  Since many ITSP do not honor the REFER 
message, we have found it necessary to run a dedicated OSBC instance as 
a media anchor to shield the ITSP from the referred calls.


HTH


sales@ER wrote:
> Hi All
>
> I'm stilll fairly new to SBC thinking and came across and publication that
> is making the distrinction.
>
> Is openSBC following in the foot steps of Peering Edge or Access Edge SBC's.
>
> Further, asking because i have run into a situation that make me think i may
> in fact need two SBC's to get sipX to work.
>
> One SBC to register phones (sipX side) and the Second SBC to deal with
> (ITSPside Peering) because using one (1) SBC i can register phones using
> B2BuaUpperRegistration but refuses to allow outbound calls.  SBC keeps
> routing calls back to the sipX.
>
> Has anyone run into this problem?  Has anyone try setting up two (2) SBC's
> in the fashion i am suggesting?
>
> Warren Kreckler
>
>
>
> -------------------------------------------------------------------------
> 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-osbcdevel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-osbcdevel
>
>