Archive for October, 2012

Avaya Asterisk Logger

Posted: October 16, 2012 in Asterisk, TSAPI

Introduction

The Avaya Asterisk Logger (AstLogger) is a server application that triggers call recording on Asterisk side for Avaya CM. The software uses Avaya TSAPI library, it makes Single Step Conference (SSC) call to an Avaya agent extension and bridges the voice path between Avaya and Asterisk. After the voice path is established, Asterisk is responsible for call recording. Call details information is stored in MySQL database, a web based software called AstLoggerWeb is developed for searching of call records based on information such as calling number, called number, agent ID, etc. The software can also act as an auto-greeting server for call center agents, multiple greetings can be defined for an agent. 

Before installation of the software, you need to make sure a IP trunk is setup between Avaya and Asterisk. I have tested successfully using Asterisk 11 and OOH323 or SIP trunks between Asterisk and Avaya. Moreover, ask your Avaya administrator the dialing prefix to access Asterisk from Avaya, normally it is the combination of AAR FAC plus the route pattern.

Prerequisites

Please make sure you have the following Avaya features and systems enabled or installed:

  • AVAYA ASAI CTI STATION SFTW LIC or few idle phones as phantom devices
  • AVAYA ASAI PHANTOM CALLS SFTW LIC or few idle phones as phantom devices
  • MySQL Database Server
  • Asterisk Server

System Architecture

  • AstLogger triggers the bridging of voice path between Avaya and Asterisk via TSAPI and FastAGI.
  • Asterisk is responsible for call recording.
  • Asterisk writes all voice files to a distributed network file system such as MooseFS so voice files can be consolidated in one place such as data center and the files can be shared among different application. For example, AstLoggerWeb.
  • AstLogger writes call details information and business data (via AstLogger API) to MySQL database.
  • AstLoggerWeb retrieves call records based on user provided data such as calling number, called number, agent ID, etc.
  • The architecture supports multiple Asterisk servers for redundancy and load sharing.

Preparation and Password Encryption

  • A Microsoft Access MDB file is used to store the username and password of Avaya AES for this software. 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 password for the CTI user of Avaya AES, then use the encrypted password keyword for parameter al_tlink_01 and al_tlink_02. For example, the encrypted password for “p@ssword” is “R3NIw1yJMLlnPFzEQtuh2A==”.
  • encryptpasswd

64 bit Windows System 

  • For 64 bit Windows system, please follow the steps below
    • Download and install the Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package MFC Security Update http://www.microsoft.com/en-hk/download/details.aspx?id=26368
    • Configure ODBC System DSN using
      C:\Windows\SysWOW64\odbcad32.exe
    • Stop the Windows firewall because it enables by default which may block the communication between Asterisk and AstLogger.

OVA File for Testing

centos

We also create a OVA file which you can deploy it to VirtualBox or VMware Workstation or Player for testing.  After deploying the OVA file, please modify the following for your own environment

  • IP address of the VM
  • Edit /usr/lib/tslibrc, change 127.0.0.1 to the IP address of your Avaya AES
  • Telnet to AstLogger console port 14005, update the parameters called al_tlink_01, al_tlink_02 and other parameters
  • Once the changes are completed, reboot the VM

The username and password of the OVA VM is

  • OS : root/P@ssw0rd
  • MySQL: root/P@ssw0rd
  • AstLogger console: tcpgate/tcpgate01
  • uuiSVR console: tcpgate/tcpgate01
  • alarchived console: tcpgate/tcpgate01

