Ticket #2929 (new Feature Requests)

Opened 5 years ago

Last modified 5 years ago

Multi-tennant

Reported by: jroper Assigned to: p_lindheimer
Priority: trivial Milestone: Undetermined
Component: Core Version: 2.5-branch
Keywords: Multi-tennant IPCentrex Cc:
Confirmation: Unreviewed Distro:
Backend Engine: All Distro Ver:
Backend Ver: SVN Revision (if applicable):

Description

Hi

You did say that that the feature list was not yet closed, therefore I offer suggestions for two features that would give a workable IP-Centrex / Multi tennant system when combined with A2Billing.

1. The ability to select a trunk based on extension, therefore extensions tagged can use certain trunks/Outbound Routes, but not others - In reality,we can do this in A2B, so a nice to have rather than a necessay.

2. More importantly, being able to stop one group of extensions being able to call another group of extensions. E.g. so that say when a call is parked, or transfered, it cannot be picked or transferred to another group of extensions.

This used to be possible in earlier versions of FPBX (pre-parking lot) by changing the context that the Extensions lived in. E.g. extensions could only call other extensions in their own context.

Joe Roper

Change History

07/20/08 21:16:12 changed by p_lindheimer

  • milestone changed from Cut Line to 4.0.

I don't believe it was ever possible to restrict extensions from calling each other unless you restricted them from calling any other extension as they have always lived in the same context together. Anyhow, the dial context ability is planned when routing and trunks are revamped, it's not a feature that will be able to get slipped in at the last minute. I believe there are probably tickets that cover these requests but for now am categorizing to 4.0 (which really means we will review all feature requests next release to figure out what to work on).

07/21/08 14:03:10 changed by jroper

I'd need to check back, but you used to be able to put in something like:-

[ipcentrex-1] include=>from-internal

Then change the extension's context from "from-internal" to "ipcentrex-1"

This would mean that all extensions in ipcentrex-1 could call one another, and any extensions remaining in "from-internal" as well as all the other stuff such as feature codes, outbound routes etc.

when another context was added: -

[ipcentrex-2] include=>from-internal

extensions in this context could only phone each other in the same [ipcentrex-2] context, but could not phone anyone in [ipcentrex-1].

I'm sure that is how it used to work, however, things have become considerably more complex in FreePBX, and quite rightly so, as we now enjoy far more features.

Joe

07/21/08 20:35:27 changed by p_lindheimer

I guess I would have to look at some really old dialplan, but as far as I can remember back, all the extensions were in one context, so to do what you want, one would have had to manually create the separate dial contexts (which could still be done today manually)