Jump to: navigation, search

T-Lib-Initiated SingleStepTransfer User Busy


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.


SIP Endpoint SDK T-Lib-Initiated SingleStepTransfer User Busy.jpg

This page was last edited on August 31, 2017, at 13:51.
Comments or questions about this documentation? Contact us for support!