Hi all, I talked to Ranga and Bob yesterday, and here are the answers.
> 1. sipXbridge is listed in the SBC options for 'Additional > SBC'. If sipXbridge isn't valid as the default SBC, why is > it a valid SBC for exceptions? sipXbridge isn't a valid Default SBC, because sipXecs built-in NAT Traversal would then not function, see XX-7340 [1]. In additional 'Additional SBC' however, exception Domains and Subnets are specified explicitly. There are no problems using sipXbridge, as long as you don't specify a domain/subnet being used by a remote worker. Though, I'm not sure how likely it is that an external SBC would be used for some domains/subnets, and then sipXbridge for others... > 2. You can't create an 'Additional SBC' with the default > "None" SBC value. So if I choose to send default "internet > calls" via an SBC, all "internet calls" must then go through > some SBC. Why can't I have domain/subnet exceptions that are > sent directly? 'Intranet Domains' and 'Intranet Subnets' are the exceptions that are sent directly, rather than via the Default SBC. The way these are laid out does not make this apparent. It would be better to show a single table of all "exception" Domains and Subnets. (i.e. Those not sent via the Default SBC.) And then in the table show which are sent directly, versus which are sent via an auxiliary SBC. -Paul [email protected] [1] http://track.sipfoundry.org/browse/XX-7340 If 'Enable Internet Calling' is enabled and sipXbridge is being utilized as an SBC then NAT traversal does not work properly. _______________________________________________ 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/
