Open Source Training Seminar FreePBX Paid Support

Ticket #1799 (closed Feature Requests: wontfix)

Opened 2 years ago

Last modified 2 years ago

Outbound Route Mapping

Reported by: KMorley Assigned to:
Priority: minor Milestone: 2.3
Component: Core - Trunks/Routing Version: 2.2.1
Keywords: Outbound Route Mapping Cc:
Confirmation: SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

Currently, inbound calls can be routed using the callerID and trunk info combination. By comparison, outbound call rotuting is very simplistic: outbound calls are routed strictly by the number dialed. In my companies case, I need more control.

I propose factoring the extension number in with the dialed number to determine the outbound route. In my companies case, I would prefer that outgoing calls from X101 be routed to a different outgoing trunk than calls from X102, even if the number dialed is identical.

I realize that I have control over the Caller ID friom the extensions, but we use two accounts billed seperately. I need outgoing calls from X101 to go over one trunk and calls from X102 to go over another.

It seems like it would be easy to add if done the same way (and probably using some of the same code) as the incoming routing screen. Also, this might be useful with the multi-tenant project now being considered.

Change History

02/19/07 09:12:34 changed by gregmac

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

#1690 is the solution to this problem. It is based on a context you specify for the user though, there is no limitation of having patterns for extension numbers. This goes along with one of our design goals of keeping extensions portable (eg, if someone using extension 102 moves from office A to office B, they can keep their number, even using something like FreepbxCluster).

I'm going to close this ticket (normally we don't close feature requests) as I don't feel it adds anything beyond what #1690 will do, and I think it would just make the GUI overly complex to have both. If you disagree, feel free to reopen and make the case for why extension-pattern-based routing would be useful.

02/19/07 09:17:26 changed by wiseoldowl

Also you may want to see the instructions for Custom Contexts at

http://www.aussievoip.com/wiki/freePBX-CustomContexts

While this is currently an unsupported module, if you need this capability NOW it will give it to you, just be aware that things may be done somewhat differently in future versions.

02/19/07 09:20:26 changed by wiseoldowl

One addendum, I don't mean to imply that Custom Contexts will allow you to do extension-pattern-based routing, just that it will let you assign different routes to different extensions and/or change the priority of routes used by different extensions.

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads