Ticket #692 (closed Feature Requests: duplicate)

Opened 3 years ago

Last modified 2 years ago

Outbound Routing based on call source

Reported by: webrainstorm Assigned to:
Priority: blocker Milestone: 2.2
Component: Core Version: next release
Keywords: outbound routing Cc:
Confirmation: SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

Hi all,

we're willing to implement the possibility to specify outbound routing criteria based on the extension originating the call. Before starting the implementation we're willing to know if somebody is doing the same thing or if the topic has already been discussed and you have decided some implementations guidelines.

I've seen on the mailing lists many user asking for custom configs that can be solved with this feature

Someone is interested in this functionality ?

Regards

Edoardo

Change History

04/23/06 14:49:40 changed by RobThomas

As far as I know, no-one's working on routing based on extension.

--Rob

05/19/06 08:04:24 changed by SnoWolfe

I submitted a module that sorta does that. We are actually using it for outbound routing, although i used inbound routing rules.

05/19/06 08:05:36 changed by SnoWolfe

The docs I wrote were directed more for an end user installing, but I had to add a couple of lines to the core extensions. So the instructions may seem a bit abrasive.

05/19/06 22:32:21 changed by RobThomas

SnoWolfe - Which module is that?

05/22/06 08:44:28 changed by SnoWolfe

#788 - Custom Routing Based on Caller ID

05/28/06 06:23:55 changed by wozto1s

  • milestone set to 2.2.

06/20/06 07:55:02 changed by gregmac

Redirected #636 here

07/17/06 17:41:37 changed by gregmac

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

dupe of #461

01/08/07 11:46:44 changed by

  • milestone deleted.

Milestone 2.2 deleted

01/08/07 12:55:40 changed by vgster

  • milestone set to 2.2.