[asterisk-users] call forwarding number from outside.

[Danny Nicholas]

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Kevin P.
Fleming
Sent: Friday, July 29, 2011 8:49 AM
To: asterisk-users at lists.digium.com
Subject: Re: [asterisk-users] call forwarding number from outside.

On 07/29/2011 09:12 AM, Eric Wieling wrote:
>
>> -----Original Message-----
>> From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users- 
>> bounces at lists.digium.com] On Behalf Of Danny Nicholas
>> Sent: Friday, July 29, 2011 9:06 AM
>> To: 'Asterisk Users Mailing List - Non-Commercial Discussion'
>> Cc: jim.smithson at debsinc.com
>> Subject: Re: [asterisk-users] call forwarding number from outside.
>>
>> The issue with assisted transfer is that the "assisting transferer" 
>> is a second call
>>
>> Outside ->  A
>>
>> A answers
>>
>> A calls B to tell them they have a call (call #2 with ID of A
>>
>> A transfers Outside but the ID stays A
>>
>>
>>
>> Blind Transfer
>>
>> Outside ->  A
>>
>> A answers
>>
>> A blind transfers to B (1 call - keeps ID.
>>
>
>  From the output of "core show application dial":
>
>      f: Force the callerid of the *calling* channel to be set as the
>      extension associated with the channel using a dialplan 'hint'. For
example,
>      some PSTNs do not allow CallerID to be set to anything other than the
>      number assigned to the caller.

In Asterisk 1.8 and later, if the phones (endpoints) support it, the
connected party display on the phone will update *after* the transfer has
been completed to show who the person is talking to (not the person who
performed the transfer).

--
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kfleming at digium.com | SIP: kpfleming at digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at
www.digium.com & www.asterisk.org

Couple of questions - 
This "magic trick" is contained in app_dial?
Functionality is inherent to 1.8/10.X structure so we can't re-invent this
in our old 1.4/1.6 installs?