Ticket #663 (new Feature Requests)

Opened 7 years ago

Last modified 5 years ago

Enhance Call Forwarding Options to allow for different internal / external numbers

Reported by: TheGreyElf Assigned to:
Priority: minor Milestone: Undetermined
Component: Call Forward Version: Eventually
Keywords: Cc:
Confirmation: Unreviewed Distro:
Backend Engine: All Distro Ver:
Backend Ver: SVN Revision (if applicable):

Description

Would be good to allow two different destinations depending on where the call came from. I.e. one route for calls [from-internal] and another for [from-trunk]

Change History

10/25/06 03:54:06 changed by gregmac

  • priority changed from 1 to 5.

This will be fairly difficult to implement, just because it will require a somewhat complex UI.. need more feedback/ideas and a plan prior to implementing this.

01/07/07 00:49:04 changed by wiseoldowl

I think this may be something else that naftali5's Custom Contexts module (see #1447) would permit, at least to some degree.

01/11/07 09:25:40 changed by mbrevda

this might be best grouped with #1592 with a milestone of freepbx 3. These two tickets combined with #993 will create a ultra-powerful app with always on, always there, always available, never-need-to-wait capabilities

06/25/07 11:39:58 changed by wvroger

  • engine_version changed.
  • svn_rev changed.

this would be a good reason to use the follow-me module that is already implemented and being used in 2.0+

07/07/08 22:58:45 changed by WAudette

  • owner changed.
  • confirmation set to Unreviewed.
  • component changed from Applications Module to Call Forward.

Does the use of Follow-Me suffice to close this ticket? I know it can be used this way.

WAudette...

07/08/08 00:05:15 changed by mbrevda

An how will you route a call that comes in thru disa with callerid set as a local extension "user" <203>? This is kinda difficult to implement

07/24/08 20:59:27 changed by ryppn

  • milestone set to Cut Line.