New Snapshot

[Nicolás Gudiño <nicolas@xxxxxxxxxxxx>]

Hi All,

I have packaged a new snapshot release, including attendant transfers 
and some bug fixes, including the blind transfer that went to nowhere 
when no voicemail extension was defined. Instructions to enable 
attendant transfers are inside op_server.cfg. You have 3 new parameters 
to add, if found, attendant transfers wil take over the barge 
functionality. So you cannot have both on the same panel context as for 
now. Attendant transfers use meetme for bridging channels, that means 
that you will probably have strange CDR records, and possible some 
other issues as meetme is not the same a a standard bridged call.

To peform the attendant transfer, you have to drag the destination 
phone into your own. Everything else will be fairly automatic:

1) You and the person you were talkin to are redirected into a 
conference room
2) The person you were talking to is redirected to a special hold 
extension
3) Destination is placed into the same conference (originate a call to 
meetme), you can talk normally.

4)
  a) If you hangup, the hold extension will be redirected into the 
meetme (to talk to destination)
  b) If destination hangs up, hold extension will be redirected into 
the meetme (to keep talking to you)

5) If for some reason the destination extension fails to pickup in step 
3 (originatefailure), and you have defined 
"attendant_failure_redirect_to"  parameter in op_server.cfg, the person 
you were talking to is redirected to that extension instead of the 
meetme room. That extension might be static or constructed using the 
original destination extension, so you can for example redirect the 
caller directly to voicemail, or to a queue, or whatever.

This feature was sponsored, it is not ideal to use meetme but there is 
no other way to do it using stock asterisk without patches.

Best regards,

--
Nicolas Gudino
Buenos Aires - Argentina