On Tue, Dec 15, 2009 at 10:25 AM, Scott Lawrence <[email protected]> wrote: > On Tue, 2009-12-15 at 10:15 -0500, M. Ranganathan wrote: >> Hello, >> >> In 4.2 we will have a "disable gateway" feature. This allows a >> specific ITSP gateway to be disabled. Thus a pbx user cannot make >> outbound calls using that gateway. However, this does not block >> inbound calls from the ITSP. Would it be useful to have a "disable >> ITSP" feature that allows inbound calls from the ITSP to be blocked ? > > Why do we need a disable gateway feature in the first place?
Its a convenience feature that caches the account information. When you re-enable it, the account information re-appears in sipxbridge.xml. If you did not have this feature, when you disable the dial plan, the account information still remains in sipxbridge.xml thereby resulting in registration refereshes. Hence we needed a means to disable this. In 4.1 the disable gateway feature does remove the ITSP record from sipxbridge.xml but it does not block inbound calls. > > We already have an enable/disable on entire dial plans and an > enable/disable on gateways within a dial plan - how many ways do we need > to do the same thing? > > > > > -- M. Ranganathan _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