Windows Installation Procedure 

  • Download and install the TSAPI client for Windows 32-bit from Avaya web site, it contains the TSAPI run-time library files. You need to register DevConnect before you can access the download page.
  • Download the Avaya Asterisk Logger zip file here or backup site
  • Follow the installation steps below to install the AstLogger software.
    • Extract all files into a directory c:\program files\astlogger
    • Open Windows Command Prompt, enter the following commands to register the program as Windows Service
      • cd c:\program files\astlogger
      • astlogger -i
    • Open ODBC Setting, create a System DSN called ASTLOGGERCFG for Microsoft Access Driver and point to astlogger.mdb which is located in the directory c:\program files\astlogger
    • Open the tParameter table of the Microsoft Access database, edit the value of parameters al_tlink_01 and al_tlink_02 to the TLINK names exported by your  Avaya AES. If you have only one Avaya AES, modify the parameter al_tlink_01 only, leave al_tlink_02 blank.
    • Edit the value of parameter al_phantomdigits to define the number of digits of your phantom device. If your Avaya use 5 digits dialing plan, the value is 5.
    • Edit the value of parameter al_phantomthreadsize to define the number of threads that are responsible to trigger call recording simultaneously, the default value is 10.
    • Edit the value of parameter al_recordformat to define the call recording format such as wav, mp3 or ogg, etc. The mp3 and ogg format is now supported if you compiled sox with mp3 and ogg supported. Edit the parameter al_cmdsoxmp3 when your SOX UNIX path is different than the default “/usr/local/bin/sox -r 8000 -c 1“. Also edit the parameter al_cmdrm because Asterisk will record voice file in .wav format first, then convert it to mp3 or ogg and finally delete the .wav file. The default value for al_cmdrm is “/bin/rm“. Or you can use the lame command directly for al_cmdsoxmp3 parameter, the parameter value is “/usr/bin/lame –silent” by default.
    • Edit the value of parameter al_cmdchownchmod enable other application such as apache reads the stored voice files. The command will be executed after a record file is created, the default value is “/bin/chmod o+r“.
    • Edit the value of parameter al_recordmode to define the technology such as Single Step Conference (ssc) or Service Observation (so) is used to trigger call recording. Only ssc is support currently.
    • Edit the value of parameter al_appendphantomvdnprefix to append the phantom device extension number to the record vdn prefix (dialing prefix to Asterisk) when callerid and callername variables can not be exchanged between Avaya and Asterisk, the phantom device extension number will be used as a bridge for information exchange between Avaya and Asterisk. The default value is “yes“.
    • Edit the value of parameter al_fagiport to define the port number for FastAGI interface, the default value is 4573. To increase the FAGI worker and buffer size, edit the parameters al_fagiworkersize and al_fagibuffersize.
    • Edit the value of parameter al_ueventbuffersize to define the internal TSAPI Unsolicited Event buffer size, the default value is 256.
    • Edit the value of parameter al_ueventworkersize to define the internal TSAPI Unsolicted Event worker size, the default value is 10.
    • Edit the value of parameter al_greetingenable to enable or disable auto-greeting module, the default value is “no“.
    • Edit the value of parameter al_greetingtimelimit to limit the time to trigger auto greeting. The default value is 2 seconds.
    • Edit the value of parameter al_greetingpath to define the path where agent greeting voice files are stored, the default value is “/var/spool/asterisk/voicemail/device/“.
    • Edit the value of parameter al_uuisvr to define uuiSVR IP and listening port. The default value is “127.0.0.1,5100“.
    • Follow the section Installation of AstLogger Database to install the call record database.
    • Follow this link to download MySQL ODBC driver and install the ODBC driver.
    • Open ODBC Setting, create a System DSN called ASTLOGGERCINFOCFG for MySQL ODBC Driver, MySQL is used to store call details information such as calling number, called number, record path, etc. User is “astlogger” and Password is “astavaya”.  If you want to use different DSN, username and password. Edit the three parameters follow:
      • al_callinfodsn, this is the name of the ODBC System DSN.
      • al_callinfousername, this is the username used to connect the AstLogger Database.
      • al_callinfopasswd, this is the password used to connect the AstLogger Database.
    • astloggercinfocfg
    • Start the Windows Service astlogger
    • Telnet to localhost and port number 14005, enter username tcpgate and password tcpgate01 to access the program console
    • Enter the following command in the program console to add monitored ACD number. E.g. 10001 is split number
      • add acd 10001
    • Enter the following command to add phantom device which is responsible to trigger call recording. E.g. 20001 is phantom device number
      • add phantom 20001
    • Enter the following command to add your target agent extension for call recording. E.g. 30001 is agent extension
      • add extension 30001
    • Enter the following command to add dialing prefix to access Asterisk for specific Avaya VDN or split numbers. E.g. 40001 is VDN number in Avaya and 459 is dialing prefix to access Asterisk dialplan X for program X.
      • add recordvdnprefix 40001 459 469
      • Hint: 469 is secondary prefix which will be used when an emergency split has login agent. To specify the emergency split, assign a split to the parameter al_emergencysplit
    • Enter the following command to add call recording location for specific Avaya VDN or split number. E.g. 40001 is VDN number and all record files stored in location “/tmp/X/“.
      • add recordpath 40001 /tmp/X/
    • Enter the following command to define Music On Hold mapping. E.g. 40001 is VDN number and use music on hold class orange.
      • add moh 40001 orange
    • 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
    • Enter the following command in the program console, you will get current recording information.
      • disp callinfo
  • Follow the installation steps below to install the uuiSVR software.
    • Open Windows Command Prompt, enter the following commands to register the program as Windows Service
      • cd c:\program files\astlogger
      • uuiSVR -i
    • Open ODBC Setting, create System DSN called UUISVRCFG for Microsoft Access Driver and point to uuiSVR.mdb which is located in the directory c:\program files\astlogger
    • Start the service uuiSVR

