Ticket #54 (new Feature Requests: None)

Opened 7 years ago

Last modified 4 years ago

Ability to do DID-to-extension range mapping

Reported by: jason_d_becker Assigned to:
Priority: minor Milestone: Undetermined
Component: Core - Users/Devices Version:
Keywords: Cc:
Confirmation: Unreviewed SVN Revision (if applicable):
Backend Engine: Asterisk 1.4.x Backend Engine Version:

Description (Last modified by wozto1s) 

Had a suggestion that the interface provide for the
capability to do mapping like a range of DIDs to a
range of extensions. e.g.:

DIDs 4031234500 - 4031234599 mapped to extensions 4500
- 4599

Seems like a reasonable request.

Change History

03/16/05 18:04:27 changed by gregmac 

Logged In: YES 
user_id=1174590

this sounds pretty complex (as far as putting into a web
interface), because theres just so many possibilites..

It's still an easy thing to do but i'd suggest doing it in
ext-did-custom

exten => 40312345XX,1,Macro(exten,vm,${EXTEN:6})

04/13/06 00:29:53 changed by p_lindheimer

I think this is better handled by assinging the DID to the user/extension in the same way you can assing a CID to the user/extension. This is the logical place where information for unique to a user/extension is placed and the DID is just one more piece. I have made that modification to freebpx on the page.user.php and page.extension.php pages and added the additional code needed in functions.inc.php (for core) as well as a modification to the extenions.conf. It also adds a DID field in the users table. I'll be getting this in within the next couple of day for review.

04/15/06 21:21:50 changed by wozto1s

  • owner deleted.
  • status changed from assigned to new.
  • description changed.
  • milestone set to 2.2.

05/29/06 05:46:43 changed by RobThomas

I think this would be a one-off thing. You'd create the xtns, and then run a script that populates the DIDs if they're not already set. It wouldn't be a configuration option.

05/29/06 09:04:06 changed by p_lindheimer

my opinion on this is that it is already half there with the direct did functionality.

There have been other request for 'bulk extension loads' to do bulk provisioning. I would think that adding such functionality (import from excel spreadsheet for example) would suffice to do the next step, since the direct did can be included there.

I think once both of these are covered, the remaining cases will be corner cases and not worth trying to do anything for. (So I would suggest closing this one since directdids are already implemented and bulk extension loading is already requested elsewhere)

06/25/06 05:55:05 changed by RobThomas

  • milestone deleted.

I'm taking this out of the 2.2 milestones. It's really quite difficult to do as a global setting (no, really, it is 8). It's still something that, I'm sure, people WILL want, so I'll leave it here as something for someone to do.

06/25/06 05:55:34 changed by RobThomas

(Note - this will be quite EASY to do with asterisk 1.4 and TryExten?() - it'll probably happen then)

07/05/06 22:15:11 changed by gregmac

  • priority changed from 1 to 5.

06/03/07 07:00:59 changed by mbrevda

  • engine changed from All to Asterisk 1.4.x.
  • engine_version changed.
  • svn_rev changed.

07/24/08 16:09:15 changed by p_lindheimer

  • confirmation set to Unreviewed.
  • component changed from Web interface to Core - Users/Devices.
  • version deleted.
  • milestone set to 4.0.

10/19/08 15:35:15 changed by mbrevda

see also #2667