Ticket #2833 (closed Feature Requests: fixed)

Opened 4 years ago

Last modified 2 years ago

DID Routing direct to trunk

Reported by: adamruck Assigned to: p_lindheimer
Priority: minor Milestone: 2.8
Component: Core - Trunks/Routing Version:
Keywords: Cc:
Confirmation: Confirmed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

Hi Everyone,

First let me thank you for all of you hard work.

My company has two pbx's. One is dedicated to our support department, and the other is for everyone else. Obviously we have an iax trunk that connects them.

I have some DID's that I need to forward from pbx1 to pbx2. Right now I have done this by adding the DID to be forwarded to the outbound route of the iax trunk, and then including that route in my from-pstn-custom context.

It would be much cleaner if under the "Destinations" section of the inbound routes page, I could choose a trunk to send the call down. Any thoughts?

Regards,

Adam Ruck

Change History

07/12/08 20:50:19 changed by p_lindheimer

  • confirmation changed from Unreviewed to Confirmed.
  • component changed from - choose - to Core - Trunks/Routing.
  • milestone changed from Cut Line to 2.5.

07/15/08 20:13:54 changed by p_lindheimer

  • summary changed from DID Routing to DID Routing direct to trunk.
  • milestone changed from 2.5 to 3.0.

08/22/09 16:59:03 changed by p_lindheimer

  • version deleted.
  • milestone changed from 2.6 to 2.7.

02/28/10 09:57:13 changed by p_lindheimer

  • milestone changed from Cut Line to 2.8.

03/12/10 15:37:11 changed by SkykingOH

I am so excited to see this in the milestones.

We have been talking about this feature for some time now. As mult-site implementations become more popular the ability to direct DID's to remote machines is critical.

The only option now is to setup a custom extension with the dial string chan_tachnology/trunk_name/digits_to_send in the dial field. This solution does not scale well.

If a trunk could be a destination of a route (and even and IVR selection) that would solve this issue and create a cleaner configuration.

I will be watching and evangelizing this feature!

03/12/10 15:41:38 changed by p_lindheimer

Just to be clear, being in the Milestone means it is being considered, not necessarily an done deal. But it's good to see there is excitement about this and all the other stuff to come.

03/13/10 01:44:59 changed by p_lindheimer

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

(In [9210]) closes #2833 add trunks as a destination option