Author Message
BrentThomas
Joined: Jan 15, 2011
Messages: 0
Offline
Hello looking for which API's to use for warm and blind xfer, this has been requested by T-Mobile. Also is their any issues to use these API's to xfer to a VDN.
DipeshGandhi2 [Avatar]

Joined: Nov 14, 2011
Messages: 35
Offline
Hi Brent,

There is not specific API for transfer but you can use playVoiceXmlMessage API under Audio Call Web Services. This will require for you to create a VoiceXML script in which you can place <transfer> element tag. Here you can define transfer type (bridge, blind, refer) and transfer to VDN. When you invoke playVoiceXmlMessage you will need to provide audioURL path which is location of the VXML script.

Thanks,
Dipesh

Dipesh Gandhi
Software Engineer, Avaya DevConnect

DipeshGandhi2 [Avatar]

Joined: Nov 14, 2011
Messages: 35
Offline
Brent - I apologize, I overlooked some options that are available to you under Call Extensions web service. Under Call Extensions, you may use singleStepTransfer or redirectCall API's for blind transfer. The singleStepTransfer will act as true blind transfer whereas with redirectCall behaves similarly but only transfer at ringing event.

For warm transfer you may use both consultationCall with consultationComplete API's. These API's put together will provide the warm transfer capability. The consultationCall will place existing call on hold and place call to consulting endpoint. To finish, consultationComplete will transfer the held party to the consulted party.

For more information on these API's, please see Avaya ACE WEB Services documentation - Chapter 8: Third Party Call Extensions.

Please let me know if you have further questions.

Dipesh Gandhi
Software Engineer, Avaya DevConnect

DipeshGandhi2 [Avatar]

Joined: Nov 14, 2011
Messages: 35
Offline
Brent,

Another note that Third Party Call Extensions does require that the call is built using Third Party Call Control V2 using makeCall. In other words, ACE must be aware of the call for Call Extensions to function.

Similarly if you are working with Third Party Call Control v3, there is transferCallParticipant API that will help achieve transfer. With TPCCv3, the makeCallSession must be used to build the call in order for transfer to work.

As you can see with both of the transfer capabilities of ACE, it requires the call to be outbound.

Dipesh Gandhi
Software Engineer, Avaya DevConnect

DipeshGandhi2 [Avatar]

Joined: Nov 14, 2011
Messages: 35
Offline
Brent,

If you subscribe for call notifications on a device (e.g. setting call monitor on device using Call Notification web services startCallNotification API), this will also provide Call ID which you may use to invoke Third Party Call Extension services. With the Call ID you can invoke singleStepTransfer or consult API calls as I mentioned previously.

Dipesh Gandhi
Software Engineer, Avaya DevConnect

Go to:   
Mobile view