Presentation is loading. Please wait.

Presentation is loading. Please wait.

SV8100 and CTI October 2011, Overview.

Similar presentations


Presentation on theme: "SV8100 and CTI October 2011, Overview."— Presentation transcript:

1 SV8100 and CTI October 2011, Overview

2 Agenda SV8100 CTI overview SV8100 CTI pricing aspects
What is CTI Call Control: 1st and 3rd party SV8100 CTI overview SV8100 CTI pricing aspects SV8100 compatibility diagram

3 CTI What is CTI? Computer Telephony Integration, also called computer–telephone integration or CTI, is technology that allows interactions on a telephone and a computer to be integrated or coordinated The following functions can be implemented using CTI: Call information display (e.g. caller's number) Automatic dialing and computer controlled dialing (e.g. click to dial) Phone control (answer, hang up, transfer, forward, hold, conference, etc.) Coordinated phone and data transfers between two parties (i.e. pass on the Screen pop with the call) Two forms of CTI 1st Party Call Control 3rd party Call control

4 First Party vs. Third Party Call Control
User PC connects directly to the SV8100 Individual user controls telephone call 3rd Party Network server acts as “home base” PC talks to the CTI server Server controls the switch Logical link between PC and phone

5 SV8100 CTI Offering SV8100 External Application Interfaces
Using a TAPI Service Provider (TSP) for using TAPI enabled applications e.g. dialing from Outlook and call pop-ups (via middleware) with Outlook info 1st party CTI (Tapi 1.4) and 3rd party CTI (Tapi 2.1) available NEC platform TSP Interfaces One and the same interface made available for all NEC platforms: One time application development for apps on all our platforms (does need application verification per platform because of different system behavior, e.g. in timing) Provides 3rd party CTI (Tapi 2.x) NEC CTI Software Development Kit For software development Rich interface SDK (more than TAPI 2.x) Excellent developers manuals including source code samples Desktop Suite (DTS)1st Party TAPI When using DTS, a 1st party TAPI interface can be provided (sub-set of TAPI 1.4) Comes for free with DTS Assistant and Attendant Business ConneCT (BCT) 3rd Party TAPI All BCT clients have a 3rd party TAPI 2.x interface which supports Click to dial E.g. Click to dial out of Outlook Comes included in a BCT client Notes: To know which one to use, please also refer to the compatibility matrix at the end option 2 and 3 will be bundled in the near future

6 1) SV8100 External Application Interfaces: TAPI
Using a TAPI Service Provider (TSP) for interfacing with TAPI enabled applications e.g. dialing from Outlook and call pop-ups (via middleware) with Outlook contact info Available: 1st party CTI (Tapi 1.4) 3rd party CTI (Tapi 2.1) Windows 7 (32 & 64 bit) Windws Server 2008 R2 The TSP drivers are made available, FOC, on the technical system CD and Software database Requires one or more licenses in the SV8100 (see next page) We provide a TAPI interface with a list of supported functions. It is the developers responsibility to meet the requirements for their application for the relevant call scenario’s. Note: SBS/terminal services support is scheduled after the R6 release of the SV8100

7 SV8100 TAPI interface Ordering
For first party, one pays per client license For third party it is a one time fee

8 2) NEC platform TSP interface
Using a TAPI Service Provider (TSP) for interfacing with TAPI enabled applications e.g. dialing from Outlook and call pop-ups with Outlook info The same interface made available for all NEC platforms: One time application development for apps on all our platforms (does need application verification per platform because of different system behavior, e.g. in timing) Provides 3rd party CTI (TAPI 2.x) The TSP drivers are made FOC available on the technical system CD and the SW database (BusinessNet) Requires licenses in the SV8100 and the CTI server 1 OAI lic in the SV8100, 1 CTI Application license and dongle A license per running application A license per end user Support on interface messages described in the manuals is given, application integration support can be provided (paid-for service) Runs also on SBS Windows W has not been tested at this stage, W2008 R2 64 bit support is planned for release in January 2012

9 NEC platform TSP interface architecture
For any NEC IP-PBX 3rd party call control Application ‘talks’ to Microsoft TAPI Licensed: In SV8100 In CTI server TSP On BusinessNet Software Database SV8100 Technical DVD

10 NEC platform TSP interface licensing
Per TSP server: a dongle, a SOPHO CTI Appl. license, an SV8100 OAI license Per Application: a CTI Desktop Appl. link license (first one is FOC and part of TSP server licenses) Per seat: a CTI Desktop Appl. Seat license

11 3) NEC CTI Software Development Kit
Using the SDK, one can develop an interface on an application, enabling 3rd party call control within the application E.g. Screen pop from a CRM application Provides more features than TAPI 2.x The SDK is a Win API (C++) Licensed: In SV8100 In the CTI server The same interface made available for all NEC platforms: One time application development for apps on all our platforms There can be a difference in feature set and timing, needs testing on every platform The SDK is made FOC available on the SW database Excellent developers manuals including source code samples Support on interface messages described in the manuals is given, application integration support can be provided (paid-for service)

12 Software Development Kit (SDK)
3rd party call control Win API (C++) Licensed: In SV8100 In CTI server SDK in BusinessNet Software Database Application protocol 3rd party Application and CTI server (API)

13 NEC CTI SDK licensing Per CTI server: a dongle, a SOPHO CTI Appl. license, an SV8100 OAI license Per Application: a CTI External Appl. link license Per seat: a CTI External Appl. Seat license

14 4) Desktop Suite 1st party TAPI
The first party TAPI driver and Desktop Suite cannot be run on the same machine, therefore included with the Desktop Suite is a 1st-Party TSP (NEC CTI Client Device) to support dialing from TAPI-compliant applications in parallel Built in, so no license required. The TSP is a sub-set of TAPI 1.4 command set: Make Call Dial / Drop Answer Hold / Unhold Blind Transfer / Setup Transfer / Complete Transfer Setup Conference / Add To Conference

15 Desktop Suite 1st party TAPI
1st party call control Subset of TAPI 1.4 No extra license For DTS Assistant and Attendant Note: for Attendant it also requires 3rd party TAPI in the SV8100 1st party TAPI (e.g. screen pop on Assistant)

16 Wrap up: SV8100 CTI Offering and licensing
SV8100 External Application Interfaces 1st party CTI (Tapi 1.4): per client 3rd party CTI (Tapi 2.1): one license NEC platform TSP Interfaces 3rd party CTI (Tapi 2.x): per TSP server, per Application, per Seat NEC CTI Software Development Kit Rich interface SDK: per CTI server, per Application, per Seat Desktop Suite 1st Party TAPI 1st party CTI (Tapi 1.4): Comes with a DTS client BCT 3rd party TAPI 3rd party CTI (Tapi 2.x): Comes with BCT client

17 Compatibility matrix Yes No NEC platf. TSP DTS 1st party BCT 3rd party
Installed: Compatible with: SV8100 1st party SV8100 3rd party NEC platformTSP NEC SDK DTS (attendant/shared services) DTS (other) BCT Clients Yes No NEC platf. TSP DTS 1st party BCT 3rd party Note: BCT clients: any BCT operator, employee or agent

18


Download ppt "SV8100 and CTI October 2011, Overview."

Similar presentations


Ads by Google