Installing and configuring Avaya Enhanced Caller ID (ECID)
|
|
- Chad Jordan
- 6 years ago
- Views:
Transcription
1 Installing and configuring Avaya Enhanced Caller ID (ECID) Release 1.0 March 2012
2 2012 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document might be incorporated in future releases. Documentation disclaimer Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya s agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all the time and we have no control over the availability of the linked pages. Warranty Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product, while under warranty, is available through the Avaya Support Web site: License USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER S ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEB SITE ("GENERAL LICENSE TERMS"). IFYOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN (10) DAYS OF DELIVERY FOR A REFUND OR CREDIT. Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. "Designated Processor" means a single stand-alone computing device. "Server" means a Designated Processor that hosts a software application to be accessed by multiple users. "Software" means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone Products or pre-installed on Hardware. "Hardware" means the standard hardware Products, originally sold by Avaya and ultimately utilized by End User. License type(s) Designated System(s) License (DS). End User may install and use each copy of the Software on only one Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. Avaya may require the Designated Processor(s) to be identified by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A "Unit" means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Software. Units may be linked to a specific, identified Server. Database License (DL). Customer may install and use each copy of the Software on one Server or on multiple Servers provided that each of the Servers on which the Software is installed communicate with no more than a single instance of the same database. CPU License (CP). End User may install and use each copy of the Software on a number of Servers up to the number indicated by Avaya provided that the performance capacity of the Server(s) does not exceed the performance capacity specified for the Software. End User may not re-install or operate the Software on Server(s) with a larger performance capacity without Avaya s prior consent and payment of an upgrade fee. Named User License (NU). Customer may: (i) install and use the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a Server so long as only authorized Named Users access and use the Software. "Named User," means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya s sole discretion, a "Named User" may be, without limitation, designated by name, corporate function (e.g., webmaster or helpdesk), an or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Product. Shrinkwrap License (SR). With respect to Software that contains elements provided by third party suppliers, End User may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as "shrinkwrap" or "clickwrap" license accompanying or applicable to the Software ("Shrinkwrap License"). The text of the Shrinkwrap License will be available from Avaya upon End User's request (see.third-party Components" for more information). Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law. Third-party components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the Product ("Third Party Terms"). Information identifying Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: Preventing toll fraud "Toll fraud" is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company s behalf). Be aware that there can be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya fraud intervention If you suspect that you are being victimized by toll fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at for the United States and Canada. For additional support telephone numbers, see the Avaya Support Web site: Trademarks Avaya is a registered trademark of Avaya Inc. MultiVantage is a trademark of Avaya Inc. All non-avaya trademarks are the property of their respective owners. Downloading documents For the most current versions of documentation, see the Avaya Support Web site: Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is in the United States. For additional support telephone numbers, see the Avaya Support Web site: March
3 Table of contents Table of contents About this document... 6 Intended audience... 6 Related documents... 6 ECID installation roadmap... 7 Environment configuration... 8 Hardware requirements... 8 Software requirements... 8 ECID installation Verifying the Java version Postgres configuration Installing the ECID postgres database Starting PostgresSQL automatically at system start up Creating system users JBoss/Mobicents execution environment Installing and configuring the ECID application Launching JBoss service Next steps Post-installation steps Hardening the system Linux OS Postgres DB JBoss Mobicents Verification March
4 Table of contents Configuring ECID as a Sequenced App on Session Manager Reconfiguring Communication Manager trunking to route calls through Session Manager Adding ECID as a SIP entity Configuring entity links Configuring the SIP entity as a Session Manager application Creating an application sequence Adding implicit users Removing ECID configuration on Session Manager Configure an adaptation for the ECID server on Session Manager Uninstalling ECID Information repository integration with Talend Open Studio Getting started with Talend Open Studio Installing Talend Open Studio Importing sample connectors Customizing the connectors Deploying the Talend integration jobs Scheduling Talend jobs Service configuration Modifying the config properties List of configuration properties Upgrading the ECID components Updating the ECID environment Updating postgres Modifying Talend job credentials Updating JBoss/Mobicents Troubleshooting the ECID configuration Appendix 1: Using Talend through Avaya Secure Access Link Appendix 2: Application Support Handoff collateral March
5 Table of figures Table of figures Figure 1 RHEL 5.5 customize software screen, example Figure 2 RHEL 5.5 customize software screen, example Figure 3 Trunks terminating on Communication Manager (left image), and trunks terminating on Session Manager (right image) Figure 4 Trunk routing, example Figure 5 Trunk routing, example Figure 6 Trunk routing, example Figure 7 Trunk routing, example Figure 8 Trunk routing, example Figure 9 Trunk routing, example Figure 10 Trunk routing, example Figure 11 Trunk routing, example Figure 12 Trunk routing, example Figure 13 SIP entity details page, example Figure 14 - SIP entity details page, example Figure 15 Application Editor page Figure 16 Application Sequence Editor page Figure 17 Implicit user page Figure 18 Adaptation details page Figure 19 Replica groups page Figure 20 Talend Open Studio page, example Figure 21 Talend Open Studio page, example Figure 22 Talend Open Studio, example Figure 23 Talen Open Studio, example Figure 24 Missing log4j components Figure 25 Talen Open Studio, example Figure 26 Scheduling Talend job, example Figure 27 ecid.properties file example Figure 28 Service_Data_run.sh command example Figure 29 netstat output example Figure 30 SSH screen Figure 31 PuTTY screen, example Figure 32 - PuTTY screen, example Figure 33 - PuTTY screen, example Figure 34 - PuTTY screen, example Figure 35 - PuTTY screen, example Figure 36 Talend Open Studio screen, example Figure 37 - Talend Open Studio screen, example March
6 About this document About this document The Installing and configuring Avaya Enhanced Caller ID (ECID) guide provides information on environment configuration for installing ECID in the Avaya Aura environment and also provides detailed installation procedures. Intended audience The document is addressed to Avaya Professional Services professionals or Avaya channel partners engaged in installing and configuring the ECID application at the customer sites. Related documents The Installing and configuring Avaya ECID guide is part of the ECID documentation set. The other documents in the documentation set are as follows: Administering Avaya Enhanced Caller ID (ECID) Provides information on administering the Enhanced Caller ID (ECID) application. Avaya Enhanced Caller ID Release Notes Provides information on the latest version of ECID. March
7 ECID installation roadmap ECID installation roadmap An overview of the tasks involved in installing and configuring ECID is as follows: Checking the hardware and software requirements. Configuring the required applications, for example, Avaya Aura Session Manager and Avaya Aura Communication Manager. Installing ECID on a dedicated server and then performing integration with information systems of the customer using Talend Open Studio. Configuring ECID as a sequenced application invoked by Session Manager. Performing acceptance testing to confirm proper operation of ECID. March
8 Environment configuration Environment configuration Hardware requirements ECID works in an Avaya Aura environment. The minimum hardware requirements are as follows. Hardware requirement Description Processor RAM Hard disk drive Network Screen resolution Intel Xeon E5520 Quad-Core processor, 8MB cache, 2.26 GHz 4GB ECC DDR3 10K RPM, 2 x 146GB SAS (Serial-Attach SCSI) 100 BaseT Ethernet NIC with mode as full duplex or higher with 16-bit color Avaya has performed limited verification of the ECID application and environment on VMWare Hypervisor Update 1, using a virtual machine with configuration consistent with the parameters in the hardware requirements table in this section. Avaya has not verified operation in the other virtualized environments. Software requirements Ensure that you have the following installed on your server before starting the ECID installation: Red Hat Enterprise Linux (RHEL) 5.5, 32 bit Oracle JDK version 1.6. Note: Download the JDK file, that is, the jdk-6u30-linux-i586-rpm.bin file from the following location before starting the installation: Important: While installing Red Hat Enterprise Linux 5.5, on the customize software screen, select the March
9 Environment configuration Customize now option, and then click Next. Figure 1 RHEL 5.5 customize software screen, example 1 March
10 Environment configuration On the next screen, select the Base System option from the left navigation menu and clear the selection for the Java option in the right menu. Then, click Next and continue with the installation. Figure 2 RHEL 5.5 customize software screen, example 2 Prerequisites: Ensure that you have the following RPMs ready before starting with the ECID installation. Avaya provides these RPMs, and these RPMs constitute the ECID application and the required environment: Seqapps 1.0 Postgres Avaya JBoss MSS March
11 ECID installation ECID installation ECID installation involves multiple stages to install the foundational components on which ECID relies, and then installing the ECID application. The following sections describe the various components required to make the ECID application operational. Important: To perform the tasks mentioned in this section, you must use a Linux shell and log on to the server as a root user. Note: Before you start the installation process, copy all the installation packages to the /tmp folder on the ECID server, and then perform the installation activities from this folder. Verifying the Java version To check the Java version in your system, run the following command: # java -version The system must display the following output for the right Java version: java version "1.6.0_30" Java(TM) SE Runtime Environment (build 1.6.0_30-b12) Java HotSpot(TM) Server VM (build 20.5-b03, mixed mode) If the system displays a different output, then run the following commands: # cd /usr/bin # ln -fs /usr/java/jdk1.6.0_30/bin/java /usr/bin/java Run the following command again to verify the Java version: # java -version Verify that the system displays the right Java version as mentioned at the start of the Verifying the Java version section. March
12 ECID installation Postgres configuration Installing the ECID postgres database To install the ECID postgres database, use Red Hat Enterprise Linux s rpm(8) utility: # rpm -i postgres i386.openscg.rpm # service postgres-9.0-openscg start Answer the following question as yes: Confirm Port 5432 [yes]: yes Enter your superuser password when the system prompts you for the password: Enter Superuser-password Note: Make a note of the superuser password as you will need to provide this password at a later stage during the installation. Answer the following question as yes so that the postgres service restarts automatically when the server reboots Do you want PostgreSQL server to be started on boot (y/n) [y]: y # service postgres-9.0-openscg start Starting PostgresSQL automatically at system start up 1. Verify that the S85postgres-9.0-openscg file is in the /etc/rc5.d directory. 2. (Optional) I. If the file does not exist in the respective directory, run the following commands: # chkconfig postgres-9.0-openscg on # cd /etc/rc5.d # ls -l II. Verify that the S85postgres-9.0-openscg file is present in the /etc/rc5.d directory. March
13 ECID installation Creating system users You must create a jboss user and group to own and run the mobicents/jboss processes as a user other than root. Also, create a craft user to allow non-network administrators or personnel who should not have root access to the server, to login in and perform operational and maintenance activities related only to Sequenced Applications. The craft userid should be added to the jboss and postgres groups for this purpose. To create and configure these user accounts, run the following commands: # useradd jboss # useradd -p `perl -e 'print crypt("craft01", "salt")'` craft # usermod -a -G postgres,jboss craft JBoss/Mobicents execution environment Install JBoss/Mobicents: # rpm -Uvh mss-<version>_<release>.noarch.rpm # cd /opt/avaya/ # chown -R jboss:jboss mss-<version>_<release> # chmod -R 775 mss-<version>_<release> Note: The mss-<version>_<release>, for example mss final_jboss_jdk6_5.1.0.ga, is the mobicents/jboss directory. Installing and configuring the ECID application 1. Install the ECID application: # rpm -i seqapps-1.0-<buildnumber>.noarch.rpm --replacefiles 2>&1 tee -a /var/log/seqappsinstalllog When the system prompts you for the password, enter the password from the postgresql installation. March
14 ECID installation Note: The Seqapps installer prompts for the password for the user postgres. If you provide an incorrect password, the installer proceeds with the installation, but the configuration remains incomplete. To resolve an incomplete installation, remove the Seqapps rpm and reinstall the application. 2. Configure ECID: # cd /opt/avaya/mss/server/default/conf/seqapps_services # unzip Service_Data_0.1.zip # cd Service_Data_0.1/Service_Data # chmod +x Service_Data_run.sh #./Service_Data_run.sh # cd /opt/avaya/mss/server/default # chown -R jboss:jboss log # chmod -R 770 log Launching JBoss service Start ECID by launching the JBoss service: # service jboss start Next steps The ECID installation is now complete. Perform the following steps to complete the configuration: Hardening the system for hardening the server Configuring Avaya Aura Session Manager Configuring the Talend-Job March
15 Post-installation steps Post-installation steps Important: To perform the tasks mentioned in this section, you must use a Linux shell and log on to the server as a root user. Hardening the system Linux OS Harden OS Important: You must perform the tasks in the same order as mentioned in this section; else you might lose your access to the server. Ensure that you create a craft user login and, using the craft user login, you can create an SSH connection to the server remotely. For more information on creating a craft user login, see the Create System Users section in this document. 1. Set up an HTTP proxy: # export http_proxy= host>:<proxy port> 2. Run harden.pl: # cd /opt/avaya/scripts/ # unzip Log4perl.zip # perl harden.pl 3. Check for errors in the log files located under: /tmp/seqapps/log 4. Disable the VNC server: # /sbin/chkconfig --list grep vnc vncserver 0:off 1:off 2:on 3:on 4:on 5:on 6:off # /sbin/chkconfig vncserver off # /sbin/chkconfig --list grep vnc vncserver 0:off 1:off 2:off 3:off 4:off 5:off 6:off 5. Reboot the server. March
16 Post-installation steps Postgres DB Disabling or limiting network access 1. To completely disable network access to the postgres database, edit the configuration file located at /opt/postgres/9.0/data/postgresql.conf, and change the value of listen_address to localhost. listen_addresses = 'localhost' listen on; # what IP address(es) to 2. (Optional) Alternatively, by specifying IP addresses separated by a comma, you can ensure access to the network is limited to the listed IP addresses. Note: For more convenience, list the IP addresses on the GUI tool, such as pgadmin, when you are installing the system, upgrading the system, or troubleshooting errors in the system. After listing the IP addresses on the GUI tool, change the IP address of the server to localhost. listen_addresses = 'localhost, ' address(es) to listen on; # what IP 3. Restart Postgres: # service postgres-9.0-openscg restart Restoring network access If you disabled the network access completely, for commissioning the ECID server or to facilitate field support, you might choose to re-enable the network access. 1. To activate network connections to the postgres database, edit the configuration file located at /opt/postgres/9.0/data/postgresql.conf, and change the value of listen_address value to asterisk (*). listen_addresses = '*' # what IP address(es) to listen on; 2. Restart postgres: # service postgres-9.0-openscg restart Note: You should disable the network access after commissioning or after completing the field support work. For more information, see the Disabling Network Access section in this document. March
17 Post-installation steps JBoss Mobicents Network Interface Binding 1. Mobicents should only bind to localhost ( ). Modify /opt/avaya/mss/bin/jboss script and change the JBOSS_HOST to : ######JBOSS_HOST=${JBOSS_HOST:-" "} JBOSS_HOST=${JBOSS_HOST:-" "} 2. Verify the result by checking for "-b " in the JBoss startup message: # service jboss start JBOSS_CMD_START = cd /opt/avaya/mss/bin; /opt/avaya/mss/bin/run.sh -c default -b Disabling the JMXConsole and Web console Disable the JMXConsole and the Web console, which are not being used by ECID: # mkdir ~/jboss_consoles_backup # service jboss stop # ps -ef grep jboss ### make sure jboss stop running # cd /opt/avaya/mss/server/default/deploy # mv management jmx-console.war ~/jboss_consoles_backup # service jboss start Verification Port Scan From a different machine on the same network as the ECID server, run nmap to scan for open TCP ports and UDP ports. You can install nmap by running the following command: # yum install nmap Note: You can download a Windows version of nmap from the following location: You can run nmap from an MS Dos prompt on a Windows machine by using an identical syntax to that of the Linux version as shown in the following sections. 1. Run a scan for all the open TCP ports on the server: March
18 Post-installation steps # nmap -v -P0 -st -p- -on TCP.txt <IP address of the server> The result should look similar to the following example:... Interesting ports on <IP address of the server>: Not shown: closed ports PORT STATE SERVICE 22/tcp open ssh 111/tcp open rpcbind 5080/tcp open unknown 5802/tcp open vnc-http /tcp open vnc /tcp open unknown Ensure only the following ports are open: o o o o o o 22 (ssh), 111 (rpcbind), 5802 (vnc-http-2) 5902 (vnc-2) 5080 (unknown/sip) another random port labeled as unknown (56281 in the example shown above) 3. Navigate to the ECID server. Ensure port 5080 and the random port are dedicated to the Mobicents process: # ps -ef grep java root :28 pts/0 00:02:10 java - Dprogram.name=run.sh -server... [root@ott ~]# netstat -ap grep 5080 tcp 0 0 *:5080 *:* LISTEN 29211/java March
19 Post-installation steps tcp :5080 pv-asm1- sip.sc.sc:37962 ESTABLISHED 29211/java udp 0 0 *:5080 *:* 29211/java [root@ott ~]# netstat -ap grep tcp 0 0 *:56281 *:* LISTEN 29211/java 4. Run a scan of all the open UDP ports on the server: Note: Run this command on the ECID server. # ss -u -a The result should look similar to the following example, that is, the UDP ports that process network traffic must be restricted to 5080, sunrpc, and ipp: State Recv-Q Send-Q Local Address:Port Peer Address:Port UNCONN :healthpolling *:* UNCONN :healthtrap *:* ESTAB : :55639 UNCONN 0 0 *:5080 *:* UNCONN 0 0 *:sunrpc *:* UNCONN 0 0 *:ipp *:* Note: If you get an ss does not exist error message, then install ss by running the following command: yum install ss 5. (Optional) To determine which service or process a particular open port processes, use the following command: March
20 Post-installation steps # netstat -ap grep xxxx 6. (Optional) Use the following command to disable unnecessary services: # /sbin/chkconfig <service name> off 7. (Optional) Reboot the server. 8. (Optional) After rebooting the server, verify that the ports are no longer open. SSH VNC Note: Perform the steps 7 and 8 only if you have performed step 6. Confirm that you can use your craft user login to create an SSH connection to the server remotely. Ensure that you cannot use a root user login to connect to the server using SSH. Ensure you can no longer connect through VNC. Postgres database 1. If you have disabled network access to the postgres database, when you try to connect pgadmin to the network, the system displays the following error: Server doesn't listen To connect pgadmin to the network, enable network access to the postgres database. JBoss/Mobicents 1. Verify that JMXConsole is not accessible either locally ( or remotely ( ip>:8080/jmx-console). 2. Verify that Web Console is not accessible either locally ( or remotely ( ip>:8080/web-console). ECID Sequenced Application Perform regression tests for different call scenarios to ensure ECID functions normally. March
21 Post-installation steps Configuring ECID as a Sequenced App on Session Manager You can use implicit sequencing if you are using Avaya Aura Session Manager to route external calls. To be able to do so, you might require to make changes in the existing call routing. For example, if a CM-ES has a private trunk, that is a direct termination trunk, and the system receives an external call, the CM-ES routes the call over the private trunk. The Session Manager is not be involved, and therefore the system cannot generate the implicit sequenced applications. You must reconfigure trunk routing for ensuring full functionality of the ECID application. Important: After making configuration changes to the Session Manager Web interface, you must perform a replication for your changes to take effect. For more information, see the Performing a replication section in this document. Reconfiguring Communication Manager trunking to route calls through Session Manager ECID can support various configurations for PSTN trunking. These configurations can be divided into two groups: trunks terminating on gateways attached to a Session Manager, and trunks terminating on gateways attached to a Communication Manager. Figure 3 Trunks terminating on Communication Manager (left image), and trunks terminating on Session Manager (right image) For configurations that have trunking delivered to Session Manager, application sequencing is straightforward, meaning you do not require to make trunking changes. For configurations that have trunking delivered to a Communication Manager, you must invoke Automatic Alternate Routing (AAR) to force incoming calls to be routed through the Session Manager. The following section shows an example of setting up routing. March
22 Post-installation steps Sample routing scenarios are as follows: ISDN trunk to the PSTN Local Subscriber Number: 94 DID range: The Local Service Provider sends the digits 94xxxx in the destination address for each call. Incoming Trunk from PSTN inserts number zero and an asterisk (0*) Zero (0) is FAC for ARS table, meaning that the system routs the call to the ARS-table and truncates the leading zero (0): Figure 4 Trunk routing, example 1 Within ARS DIGIT Conversion we are routing the call to AAR table and truncating the leading 3 digits *94, meaning that the remaining digits are 4 digits in length which is the extension number of the users: March
23 Post-installation steps Figure 5 Trunk routing, example 2 Within the AAR analysis the call is routed to the route-pattern 3: Figure 6 Trunk routing, example 3 March
24 Post-installation steps Within the route pattern, the system routes the call to trunk 3 which is the SIP-Trunk to Session Manager: Trunk 3 to Session Manager: Figure 7 Trunk routing, example 4 Figure 8 Trunk routing, example 5 March
25 Post-installation steps Figure 9 Trunk routing, example 6 Figure 10 Trunk routing, example 7 March
26 Post-installation steps Figure 11 Trunk routing, example 8 Figure 12 Trunk routing, example 9 March
27 Post-installation steps Adding ECID as a SIP entity 1. Log on to the System Manager (SMGR) Web interface by using the following URL: 2. On the home page, go to Elements> Routing. 3. Go to Routing> SIP Entities, and then click New. 4. On the SIP Entity Details page, enter values for the following parameters: Name: Enter the name of the SIP entity representing your ECID server to SMGR. FQDN: Enter the FQDN or the IP Address of your ECID server. Type: Enter SIP Trunk as the value. Location: Select the required location from the drop-down menu. Time Zone: Select the time zone of your location. SIP Timer B/F: Leave the field with default values (4 seconds). Call Detail Recording: Set the value to none. SIP Link Monitoring: Set the value to Use Session Manager Configuration. 5. Click Commit. March
28 Post-installation steps Figure 13 SIP entity details page, example 1 Configuring entity links 1. Go to Routing> SIP Entities page, and then click on the SIP entity that you added in the previous procedure. 2. At the bottom of the page, under Entity Links, click Add. 3. On the SIP Entity Details page, enter values for the following parameters: SIP Entity 1: Select the entity from the drop-down menu that represents your Avaya Session Manager. Protocol: Set the value to TCP. Port: Set the value to SIP Entity 2: Select the entity you just added. Port: Set the value to Click Commit. March
29 Post-installation steps Figure 14 - SIP entity details page, example 2 Configuring the SIP entity as a Session Manager application 1. Go to the System Manager Home page. 2. Under the Elements section, click Session Manager. 3. Go to Session Manager> Application Configuration> Applications, and then click New. 4. Enter values for the following parameters: Name: Enter the name of the application that is associated with your ECID server SIP entity. SIP Entity: Set the value to SIP entity that you added in the previous procedure. 5. Click Commit. March
30 Post-installation steps Figure 15 Application Editor page Creating an application sequence 1. Go to Session Manager> Application Configuration> Application Sequences, and then click New. 2. Enter values for the following parameters: Name: Enter the name of the application sequence associated with the application you want to sequence. In the Available Application list at the bottom of the Application Sequence Editor page, click the + icon. After Session Manager displays your application in the Applications in this Sequence section, clear the Mandatory check box. Note: By default Session Manager requires each Sequenced Application to complete execution if the Application fails, or becomes unreachable; Session Manager cannot continue to set up calls. By resetting the Mandatory check box, ECID is instead configured to be a non-critical application: Session Manager will abandon sequencing through ECID in the event of system failure or request time-out, allowing the missioncritical activity of call setup to continue. 3. Click Commit. March
31 Post-installation steps Figure 16 Application Sequence Editor page Adding implicit users 1. Go to Session Manager> Application Configuration> Implicit Users, and then click New. 2. Enter values for the following parameters: Pattern: This field must contain either a single number or a range of numbers that Session Manager sequences in your application sequence. Note: For example, to specify a range of 10-digit numbers starting with 613, enter 613xxxxxxx. Min/Max: Enter the number of digits that Session Manager matches. SIP Domain: Enter the domain of the number or range of numbers that you entered in the Min/Max field. Origination Application Sequence: For the number or range of numbers you entered in the Min/Max field, specify the Application Sequence that Session Manager sequences at the originating end. March
32 Post-installation steps Termination Application Sequence: For the number or range of numbers you entered in the Min/Max field, specify the Application Sequence that Session Manager sequences at the terminating end. Figure 17 Implicit user page 3. Click Commit. Removing ECID configuration on Session Manager After a permanent uninstall of the ECID package from the server, you must remove the Session Manager configurations that you added during the installation procedure. To remove the ECID Session Manager configurations, delete each configured ECID element in the following sequence: Implicit users Application sequence Application Entity link Entity Perform a replication after you complete deleting the configured ECID elements. March
33 Post-installation steps Configure an adaptation for the ECID server on Session Manager If you set up the SIP trunks and Talend customer data transformation job correctly, you do not need to set up any adaptation specifically for the ECID server. This is only a last resort. SIP trunks: Elements of SIP trunks are set up correctly in Session Manager. For example, dialplans and call routing. Talend customer data transformation job: Stripping a digit or adding a digit and adding a plus sign (+) and a pound sign (#) to phone numbers in the database. The digits and signs are added to phone numbers to ensure that the phone numbers match the phone numbers of the calling endpoints. The ECID server receives the phone numbers of the calling endpoints from Session Manager in SIP messages. Adaptations on the Session Manager modify the following content of SIP message headers: Source domain. Destination domain. Digit manipulations on source headers. For example, From and P-Asserted-Identity. Details of destination headers. By creating an adaptation for the ECID server, you can manipulate SIP messages between the ECID server and Session Manager. The following procedure describes creating an adaptation for the ECID server that manipulates phone numbers in the following manner: Adds +1 to a 10-digit number that matches the xxxx pattern in SIP messages. The ECID server receives these SIP messages from Session Manager. Removes +1 from a 10-digit number that matches the xxxx pattern in SIP messages. Session Manager receives these SIP messages from the ECID server. To create an adaptation for the ECID server: 1. On the SMGR GUI Home page, go to Elements> Routing. 2. Go to Routing> Adaptations and then click New. 3. Enter values for the following parameters: March
34 Post-installation steps Adaptation name: Enter the name of a SIP entity on your ECID server. This name must be unique to the SIP entity on your ECID server. Module name: Select DigitConversionAdapter as the value from the drop-down menu. In the Digit Conversion for Outgoing Calls from SM section, click Add. Enter the required values as shown in the following graphic to add a +1 to any ten digit calling number matching a xxxx pattern in messages going out from the Session Manager. In the Digit Conversion for Incoming Calls to SM section, click Add. Enter the required values as shown in the following graphic to remove the +1 from the calling number in messages coming into the Session Manager. 4. Click Commit. Note: When you add digit conversion entries, set the Address to modify field to Origination. The value Origination ensures that phone numbers of only the source endpoints in SIP message headers are manipulated. 5. Go to Routing> SIP Entities, and then click on the ECID SIP Entity in the list. For the Adaptation field, select the adaptation you just created. Click Commit. March
35 Post-installation steps Figure 18 Adaptation details page Note: After completing the configuration changes on the System Manager Web interface, you must perform a replication for the changes to take effect immediately. March
36 Post-installation steps Performing a replication 1. On the System Manager (SMGR) Web interface Home page, go to Services> Replication. 2. Select the check box for the Replica Group that is associated with your Session Manager. 3. Click Repair. Figure 19 Replica groups page March
37 Upgrading ECID Uninstalling ECID Important: To perform the tasks mentioned in this section, you must use a Linux shell and log on to the server as a root user. Run the following command: # rpm -ev <component> (eg: seqapps mss postgres-9.0) 2>&1 tee -a /var/log/rpmlog Note: The Seqapps uninstaller prompts for the password for the user postgres and subsequently removes the data from postgres. To successfully clean up this data, remove all the existing connections to the database, that is, disconnect from pgadmin, if connected. March
38 Information repository integration with Talend Open Studio Information repository integration with Talend Open Studio The ECID sequenced application works on the phone number data stored on the sequencing application service in a postgres database. One recommended method of synchronizing customer data into the expected format is to develop a standalone java application, customized and scheduled using cron through Talend Open Studio. Getting started with Talend Open Studio Installing Talend Open Studio Obtain the open source version of Talend Open Studio from: Importing sample connectors Sample Talend jobs, which integrate sample data from a MySQL source or LDAP source are available in the TOS Project at <directory>. An example of the directory path is as follows: </opt/avaya/mss/server/default/conf/seqapps_services/ecid.zip> To create an integration job based on one of these sample Talend jobs: 1. On the Talend Open Studio for Data Integration screen, click Advanced. March
39 Information repository integration with Talend Open Studio Figure 20 Talend Open Studio page, example 1 2. On the Talend Open Studio for Data Integration screen, click Import to import an existing project as local. Figure 21 Talend Open Studio page, example 2 3. On the Import screen, in the Project name field, enter project name. 4. Select the Select archive file option, and then browse to the existing project file location and select the required project file. March
40 Information repository integration with Talend Open Studio Figure 22 Talend Open Studio, example 3 5. On the Talend Open Studio for Data Integration screen, click Open. March
41 Information repository integration with Talend Open Studio Figure 23 Talen Open Studio, example 4 The system might display a dialog box showing the missing log4j components as shown in the following image. Figure 24 Missing log4j components To load these missing log4j components, set the components folder as follows: Window>Preferences>Talend>Components>User component folder = {workspace_dir}/{project}/components Customizing the connectors With contexts, you can modify credentials even after you deploy the Talend job. To test the modification of credentials within Talend, perform the following procedure: March
42 Information repository integration with Talend Open Studio 1. Open the context. For example, PostgreSQL Select the values of the context as a table or a tree. 3. Modify the values of the context. Deploying the Talend integration jobs Avaya recommends that you deploy the data integration job as a standalone Java application, and then schedule the job to run as a cron job. Important: To perform the tasks mentioned in this section, you must use a Linux shell and log on to the server as a root user. To deploy a Talend integration job, perform the following tasks: 1. Right click the respective job. 2. Select Export Job on the shortcut menu to export the job as an autonomous Job. Figure 25 Talen Open Studio, example 4 3. Unzip the job file to the following location on the ECID server: /opt/avaya/talend-jobs March
43 Information repository integration with Talend Open Studio 4. Run the following commands on the ECID server: # cd /opt/avaya/talend-jobs/ # unzip <job_version>.zip # chmod 755 <job_version>/<job>/<job>_run.sh Note: The system displays the context as a properties file in the file structure. 5. Make sure the customer's source repository (MySQL or LDAP) is set up to allow requests from the ECID server. March
44 Information repository integration with Talend Open Studio Scheduling Talend jobs Important: To perform the tasks mentioned in this section, you must use a Linux shell and log on to the server as a root user. To schedule a Talend job, add the deployed script to the folder /etc/crontab. Figure 26 Scheduling Talend job, example 1 Talend Open Studio provides a deprecated helper plug-in to design crontab entries. To schedule a Talend job, navigate to Window> ShowView> Talend> Scheduler. March
45 Service configuration Service configuration Important: To perform the tasks mentioned in this section, you must use a Linux shell and log on to the server as a root user. Modifying the config properties 1. Run the following command: # cd /opt/avaya/mss/server/default/conf/seqapps_services/ 2. Modify the service configuration properties in the ecid.properties file as required, using vi or any other preferred editor. 3. Run the following commands: # cd Service_Data_0.1/Service_Data/ #./Service_Data_run.sh Figure 27 ecid.properties file example Figure 28 Service_Data_run.sh command example 4. Restart the JBoss service on the Linux server for the changes to take effect. March
46 Service configuration List of configuration properties The following table lists the configuration properties. March
47 Service configuration Property name Recommend ed to change (if required) Valid values Default value Property description scriptlocation No (change only after consultation) Any Linux path location ending in the service script's file-name /opt/avaya/ms s/server/defau lt/conf/seqapp s_services/eci D.service Specifies the location of the original/modified service script to be invoked by the application when a call is routed through the Seqapp server. prefixsymbol Yes True/false False Specifies whether a symbol should be prefixed to the enhanced caller name that the ECID service adds. symboltoprefix Yes Any keyboard character except double-quote and back-slash characters * Specifies the symbol to be prefixed to the enhanced caller name that the ECID service adds. appdataloadquery No (change only after consultation) Any SQL SELECT query SELECT "phone_numb er", "display_name " FROM ecid_data Specifies the query used to load service specific data into memory. appdatasearchvalu e No (change only after consultation) Column name from service specific data table display_name Specifies the name of the result column for the search on the service-specific data that the service invokes. apptblupdatecheck Interval Yes Any integer greater than or equal to 1 20 Specifies the interval (in minutes) that the application will check for any updates from Talend to the service specific table. March
48 Upgrading the ECID components Upgrading the ECID components Important: To perform the tasks mentioned in this section, you must use a Linux shell and log on to the server as a root user. Updating the ECID environment Type the following command: # rpm -Uvh seqapps-1.0-<buildnumber>.noarch.rpm --replacefiles 2>&1 tee -a /var/log/seqappsinstalllog Updating postgres 1. Back up database tables. For more information, see the Updating JBoss/Mobicents section in this document. 2. Update the postgres RPM: # rpm -Uvh postgres-<version>...rpm 3. Restore the database tables. For more information, see the Updating JBoss/Mobicents section in this document. 4. Restart JBoss: # service jboss restart March
49 Upgrading the ECID components Modifying Talend job credentials You can modify the user credentials such as user name and password that Talend uses to connect to the customers external databases or LDAP server without using the Talend Open Studio software by making changes to the Default.properties file. To modify the user credentials: 1. Locate the Default.properties file in your server. 2. Open the file using a text editor. 3. Modify the relevant information in the file. 4. Save the changes. Example of a Default.properties file for SQL server is as follows: # #Tue Dec 13 11:06:57 EST 2011 DemoCustomerData_Database=<customerdbname> DemoCustomerData_Password=<customerdbpass> postgres_avayaseqapps_password=seqappspass DemoCustomerData_AdditionalParams=noDatetimeStringSync\=true postgres_avayaseqapps_port=5432 postgres_avayaseqapps_database=seqapps postgres_avayaseqapps_login=seqappsuser DemoCustomerData_Server=<serverip> DemoCustomerData_Port=3306 postgres_avayaseqapps_server=localhost DemoCustomerData_Login=<customerdbuser> postgres_avayaseqapps_schema Example of a Default.properties file for LDAP Server is as follows: # #Tue Dec 13 11:06:24 EST 2011 LDAPSource_CountLimit=99999 postgres_avayaseqapps_password=seqappspass March
50 Upgrading the ECID components postgres_avayaseqapps_port=5432 LDAPSource_Filter=(&(objectClass\=*)) postgres_avayaseqapps_database=seqapps postgres_avayaseqapps_login=seqappsuser LDAPSource_Host=ldap.example.com postgres_avayaseqapps_server=localhost postgres_avayaseqapps_schema= LDAPSource_TimeOutLimit=0 LDAPSource_Port=389 Updating JBoss/Mobicents 1. Back up the database tables. Use the following steps for backing up and restoring the ECID database. To back up the ECID data into an sql file: 1. Log on to the server using a Linux shell. To log on, use craft as the user name and craft01 as the password. 2. Run the following command to go to the scripts folder: # cd /opt/avaya/scripts 3. Run the following command to view the backup script in the scripts folder: # ls la The backup script is seqappsbackup.sh. 4. Run the following command and then press Enter. # sh seqappsbackup.sh The system stores the backup file in /opt/avaya/scripts/backup 5. Perform the following steps to verify the backup file: a. Go to /opt/avaya/scripts/backup b. Open the sql file to verify the backed up data. To restore ECID data from a previous backup: March
51 Upgrading the ECID components 1. Log on to the server using a Linux shell. To log on, use craft as the user name and craft01 as the password. 2. Run the following command to go to the scripts folder: # cd /opt/avaya/scripts 3. Run the following command to view the restore script in the scripts folder: # ls la The restore script is seqappsrestore.sh. 4. Run the following command, and then press Enter. # sh seqappsrestore.sh 5. Enter the name of the sql file from where you want to restore data. The file is stored at the following location: /opt/avaya/scripts/backup 6. At the prompt to confirm the restoration process, enter Y. The seqapps restore process is successful if the system displays the following message: Database 'seqapps' has been successfully restored. 2. Uninstall the ECID application: # rpm --ev seqapps 3. Update the new JBoss/Mobicents rpm: # rpm -Uvh mss-<version>_<release>.noarch.rpm # cd /opt/avaya/ # chown -R jboss:jboss mss-<version>_<release> # chmod -R 775 mss-<version>_<release> 4. Install the ECID application: # rpm -i seqapps-1.0-<buildnumber>.noarch.rpm --replacefiles 2>&1 tee -a /var/log/seqappsinstalllog 5. Restart JBossservice: # service jboss restart March
52 Troubleshooting the ECID configuration Troubleshooting the ECID configuration Symptom Diagnosis Action required Avaya phones do not display contact names from the customer database. Talend job accessing Active Directory-based LDAP service stops after retrieving partial list of entries. JBoss process is running on the Sequenced Applications server but the SM Dashboard shows the Sequenced Applications Server Entity as 'DOWN'" Avaya IP Phones store contact information with display names. Depending on the phone model used, if the received call comes from an existing contact stored on the phone, the phone might override the caller ID information received with the locally stored display name for the contact. With this Contact Pairing feature, the phone overrides the display name information received with the incoming call and displays the name stored locally on the phone. Active Directory services might be configured to limit the number of responses, for example, up to Run the following command: netstat -nat grep :5080 If the output is not as shown in the following image (netstat), it might be because port 5080 on the Sequenced Application Server is not open to accept TCP or UDP connections. Disable Contact Pairing for the affected stations on Avaya Aura Communication Manager. Ensure that you select the Paging checkbox on the Basic tab for configuring LDAP component. Run the following command to add rules to the Linux firewall to allow TCP and UDP traffic on port 5080: iptables -A INPUT -p tcp --dport j ACCEPT iptables -A OUTPUT -p tcp --sport j ACCEPT March
53 Troubleshooting the ECID configuration Symptom Diagnosis Action required iptables -A INPUT -p udp --dport j ACCEPT iptables -A OUTPUT -p udp --sport j ACCEPT service iptables restart Figure 29 netstat output example Allowing remote connection to the database: Allow remote connection to the database for pgadmin to connect from a remote host by extending /opt/postgres/9.0/data/pg_hba.conf with the following command: # host all all <IP-Network-Adress> /<subnet-mask> md5 For example: host all all 1xx.1yy.0.0/24 md5 Then type the following command: # service postgres-9.0-openscg restart Note: pgadmin is a free and open source GUI administration tool for PostgreSQL. You should use pgadmin only for debugging purpose. March
54 Appendix 1: Using Talend through Avaya Secure Access Link Appendix 1: Using Talend through Avaya Secure Access Link You must use Avaya Secure Access Link (SAL) for performing remote configurations through the Talend Open Studio. Perform the following tasks to set up your system for a remote configuration using the port-forwarding feature of PuTTy: 1. Create an SSH connection to System Manager. The following screen shows that the SSH connection is ready: 2. Open PuTTY. Figure 30 SSH screen 3. In the Session tab, enter values for the following parameters: Host Name or IP Address: localhost Port: 22 Connection Type: SSH March
55 Appendix 1: Using Talend through Avaya Secure Access Link Figure 31 PuTTY screen, example 1 4. Go to Connection> SSH> Tunnels, and enter the following for the tunnel connection to the customer database holding the customer information: Source Port: 389 The source port is the customer database connection port. Destination: :389 The destination is the customer database private IP address and connection port. March
56 Appendix 1: Using Talend through Avaya Secure Access Link 5. Click Add. Figure 32 - PuTTY screen, example 2 6. Add a second tunnel connection to the CNAM postgres database by entering the following: Source Port: 5432 The source port is the postgres connection port. Destination: :5432 The destination is the CNAM server IP address and the postgres connection port. 7. Click Add. March
57 Appendix 1: Using Talend through Avaya Secure Access Link Figure 33 - PuTTY screen, example 3 March
58 Appendix 1: Using Talend through Avaya Secure Access Link Figure 34 - PuTTY screen, example 4 March
59 Appendix 1: Using Talend through Avaya Secure Access Link 8. Go to the Connection tab and enter the following: Seconds between keepalives: 60 Figure 35 - PuTTY screen, example 5 9. Click Open, and then log on to the System Manager command line interface by using admin as the user name and password. You can now switch between the System Manager server and the customer database of the customer and CNAM postgres database using localhost as your reference. 10. Open the Talend Open Studio application. 11. Change any references to the customer IP addresses to localhost in the customer database of the customer and CNAM server postgres database. March
60 Appendix 1: Using Talend through Avaya Secure Access Link Figure 36 Talend Open Studio screen, example 1 Figure 37 - Talend Open Studio screen, example 2 March
Administering Avaya Enhanced Caller ID (ECID)
Administering Avaya Enhanced Caller ID (ECID) Release 1.0 March 2012 2012 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete
More informationRelease Notes for Avaya Proactive Contact 5.0 Agent. Release Notes for Avaya Proactive Contact 5.0 Agent
Release Notes for Avaya Proactive Contact 5.0 Agent Copyright@2011 Notice: While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing,
More informationImplementing Avaya Flare Experience for Windows
Implementing Avaya Flare Experience for Windows 18-604043 Issue 1 July 2012 2012 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document
More informationProduct Release Notes for Avaya Proactive Contact Supervisor
Product Release Notes for Avaya Proactive Contact 4.1.2 Supervisor Page 1 Notice: While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time
More informationAvaya Callback Assist Release Notes
Avaya Callback Assist Release Notes Release 4.1.6 May 2014 2014 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and
More informationAvaya Aura 6.2 Feature Pack 2
Avaya Aura 6.2 Feature Pack 2 WebLM 6.3.2 on VMware Release Notes Release 6.3.2 Issue: 1.0 May 2013 1 2013 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information
More informationMigrating from Intuity Audix LX R 1.1 to Communication Manager Messaging R Stand-Alone
Migrating from Intuity Audix LX R 1.1 to Communication Manager Messaging R 4.0.2 Stand-Alone February 2009 Contents Migrating from IA LX R1.1 to CMM R4.0.2........................... 5 Overview...........................................
More informationRelease Notes for Avaya Proactive Contact 5.0 Supervisor. Release Notes for Avaya Proactive Contact 5.0 Supervisor
Release Notes for Avaya Proactive Contact 5.0 Supervisor Copyright@2011 Notice: While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time
More informationTroubleshooting Avaya Aura TM Presence Services
Troubleshooting Avaya Aura TM Presence Services Release 5.2 December 2009 2005 to 2009 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document
More informationRelease (JITC) for Breeze (SP1)
Release 5.1.0.0.392 (JITC) for Breeze 3.6.0.1 (SP1) Release Notes Issue 1.0 Feb-12, 2019 1 Table of Contents Document changes... 4 Introduction... 4 Product compatibility... 4 Required patches... 4 Installation...
More informationInstalling and Upgrading Avaya Aura System Manager
Installing and Upgrading Avaya Aura System Manager Beta Release 5.2 November 2009 2009 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document
More informationIntelligent Customer Routing Release Notes
Intelligent Customer Routing Release Notes Release 7.0 Issue 1.0 December 2013 Release Notes 1 2013 Avaya Inc. All Rights Reserved Notice While reasonable efforts were made to ensure that the information
More informationAvaya CT for Siebel 7 Release 4.0 User Guide
Avaya CT for Siebel 7 Release 4.0 User Guide September 2006 2006 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and
More informationRelease Notes for Avaya Proactive Contact Supervisor
Release Notes for Avaya Proactive Contact 4.2.3 Supervisor Copyright@2013 Notice: While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time
More informationUsing Manage Alarm Tool
Using Manage Alarm Tool Release 1.0 Issue 1 April 2013 2013 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and
More informationAvaya Aura System Platform Overview
Avaya Aura System Platform Overview Release 6.0 June 2010 2010 Avaya Inc. All Rights Reserved. Notices While reasonable efforts have been made to ensure that the information in this document is complete
More informationIP Office 9.0 IP Office Server Edition Reference Configuration
IP Office 9.0 IP Office Server Edition Reference Configuration Release 9.0.3 15-604135 May 2014 2014 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information
More informationAvaya Communications Process Manager Release 2.2 Web Portal Help for Administrative Users
Avaya Communications Process Manager Release 2.2 Web Portal Help for Administrative Users Document No. 04-601163 August 2008 Issue 10 2008 Avaya Inc. All Rights Reserved. Notice While reasonable efforts
More informationAvaya Session Border Controller for Enterprise 6.3 SP4 Release Notes
Avaya Session Border Controller for Enterprise 6.3 SP4 Release Notes Release 6.3 SP4 Issue 1 August 2015 1 Notice While reasonable efforts were made to ensure that the information in this document was
More informationAvaya Communications Process Manager Release 2.2 Web Portal Help for Non-administrative Users
Avaya Communications Process Manager Release 2.2 Web Portal Help for Non-administrative Users Document No. 04-601161 August 2008 Issue 12 2008 Avaya Inc. All Rights Reserved. Notice While reasonable efforts
More informationAvaya CT for Siebel 7 Version 4.0 Release Notes
Avaya CT for Siebel 7 Version 4.0 Release Notes September 2006 2006 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete
More informationAvaya Call Management System CMS Upgrade Express (CUE) Customer Requirements
Avaya Call Management System CMS Upgrade Express (CUE) Customer Requirements February 2010 2010 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information
More informationAvaya Contact Center Express Release 4.1 XMPP Gateway
Avaya Contact Center Express Release 4.1 XMPP Gateway Release 4.1 January 2010 2005 to 2009 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this
More informationAvaya Contact Center Express Release 5.0 XMPP Gateway
Avaya Contact Center Express Release 5.0 XMPP Gateway Release 5.0 August 2010 2005 to 2010 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this
More informationAdministering Avaya Flare Communicator for ipad Devices and Windows
Administering Avaya Flare Communicator for ipad Devices and Windows 01.AF June 2012 2012 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in
More informationRelease Notes for Avaya Proactive Contact Supervisor
Release Notes for Avaya Proactive Contact 4.2.1 Supervisor Copyright@2010 Notice: While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time
More informationAvaya Call Management System Release 15 Change Description
Avaya Call Management System Release 15 Change Description May 2009 2009 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete
More informationInstalling Avaya Agile Communication Environment Foundation Toolkit
Installing Avaya Agile Communication Environment Foundation Toolkit 2.3.2 Issue 1 March 2011 2011 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information
More informationAvaya Scopia Mobile Android Release (SP12)
Avaya Scopia Mobile Android Release 8.3.12 (SP12) Release Notes Issue 1.0 revision 1 9 th January 2019 2016 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the
More informationAvaya one-x Mobile 5.2 SP6 Release Notes
Avaya one-x Mobile 5.2 SP6 Release Notes Release Notes Build # 5.2.6.0.7 Issue 1 June 26 th, 2011 2010 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information
More informationAvaya Aura Messaging Web Access Feature Description
Avaya Aura Messaging Web Access Feature Description Release 6.3.1 Issue 2 July 2014 2014 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in
More informationUpgrading Intelligent Customer Routing
Upgrading Intelligent Customer Routing Release 7.0 Issue 1 December 2013 2013 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document
More informationAvaya Aura Call Center Elite Documentation Roadmap
Avaya Aura Call Center Elite Documentation Roadmap May 2013 2013 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete
More informationAvaya Contact Center Express Release 4.1 License Director User Guide
Avaya Contact Center Express Release 4.1 License Director User Guide Release 4.1 January 2010 2005 to 2009 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information
More informationAvaya one-x Communicator Centralized Administration Tool
Avaya one-x Communicator Centralized Administration Tool August 2010 2010 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document
More informationAVAYA IP Flow Manager. Release Notes. Release 2.1. August 14 th, 2014 Issue 1.1 CID:
AVAYA IP Flow Manager Release 2.1 Release Notes August 14 th, 2014 Issue 1.1 CID: 166826 2014 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information
More informationAvaya Aura Experience Portal Release 6.0 Service Pack 2 Intelligent Customer Routing
Avaya Aura Experience Portal Release 6.0 Service Pack 2 Intelligent Customer Routing Developer Guide Released in: December 2012 Developer Guide 1 2012 Avaya Inc. All Rights Reserved Notice While reasonable
More informationProduct Release Notes for Avaya Proactive Contact Database
Product Release Notes for Avaya Proactive Contact 4.1.2 Database Page 1 Notice: While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time
More informationAvaya Call Management System Documentation Roadmap
Documentation Roadmap Release 18 Issue 1 October 2015 2015, Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and
More informationConverged Network Analyzer Command Reference Guide Addendum
Converged Network Analyzer Command Reference Guide Addendum for the Converged Network Analyzer (CNA), Adaptive Path Controller-Enterprise (APC-E), Adaptive Path Controller-Internet (APC-I), and the CNA
More informationAvaya Client Applications Configurator User Guide
Avaya Client Applications Configurator User Guide Release 6.3 02-604198 Issue 02.01 February 2014 2014 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the
More informationAvaya Agile Communication Environment Communicator Add-in User Guide
Avaya Agile Communication Environment Communicator Add-in User Guide Release 3.0 April 2012 2012 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information
More informationAdministering Avaya Flare Experience for Windows
Administering Avaya Flare Experience for Windows Release 1.1 18-604156 Issue 4 September 2013 2013 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information
More informationAvaya Aura Call Center Elite Multichannel Documentation Roadmap
Multichannel Documentation Roadmap Release 6.4 Issue 2 April 2015 2015 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is
More informationUser Guide for Avaya Equinox Add-in for IBM Lotus Notes
User Guide for Avaya Equinox Add-in for IBM Lotus Notes Release 9.0 Issue 1 January 2017 2014-2017, Avaya, Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information
More informationUsing Avaya one-x Agent
Using Avaya one-x Agent Release 1.0 June 2009 2009 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at
More informationIP Office Release 9.0
Embedded Voicemail User Guide (IP Office Mode) 15-604067 Issue 13a - (13 February 2014) 2014 AVAYA All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in
More informationAvaya Web Conferencing Administrator's Guide
Avaya Web Conferencing Administrator's Guide Version 4.1.20 October 2008 Document number 04-603073 2008 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information
More informationAvaya one-x Mobile 5.2 GA Release Notes
Avaya one-x Mobile 5.2 GA Release Notes Release Notes Build # 5.2.0.0.68 Issue 1 December 17 th, 2009 2009 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information
More informationAdministering Intelligent Customer Routing
Administering Intelligent Customer Routing Release 7.0 Issue 1 December 2013 2013 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document
More informationIP Office. TAPI Link Installation Issue 12a - (14 January 2013)
TAPI Link Installation 15-601034 Issue 12a - (14 January 2013) 2013 AVAYA All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete
More informationAvaya Agile Communication Environment Web Browser and Office Add-ins Application Fundamentals
Avaya Agile Communication Environment Web Browser and Office Add-ins Application Fundamentals Release 2.3.2 NN10850-031, 05.02 March 2011 2011 Avaya Inc. All Rights Reserved. Notice While reasonable efforts
More informationAvaya CMS Supervisor Reports
Avaya CMS Supervisor Reports Release 16.1 June 2010 2010 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate
More informationRelease Notes for Operation Support System Release
Release Notes for Operation Support System Release 1.2.0.1 Release Notes Issue 1.2.0.1, 12/10/2016 2016 Notice While reasonable efforts have been made to ensure that the information in this document is
More informationAvaya Aura Contact Center Documentation Roadmap
Documentation Roadmap Release 6.3 NN44400-113 Issue 04.02 May 2013 2013 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is
More informationRelease Notes for Avaya Proactive Contact Supervisor. Release Notes for Avaya Proactive Contact Supervisor
Release Notes for Avaya Proactive Contact 5.0.1 Supervisor Copyright@2011 Notice: While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time
More informationIP Office Basic Edition
Norstar Mode - Embedded Voicemail User Guide (IP Office Mode) 15-604067 Issue 12f - (19 August 2013) 2013 AVAYA All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information
More informationAvaya Event Processor Release 2.2 Operations, Administration, and Maintenance Interface
Avaya Event Processor Release 2.2 Operations, Administration, and Maintenance Interface Document ID: 13-603114 Release 2.2 July 2008 Issue No.1 2008 Avaya Inc. All Rights Reserved. Notice While reasonable
More informationIP Office Platform. Using Voic Pro in Intuity Mode Issue 10a - (16 January 2015)
Using Voicemail Pro in Intuity Mode 15-601066 Issue 10a - (16 January 2015) 2015 AVAYA All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document
More informationQuick Install for Avaya Aura Device Services
Quick Install for Avaya Aura Device Services Release 1.0 Issue 2 March 2017 2016-2017 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this
More informationUsing Avaya Aura Messaging Web Access
Using Avaya Aura Messaging Web Access Release 6.3.1 Issue 4 July 2014 2014 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document
More informationQuick Install for Avaya Aura Device Services
Quick Install for Avaya Aura Device Services Release 7.1 Issue 1 July 2017 2016-2017 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this
More informationImplementing and Administering Services-VM on Avaya Aura System Platform
Implementing and Administering Services-VM on Avaya Aura System Platform Release 2.0 January 2013 Issue 1 2013 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that
More informationAvaya Aura 6.2 Feature Pack 3
Avaya Aura 6.2 Feature Pack 3 WebLM 6.3.4 on VMware Release Notes Release 6.3.4 Issue: 1.2 October 2013 Copyright 2013 Avaya Inc. All rights reserved. Use pursuant to the terms of your signed agreement
More informationAdministering Avaya Flare Experience for ipad Devices and Windows
Administering Avaya Flare Experience for ipad Devices and Windows 01.AF December 2012 2012 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information
More informationIP Office. Embedded Voic User Guide (IP Office Mode) Issue 12a (26 February 2013)
Embedded Voicemail User Guide (IP Office Mode) 15-604067 Issue 12a (26 February 2013) 2013 AVAYA All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this
More informationIP Office Release 7.0 IP Office Essential Edition - Quick Version Embedded Voic User Guide
IP Office Essential Edition - Quick Version Embedded Voicemail User Guide 15-604067 Issue 09a - (21 February 2011) 2011 AVAYA All Rights Reserved. Notices While reasonable efforts have been made to ensure
More informationAvaya Equinox VDI Release 3.0 Service Pack 1
Avaya Equinox VDI Release 3.0 Service Pack 1 Release Notes Issue 1.0 February 5, 2019 2019 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this
More informationUser Guide. License Director. Release 4.0
User Guide License Director Release 4.0 Printed on 11 March, 2009 2009 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete
More informationAvaya Session Border Controller for Enterprise 7.0 Release Notes
Avaya Session Border Controller for Enterprise 7.0 Release Notes Release 7.0 Issue 2 July 2016 1 Notice While reasonable efforts were made to ensure that the information in this document was complete and
More informationRelease Notes for Avaya Aura Appliance Virtualization Platform Release
Release Notes for Avaya Aura Appliance Virtualization Platform Release 7.0.0.0 Release Notes Issue 1.0, August 24, 2015 2015 Avaya Inc. All rights reserved. Notice While reasonable efforts have been made
More informationAvaya Conference Viewer Release 5.0 User Guide
Avaya Conference Viewer Release 5.0 User Guide 04-602196 Release 5.0 August 2007 Issue 1 2007 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in
More informationUpgrading to Avaya Aura Experience Portal 7.1
Upgrading to Avaya Aura Experience Portal 7.1 Release 7.1 Issue 1 May 2016 2012-2016, Avaya, Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this
More informationIP Office 6.1 Embedded Voic Mailbox User Guide
Embedded Voicemail Mailbox User Guide 15-604067 Issue 08a - (18 August 2010) 2010 AVAYA All Rights Reserved. Notices While reasonable efforts have been made to ensure that the information in this document
More informationIntelligent Customer Routing. Release Notes
Intelligent Customer Routing Release Notes Release 7.0.1 March 2015 2015 Avaya Inc. All Rights Reserved Notice While reasonable efforts have been made to ensure that the information in this document is
More informationOverview of Avaya Aura System Platform
Overview of Avaya Aura System Platform Release 6.2.1 July 2012 2012 Avaya Inc. All Rights Reserved. Notices While reasonable efforts have been made to ensure that the information in this document is complete
More informationImplementing and Administering Services-VM on Avaya Aura System Platform
Implementing and Administering Services-VM on Avaya Aura System Platform Release 4.0 Issue 2 February 2018 2013-2018, Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure
More informationUsing Avaya Communicator for Microsoft Lync 2013 on IP Office Platform
Using Avaya Communicator for Microsoft Lync 2013 on IP Office Platform Release 9.1 02-604413 Issue 2 May 2015 2015 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure
More informationAdministering standalone Avaya WebLM
Administering standalone Avaya WebLM Release 7.0.1 Issue 3 June 2017 2016-2017, Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document
More informationBM32 Button Module User Guide
BM3 Button Module User Guide 16-601450 Issue 1 April 007 007 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate
More informationConfiguring SIP Enablement Services Edge 5.x for Avaya Aura Communication Manager Branch
Configuring SIP Enablement Services Edge 5.x for Avaya Aura Communication Manager Branch 03-602026 Issue 3 May 2009 2009 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure
More informationInstalling Server Applications for Avaya one-x Agent
Installing Server Applications for Avaya one-x Agent Release 2.5.4 (H.323) Issue 1 December 2013 2013 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information
More informationIP Office Intuity Mailbox Mode User Guide
Intuity Mailbox Mode User Guide 15-601130 EN-S Issue 12b - (03 October 2011) 2011 AVAYA All Rights Reserved. Notices While reasonable efforts have been made to ensure that the information in this document
More informationAvaya Meeting Exchange Web Portal 5.0 Release Notes
Avaya Meeting Exchange Web Portal 5.0 Release Notes 04-602190 Issue 1 August 2007 2007 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document
More informationAvaya Aura Documentation Catalog
Avaya Aura Documentation Catalog Release 8.0 Issue 1 July 2018 2018, Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete
More informationMigrating the Avaya Aura System Manager data to 6.3 using Data Migration Utility
Migrating the Avaya Aura System Manager data to 6.3 using Data Migration Utility Release 6.3 Issue 1 May 2013 2013 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure
More informationAvaya Call Management System Network Reporting
Avaya Call Management System Network Reporting Release 16.x November 2010 2010 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document
More informationEngagement Call Control Release Notes
Engagement Call Control Release Notes Release 3.3 Issue 1 July 2017 2017, Avaya, Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document
More informationAvaya Aura Call Center Elite Documentation Roadmap
Avaya Aura Call Center Elite Documentation Roadmap Release 7.1 Issue 1 May 2017 2014-2017, Avaya, Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information
More informationAvaya Aura Presence Services Overview and Specification
Avaya Aura Presence Services Overview and Specification Release 7.0 Issue 1 August 2015 2015 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information
More informationAvaya IQ Administration
Avaya IQ Administration Release 4.1 March 2008 2008 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at
More informationMaintaining and Troubleshooting Avaya one-x Agent
Maintaining and Troubleshooting Avaya one-x Agent Release 1.0 June 2009 2009 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was
More informationRelease Notes for Avaya Engagement Designer Release 3.1 Service Pack 2 ( ) Release Notes Issue 1, 2/18/2016
Release Notes for Avaya Engagement Designer Release 3.1 Service Pack 2 (3.1.0.2 ) Release Notes Issue 1, 2/18/2016 Notice While reasonable efforts have been made to ensure that the information in this
More informationAvaya Agile Communication Environment Mobility Application for BlackBerry
Avaya Agile Communication Environment Mobility Application for BlackBerry Release 2.3.2 NN10850-028, 04.02 March 2011 2011 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made
More informationAvaya IP Agent Release 6.0 Installation and User Guide
Avaya IP Agent Release 6.0 Installation and User Guide August 2005 2005 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete
More informationAvaya Agent for Desktop Release Notes
Avaya Agent for Desktop Release Notes Release 1.4.3 Issue 1.0 October 2016 2015-2016 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this
More informationAvaya IQ Standard Reports
Avaya IQ Standard Reports Release 5.2 April 2015 2015 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate
More informationAvaya Converged Platform 130 Series. idrac9 Best Practices
Avaya Converged Platform 130 Series idrac9 Best Practices Release 4.0 December 2018 2018 Avaya Inc. All Rights Reserved Notice While reasonable efforts were made to ensure that the information in this
More informationIP Office. IP Office Mailbox Mode User Guide Issue 11b - (15 May 2010)
Mailbox Mode User Guide 15-601131 Issue 11b - (15 May 2010) 2010 AVAYA All Rights Reserved. Notices While reasonable efforts have been made to ensure that the information in this document is complete and
More informationAvaya IQ Report Designer
Avaya IQ Report Designer Release 5.0 April 2010 2010 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate
More information