Difference between revisions of "Blind Transfer During Connection"
From Zenitel Wiki
(→Software Operation) |
|||
Line 1: | Line 1: | ||
− | {{ | + | {{AI}} |
== Description == | == Description == | ||
The regular Call Transfer is capable of doing transfer only after a successful inquiry to another station during connection. <br /> | The regular Call Transfer is capable of doing transfer only after a successful inquiry to another station during connection. <br /> | ||
Line 34: | Line 34: | ||
===Known limitations=== | ===Known limitations=== | ||
− | |||
*A (AlphaCom) calls B (SIP) and A try to transfer B to a ringing group. This is currently not supported. ( A (SIP) calls B (AlphaCom) and B transfer to Ringing group is working) | *A (AlphaCom) calls B (SIP) and A try to transfer B to a ringing group. This is currently not supported. ( A (SIP) calls B (AlphaCom) and B transfer to Ringing group is working) | ||
− | |||
− | |||
− | |||
Revision as of 14:27, 20 May 2022
Description
The regular Call Transfer is capable of doing transfer only after a successful inquiry to another station during connection.
This means if no answer during inquiry it is not possible to transfer the call to a private ringing station or a ringing group.
Blind transfer is based on the Inquiry Call feature.
Configuring Inquiry with parameter 1 = 1 will activate transfer directly to the feature directory number dialed during Inquiry.
This extends the transfer feature to also give the possibility to do transfer to:
- Stations in private
- Ringing groups
- SIP phones
- Group call
- ++
In combination with automatic search a switchboard operation can be made.
The search string number counter and station is reset when preforming a blind transfer.
Example:
- A is a switchboard defined as ringing group 1.
- B and C are users with automatic search on private ringing /busy programmed as ringing group 1.
- D is someone calling to the switchboard, could be SIP or AlphaCom station.
- D calls A
- A does a blind transfer to B, B is private ringing
- After private ringing timeout D is activating ringing group 1 call back to A, from B's first search string
- A does a blind transfer to C, C is busy
- D is activating ringing group 1 call back to A, from C's first search string
etc. etc.
Known limitations
- A (AlphaCom) calls B (SIP) and A try to transfer B to a ringing group. This is currently not supported. ( A (SIP) calls B (AlphaCom) and B transfer to Ringing group is working)