[Asterisk-Users] How to get call back when transfer fails

Andrew Kohlsmith akohlsmith-asterisk at benshaw.com
Thu Apr 22 16:58:49 MST 2004


> I think that is a great idea.  Rather than the phrase you used above,
> something along the lines of "<recorded name> is unavailable.  To be
> transferred to voice mail, press 1.  To return to the previous person
> you spoke with, press 2."  There has to be a more elegant way to say it,
> but you get the idea.

Well I was looking at it more as what the receptionist would hear trying to 
send a call to someone's extension.  I like what you just explained though -- 
it almost eliminates the need for assisted transfer and makes it very 
friendly to the person on the other side.

It's also paving the way to assisted transfer (where you page the extension, 
say "xyz is on the line" and then when you hang up they're connected).

> You could take it to the next step and have a single operator queue, and
> have another option of "To be placed on hold and wait for the person to
> become available, press 3."  Then if they choose that option, "You will
> be connected as soon as the person is available.  Maximum wait time is 3
> minutes, at which time you will be transferred to voice mail.  You may
> press the * key at any time to be immediately transferred to voicemail."

Yes that is very nice!

> The options you are opening up with your idea are tremendous, and will
> help asterisk fit in with and replace some other existing PBX solutions.

Exactly why I'm trying to do it.  :-)

As I said I am hoping to modify res_parking and app_parkandannounce to create 
a more generic app_park, where it returns ${PARKEDAT}, jumps to n+101 if it 
can't park and last but not least OPTIONALLY announces the park location.

I have to say I am really pleased with how modular asterisk is.  Most of the 
apps are under a thousand lines of code, and the whole thing seems to be 
geared for maximum modularity. 

Regards,
Andrew



More information about the asterisk-users mailing list