Re: [OpenSBC] Trunk Problem

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

Hi

Main Trunk and SIP Trunk can't have the same ipaddress:port according to the
web admin OSBC  Transport Status log.  In the the General Parameter i have
set the interface to the first Active NIC ipaddress:port x.x.x.241:5060 (box
with two NIC) this also disables as far as OSBC is concerned the Main Trunks
localhost 127.0.0.1 address

Main Trunk x.x.x.241:5060
SIP Trunk x.x.x.241:5060 error already in uses x.x.x.241:5060

What should i do to remove this confick?

If i change the Main Trunk's port to 9000 would this screw up Sip transport?
And what else would i need to change to get this to work?

Warren Kreckler



----- Original Message ----- 
From: "ehernaez" <ope...@op...>
To: <ope...@li...>
Sent: Monday, December 24, 2007 3:54 PM
Subject: Re: [OpenSBC] Peering Edge or Access Edge SBC's


> {noformat}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{noformat}
>
> -------------------------------------------------------------------------
> 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
>