Open Source Training Seminar FreePBX Paid Support

Ticket #993 (closed Feature Requests: fixed)

Opened 2 years ago

Last modified 3 months ago

Private queue for every extension

Reported by: lazytt Assigned to:
Priority: minor Milestone: 2.5
Component: Core - Users/Devices Version:
Keywords: Cc:
Confirmation: Confirmed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

I would like to suggest the folowing feature: usualy when an extension is called if the extensions is busy the call goes to Voice Mail. But maybe the caller want to HOLD untill the extension becomes avalible? Althought this may not be usefull in home setups (as people tend to talk (read=yap) a long time AND the next call usualy isnt time critical), it would be very benificial to a bussnies setup (where a. the calls are usualy short and to the point (unless my wife works there! ;-)) and b. I NEED to speak to you so i dont mind holding a bit). Takning this a sep further migh include an IVR "the extension u called is busy. Press 1 to leave a message or continue to hold".

Change History

11/30/06 07:45:14 changed by lazytt

from #freepbx <groogs> .. he wants to be able to intercom the people in the queue, have BLFs for them, but not actually have anyone call them directly.. oh, unless they need to, but then sometimes they have to go to the queue anyways <groogs> and it has to do all that without people remembering different extension numbers !

11/30/06 08:11:11 changed by lazytt

oh, and i want to be able to do call pickup

01/11/07 04:04:41 changed by vgster

  • engine set to Asterisk <1.2.
  • engine_version changed.
  • svn_rev changed.

You can do call pickup already. Or did you mean call pickup in a difference sense to picking up a call on a ringing phone.

01/11/07 04:26:26 changed by lazytt

i meant that the numbering of the extension must be in such a way the the typical user can remember how to do call pick up. At the moment we call extensions using its q (i.e. q303 ring extension 203, so ide call 303 to get thru to 203). But then everyone needs to remember that call pick for extension 303 instead of **303 is really **203 (on grandstreams anyway).

01/14/07 10:55:36 changed by wiseoldowl

Just commenting on the part, "But maybe the caller want to HOLD untill the extension becomes avalible?" And now that I think about it, I cannot think of any way in FreePBX to do what in some systems is called "camp-on". The idea of camp-on is that in a situation where the called extension is busy, the caller hears a recording that says something like "(called user) is on another call. You may hold to wait for the line to become available, or press 1 at any time to leave a voicemail message." The caller then hears a couple minutes of music-on-hold, then usually a reassurance message (e.g. "(caller user) is still on another call. You may continue to hold, or press 1 at any time to leave a voicemail message. No further announcements will he heard"), then music-on-hold until the caller presses 1 (or hangs up). Of course, if at any time during this the called extension becomes free, the recording or music is cut off and the call is immediately put through.

I think we've all encountered this feature when calling a large business, but I have not seen any way to do it in FreePBX. If it is possible to do in Asterisk, then the best approach might be to use an AGI script to do it, and then under the "status" dropdown in each extension's Voicemail & Directory section add a new option - in addition to "Enabled" or "Diasbled" add "Camp-On", which would activate this behavior

01/14/07 11:18:42 changed by wiseoldowl

Oh, and now that I think about it, with camp-on the caller could also be given other options, such as "press 1 to leave a voicemail, press 2 to try another extension, press 3 to return to the main menu, or 0 to speak to an operator" - which almost implies an IVR-like structure, except that it would be interruptable if the called extension hangs up, and on timeout would play music on hold but still wait for the called extension to become free.

This might imply that the IVR code could be adapted to allow entry "seeded" with a called extension number. If it is entered that way, while playing messages and so forth it could check once per second to see if the called extension has become free, and if so abort playing messages and transfer the call. If the caller presses 1 to continue to hold, it would return to the same IVR after a couple of minutes, except that at the beginning announcement it would say "(caller user) is still busy" rather than "...is busy". Also I may not have made clear is that (called user) is whatever would be played if normal voicemail were used and the user had recorded his/her name but not a busy or unavailable message. So it would either say "Mary Smith" (if Mary had recorded her name) or "the person at extension (whatever)" and then "is (still) busy".

Basically here's a flowchart of what I'm thinking:

Incoming call --> main IVR --> caller makes IVR selection (to extension) --> extension is busy --> enters "camp-on" IVR (from here on keeps checking and will transfer call immediately if called extension becomes free, though that is canceled if caller makes a selection at IVR not to wait) --> caller elects to wait (makes no selection at IVR) --> music on hold for 2 minutes (still listening for caller to make IVR selection) --> camp-on IVR repeats with "reassurance" message played --> music-on-hold until called extension becomes free or caller makes IVR selection or hangs up

As you can see this would be significantly different from normal IVR operation yet could probably utilize much of the same code, IF it is even possible to do something like this in Asterisk.

01/14/07 21:22:52 changed by gregmac

  • component changed from - choose - to Core - Users/Devices.
  • milestone set to 3.0.

01/15/07 03:14:12 changed by lazytt

Thanks gregmac! you beat me to it. i was going to say - now that we have an "official" name and a clear goal, we really are trying to do the same thing as #1592. I see both ideas as two sides to the same coin, i.e. the call should end up (and possibly ALWAYS start off - depending on the requirments of the situation) in the camp-on state. Possibly in a queue of sorts (so that more than one caller can camp-on a given extension) but always end in the options menu as per #1592

11/13/07 19:54:30 changed by p_lindheimer

  • confirmation set to Confirmed.
  • milestone deleted.

07/24/08 18:47:02 changed by ryppn

  • milestone set to Cut Line.

07/24/08 18:52:29 changed by lazytt

  • status changed from new to closed.
  • resolution set to fixed.
  • milestone changed from Cut Line to 2.5.

lets call this vmx

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads