41
Avaya Aura Contact Center Application Development and Integration Capabilities Seamus Hayes

AACC Application Development and Integration Capabilities

Embed Size (px)

Citation preview

Page 1: AACC Application Development and Integration Capabilities

Avaya Aura Contact CenterApplication Development and Integration CapabilitiesSeamus Hayes

Page 2: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 2

Agenda

Introduction CCT Explained, (including demonstration) Thinking about SOA and Web Services Overview of Open Interfaces Demonstrations Where to find more info What APS can offer

Page 3: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved.

Introduction

3

Avaya Aura Contact Center provides a number of different API’s to support 3rd party integration: CTI – Communications Control Toolkit Real Time API’s Agent / Supervisor Administration ODBC connections for Historical Data Numerous web services to enhance and expand

multimedia contact handling 3rd party contact integration

Page 4: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 44© 2010 Avaya Inc. All rights reserved. 4© 2010 Avaya Inc. All rights reserved.

Communication Control Toolkit SDK

Page 5: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved.

Communication Control Toolkit SDK

Control of voice & multimedia contacts

control of terminals & agents

CCT is a Communications Control API implemented in .NET

Each API has working reference client with source code provided in SDK

Three levels of API abstraction: full, lite and graphical

5

Page 6: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 6

Communication Control Toolkit SDK

Session – represents the client application view of resources managed by CCT server based on client’s credentials

CCT SDK Allows applications to log in their configured agents Toolkit – represents the

client application connection to the remote CCT server

6

Page 7: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 7

Communication Control Toolkit SDK

Applications can query active calls and register for events

Address – represents a logical communication end-point– Examples: telephone number,

email address, SIP URL

Connection – represents an association between a Contact and an Address

Contact – models a communication session– Examples: telephone call, instant

message session, video call

Call

Cxn

Addr

Cxn

Addr

[email protected]

[email protected]

7

Page 8: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 8

Communication Control Toolkit SDK

3rd developers can customize their agent desktops

Terminal - represents a physical connection endpoint (including software applications)– Examples: telephone set,

SIP softphone, email client

TerminalConnection – represents the relationship between a Terminal and a Connection

Call

TrmCxnCxn

Addr

Trm

TrmCxnCxn

Addr

Trm

[email protected] [email protected]

[email protected] [email protected]

8

Page 9: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 99© 2010 Avaya Inc. All rights reserved. 9© 2010 Avaya Inc. All rights reserved.

CCT .NET SDK Demonstration

Page 10: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 1010© 2010 Avaya Inc. All rights reserved. 10© 2010 Avaya Inc. All rights reserved.

Thinking about SOA and Web Services

Page 11: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 1111© 2010 Avaya Inc. All rights reserved. 11© 2010 Avaya Inc. All rights reserved.

How do you get the best value from your Contact Center?

Page 12: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved.

Getting the most out of your Contact Center

Integration of core the Contact Center to key business systems:– Call Recording and Quality Monitoring Solutions

– Work Force Management Systems

– Historical Data Archives

– Wall boards

– CRM / ERP Systems

– Agent Desktop Clients

12

Page 13: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 1313© 2010 Avaya Inc. All rights reserved. 13© 2010 Avaya Inc. All rights reserved.

How were these integrations achieved up to now?

Page 14: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved.

Traditional Contact Center API’s

CTI Protocols

Real time API’s

Historical Data API’s

Propriety Event Feeds

14

NOTE: All of the existing legacy API’s will continue to be supported with Avaya Aura Contact Center

Page 15: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 1515© 2010 Avaya Inc. All rights reserved. 15© 2010 Avaya Inc. All rights reserved.

Introducing Web Services and SOA

Page 16: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 16

SOA Open Interfaces

SOA is an architectural style whose goal is to achieve loose coupling among interacting software agents

SOA services have self-describing interfaces in platform-independent XML documents. Web Services Description Language (WSDL) is the standard used to describe the services.

What is SOA?

Page 17: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved.

Opening the door to integration

17

Contact Center integration no longer limited to Operating System, Device or Media Channel

Page 18: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved.

Avaya Aura Contact Center- Available Web Services

AACC

Open Interfaces

Web Communication

User Provisioning

Host Data Exchange

Email Handling

“CTI” Desktop Integration

Campaign Management

18

Open Queue

OQ

Open Networking

Page 19: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 19

Open Interfaces CCT

This provides a cross-platform, technology independent, lightweight SDK for integrating desktop and Enterprise applications with the Contact Center.

Asynchronous events to be pushed to clients Supports using a Web Service Notification Standard (WS-Notification).

CCT Features available as web services

Page 20: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 20

Open Interfaces CCMM Agent

