advanced retry-dial (callback) funtionality

One of the biggest drawbacks should a newcomer to an Asterisk PBX find, migrating from legacy analog one is the callback behaviour.

User got used to pressing one button to activate the service, thus "capturing" the line, so when the called party hangs, a call is placed between them. For example, on the popular Spanish IBERCOM PBX, this behabiour is obtained when user press *6.

Current developments simulate that callback by placing the callback reversely, starting at the callee phone, and ending at the caller one. This behaviour is inverse to what the user has been using for a long time, and in the short term can produce multiple problems.

The callback scheme is as follows:

1. Calling party, after calling busy destination, listens to a hearing pointing the possibily to activate the callback by pressing 6.

2. When called party hangs, our script gets an event, and searches through the database, checking if there is a callback service activated.

3. If affirmative and being under the callback expiry time, the script then checks if the parties are available. Should any of them be busy, the callback is postponed.

4. If either of them are idle, then the callback is placed with a caller id as follows:

Callback from ext1. to ext2.

where ext1 is the calling party and ext2 is the called one.


Detailed description of the service, forums and code, can be obtaind from Asterisk Arena here
One of the biggest drawbacks should a newcomer to an Asterisk PBX find, migrating from legacy analog one is the callback behaviour.

User got used to pressing one button to activate the service, thus "capturing" the line, so when the called party hangs, a call is placed between them. For example, on the popular Spanish IBERCOM PBX, this behabiour is obtained when user press *6.

Current developments simulate that callback by placing the callback reversely, starting at the callee phone, and ending at the caller one. This behaviour is inverse to what the user has been using for a long time, and in the short term can produce multiple problems.

The callback scheme is as follows:

1. Calling party, after calling busy destination, listens to a hearing pointing the possibily to activate the callback by pressing 6.

2. When called party hangs, our script gets an event, and searches through the database, checking if there is a callback service activated.

3. If affirmative and being under the callback expiry time, the script then checks if the parties are available. Should any of them be busy, the callback is postponed.

4. If either of them are idle, then the callback is placed with a caller id as follows:

Callback from ext1. to ext2.

where ext1 is the calling party and ext2 is the called one.


Detailed description of the service, forums and code, can be obtaind from Asterisk Arena here
Created by: agorosti, Last modification: Sun 08 of Mar, 2009 (13:25 UTC)
Please update this page with new information, just login and click on the "Edit" or "Discussion" tab. Get a free login here: Register Thanks! - Find us on Google+