RedHat/CentOS 6.x Installation Procedure

  • centosredhat
  • The following is for RedHat/CentOS 6 32bit only, other Linux distributions are not supported
  • Avaya provides only 32bit version of TSAPI SDK, the executable filename provided by AstLogger is called “uuiSVR” and “AstLogger”.
  • Login as root and execute the following commands
  • Install the following packages for 64bit OS
  • yum install 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 32bit and 64bit 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 astlogger;
  • > create database uuisvr;
  • > create database alarchived;
  • > create user 'tcpgate'@'localhost' identified by 'tcpgate';
  • > create user 'astlogger'@'localhost' identified by 'astavaya';
  • > grant all on astlogger.* to 'tcpgate'@'localhost';
  • > grant all on astlogger.* to 'astlogger'@'localhost';
  • > grant all on uuisvr.* to 'tcpgate'@'localhost';
  • > grant all on alarchived.* to 'tcpgate'@'localhost';
  • > flush privileges;
  • > quit
  • mysql -h localhost -u astlogger -p astlogger < astlogger.sql
  • mysql -h localhost -u tcpgate -p uuisvr < uuisvr.sql
  • mysql -h localhost -u tcpgate -p alarchived < alarchived.sql
  • Copy the following to /etc/odbc.ini file
    • [ASTLOGGERCFG]
      Description = MySQL connection to AstLogger
      Driver = MySQL
      Server = localhost
      Port = 3306
      Database = astlogger
    • [ASTLOGGERCINFOCFG]
      Description = MySQL connection to AstLogger
      Driver = MySQL
      Server = localhost
      Port = 3306
      Database = astlogger
    • [ALARCHIVEDCFG]
      Description = MySQL connection to AstLogger Archive Daemon
      Driver = MySQL
      Server = localhost
      Port = 3306
      Database = alarchived
    • [UUISVRCFG]
      Description = MySQL connection to uuiSVR
      Driver = MySQL
      Server = localhost
      Port = 3306
      Database = uuisvr
  • Create user and copy files
  • mkdir /usr/local/astlogger
  • cp AstLogger /usr/local/astlogger
  • cp alarchived /usr/local/astlogger
  • cp uuiSVR /usr/local/astlogger
  • chmod +x /usr/local/astlogger/AstLogger
  • chmod +x /usr/local/astlogger/uuiSVR
  • chmod +x /usr/local/astlogger/alarchived
  • chown -R asterisk.asterisk /usr/local/astlogger
  • mkdir -p /var/log/astlogger
  • mkdir -p /var/log/uuisvr
  • mkdir -p /var/log/alarchived
  • chown -R asterisk.asterisk /var/log/astlogger
  • chown -R asterisk.asterisk /var/log/uuisvr
  • chown -R asterisk.asterisk /var/log/alarchived
  • Auto start the daemon after server reboot
  • echo "rm /tmp/astlogger.log" >> /etc/rc.local
  • echo "su asterisk -c '/usr/local/astlogger/AstLogger'" >> /etc/rc.local
  • echo "rm /tmp/uuisvr.log" >> /etc/rc.local
  • echo "su asterisk -c '/usr/local/astlogger/uuiSVR'" >> /etc/rc.local
  • echo "rm /tmp/alarchived.log" >> /etc/rc.local
  • echo "su asterisk -c '/usr/local/astlogger/alarchived'" >> /etc/rc.local

