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. > 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] _______________________________________________ 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/
