Ticket #803 (new Feature Requests)

Opened 3 years ago

Last modified 4 months ago

something like traffic relationship

Reported by: Wanninger Assigned to:
Priority: minor Milestone: Cut Line
Component: - choose - Version:
Keywords: traffic relationship Cc:
Confirmation: Unreviewed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

I'm not sure whether "traffic relationship" is the correct name for it or not.

I'll try to describe it.

An index in users/extensions and trunks is neccessary.

e.g. I'll put index 100 to exten's 100...199 and index 200 to enten's 200...299 and so on. Then I'll put index 100 also to ZAP/SIP trunk 1 and index 200 to ZAP/SIP trunk 2 and so on.

The next step is to create a matrix in which I define which index to which other index can make a call.

For example:

            to 100     to 200     to 300     to 400

from 100       x          yes        yes        no

from 200       no         x          no         no

from 300       no         yes        x          no

from 400       yes        yes        yes        x


A function like this is usefull if you want to forbid calls from one index group to another including the corresponding trunk. Or you want to allow only calls inside an index group but a special index group should be allowed to call any other index group too.

In professional environments this is used to isolate companies against each other which are all hosted on one PBX.

Greets Wanninger

Change History

05/06/06 18:16:48 changed by p_lindheimer

This sounds to me that you are saying "I want multi-tenant" by proposing an implementation as a partial solution - as there is a lot more you would have to do then described here. It may be better to just say "I want multi-tenant" as I suspect if this were implemented, all sorts of other issues will next arrise. (IVR access to extensions gives everyone; I want the same extension range for different tenants; etc.)

Now a little closer to home (and I believe the request is here somewhere) - an ability to easily group extensions/users into varying contexts, and then when creating outbound routes, allow/restrict some of these contexts such that you can create priviledges. (e.g. reception phone, internal calls only (no outbound routes except emergency), other users local/longdistance outbound routes, other users all outbound routes, etc.)

05/07/06 02:34:43 changed by Wanninger

That's nice, "multi-tenant" would have never come to my mind ;-)

O.K. you've described it with all possible consequences. And you're right. In large enterprise environments we say "devided to rate-areas", and there we work with fqdn numbers e.g. E164. country-code + area-code + localdest-code + extension. In such a system we are working allways with the whole number and not with the extens only. Every system connected to the PBX is doing so too. E.g. IVR, VM, CDR...

You second explanation is, I think so, the closest description to what I want.

I simply would like to have the possibility to group some extens which are only allowed to make out-calls via zap/sip trunk 1, and the next group of extens can only use zap/sip trunk 2, and so on. Every group of extens should pay their own charges on their own trunks.

THX

11/28/06 01:46:44 changed by naftali5

some of this is here #1447

07/24/08 18:39:23 changed by ryppn

  • confirmation set to Unreviewed.
  • engine_version changed.
  • svn_rev changed.
  • milestone set to Cut Line.
Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads