(Created target blank page For Version: SESDK:9.0.0OSX) |
(Update with the copy of version: 9.0.0OSXDRAFT) |
||
| Line 1: | Line 1: | ||
| − | + | = T-Lib-Initiated SingleStepTransfer User Busy = | |
| + | |||
| + | {{Documentation:SESN:Library:t-lib-init1steptransferuserbusy:81Source}} | ||
| + | |||
| + | [[Category:V:SESDK:9.0.0OSX]] | ||
Latest revision as of 13:51, August 31, 2017
T-Lib-Initiated SingleStepTransfer User Busy
Description
If a single-step transfer is attempted and UA3 returns a busy signal or a no-answer event and rejects the attempted transfer, UA2 may or may not be available to pick up the dropped call. Note that due to the nature of single-step transfers, a call can be dropped in these cases. In addition to that, there is no guarantee that UA2 will still be available if UA3 reports busy or does not answer within a reasonable time. Thus, if your contact center requires that calls not be dropped, you should use consult transfer, not single-step transfer.
Diagram
This page was last edited on August 31, 2017, at 13:51.
Comments or questions about this documentation? Contact us for support!