Advanced Features 

  • To enable call log centralization, assign IP address and listening port of the centralized log server for the parameter al_callloghost and al_calllogport.
  • To enable trunk side record, assign “yes” to parameter al_trunkrecording.
  • To enable scanning of configuraiotn database for addition or deletion of devices, assign “yes” to parameter al_scandbconfig and al_scandbconfiginterval by interval of seconds.

Asterisk Configuration for Default Recording Mode

  • Add a dialplan under the context of the trunk that you setup between Avaya and Asterisk, e.g.
  • agi
  • For FastAGI host, enter the IP address of the AstLogger machine. For example, the IP address 10.10.1.111.
  • Next to the IP address is the FastAGI network_script, the AstLogger called it application. Enter “recording” for default recording mode.
  • Next to the application name is the target extension number of this dialplan. Phantom device extension is appended in case callerid or callername variables cannot be exchange between Avaya and Asterisk.

Asterisk Configuration for Meeting Recording Mode

  • Add a dialplan under the context of the trunk that you setup between Avaya and Asterisk, e.g.
  • meeting
  • For FastAGI host, enter the IP address of the AstLogger machine. For example, the IP address 10.10.1.111.
  • Next to the IP address is the FastAGI network_script, the AstLogger called it application. Enter “meeting” for meeting recording mode.
  • Next to the application name is the target extension number of this dialplan. Phantom device extension is appended in case callerid or callername variables cannot be exchange between Avaya and Asterisk.

Installation of AstLogger Database

  • Download the Avaya Asterisk Logger zip file, unzip it and there is a SQL script file called astlogger.sql
  • Follow the steps below to create the required database and user
    • Create a database called “astlogger”, the SQL statement as follow:
    • CREATE DATABASE astlogger;
    • Create a user called “astlogger” and password “astavaya”
    • CREATE USER 'astlogger'@'localhost' IDENTIFIED BY 'astavaya';
    • CREATE USER 'astlogger'@'%'  IDENTIFIED BY 'astavaya';
    • GRANT ALL ON astlogger.* TO 'astlogger'@'localhost';
    • GRANT ALL ON astlogger.* TO 'astlogger'@'%';
    • FLUSH PRIVILEGES;
    • Use mysql to import table definitions
    • mysql -h localhost -u astlogger -p astlogger < astlogger.sql

AstLogger API

  • AstLogger API is for logging of application data related to a voice record, 10 data fields are supported. API is provided as OCX and DLL formats, the library files and sample applications are provided in the zip file.
  • To enable API support, enter the following command in the program console
    • add tcp 5002 * * custom alapi
    • Hint: API server will be listen on port 5002.
  • Call info record will be deleted immediately after agent call hangup, to enable agent write application data after call end, edit the parameter al_recorddeletedelay in the astlogger.mdb.  If you want agent can write record in 30 seconds after call hangup, set the value to 30.

AstLogger REST interface

AstLogger WebSocket interface

  • AstLogger WebSocket interface is for Web application integration
  • To add WebSocket interface port, enter the following command
    • add tcp 9090 * * custom alws 
  • WebSocket interface accepts JSON request, returns JSON response and delivers unsolicited JSON evens
  • The JSON strings for Connect request and response are
    • {id: “1”, request: “connect”, extension: “12345”, agentid: “56789”}
    • {msgtype: “response”, id: “1”, result: “success”}
  • The JSON strings for Disconnect request and response are
    • {id: “2”, request: “disconnect”}
    • {msgtype: “response”, id: “2”, result: “success”}
  • The JSON strings for SaveData request and response are
    • {id: “3”, request: “savedata”, extension: “12345”, recordkey: “12345.6789”, data0: “hello”, data9: “world”}
    • {msgtype: “response”, id: “3”, result: “success”}
  • The JSON string for RecordStart event is
    • {msgtype: “event”, eventtype: “recordstart”, extension: “12345”, recordkey: “12345.6789”, ucid: “00001094861421138402”, calling: “12345”, called: “12346”}
  • The JSON string for  RecordEnd event is
    • {msgtype: “event”, eventtype: “recordend”, extension: “12345”, recordkey: “12345.6789”}

AstLogger Web

  • AstLogger Web is a web based application for searching of call recording based on parameters such as date time, extension number, agent ID, calling number, etc.
  • AstLogger Web 1.3 is released. The screen dump is follow:

astlogger

  • Follow the steps below for the installation and configuration of AstLogger Web for CentOS. The steps for other Linux distribution are similar.
    • yum install httpd
    • chkconfig httpd on
    • service httpd start
      • Hint: if you do not install httpd before
    • cp astlogger.tar.gz /var/www/html
      • Hint: the astlogger.tar.gz is within the astlogger-x.x.rar file
    • cd /var/www/html
    • tar xzvf astlogger.tar.gz
    • cd /var/www/html/astlogger
    • ln -sf /mnt .
      • Hint: to symbolic link voice record directory to AstLogger Web directory
    • chown -R asterisk.asterisk /var/www/html/astlogger
      • Hint: change the ownership to asterisk
    • yum install php
    • yum install php-mysql
    • service httpd restart
    • vi config.php
      • Hint: change the $mysqlHost in config.php to the ip address of your sql server
    • http://ip-of-astlogger-web/astlogger/
      • Hint: default admin username is admin and password P@ssw0rd

AstLogger Desktop

  • Follow this link to find the details of the application

Monitor AstLogger Status

  • AstLogger supports monitoring of AstLogger status via the AstLogger Web
  • In the program console of AstLogger, enter the following command to enable this feature
    • add tcp 5002 * * custom alxml
  • From the AstLogger Web, select the Add Logger

addlogger

  • After the logger is added, select the Logger Status from menu to view the logger status

CentOS 6.x AstLogger Archive Daemon Installation

  • Prerequisite
    • The AstLogger uses MySQL configuration database instead of astlogger.mdb.
    • The AstLogger configuration database should be installed on the same MySQL that used by AstLogger Archive Daemon.
  • The AstLogger Archive Daemon is for archiving of voice files to backup directory and deletion of voice files which over retention period set by the program.
  • The executable file of AstLogger Archive Daemon 32bit version is “alarchived”, the 64bit version is “alarchived64”.
  • Install the following packages
  • 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 alarchived;
  • create user 'tcpgate'@'localhost' identified by 'tcpgate';
  • grant all on alarchived.* to 'tcpgate'@'localhost';
  • flush privileges;
  • quit
  • mysql -h localhost -u tcpgate -p alarchived < alarchived.sql
  • Copy the following to /etc/odbc.ini file
    • [ASTLOGGERCINFOCFG]
      Description = MySQL connection to AstLogger
      Driver = MySQL
      Server = localhost
      Port = 3306
      Database = astlogger
    • [ALARCHIVEDCFG]
      Description = MySQL connection to AstLogger Archive Daemon
      Driver = MySQL
      Server = localhost
      Port = 3306
      Database = alarchived
  • Create user and copy files
  • mkdir /usr/local/astlogger
  • cp alarchived /usr/local/astlogger
  • chmod +x /usr/local/astlogger/alarchived
  • chown -R asterisk.asterisk /usr/local/astlogger
  • mkdir -p /var/log/alarchived
  • chown -R asterisk.asterisk /var/log/alarchived
  • Auto start the daemon after server reboot for 32bit version
  • echo "rm -f /tmp/alarchived.log" >> /etc/rc.local
  • echo "su asterisk -c '/usr/local/astlogger/alarchived'" >> /etc/rc.local
  • Auto start the daemon after server reboot for 64bit version
  • echo "rm -f /tmp/alarchived64.log" >> /etc/rc.local
  • echo "su asterisk -c '/usr/local/astlogger/alarchived64'" >> /etc/rc.local
  • Telnet to the program console, the console port number is 14020, enter username tcpgate and password tcpgate01
  • If your archive directory mount point is /archive/, execute the following command to add archive directory
    • add archivepath /archive/
    • Hint: make sure the /archive/ directory is writable by user asterisk
    • Hint: archiving interval can be fine tuned by a parameter called al_archiveschedulerinterval which the default value is 30 seconds.
  • The program monitors the recordpath usage and deletes voice files in the record paths automatically when the usage  reached a defined level. The threshold parameter is called al_hddthreshold, by default it it set to 90 percent, meaning of deletion old files when the usage level reached 90%. The monitor interval can be fine tuned by a parameter called al_hddcleanerinterval which the default value is 10 seconds. Also, a parameter called al_purgewithoutarchive to control file deletion can be performed without archiving, the default value is “no”.
  • If you have retention period requuirement on recordpath or archivepath, execute the following command to add retention rule. Please pay attention to this command because voice files may be deleted before they are archived when the archiving function is failed longer than the retention period.
    • add retentiondir /mnt/ 90 90DaysRetentionPeriod
    • Hint: the program deletes files in directory /mnt/ when its creation time is over 90 days
    • Hint: retention thread execution interval can be fine tuned by a parameter called al_retentionschedulerinterval, the default value is 30 seconds.