Avaya Aura Contact Center delivers web services to assist in the processing of Email Contacts received into monitored mailboxes.

Applications will be able to– Read Email Contacts

– Reply to and Forward email contacts

Ability to access the CCMM database to retrieve E-Mail

Page 21: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 21

Open Interfaces CCMM Outbound

Avaya Aura Contact Center provides an open interface for integrating 3rd Party applications with Outbound Campaigns.

This includes the ability to– to add contacts to an existing

campaign

– close contacts already created as part of a campaign

Can query and modify existing campaigns.

Page 22: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 22

Open Interfaces CCMA

Avaya Aura Contact Center supports User provisioning via a web-service interface – e.g. supporting Enterprise workflow which automatically pushes user data into all enterprise applications.

This includes the ability to

– add agents/supervisors

– query agents/supervisors

– Add/Query skillsets

–Manage agent to skillset assignments

User provisioning through SOAP or REST web services.

Page 23: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 23

Open Interfaces Open Queue

Avaya Aura Contact Center supports the queuing of third-party contact-types.

Ability to queue custom contact-types.

These Contact types can be as diversified as CRM Records Issue Tracking System Virtual World Postal Mail

Page 24: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 24

Open Interfaces Open Networking

Avaya Aura Contact Center exposes a Universal Networking feature allowing 3rd party applications to transfer calls and data into CC without using traditional CTI methods

Transfer call attached data without using CTI.

Avaya Aura Contact Center

3rd Party System (e.g., IVR)

Call and associated data transferred to

Contact Center using web service call

Call and associated data presented to

agent

Page 25: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 25

Web Communication Manager

Can be used for web-site or application integration

Contains a set of sample web pages written in JSP

Sample pages use the web services

WCM features:– Submit Text Chat– Request Immediate Telephone Callback– Request Scheduled Telephone Callback– Submit HTML form via email

Set of web services hosted by CCMM

Page 26: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 2626© 2010 Avaya Inc. All rights reserved. 26© 2010 Avaya Inc. All rights reserved.

Open Interfaces Demonstrations

Page 27: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 2727© 2010 Avaya Inc. All rights reserved. 27© 2010 Avaya Inc. All rights reserved.

Open IVR IntegrationUsing AVP as an example

Page 28: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved.

AACC 6.1 interop with AVP(SIP Interface)

AVP connects to AACC 6.1 via SIP trunks.

AVP can do sip refers to an AACC6.1 acquired landing pad CDN

Support Versions– Voice Portal: VP 5.0, VP5.1

– Dialog Designer: DD 5.0, DD5.1

AACC 6.1 support front end VP integration.

28

Page 29: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved.

Setting up the Voice Portal

SIP route configured at VPMS, – include MBT SES endpoint.

Landing pad application deployed and enabled on AVP.– Use Dialog Designer

AVP speech server resources configured and enabled– Configure CS1000 SIP Proxy and SIP Domain

– Configure Max no of Channels

29

Page 30: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved.

Setting up the AVP

30

Page 31: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved.

Setting up the AVP

31

Page 32: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved.

Dialog Designer Example

32

Page 33: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved.

Setting up the AACC

Enable Open Networking Feature– CCMS Server Configuration utility– License Tab– Select Open Queue Universal Networking

Open Queue must also be enabled– Support Call Attached Data

– Configure Open Queue on both CCT and CCMS

Create CDN Landing Pads– CCMA – Configuration

33

Page 34: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved.

Setting up the AACC

34

Page 35: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved.

Setting up the AACC

35

Page 36: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved.

Setting up the AACC

36

Page 37: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved.

Open Interface Universal Networking

The web service will enable a Third Party application to perform the transfer of a call between different nodes in a network with all data associated with the call being preserved

SDK Information– http:// <CCMS

hostName>:9080/SOAOI/services/OpenNetworking?wsdl

37

Page 38: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved.

AVP landing pad application configuration

The Landing pad DD application is deployed on the associated application server. Various application system configuration parameters can be configured in the file config.properties file.

DestinationCDN is the final DN resource to which the call ends up e.g. CDN, ACD queue

URL contains the IP address of the landing pad CCMS

Call attached data is configurable using the CAD and key value variables in landing pad application.

XFER determines the call transfer type e.g. blind, bridge or consult

38

Page 39: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 3939© 2010 Avaya Inc. All rights reserved. 39© 2010 Avaya Inc. All rights reserved.

Obtaining more information on the Open Interfaces available from AACC

Page 40: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved.

Where to find more information?

All Web Service SDK’s are available to Dev Connect members.

Sample applications are also available on the Dev Connect site.

40

Page 41: AACC Application Development and Integration Capabilities

© 2010 Avaya Inc. All rights reserved. 41