Open Source Training Seminar FreePBX Paid Support

Ticket #152 (assigned Feature Requests: None)

Opened 3 years ago

Last modified 2 years ago

Create subsets of ext-local for each tenant group

Reported by: peter_foti Assigned to: nobody (accepted)
Priority: minor Milestone: 4.0
Component: None Version: None
Keywords: Cc:
Confirmation: SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description (Last modified by gregmac) 

If you intend to use this in a multi-tenant
environment, you would NOT want to be able to dial
accross tenants.  For example, tenant 1 is Company ABC
with extensions 200 - 299, tenant 2 is Company XYZ with
extensions 300 - 399.  If these companies are totally
unrelated, then 200 should never be allowed to dial
300.  Likewise, a group ring should not be able to dial
across tenants (for example, a group ring configured to
dial extensions 200 and 300).  Currently, there is
nothing to prevent this.

Could this be made configurable?  For example, a
checkbox to
allow dialing across departments/tenants?

Please consider this type of separation for a future
release.

Change History

05/15/05 08:17:29 changed by p2pvoice 

Logged In: YES 
user_id=1239220

I agree.
Please see my comments in Item # 1200740 that was posted
afyer this.

Thanks

06/26/06 17:01:17 changed by gregmac

  • description changed.

This should be rolled into #461

06/26/06 17:11:48 changed by gregmac

  • summary changed from Config option to prevent inter-department/tenant dialing to Create subsets of ext-local for each tenant group.
  • milestone set to 2.2.

This ticket has been reduced in scope.

A context should be created for each tenant group to allow inclusion in groups as described in #461. Extensions should still be added to ext-local for backwards compatibility, and people who don't want to bother with permission groups (ie, the way they are now). In other words, this change shouldn't affect any current behaviour and can be included at any time.

10/16/06 03:57:29 changed by RobThomas

  • milestone changed from 2.2 to 2.3.

I think we can take this (and #461) out of 2.2.. We've got enough changes to scare the users with 8)

01/06/07 20:44:51 changed by wiseoldowl

This should be doable with naftali5's Custom Contexts module (see #1447).

01/08/07 11:46:49 changed by

  • milestone deleted.

Milestone 2.3 deleted

01/08/07 12:07:31 changed by vgster

  • milestone set to 2.3.
Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads