Open Source Training Seminar FreePBX Paid Support

Ticket #1021 (new Feature Requests)

Opened 2 years ago

Last modified 1 month ago

Separate contexts for each trunk

Reported by: gregmac Assigned to: gregmac
Priority: minor Milestone: 4.0
Component: Core Version:
Keywords: Cc:
Confirmation: Unreviewed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

Each trunk should have its own [from-trunk-X] context so we can do trunk-specific modifications, eg, setting a variable to show what trunk the call came in on, changing CID info as per #921, do any other security checks.

Change History

07/13/06 19:18:03 changed by gregmac

Dependant on #1022

11/10/06 08:27:54 changed by gregmac

#888 marked as dupe

01/23/07 15:07:13 changed by naftali5

actually, once this is done, inbound routing should have a choice of routing based on

  1. CID
  2. DID
  3. Zap Channel
  4. Trunk

(I had actually been thinking about adding an optional context to routing, and if entered will create the route in the selected context instead of in from-did making it the simplest way of routing calls with no DID info - with this idea, though, it could be a drop down, much cleaner)

07/24/08 18:52:10 changed by ryppn

  • confirmation set to Unreviewed.
  • engine_version changed.
  • svn_rev changed.
  • milestone set to 4.0.
Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads