Transfer types: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
Dcunningham (talk | contribs) No edit summary |
Dcunningham (talk | contribs) No edit summary |
||
| Line 4: | Line 4: | ||
* Features.conf attended transfer |
* Features.conf attended transfer |
||
* Features.conf blind transfer |
* Features.conf blind transfer |
||
* SIP REFER attended transfer |
* SIP REFER attended transfer, first call transferred to second |
||
* SIP REFER attended transfer, second calls transferred to first (Polycom) |
|||
* SIP REFER blind transfer |
* SIP REFER blind transfer |
||
* SIP 302 redirection |
* SIP 302 redirection |
||
Revision as of 03:13, 31 March 2022
The following are types of transfer in Enswitch. Taking in combination with each other, there are a lot of possible permutations - over 2,000 possible items to check are working.
Methods:
- Features.conf attended transfer
- Features.conf blind transfer
- SIP REFER attended transfer, first call transferred to second
- SIP REFER attended transfer, second calls transferred to first (Polycom)
- SIP REFER blind transfer
- SIP 302 redirection
- Asterisk AMI redirect (eg web control panel)
- Call park
- Holding slots
Party:
- Transfer by calling party
- Transfer by 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:
- Direct to telephone line
- To telephone via queue or hunt group (adds a Local dial)
- 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)
- Billing of call