Ticket #3736 (new Module Submissions)

Opened 9 months ago

Last modified 1 month ago

callroute module allows temporary redirecting of calls based on CallerID to the entered destinations

Reported by: joshmarquis Assigned to:
Priority: minor Milestone: Cut Line
Component: Third Party Module Version: 2.5-branch
Keywords: cid route incoming Cc:
Confirmation: Unreviewed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

I created this module to provide the same functionality as seen by some large PBX systems. A couple vendors I have worked with provide their support staff with the ability to redirect a clients call back to one particular technician based on CallerID. This saves the client from having to wade through the IVR or waiting in the queue.

Couple spots to smooth out but it's 100% functional at this time.

Attachments

callroute-1.0.tar.gz (4.8 kB) - added by joshmarquis on 06/24/09 19:57:10.

Change History

06/24/09 19:57:10 changed by joshmarquis

  • attachment callroute-1.0.tar.gz added.

(follow-up: ↓ 3 ) 06/24/09 22:57:26 changed by lazytt

Hmm, the concept here is really nice. Before installing it, I imagined that it would auto-magically remember which client to be routed to which extension. Being that you need to set up the routes manually, I don't see how its any different than a dumb-down version of inbound routes.

06/24/09 22:58:17 changed by lazytt

Also, there is no validation in place to prevent bogus input.

(in reply to: ↑ 1 ) 06/25/09 14:23:15 changed by joshmarquis

Replying to lazytt:

Hmm, the concept here is really nice. Before installing it, I imagined that it would auto-magically remember which client to be routed to which extension. Being that you need to set up the routes manually, I don't see how its any different than a dumb-down version of inbound routes.

It's main purpose is to allow the end user to route a number to their or another extension via a feature code. The FreePBX setup interface allows any destination to be entered. Although one could do this through inbound routes, the end user doesn't normally have that access.

I agree about the validation, that is something I hope to add.

08/23/09 20:52:12 changed by p_lindheimer

  • milestone changed from 2.6 to 2.7.

01/30/10 19:43:12 changed by p_lindheimer

  • milestone changed from 2.7 to 2.8.