On Tue, Feb 9, 2010 at 12:51 PM, David Saint <[email protected]> wrote:
> > > Dave wrote: > > ... > > > Perhaps this could be viewed as an SBC device running > > within a sipXecs > > > service. The service is responsible for service-level configuration > > > (e.g. the logging level) and the SBC device is responsible for > > > everything else (e.g. the ITSP accounts). > > > Keeping the Internal SBC device within the Devices->SBCs > > menu would be > > > more intuitive for anyone currently using an External SBC. > > > > That sounds complex. And I've been told that it is not > > helpful to think of sipXbridge as an SBC. > > > > Luckily all the settings under Devices->SBCs->sipXbridge-1 > > are just duplicated from System->Serves->(FQDN)->SIP > > Trunking. So I think we can suppress the "sipXbridge-1" SBC > > entry without problem. > > > > The settings aren't really duplicated, the SIP Trunk service > just redirects the browser to EditSbcDevice. > > > > > > Also I'm not sure how the Gateway -> Route drop-down list > > would work > > > without the Internal SBC device. > > > > We could simply tuck Route under Advanced, and quietly > > default it to "sipXbridge-1". Ranga tells me that forgetting > > to manually set the Route is a common source of problems. > > Let's make it automatic. > > > > Of course, the "SIP Trunking" role for the server must be > > enabled first. But that's just another manual step that > > causes problems when forgotten. Let's just enable that by > > default too. > > > > Thoughts? > > > > > > -Paul > > [email protected] > > > > Not all Gateways require an SBC (e.g. an Audiocodes Mediant1000 > doesn't require an SBC), so always defaulting to having one would be > confusing too. > It feels like we have two completely different kinds of Gateways: > 1. Gateways that don't use an SBC, and don't have ITSP information. > 2. Gateways that are merely providing ITSP information for an SBC. > Maybe these two types of gateways should be separated so that we don't > display ITSP and SBC information for non-SBC gateways. > > Once we know we have an SBC Gateway we could default the Route to > the first available SBC and (if no SBC is available) enable > SIP Trunking on the primary server. > > One thing that puzzles me is where the Gateway Route description states: > "Session Border Controller (SBC), SIP aware firewall or SIP proxy that > > processes calls directed at the provider served by this SIP trunk." > but the drop-down menu only allows SBCs. Why are these other devices > mentioned here? > > Dave. > _______________________________________________ > sipx-dev mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ > Because I can use an Ingate as an unmanaged gateway and let it connect to my siptrunk provider and remote users. I can also set up both that and sipxbridge. At that point if I want to make a choice for enum or internet dialing, I have to choose it (instead of sipxbridge_sbc) in the domain dropdown list for Internet calls, or leave it unchecked for sipxbridge, for example. It makes sense (to me) that only an SBC gets there if the dial plan allows you to select a gateway, which would bypass that need.
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
