The transferring is done by the user on the phone itself. CUAE doesn't
do it

Phone A calls Phone B
B answers
B consult transfers to Phone C
This is where the script gets the hangup event and stops getting anymore
events
Phone C hangs up
No events raised in CUAE

Thanks

Jason

-----Original Message-----
From: Zafar Shakeel (zshakeel) mailto:zshakeel@cisco.com
Sent: Tuesday, July 08, 2008 2:46 PM
To: Jason Freitas
Subject: RE: [Cuae-developers] Jtapi transfer question

Hi Jason:

Just trying to create the flow here. If phone A is being monitored and
it receives a call, a jtapiIncomingCall event would be fired and your
application script will get invoked. What kind of transfer is happening
here ? Is it a Jtapi's transfer API, or a consult transfer etc ?

Thanks,

-Zafar

-----Original Message-----
From: cuae-developers-bounces@developer.cisco.com
mailto:cuae-developers-bounces@developer.cisco.com On Behalf Of Jason
Freitas
Sent: Tuesday, July 08, 2008 3:56 PM
To: cuae-developers@developer.cisco.com
Subject: [Cuae-developers] Jtapi transfer question

Hi,

I have a script that triggers off a jtapiIncomingCall event. If a call
is transferred to the phone it triggers the app, but as soon as the
transfer completes the app receives a jtapiRemoteHangup event even
though the call is still active. More importantly it doesn't receive
any jtapi events after the hangup, no callactive, callinactive or hangup
events when the final call hangs up. Is this normal? Is there any way
to keep catching events or do I have to poll with JTapiGetDeviceStatus?

Thanks

Jason

_______________________________________________
Cuae-developers mailing list
Cuae-developers@developer.cisco.com

_______________________________________________
Cuae-developers mailing list
Cuae-developers@developer.cisco.com