Transfer types

The following are types of transfer in Enswitch. Taking in combination with each other, there are thousands of permutations to consider.

Methods:

• Features.conf attended transfer
• Features.conf blind transfer
• SIP REFER attended transfer, first call transferred to second (first call's Call-ID is in the Refer-To data)
• SIP REFER attended transfer, second calls transferred to first (second call's Call-ID is in the Refer-To data, used by Polycom)
• SIP REFER blind transfer
• SIP 302 redirection
• Asterisk AMI redirect (eg web control panel)
• Call park
• Holding slots
• Take call feature prefix

Party:

• Transfer by calling party
• Transfer by called party
• Transfer by party which did call pickup (using ** or *** and is really a calling but a user might think of as the called party)

Call status:

• Transferred call was answered when transfer starts
• Transferred call was ringing when transfer starts
• Transfer destination was answered when transfer completes
• Transfer destination was ringing when transfer completes
• Transfer destination does not answer call
• Call park times out and rings back parking party

Features:

• Transferred call is direct to telephone line
• Transferred call is via queue or hunt group (adds a Local dial)
• Transferred call is to external destination
• Transfer destination is direct to telephone line
• Transfer destination is via queue or hunt group (adds a Local dial)
• Transfer destination is to external destination

Servers:

• Call legs on all same Asterisk server
• Call legs across multiple Asterisk servers in cluster

Affected features:

• Control panel (uses active table)
• Busy lamps (uses active table)
• Queue destinations (uses active and queue_destinations tables)
• Queue event log (queue_events table)
• Billing (billed correctly)
• Call recording (records all call legs with no duplicates)