Beruflich Dokumente
Kultur Dokumente
N
e
t
w
o
r
k
C
o
n
f
i
g
u
r
a
t
i
o
n
D
i
a
g
r
a
m
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
4 of 27
aes-ess.doc
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
5 of 27
aes-ess.doc
2. Equipment and Software Validated
The following equipment and software were used for the sample configuration provided:
Equipment Software
Avaya Communication Manager
Avaya S8710 Media Server
Avaya S8500 Local Survivable Processor
Avaya S8300 Local Survivable Processor
3.1 (R013x.01.0.628.6)
3.1 (R013x.01.0.628.6)
3.1 (R013x.01.0.628.6)
Avaya G650 Media gateway
IPSI (TN2312BP)
C-LAN (TN799DP)
MEDPRO (TN2602AP)
FW 030
FW 017
FW 021
Avaya G700 Media Gateway 25.22.0
Avaya G350 Media Gateway 25.22.0
Avaya G250 Media Gateway 25.22.0
Avaya MultiVantage Application Enablement Server
Red Hat Linux Enterprise Version 3.0
IBM x306 server
r3-1-0-build 33-1-0
2.4.21-32.EL
Avaya Interaction Center
Microsoft Server 2003
R7.0
Build 56
Avaya Operational Analyst R7.0
Build 27
Table 2. Equipment and Version Validated
3. Configure Avaya Communication Manager
This section details the administration on Avaya Communication Manager that must be
performed to configure the CTI link. The following commands are issued at the Avaya System
Access Terminal (SAT) screen on the S8710 Media Server at the Main office.
Step Description
1.
Issue the display system-parameters customer-options command, and verify that the
ASAI Link Core Capabilities, and Computer Telephony Adjunct Links fields are set to
y. If they are not set to y, contact your Avaya sales team or business partner. A system
license file controls the settings on the OPTIONAL FEATURES form.
Figure 2: Optional Features
display system-parameters customer-options Page 3 of 11
OPTI ONAL FEATURES
Abbr evi at ed Di al i ng Enhanced Li st ? y Audi bl e Message Wai t i ng? y
Access Secur i t y Gat eway ( ASG) ? n Aut hor i zat i on Codes? y
Anal og Tr unk I ncomi ng Cal l I D? y Backup Cl ust er Aut omat i c Takeover ? n
A/ D Gr p/ Sys Li st Di al i ng St ar t at 01? y CAS Br anch? n
Answer Super vi si on by Cal l Cl assi f i er ? y CAS Mai n? n
ARS? y Change COR by FAC? n
ARS/ AAR Par t i t i oni ng? y Computer Telephony Adjunct Links? y
ARS/ AAR Di al i ng wi t hout FAC? y Cvg Of Cal l s Redi r ect ed Of f - net ? y
ASAI Link Core Capabilities? y DCS ( Basi c) ? y
ASAI Li nk Pl us Capabi l i t i es? y DCS Cal l Cover age? y
Async. Tr ansf er Mode ( ATM) PNC? n DCS wi t h Rer out i ng? y
Async. Tr ansf er Mode ( ATM) Tr unki ng? y
ATM WAN Spar e Pr ocessor ? N Di gi t al Loss Pl an Modi f i cat i on? n
ATMS? y DS1 MSP? n
At t endant Vect or i ng? n DS1 Echo Cancel l at i on? n
( NOTE: You must l ogof f & l ogi n t o ef f ect t he per mi ssi on changes. )
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
6 of 27
aes-ess.doc
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
7 of 27
aes-ess.doc
Step Description
2. Enter the node name and IP address of the AES server on the IP NODE NAMES form.
Issue the change node-names ip command and enter the following values:
Name: aesserver
IP Address: 10.1.1.50
Note: The sample configuration assumes that the C-LANs, ESS, LSPs are already
configured.
Figure 3: IP Node Names
change node-names ip Page 1 of 1
I P NODE NAMES
Name I P Addr ess Name I P Addr ess
BO6 10 . 16 . 2 . 10 . . .
G250- BR5 10 . 15 . 2 . 11
aesserver 10 .1 .1 .50 . . .
. . .
br 3- l sp 10 . 13 . 2 . 10 . . .
br 4- el sp 10 . 14 . 2 . 9 . . .
br 4- l sp 10 . 14 . 2 . 10 . . .
br 5 10 . 15 . 2 . 10 . . .
cc- ess1 10 . 2 . 2 . 11 . . .
cc- ess2 10 . 2 . 2 . 12 . . .
cf - 1a03 10 . 1 . 2 . 15 . . .
cf - 1b03 10 . 1 . 2 . 17 . . .
cl an- 1a02 10 . 1 . 2 . 21 . . .
cl an- 1a04 10 . 1 . 2 . 23 . . .
cl an- 1b02 10 . 1 . 2 . 25 . . .
cl an- 2a02 10 . 2 . 2 . 21 . . .
def aul t 0 . 0 . 0 . 0 . . .
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
8 of 27
aes-ess.doc
Step Description
3. Enable AE Services on the IP SERVICES form.
Issue the change ip-services command and enter the following values:
Service Type: AESVCS
Enabled: y
Local Node: Select a C-LAN node name to use for connecting to the AES from
the IP NODE NAMES form, for example clan-1a02.
Remote Node and Port: <blank>
Local Port: Retain the default value 8765.
Figure 4: Change IP-Services Form (Page 1)
Once the AE Services are enabled, a third page will appear on the IP SERVICES form.
Navigate to Page 3 and enter the following values:
AE Services Server: <Hostname of AE Services Server>
Password: <Alphanumeric password for AE Services Server>
Enabled: y
Figure 5: Change IP-Services Form (Page 3)
change ip-services Page 1 of 3
I P SERVI CES
Ser vi ce Enabl ed Local Local Remot e Remot e
Type Node Por t Node Por t
AESVCS y clan-1a02 8765
change ip-services Page 3 of 3
AE Ser vi ces Admi ni st r at i on
Ser ver I D AE Ser vi ces Passwor d Enabl ed St at us
Ser ver
1: aesserver * y
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
9 of 27
aes-ess.doc
Step Description
4. Repeat Step 3 to add the second C-LAN link to be used for load balancing, for example
clan-2a02, as shown below.
Figure 6: Change IP-Services Form (Page 1)
Note: If additional C-LANs are required, repeat Step 4.
5. Enable CTI link for Avaya Interaction Center.
Issue the add cti-link <x> command, where <x> is an available CTI link number. Enter
the following values:
Extension: <Enter a valid extension>
Type: ADJ-IP
Name: <description>
Figure 7: Add CTI-LINK
change ip-services Page 1 of 3
I P SERVI CES
Ser vi ce Enabl ed Local Local Remot e Remot e
Type Node Por t Node Por t
AESVCS y cl an- 1a02
AESVCS y clan-2a02 8765
8765
add cti-link 1 Page 1 of 2
CTI LI NK
CTI Li nk: 1
Ext ensi on: 20801
Type: ADJ-IP
COR: 1
Name: ICVoice1 Server
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
10 of 27
aes-ess.doc
Step Description
6. In the sample configuration, two CTI links are administered for Avaya IC.
Repeat Step 5 to create the second link as shown below.
Figure 8: Add CTI-Link
7. Change the SURVIVABLE PROCESSOR - IP-SERVICES form for ESS.
Issue the change survivable-processor <xx> command, where <xx> is the node-name
for the ESS server. In the sample configuration, this is cc-ess1 as show in Figure 3. Enter
the following value:
Enabled: Enter i, to have ESS inherit the link data administered on the Main
Media Server.
Figure 9: Change ESS Survivable-Processor
add cti-link 2 Page 1 of 2
CTI LI NK
CTI Li nk: 2
Ext ensi on: 20802
Type: ADJ-IP
COR: 1
Name: ICVoice2 Server
change survivable-processor cc-ess1 Page 3 of 3
SURVI VABLE PROCESSOR - I P- SERVI CES
Ser vi ce Enabl ed Local Local Remot e Remot e
Type Node Por t Node Por t
AESVCS i cl an- 1a02 8765
AESVCS i cl an- 2a02 8765
4. Configure Avaya MultiVantage Application Enablement
Services
This section details the administration of Avaya MultiVantage Application Enablement Services
(AES), which must be performed for the CVLAN link needed for Avaya Interaction Center.
It is assumed that the Avaya MultiVantage AES server has IP connectivity and that AE Services
is installed and has the appropriate license. Please refer to the Avaya MultiVantage Application
Enablement Services Installation Guide [1] for a description of these procedures.
Avaya MultiVantage AES is configured using the Operation, Administration and Maintenance
(OAM) web interface. The OAM web interface is accessed by typing the following URL on a
web browser and then pressing Enter:
https://<hostname or IP address>:8443/MVAP
Step Description
1. Log in to AE Services OAM using proper credential.
Figure 10: AE Services OAM Login Screen
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
11 of 27
aes-ess.doc
Step Description
2. Select CTI OAM Admin.
Figure 11: CTI OAM Admin Screen
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
12 of 27
aes-ess.doc
Step Description
3. In the left panel of the CTI OAM Home, click on Administration Local IP.
Enter the following values:
Client Connectivity: Select 10.1.1.50 from the drop down menu. The IP address is
specified during AES software installation.
Switch Connectivity: Select 10.1.1.50 from the drop down menu.
Media Connectivity: Select 10.1.1.50 from the drop down menu.
Note: For the sample testing, a single IP address is used for all connectivity. For customer
configurations, Avaya recommends the use of a different IP address for Switch Connectivity.
Figure 12: Local IP Administration
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
13 of 27
aes-ess.doc
Step Description
4. In the left panel of the CTI OAM Home, click on Administration Switch Connections.
Enter the name for the Switch Connection (for example ccaes), and then click the Add
Connection button.
Figure 13: Switch Connection Administration
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
14 of 27
aes-ess.doc
Step Description
5. Clicking on the Add Connection Button in the previous step will bring up the Set Password
screen.
On the Set Password screen,
Enter <password>in the password field.
In the Confirm Password field, enter <password>.
Check theSecure Socket Layer (SSL), then click the Apply button.
The password entered must be same password entered in AE Services Administration Page in the
IP-Services form on Avaya Communication Manager as shown in Figure 5.
Figure 14: Password Administration
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
15 of 27
aes-ess.doc
Step Description
6. In the left panel of the CTI OAM Home, click on Administration Switch Connections.
Check the radio button for the switch connection, for example ccaes, and then click on the Edit
Connection button (not shown).
Enter the IP address of theC-LAN defined in Section 3 Step 2, for example 10.1.2.21, and then
click on Add Name or IP as shown in Figure 15.
Note 1: If an additional C-LAN address is required for load balancing, repeat the previous step to
add the IP address of the C-LAN circuit pack. In this sample configuration, an additional C-
LAN circuit pack located at Branch 2 (10.2.2.21) is added as shown in Figure 15.
Figure 15: Edit CLAN IPs
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
16 of 27
aes-ess.doc
In the left panel of the CTI OAM Home, click on Status and Control Switch Conn.
Summary to view the status of the switch connections, as shown below in Figure 16.
Figure 16: Switch Connections Summary
To view the switch connection details, from the Switch Connection Summary screen, click on
Switch Connection Details as shown below in Figure 17.
Figure 17: Switch Connections Details
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
17 of 27
aes-ess.doc
Step Description
7. In the left panel of the CTI OAM Home, click on Administration CTI Link Admin to
administer CVLAN links.
Figure 18: CTI Link Administration
Click on CVLAN Links Add Link.
Figure 19: Add CVLAN Link
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
18 of 27
aes-ess.doc
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
19 of 27
aes-ess.doc
Step Description
8. Enter the following to add a CVLAN Link:
Signal: Select an available signal number.
Proprietary: Enable Proprietary Link. This is an internal link type for Avaya
applications such as Avaya Interaction Center and Avaya Interactive Response systems.
Switch Connection: Select the name of the switch connection, for example ccaes.
Switch CTI Link Number: Select the CTI Link number administered on Avaya
Communication Manager for this CVLAN link, as per Figure 7. The CTI Link on the
Avaya Communication Manager must be administered as ADJ -IP.
Version: Select ASAI Link Version to 4 for CVLAN Client 8.2.5 or to 3 for CVLAN
Client 6.1.7.
Heartbeat: Check the box to enable the heartbeat.
Click Apply Changes for changes to take effect.
Figure 20: CVLAN Link Administration
9. Repeat Steps 7 and 8 to add an additional CVLAN Link.
Step Description
10. In the left panel of the CTI OAM Home, click on Administration CTI Link Admin
CVLAN Links.
Select the radio button for the Signal (Link) to administer CVLAN Clients.
Click the Edit Client button to assign CVLAN Clients to the Signal (Link) selected.
Figure 21: CVLAN Clients Administration
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
20 of 27
aes-ess.doc
Step Description
11. In the Add Client text box, enter the IP Address of the CVLAN client (i.e., the IP Address of the
Avaya Interaction Center Voice1, 10.1.1.61) as shown in Figure 22.
Click on the Add Client button.
Figure 22: CVLAN Client IP Address Administration
12. Repeat Steps 10 and 11 to add an additional CVLAN client (i.e., the IP Address of the Avaya
Interaction Center Voice2, 10.1.1.62)
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
21 of 27
aes-ess.doc
5. Verification Steps
Step Description
1. Issue the following commands from the Avaya Communication Manager SAT to verify the
CVLAN link between Avaya Communication Manager and Avaya AES.
status aesvcs interface to verify the status of the interface.
status aesvcs link to verify the status of the link.
status aesvcs cti-link to verify the cti-link. The cti-link <id>is defined in
Figure 7.
Figure 23: Status AESVCS Interface
Figure 24: Status AESVCS Link
Figure 25: Status AESVCS CTI-Link
st at us aesvcs ct i - l i nk
AE SERVI CES CTI LI NK STATUS
CTI Ver si on Mnt AE Ser vi ces Ser vi ce Msgs Msgs
Li nk Busy Ser ver St at e Sent Rcvd
1 4 no aesser ver est abl i shed 96 96
2 4 no aesser ver est abl i shed 96 96
st at us aesvcs l i nk
AE SERVI CES LI NK STATUS
Sr vr / AE Ser vi ces Remot e I P Remot e Local Node Msgs Msgs
Li nk Ser ver Por t Sent Rcvd
01/ 01 aesser ver 10. 1. 1. 50 34838 cl an- 2a02 293 426
01/ 02 aesser ver 10. 1. 1. 50 34841 cl an- 1a02 179 179
st at us aesvcs i nt er f ace
AE SERVI CES I NTERFACE STATUS
Local Node Enabl ed? Number of St at us
Connect i ons
cl an- 1a02 yes 1 l i st eni ng
cl an- 2a02 yes 1 l i st eni ng
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
22 of 27
aes-ess.doc
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
23 of 27
aes-ess.doc
Step Description
2. From the AES OAM - CTI OAM Home menu, click on Status and Control Switch Conn
Summary and verify the connection details as shown in Figure 26.
Figure 26: Switch Connection Details on AES Server
Step Description
3. From the AES OAM - CTI OAM Home menu, click on Status and Control Service
Summary. TheServices Summary screen appears. Click on CVLAN Services Details and
verify the status of the CVLAN service as shown in Figure 27.
Figure 27: CVLAN Service Summary on AES Server
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
24 of 27
aes-ess.doc
Step Description
4. Issue the following commands from the Avaya Communication Manager SAT on the ESS to
verify the AES link is established between the ESS and AES.
status aesvcs interface to verify the status of the interface.
status aesvcs link to verify the status of the link.
status aesvcs cti-link to verify the cti-link. The cti-link <id>is defined in
Figure 7.
Figure 28: Status AESVC Interface (ESS)
Figure 29: Status AESVCS Link (ESS)
Figure 30: Status AESVCS CTI-Link (ESS)
st at us aesvcs i nt er f ace
AE SERVI CES I NTERFACE STATUS
Local Node Enabl ed? Number of St at us
Connect i ons
cl an- 1a02 yes 1 l i st eni ng
cl an- 2a02 yes 1 l i st eni ng
st at us aesvcs l i nk
AE SERVI CES LI NK STATUS
Sr vr / AE Ser vi ces Remot e I P Remot e Local Node Msgs Msgs
Li nk Ser ver Por t Sent Rcvd
01/ 01 aesser ver 10. 1. 1. 50 41239 cl an- 2a02 215 296
01/ 02 aesser ver 10. 1. 1. 50 41408 cl an- 1a02 83 83
st at us aesvcs ct i - l i nk
AE SERVI CES CTI LI NK STATUS
CTI Ver si on Mnt AE Ser vi ces Ser vi ce Msgs Msgs
Li nk Busy Ser ver St at e Sent Rcvd
1 4 no aesser ver est abl i shed 84 77
2 4 no aesser ver est abl i shed 75 76
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
25 of 27
aes-ess.doc
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
26 of 27
aes-ess.doc
6. Conclusion
These Application Notes demonstrate how to provision Avaya Communication Manager for
AES with an ESS. In addition, these Application Notes also describe the steps required to
configure a CVLAN link between Avaya Communication Manager and Avaya Application
Enablement Services server for Avaya Interaction Center.
7. Additional References
The following documents can be found at http://support.avaya.com:
[1] Administrators Guide for Avaya Communication Manager, Issue 2, February 2006; Doc
ID: 03-300509
[2] Avaya MultiVantage Application Enablement Services Installation and Upgrade Guide
for a Bundled Server R3.1, Document ID: 02-300356.
WH; Reviewed:
PV 4/13/06
Solution & Interoperability Test Lab Application Notes
2006 Avaya Inc. All Rights Reserved.
27 of 27
aes-ess.doc
2006 Avaya Inc. All Rights Reserved.
Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and
are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the
property of their respective owners. The information provided in these Application Notes is
subject to change without notice. The configurations, technical data, and recommendations
provided in these Application Notes are believed to be accurate and dependable, but are
presented without express or implied warranty. Users are responsible for their application of any
products specified in these Application Notes.
Please e-mail any questions or comments pertaining to these Application Notes along with the
full title name and filename, located in the lower right corner, directly to the Avaya Solution &
Interoperability Test Lab at interoplabnotes@list.avaya.com