Re: What is the concept of JTAPI Superprovider ?

Automatic reply: New Message from Abhishek Malhotra in Cisco JTAPI (JTAPI)

2012-10-16T16:25:05Z

On PTO today 10/12/2012

RE: New Message from Alejandra Moreno in Cisco JTAPI (JTAPI) - Cisco JTAPI

2009-08-14T12:35:17Z

- We don¿t support 64bit platform yet. From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Wednesday, August 12, 2009 2:44 AM To: cdicuser@developer.cisco.com Subject: New Message from Alejandra Moreno in Cisco JTAPI (JTAPI) - Cisco JTAPI Questions: CiscoTerminal.getState and jre 1.6 64bit Alejandra Moreno has created a new message in the forum "Cisco JTAPI Questions": -------------------------------------------------------------- Hi, I have a very strange issue. I developed a CTI tool which uses a CTI super provider user to place calls dinamically. After updating the servers the tool was not able to place calls because the terminals never became InService. My code loops for a certain time checking the state of the terminal using CiscoTerminal.getState(). The terminal DOES deliver the InService event. I have been troubleshooting and this just happens if I use jre 1.6u7 in a 64bit server. If I use jre 1.5u14 the issues doesn't appear. And the issue doesn't appear at all in 32bit servers. I have CUCM 4.2(3)sr4b. Can someone explain this behavior? Thanks! regards, alej -- To respond to this post, please click the following link: or simply reply to this email.

RE: New Message from Anders Westlund in Cisco JTAPI (JTAPI) - Cisco JTAPI Q

2009-07-02T11:21:05Z

Call can be non-secure depending upon end point capabilities. ________________________________ From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Wednesday, July 01, 2009 8:09 AM To: cdicuser@developer.cisco.com Subject: New Message from Anders Westlund in Cisco JTAPI (JTAPI) - Cisco JTAPI Questions: Manually set securelvel of new call Anders Westlund has created a new message in the forum "Cisco JTAPI Questions": -------------------------------------------------------------- I have a Callmanager 7 that is setup to use secure connections. I have an application where I would like to force a call to be non-secure. All connections etc are secure, so I would manually need to set the call to insecure during the setup phase. Is there a way to achieve this? Thankful for ideas! BR Anders -- To respond to this post, please click the following link: or simply reply to this email.

RE: New Message from Dominik Smogor in Cisco JTAPI (JTAPI) - Cisco JTAPI Qu

2009-07-02T11:16:05Z

That's correct, Cisco JTAPI doesn't support/implement AgentTerminal. We only support RoutingPackage ( RouteSession/RouteCallBack ) in javax.telephony.CallCenter package. thx. ________________________________ From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Tuesday, June 30, 2009 3:19 AM To: cdicuser@developer.cisco.com Subject: New Message from Dominik Smogor in Cisco JTAPI (JTAPI) - Cisco JTAPI Questions: Agent ready/not ready Dominik Smogor has created a new message in the forum "Cisco JTAPI Questions": -------------------------------------------------------------- I have got UCCX instance configured to queue and distribute calls to common number to some number of agents in the call center. As long as they use Cisco Agent Desktop which allows to mark an agent as busy/ready everything works ok. We however have our custom application integrated with CCM using cisco JTAPI client (7.0.(1.1000)-1). I'm trying to find a way to mark Agent (and thus the associated telephone number) as busy using JTAPI. We have found that manipulating the state of the Agent object is the way to go. The problem is that we failed to obtain the object. 1. The Terminal implementations fails to cast to AgentTerminal (eclipse search tells that in the included jar no object actually implements it) 2. The CallCenter provider can be obtained javax.telephony.JtapiPeerFactory but methods throw not implemented exception. Does it mean that Cisco JTAPI doesn't support the Agent side. Is there some other way to controll agent state. -- To respond to this post, please click the following link: or simply reply to this email.

Re: Does Cisco JTAPI support getMessageWaiting() on CallCtrlAddress?

2008-10-31T20:49:41Z

Java doc for CiscoAddress.setMessageWaining() clearly specified "Note: This implementation currently does not enforce the following postconditions as specified in CallControlAddress: this.getMessageWaiting() == enable CallCtlAddrMessageWaitingEv gets delivered for this Address" This basically means that CiscoJTAPI currently don't provide this event. Bottom line is that we don't have a way to know existing status of MWI on phone, you can only set or unset using the interface.

Re: Meet-Me conference

2008-08-07T14:26:59Z

Meet-Me conference is not Supported by CiscoJTAPI, we don't provide participant list or CiscoConferenceStartEV or CiscoConferenceEndEv for Meet-Me conference. If you make call to already scheduled Meet-Me number, it will appear like basic call with two sides.

Re: how can I get Original Calling Number in transfer scenario?

2008-07-23T12:07:56Z

[quote]From any Connection event, you can get Connection object, from[/quote] Connection you can get specific CiscoCall. I don't see confusion here. If you are using event directly, you can typecast ConnAlertingEv to ConnEv, and get Connection using ConnEv.getConnection() and then Connection.getCall() and typecast call to CiscoCall. HTH

Re: how can I get Original Calling Number in transfer scenario?

2008-07-23T00:31:04Z

After Transfer is completed, you can look at CiscoCall.getCurrentCallingPartyAddress() or CiscoCall.getCurrentCallingPartyInfo(). HTH.

Re: What is the concept of JTAPI Superprovider ?

2008-07-17T13:19:38Z

Superprovider capability can be added to JTAPI application user by adding user to group "Standard CTI Allow Control Of All Devices" at CUCM Admin pages. This provides application ability to control any device in cluster dynamically without having device in Application user control list. The very common mis-conception about Superprovider capability is that it increases scalability limit of JTAPI, that is not be true. It only increases flexibilty to dynamically control any devices in the system however maximun number of controlled devices at a time is always bounded by JTAPI/CTI scability limits. Applicatoins can use API provider.createTerminal(String devicename) to add device in control list dynamically, however application would have burden to discover devicename through some other sources.