Ticket #3035 (closed Feature Requests: fixed)

Opened 4 years ago

Last modified 2 years ago

Outbound call trunk control by extension (in some form)

Reported by: rjenkinsgb Assigned to: p_lindheimer
Priority: major Milestone: 2.6
Component: Core - Trunks/Routing Version: 2.5-branch
Keywords: Trunk Routes Contexts Cc:
Confirmation: Confirmed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

Request: Limit or somehow control which outbound trunks or routes each extension can use.

(I know something along these lines is in progress, in a similar manner to the 'Custom Contexts' addon for 2.3)

I have no idea how you are planning to implement this, but one thought is use 'callgroup' or similar in the extension and allow outbound routes and/or trunks to optionally be restricted to extensions in a specific group or groups.

Reason: Outgoing call segregation for business departments / offices / multi-business shared sites etc. where calls are allocated to specific trunks so each office is billed seperately by 'their' trunk provider.

$500.00 extra donation as soon as this can be done without add-ons. (I consider it Major priority as the Custom Contexts module appears abandoned & a lot of people would like this ability).

Change History

08/09/08 13:09:39 changed by p_lindheimer

  • confirmation changed from Unreviewed to Confirmed.
  • milestone changed from 2.5 to 3.0.

02/13/09 11:25:33 changed by wiseoldowl

Just so you know, if you really need to do this NOW and don't want to use Custom Contexts, you can use one of the methods outlined in How to give a particular extension different or restricted trunk access for outgoing calls - these methods are not exactly elegant, but they do work in a pinch and are arguably easier to implement than Custom Contexts.

02/13/09 11:31:34 changed by wiseoldowl

See also Ticket #3450 and Ticket #3301 for similar requests.

08/15/09 20:10:43 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to fixed.

there are a few existing options such as custom-context and routepermissions.