Ticket #142 (closed Feature Requests: duplicate)

Opened 4 years ago

Last modified 2 years ago

Dial-out restrictions.

Reported by: qldrob Assigned to: nobody
Priority: blocker Milestone: 2.3
Component: Core - Users/Devices Version: None
Keywords: Cc:
Confirmation: SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description (Last modified by gregmac) 

I checked. I checked all the RFE's and the patches. If
this one's already in the system, I'm gunna have a
dummy spit.

Limit extensions to 'only internal', 'only local',
'only national' or 'unlimited' ('only international'? 8-)

Obviously this will have to tie in somehow with the
internationalisation of the telephone zones. Possibly
implemented by 'only allow 3 digit numbers to be
called' (eg, only internal) or 'don't allow anything
over 10 digits to be dialed' (only local).. ?

Possibly needed is a 'locali[zs]ation' screen.

I'm thinking about this in the context of a business
that has a 'guest' phone in their foyer. You don't want
people coming in and calling abu dhabi while they're
waitng for a job intervew or something.

Change History

05/10/05 11:30:33 changed by gregmac 

Logged In: YES 
user_id=1174590

This was planned when the routing stuff was initially added
(I thought there was an RFE, but I can't find it now). Each
route is added to its own context, these contexts could be
included differently for each user. This will likely come
after we do some major changes to the user setup since
there's no point in modifying the (outdated) extensions
screen, which will eventually get scrapped anyways.

03/12/06 08:09:21 changed by dzverdzver 

Logged In: YES 
user_id=1474205

For scalability, (sub)sets of route contexts should be 
included in different extension contexts, and then 
extensions assigned to the appropriate extension contexts. 
(as opposed to applying the route contexts directly to 
users/extensions).

So assigning different dial restrictions for an extension 
should be achieved by just switching this extension context 
to the one with appropriate dial restrictions.

Currently the support for different extensions contexts is 
very limited (from-internal being assumed as "the extension 
context" everywhere).
This will require changes also in some applications where 
from-internal is hard-coded (for example dialparties.agi, 
ref. to feature request 1448330).

10/19/06 23:32:29 changed by gregmac

  • priority changed from 4 to 1.
  • description changed.
  • milestone set to 2.3.

Should allow creation of contexts, that include various routes and applications (selectable, of course).

Each user should then be assigned to one of these contexts with a drop-down list.

We can provide a default context ("default") that has all routes and applications (eg, from-internal, as it is now).

Contexts should actually be usercontext-<whatever> to avoid naming conflicts.

This is a blocker for 2.3

10/19/06 23:33:37 changed by gregmac

  • component changed from None to Core - Users/Devices.

10/25/06 00:55:26 changed by gregmac

See also: #691

11/28/06 01:20:58 changed by naftali5

I submitted an implementation of this
#1447
It works very well for me. Contexts, though are not so easy for the simple users to understand, so I'd assume only 50% of the population would be able to _easily_ use this.

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

  • milestone deleted.

Milestone 2.3 deleted

01/08/07 12:05:48 changed by vgster

  • milestone set to 2.3.

01/23/07 05:07:33 changed by diego_iastrubni

  • engine_version changed.
  • svn_rev changed.

... and maybe also related to ticket:1690

Should we close this one and keep ticket:1960?

01/23/07 05:37:47 changed by gregmac

  • status changed from assigned to closed.
  • resolution changed from None to duplicate.

Agreed, #1690 has more updated information relevant to the current version.

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads