Attended transfers and displayed number

Hi,

I’ve got asterisk 10.6 up and running. Most works, except for some minor issues, which are due to my inexperience with Asterisk / VOIP in general.

I’ve noticed one thing, which I can’t pinpoint :

When an incoming call occures, and I do an unattended xfer, the extension receiving the call sees the inbound callers number
When doing an supervised xfer, the extension receiving the call sees the number of the call that picked up the inbound call.

voip-info has a note on this : voip-info.org/wiki/view/Aste … tures.conf, which says :

atxfer …

Note The caller ID presented to the person you are trying to transfer the call to is not what you would expect - Asterisk sets your caller ID to be the extension the call originally arrived at which may not be the same as the extension the call was answered at. There doesn’t appear to be any way of getting the correct caller ID.

That is exactly what I’m seeing. Is there a to solve this ? In case it matters : I’m using Aastra 6757i (aka 57i) phones.

Regards,

Igmar

SIP or features.conf.

For SIP, this is exactly what I would expect, with the proviso that some phones actually do blind transfers using the attended transfer mechanism.

When a SIP phone starts an attended transfer, it makes a call on its second line with no indication that this will result in a transfer and no indication as to who is on its first line (the second line may not be a second line that is directly available on the user interface). Asterisk has to treat this as a completely independent call.

When a SIP phone make a proper blind transfer, it tells Asterisk to transfer the call on the first line and Asterisk is fully aware of the fact that this is a transfer, before it starts ringing the new destination.

I can actually imagine certain cases where it would be a breach of confidentiality to reveal the identity of original caller (acting as broker).

I am not sufficiently familiar with features.conf transfers to know how CLID is handled by them.

[quote=“david55”]SIP or features.conf.

For SIP, this is exactly what I would expect, with the proviso that some phones actually do blind transfers using the attended transfer mechanism.

When a SIP phone starts an attended transfer, it makes a call on its second line with no indication that this will result in a transfer and no indication as to who is on its first line (the second line may not be a second line that is directly available on the user interface). Asterisk has to treat this as a completely independent call.
[/quote]

How does it know the SIP address to call ? Only asterisk knows the extension -> SIP address mapping. I did suspect this ,because asterisk logging was quiet after the forward. It’s nasty, since I also can’t reprogram that specific key on this phone.

[quote]
When a SIP phone make a proper blind transfer, it tells Asterisk to transfer the call on the first line and Asterisk is fully aware of the fact that this is a transfer, before it starts ringing the new destination.

I can actually imagine certain cases where it would be a breach of confidentiality to reveal the identity of original caller (acting as broker).

I am not sufficiently familiar with features.conf transfers to know how CLID is handled by them.[/quote]

Blind transfers work fine. It’s the supervised transfers that have this behaviour.

The phone dials the extension at the Asterisk server in the normal way and Asterisk tranlates this, but it does it on the basis that it is a completely independent call.