Alarm Notification

  • Alarm notification via email is supported, you need to config the following parameters:
    • al_emailserverip, this is the IP address of your email server.
    • al_emailsmtpport, this is the smtp port of email server, default value is 25.
    • al_emailusername, the uesrname to login email server.
    • al_emailpasswd, the encrypted password. The database only store encrypted password due to security reason, to generate an encrypted password, enter the following command in the program console and paste the encrypted password for the parameter al_emailpasswd.
      • genpass yourpasswordfollow
    • al_emailsenderaddress, the email address used to send notification emails.
    • al_emailauth, if authentication is required, set the value to “yes“. The default value is “no” when your mail server trust your astlogger server.
    • al_emailauth, if SSL is required, set the value to “yes“. The default value is “no“.
  • Enter the following command to add email address for the receive of alarm notification, e.g.
    • add email service@upinget.com

Known Issues

  • The AstLogger triggers call recording via Avaya AES. When Avaya AES down, there will be no recording. Please provide at least two TLINK(s) so AstLogger can re-established the Avaya AES link as quickly as possible. The parameter to configure multiple TLINK(s) is called “al_tlink_xx“.
  • When using Avaya Single Step Conference to bridge Avaya and Asterisk for call recording, three parties conference will be established between agent, customer and Asterisk. When agent holds the call, the music on hold is triggered by AstLogger and played by Asterisk instead of Avaya. Please follow the Music On Hold section to configure your music source for different VDN or split number.
  • When agent initiates a consultation call during the call recording, the agent will have two calls on Avaya side (one is OLD call, the other is NEW call). There is no recording for the NEW call until the agent complete the conference.
  • If your Asterisk version > 1.6 and using OOH323 trunk, the Asterisk answers call is longer than default 2 seconds, please adjust the parameter al_waitloggeranswer and set a value longer than default 2 seconds
  • If your Asterisk SIP trunk with Avaya sometimes timeout because of network issue, please adjust the parameter al_waitloggerretry with value “yes” for retry connection between Avaya and Asterisk.
  • The Single Step Conference failed when agent extension connected to an announcement. This explains the root cause of the problem.
  • The calling number display of Avaya phone is replaced by a word “conference 2” after recording is started. This is produced by the phantom device which bridge the Avaya and Asterisk.

Music On Hold

  • The Music On Hold class is defined and mapped by Avaya VDN or SPLIT numbers. Use the following command to map the music on hold class. E.g. 40001 is VDN number and use music on hold class orange.
    • add moh 40001 orange
  • Please follow your Asterisk manual to add music on hold files. For example, follow this music on hold to add the music on hold files.
  • For a BPO company, this feature is useful because you can play different music on hold for different company.

Support and License