« Back to Cisco JTAPI Questions

What is the concept of JTAPI Superprovider ?

Combination View Flat View Tree View
Threads [ Previous | Next ]
What is the concept of JTAPI Superprovider ?
Answer
6/12/08 4:53 AM
What is the concept of JTAPI Superprovider ?
Flag

Re: What is the concept of JTAPI Superprovider ?
Answer
6/12/08 4:54 AM as a reply to David Nguyen.
Enabling SuperProvider would not provide / place all Unified CM devices into an enumerable list of devices that helds the app user - device associations list usually.

Instead with superProvider into the picture that list will be empty, and dynamically updated whenever the application during runtime fetches the devices it wants to control using createTerminal() or Acquire() by device name (SEPxxxxxxxxxxxx) before opening it.
Flag

Re: What is the concept of JTAPI Superprovider ?
Answer
7/17/08 1:19 PM as a reply to David Nguyen.
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.
Flag

Re: What is the concept of JTAPI Superprovider ?
Answer
11/12/08 8:43 AM as a reply to David Nguyen.
Hi Vijendra and David,

Do you mean that we could set an Application User, e.g. myAppUser, then add it into "Standard CTI Allow Control Of All Devices" group.

Then in coding, we could use CiscoProvider.createTerminal("SEPXXX") to add the IP phone in the control of the myAppUser, is it? And we don't need to add the IP phones into the Control List of the Application User in CM. Is it?

2nd Question: I cannot find the Acquire() method, which class does it belong?

3rd Question: "maximun number of controlled devices at a time is always bounded by JTAPI/CTI scability limits" <-- do you know what is the limitation? Or how could we estimate it?

Thanks!!

Tony
Flag

Re: What is the concept of JTAPI Superprovider ?
Answer
11/12/08 9:34 AM as a reply to David Nguyen.
Do you mean that we could set an Application User, e.g. myAppUser, then add it into "Standard CTI Allow Control Of All Devices" group.
Then in coding, we could use CiscoProvider.createTerminal("SEPXXX") to add the IP phone in the control of the myAppUser, is it? And we don't need to add the IP phones into the Control List of the Application User in CM. Is it?

This is correct

2nd Question: I cannot find the Acquire() method, which class does it belong?

Acquire - CCiscoLineDevSpecificAcquire class - is the TAPI equivalent of the JTAPI CiscoProvider.CreateTerminal() method.

3rd Question: "maximun number of controlled devices at a time is always bounded by JTAPI/CTI scability limits" <-- do you know what is the limitation? Or how could we estimate it?

7845 (dual proc CCM)
  • CTI Devices per CCM node (up to 4): 2500
  • CTI Devices per Provider instance: 2500
  • CTI Devices max per cluster: 10,000

Lesser models of CCM
  • CTI Devices per CCM node (up to 4): 800
  • CTI Devices per Provider instance: 2500
  • CTI Devices max per cluster: 3200

These are upper bound rules of thumb. Please see the CCM SRND for details and formula for calculating specific impact of CTI applications.
Flag