Trial Licenses

Posted: June 1, 2018 in News

We offer 30 days free trial, please send us your company name and MAC address of the server that installed our tool for the application of a trial licenses. Our email address is service@upinget.com. We also prepared two VMWare OVA images for the trial, please let us know if you are interested and we will send you the download URL of the OVA files. If you use docker container, you can get the images from docker hub.

The CTI OVA image is built using CentOS6 and it contains the following tools:

Tool & Console Port number
CallAnalytics 14003
RouteMgr 14005
AvayaMonitor 14008
CallGen 14009
ivrSVR 14012
uuiSVR 14014
AutoBridge 14022
AgentLightSVR 15012
QueueLightSVR 15013
AutoAnswer 16012

The CM OVA image is built using Ubuntu 18.04 and it contains the following tools: 

Tool & Console Port number
AvayaCDR 14004
clintSVR 14011
AvayaECHI 14016
bcmsSVR 14017
cloudCDR 15004

Twilio WhatsApp Using Avaya CallBack

Posted: December 10, 2019 in News, TSAPI

Introduction

Using Twilio WhatsApp API to create a chat application is easy and powerful. In some scenarios, we need to enable the contact center to callback a customer using company’s hotline number with specific skillset of agent who has login to Avaya. The UPINGET ctiSVR has REST API which can integrate Twilio with Avaya for that particular callback scenario.

When you programming your WhatsApp chat application using the Twilio Studio, you can add a HTTP Request Widget and enter the REQUEST URL and parameters as following to integrate the ctiSVR which implements the callback function on the Avaya platform.

    • http://server:port/makecallbackcall?
    • With parameters
      • extension=xxxxx
      • destination={{trigger.message.From}}
      • callto=true
      • payload=json
      • duration=5
      • ctiToken=xxxxxxxxxx
    • The extension can be vdn, hunt group extension, agent extension or agent id
    • The destination is the mobile number which triggers the WhatsApp messages
    • The callto=true parameter tells ctiSVR to parse the destination number by configuration rules
    • The payload=json parameter tells ctiSVR to return HTTP payload in JSON format
    • The duration=5 parameter tells ctiSVR must return result in 5 seconds because it is function requirement of the Twilio HTTP Request
    • The ctiToken=xxxxxxxxxx enhance the security of ctiSVR because ctiSVR only makes call by valid token
    • Output variables
      • widgets.MY_WIDGET_NAME.parsed.result
        • The possible result is success or error
      • widgets.MY_WIDGET_NAME.parsed.error
        • The error message of the HTTP Request when the result is error
      • widgets.MY_WIDGET_NAME.parsed.callid
        • The call id of the call
      • widgets.MY_WIDGET_NAME.parsed.ucid
        • The UCID of the call
      • widgets.MY_WIDGET_NAME.parsed.phantom
        • The phantom device which makes the call
      • widgets.MY_WIDGET_NAME.parsed.answering
        • The Avaya answering device which the call is connected
      • widgets.MY_WIDGET_NAME.parsed.destination
        • The destination number after parsed by the ctiSVR

Introduction

The AutoBridge enables Home Agent solution for Avaya contact center. The tool monitors a pool of Avaya extensions in the contact center, it bridges Avaya and Asterisk extensions together whenever any of the Avaya extension has incoming or outgoing call. This enables home agent who is stayed at home can operate his/her CRM application via a VPN connection and speaks to his/her customer using an Internet SIP phone.

This solution required SIP trunks setup between the Avaya and Asterisk. Home agent using SIP phone (a hard SIP phone is preferred for better voice quality and easy of control) to connect to the Asterisk over the Internet. When the home agent login to ACD using his/her CRM application, the AutoBridge knows which Asterisk extension to be bridged with the Avaya extension that the agent is engaging in a call. The AutoBridge protects your existing Avaya investment, no modification of your CTI or CRM is required to implement the Home Agent solution.

Windows Preparation and Password Encryption

  • An access MDB file which stored the CT username and password of AE server. For security reason, a tool called encryptpasswd.exe is provided to generate encrypted password for the installation and configuration of the software
  • Execute the program, generate the encrypted passwords for the CT user of AE server, then paste the encrypted password to parameter ab_tlink. For example, the encrypted password for “p@ssword” is “R3NIw1yJMLlnPFzEQtuh2A==”

Windows 64 bit System 

  • For 64 bit Windows system, please follow the steps below
    • Configure ODBC System DSN using 32 bit version of ODBC Admin tool.
      C:WindowsSysWOW64odbcad32.exe

Windows Installation  

  • Download the TSAPI client for Windows 32-bit from Avaya web site, it contains the library files. You need to register DevConnect before you can access the download page.
  • Download the AutoBridge zip file here.
  • Follow the steps below to install the software.
    • Extract all the files into directory c:\program files\autobridge
    • Open Windows Command Prompt, enter the following commands to register the program as Windows Service
      • cd c:\program files\autobridge
      • AutoBridge -i
    • Open ODBC Setting, create System DSN called AUTOBRIDGECFG for Microsoft Access Driver and point to autobridge.mdb which is located in the directory c:\program files\autobridge
    • Open the Access file, edit the value of parameters ab_tlink_01 and ab_tlink_02 to the TLINK of your AES servers in the tParameter table
    • Start the Windows Service AutoBridge
    • Telnet to localhost and port number 14022, enter username tcpgate and password tcpgate01 to access the program console
    • Enter the following command in the program console to add extensions
      • add extension 61101
      • Hint: 61101 is agent extension
    • Enter the following command in the program console to add ACD monitoring
      • add acd 51101
      • Hint: 51101 is ACD
    • Enter the following command in the program console to add phantom devices
      • add phantom 41101
      • Hint: 41101 is phantom device
    • Enter the following command in the program console to add mapping between Avaya and Asterisk extension
      • add autobridge 10001 4511001
      • Hint: 10001 is Avaya extension, 4511001 is dialing string from Avaya to the Asterisk extension
    • Enter the following command in the program console, you will receive debug information
      • trace on asc
    • Enter the following command in the program console, you will get the help message
      • help

