AIR VoIP transfer problem

[martinep]

HI !!!
I have some problems transferring calls to a VDN on a CM3 from an AIR 1.3 with VoIp channels. The transfer is made with the A_trans ASAI function, it begins correctly, but it doesn't complete the procedure. Trace file states an "Unsucessful Selhold" error. The ASAI link is working, as I'm collecting ANI and DNIS with the A_callinfo ASAI function.
I also created an ASAI domain for the DVN that route the calls to the AIR VoIP channels and another one for the VDN where to transfer the calls (it contains only an announcement). In attachment I've put the log file and the IVR Designer screen of the TAS application.
For me this is a "blocking" problem I think this could be IR bug related to the VoIP link with the S8700, what could be the cause of the problem?

 

[Cti4all]

Not familiar with the Selhold error, but in ASAI, transfer is a few steps including:

Take Control (of call 1)
Place call 1 on hold
Make Call (call 2)
merge call 1 and call 2, drop party 1 on call 2

From the error description, I suspect perhaps a call control conflict is occurring (only one controller is allowed).

Do you have other CTI applications using call control? Commonly, Total Recall and Geotel use Call Control as a "cheap" way to track call progress through the life of the call.

Alternately, does the A_trans method allow you to specify the handler to use to initiate the transaction? If you can use the association of the event notification association on the IVR port to initiate the transfer, instead of creating a new call control association, you can possibly avoid the conflict.

Avaya T3 can use ASAI MST trace to see if the conflict is indeed due to call control conflict.