Dave wrote: ... > 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.
The "Route" setting only applies to "SIP Trunk"-type Gateways, so I think that part is covered already. > 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. It'd be simpler if sipXbridge was always on and always selected. If someone would prefer to use an external SBC, they'll have to go under Advanced and make that change explicitly. That scenario will be rare I think. So assuming we have a simple way to present sipXbridge configuration, treating it as a service instead of an SBC... Then how does XX-6944/XX-7342 get solved? A bunch of functionality gets moved from "SBC Device" classes into "Service" classes? -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/
