AvayaCPAASConference

Content Type: Widget
Categories: User Interface

Overview

This widget establishes a call between two users by invoking Avaya CPAAS REST API for conferencing. It accepts a list of numbers in the entity. ### How does this work? 1. Register an Avaya CPAAS account, note the account ID and token associated 2. Add this widget to your project 3. Configure appearance 4. Configure microflows and data entities to use as specified in the documentation 5. Pass Account ID and token along with from and to numbers to the configured microflow using entities defined in the module ### Further references 1. Avaya CPAAS: https://www.zang.io 2. Avaya Spaces for video conferencing: https://spaces.zang.io/ 3. Pricing details: https://www.zang.io/products/cloud#pricing

Documentation

Description

This widget establishes a call between two users by invoking Avaya CPAAS REST API for conferencing. It accepts a list of numbers in the entity.

Dependencies

Mendix Modeler 7.21.0

Prerequisites

  • Avaya Account for calling, conferencing, and messaging, register to Avaya Cloud account
  • For video conferencing, register an Avaya Spaces account

Configuration

  1. Common: Deals with common properties like tab index, style etc.
  2. Appearance: Deals with the look of the widget and includes setting CSS styles and text
  3. Data Source: Deals with the actual behavior of the widget.
    1. Data Object: Data entity defining all attributes to establish a conference. This is consumed in the target microflow.
    2. Source Microflow: Application layer microflow which accepts a context object as input and creates the data object specified.
    3. Target Microflow: Target microflow which accepts data object as an input and invokes Avaya CPaaS Call API for conference calling.

Dependencies

  1. AvayaCPAAS module containing helper microflows and entities.
  2. Valid InboundXML URL containing instructions to handle a call.

Usage

  1. Configure Inbound XML URL for conference calling in Constants
  2. Add widget to your project
  3. Add a source microflow which will create and return the data entity AvayaCPAAS.Conference_API_Request_List containing all required details
  4. Note that a list of numbers is required to be added to the conference separated by AvayaCPAAS.CONTACT_NO_DELIMITER
  5. Add AvayaCPAAS Conferencing widget to a page
  6. In appearance tab, set widget appearance
  7. In data source tab, set data object as AvayaCPAAS.Conference_API_Request_List
  8. Set created microflow as source
  9. Set target microflow as AvayaCPAAS.ACT_ConferenceCall_InitiateConferenceCallBulkList

Notes

  • InboundXML can be generated using the developer dashboard for testing purposes.
  • Conference name is generated dynamically.
  • Dynamic input can be accepted as HTTP parameters.

Sample snippet:

   

{{Method}}" startConferenceOnEnter="{{Start}}" endConferenceOnExit="{{End}}" beep="{{Beep}}">

{{Conference}}

References

 

Releases

Version: 2.0.0
Framework Version: 7.21.0
Release Notes: Features • Configurable Avaya Account credentials • Configurable Avaya InboundXML URL Enhancements • Better compliance with Mendix conventions Fixes • Cleaned unused data