Re: Cisco IP Communicator

To invoke any feature, the party should be in the control list and
observed.
Except for putting the call on hold and creating a new conference and
redirecting all the needed to parties to the new conference I don't see
any work around. 

-----Original Message-----
From: KRUCHIO Gabor [mailto:[email protected]] 
Sent: Thursday, June 09, 2005 9:46 PM
To: 'Discussion list for Java Telephony API'
Cc: Potluri, Mohan
Subject: RE: [JTAPI] Cisco IP Communicator

Hi Mohan,

do you know any work-around to remove a non-oserved 
external party from conference? E.g. I tried out
CallControlConnection.park() - not yet implemented, too.
But maybe there is any other more-step tricky solution.

Regards:

Gabor

> -----Original Message-----
> From: Potluri, Mohan [mailto:[email protected]]
> Sent: Thursday, June 09, 2005 8:49 PM
> To: [email protected]
> Subject: Re: [JTAPI] Cisco IP Communicator
> 
> 
> Dropping an unobserved party from conference is not
> implemented/supported by Cisco JTAPI.
> 
> 
> -----Original Message-----
> From: Discussion list for Java Telephony API
> [mailto:[email protected]] On Behalf Of Gabor Kruchio
> Sent: Thursday, June 09, 2005 12:16 AM
> To: [email protected]
> Subject: [JTAPI] Cisco IP Communicator
> 
> Hi!
> 
> Question to Cisco gurus:
> 
> Is the Cisco IP Communicator (v.1.1.3.0) a pure JTAPI application?
> 
> I mean: if I need to write my own JTAPI application on top of Cisco
> JTAPI implementation, shall I be able to implement all the features
> of the Cisco IP Communicator?
> I have special interest on the transfer and conference scenarii,
> see my previous post about removing a party from conference.
> 
> Regards:
> 
> Gabor
> 

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JTAPI-INTEREST".  For general help, send email to
[email protected] and include in the body of the message "help".