RedHat/CentOS 6.x Installation Guide

  • centosredhat
  • The following is for RedHat/CentOS 6 32 bit and 64 bit only, other Linux distributions are not supported.
  • Avaya provides only 32 bit version of TSAPI SDK, the executable filename of AutoBridge is called “AutoBridge”.
  • Login as root and execute the following commands
  • Install the following packages for 64 bit OS
  • yum install libstdc++.i686 expat.i686 openssl.i686 unixODBC.i686 mysql-libs.i686
  • wget http://mirror.centos.org/centos/6/os/i386/Packages/mysql-connector-odbc-5.1.5r1144-7.el6.i686.rpm
  • rpm -ivh mysql-connector-odbc-5.1.5r1144-7.el6.i686.rpm
  • Download Avaya Aura AE Services 7.0 TSAPI Client for RHEL 6 from DevConnect
  • chmod +x tsapi-client-linux-7.0.0-131.bin
  • Execute the installation file tsapi-client-linux-7.0.0-131.bin
    • ./tsapi-client-linux-7.0.0-131.bin
  • Edit /usr/lib/tslibrc, change 127.0.0.1 to the IP address of your Avaya AES
  • Install the following packages for 32 bit and 64 bit OS
  • yum install mysql-server mysql
  • yum install mysql-connector-odbc unixODBC
  • Config and start MySQL
  • chkconfig mysqld on
  • service mysqld start
  • Create database and user
  • mysql -u root -p
  • > create database autobridge;
  • > create user 'tcpgate'@'localhost' identified by 'tcpgate';
  • > grant all on autobridge.* to 'tcpgate'@'localhost';
  • > flush privileges;
  • > quit
  • mysql -h localhost -u tcpgate -p autobridge < autobridge.sql
  • Copy the following to /etc/odbc.ini file
    • [AUTOBRIDGECFG]
      Description = MySQL connection to AutoBridge
      Driver = MySQL
      Server = localhost
      Port = 3306
      Database = autobridge
  • Create user and copy files
  • useradd autobridge
  • mkdir /usr/local/autobridge
  • cp AutoBridge /usr/local/autobridge
  • chmod +x /usr/local/autobridge/AutoBridge
  • chown -R autobridge.autobridge /usr/local/autobridge
  • mkdir -p /var/log/autobridge
  • chown -R autobridge.autobridge /var/log/autobridge
  • Auto start the daemon after server reboot
  • echo "rm /tmp/autobridge.log" >> /etc/rc.local
  • echo "su autobridge -c '/usr/local/autobridge/AutoBridge'" >> /etc/rc.local

AvayaMonitor PRTG Integration

Posted: November 14, 2019 in News, System Monitoring

We just integrated the AvayaMonitor with PRTG, please find the screen dumps as following:

Docker Container

Posted: October 30, 2019 in News

We have created some containers for our popular tools and uploaded them to docker hub. These containers are based on CentOS 6, each installed MySQL and the tool binary itself. If you are interested, you can download them from docker hub and get a trial license from us. Enjoy!

CallAnalytics 2.0.9 Released

Posted: August 30, 2019 in News, TSAPI

CallAnalytics 2.0.9 just released, this version has the following updates.

1. Update the “origucid” field of callinfo object using the CSTA transfer event.
2. Update the “vdn” field for VDN callinfo object.
3. Add setuserdata REST API, the userdata, ucid or callid or uui as parameter.
4. The callinfo REST API supports hexucid as parameter. The hexucid can be HEX UUI sent to Asterisk in the SIP header.

DMCCLogger 1.0.5 Released

Posted: July 31, 2019 in DMCC, News

DMCCLogger 1.0.5 just released, this version has the following updates.

1. Fixed segmentation fault caused by deletion of phantom object which is a member of the call info record.
2. Collects trunk group and trunk member data from the conference event when the data is not in the delivered and established events.
3. Two parameters to load the certificate and key files, the two parameters are “dmcc_sslcertfilename” and “dmcc_sslkeyfilename”.
4. Add info field for each extension record.
5. Clear phantom connection when the extension dropped from recording by normal hangup or transfer.
6. Relogin the phantom when it is out of service during engaging in a recording call.

CallAnalytics 2.0.8 Released

Posted: July 20, 2019 in Analytics, News

CallAnalytics 2.0.8 just released, this version has the following updates.

1. Updates the vdnreport REST interface to output list of vdn reports.
2. Provides sample app CallAnalyticsLight for display of sample reports.
3. Supports secure REST interface. Two parameters to load the certificate and key files, the two parameters are “ca_sslcertfilename” and “ca_sslkeyfilename”.
4. Fixed agent map without agents for Linux version.