# Make transfers come back on no answer

**URL:** <https://community.asterisk.org/t/make-transfers-come-back-on-no-answer/17474>\
**Category:** Asterisk Support\
**Created:** [November 7, 2007, 8:46pm UTC](https://community.asterisk.org/t/make-transfers-come-back-on-no-answer/17474 "2007-11-07T20:46:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dlublink](https://avatars.discourse-cdn.com/v4/letter/d/85f322/32.png) [@dlublink](https://community.asterisk.org/u/dlublink)\
**Post date:** [November 7, 2007, 8:46pm UTC](https://community.asterisk.org/t/make-transfers-come-back-on-no-answer/17474/1 "2007-11-07T20:46:49Z")

</div>

Hey,

When transfering a call, if the end user doesn’t answer how do I make it ring back to the transfering extension?

I found this post on another forum :  
[forum.voxilla.com/asterisk-suppo … 11971.html](http://forum.voxilla.com/asterisk-support-forum/asterisk-callback-no-answer-11971.html)

But it seems to me there should be an easier way to do this than duplicating all my extensions.

Is there a way to distinguish if the called extension is being transfered or not? If there was a variable like ${TRANSFERING} that is set in the channel, I could use that for the callback without duplicating all my extensions with a prefix.

When transfering with SIP I see :

SIPTRANSFER=yes  
[SIPTRANSFER\_REFERER=david-work@sip.lublink.net](mailto:SIPTRANSFER_REFERER=david-work@sip.lublink.net)

Thanks,

David

---

<div class="post-metadata">

**Author:** ![yusuf](https://avatars.discourse-cdn.com/v4/letter/y/c68b51/32.png) [@yusuf](https://community.asterisk.org/u/yusuf)\
**Post date:** [November 8, 2007, 5:13pm UTC](https://community.asterisk.org/t/make-transfers-come-back-on-no-answer/17474/2 "2007-11-08T17:13:53Z")

</div>

Hi,

on [svn.digium.com/view/asterisk/tru … iew=markup](http://svn.digium.com/view/asterisk/trunk/CHANGES?view=markup)  
specifically:  
246 Call Features (res\_features) Changes  
247 ------------------------------------  
248 \* Added the parkedcalltransfers option to features.conf  
249 \* The built-in method for doing attended transfers has been updated to  
250 include some new options that allow you to have the transferee sent  
251 back to the person that did the transfer if the transfer is not successful.

so either wait for 1.6, or check out the lastest svn, or back-port this feature.
