Sal Supported Products

Secure Access Link Supported Products - September 20, 2012
In order for the Secure Access Link (SAL) Gateway to correctly manage a device, the correct SAL model is needed. A SAL model is a settings file that defines how the
SAL Gateway will handle alarms as well as what remote access methods are available for a particular product. It also defines what standard inventory data to collect, if enabled.
The SAL Gateway software installer is downloadable from the Product Licensing and Delivery System (PLDS). For SAL Gateway R1.x, this Generally Available (GA) installer was built with SAL models that were supported
at the time when the GA installer was built. For SAL Gateway R2.X, the models are not embedded in the installer but in a separate zip file that would be downloaded from PLDS with the SAL Gateway R2.0 installer.
Additional models that are created and updated after the GA distribution will be bundled in a model package.
This model package is uploaded to the Concentrator Servers at Avaya to be distributed to the SAL Gateways at the customer locations.
SAL Gateway Release 2.X now allows the user to change when the downloaded models should be applied. Please consult the "Indicating model distribution preferences" section in Chapter 4 of the Secure Access Link 2.X
SAL Gateway Implementation Guide.
Updating or adding new SAL models does not change the overall functionality or version of the SAL Gateway software. It only affects the SAL model version and the SAL Gateways instructions on how to handle that product.
If a SAL Gateway is restored from a backup, older models may have been restored at that time as well. If the restored model is earlier than the version listed below as the Current Model Version, please contact Avaya Global
Support Services (GSS) to obtain the latest model.
SAL Gateway Model Compatibility
SAL Gateway R1.5 is compatible with model versions 1.x.x.x.
SAL Gateway R1.8 - is compatible with model versions 1.x.x.x and 2.x.x.x.
SAL Gateway Build Latest Service Pack Releases
SAL Gateway R1.8 - Service Pack 3
SAL Production DNS / IP Destinations

Allow HTTPS--port 443, TCP--access outbound from SALGW to these destinations
SAL Remote Access server: sl1.sal.avaya.com 198.152.212.33
SAL Alarming server:
secure.alarming.avaya.com 198.152.220.247
SAL Gloabal Diagnostic Srvr: sl1d.sal.avaya.com 198.152.212.32
SAL Global Access Server: gas1.sal.avaya.com 198.152.212.31
Supported Products
Acme Packet NetNet 3800 &

4500 Series
Supported Product
Versions
3800 & 4500

Series
Alarm handling?
Yes - SNMP
Trap
Remote Access Port Requirements
Port Direction
(SAL --- ANN)
TELNET/TCP/Telnet-23 --- >
SSH/TCP/SSH-22 ----->
Inventory Collection
supported by SAL?
Auto-Onboarding
supported?
Future version
No
SAL Gateway R1.8

or later w/ Model
V2 & V3 or later
required
Yes with Model

V3 and later
Additional Comments
SAL Model Name
ACME_Net_Net
Assigned SECODES
Current Model
Version
NN38A
NN38B
NN45A
NN45B
2.0.0.0
AES
AESSW
VAES
AESSP
1.1.0.1 , 2.0.0.3
& 3.0.0.2
Alarming Port Direction (SAL ---- ANN)

SNMP/UDP/AlarmTraps-162 <--->
Application Enablement
Services (AES)
Release 3 and Yes - See

later.
"Additional
Comments"
Port Direction (SAL --- AES)

HTTP(S)/WebGUIAccess-8443,443 --->
SSH/Secure Access-22 --->
Alarming Port Direction (SAL ---- AES)
Secure Access Link Supported Products September 20, 2012
- Customer should NOT enable alarming before AES R4.2.2,

AES
regardless of using SAL or not.
- To support alarm handling, standalone SAL Gateway R1.8 or
later is required.
- For 1.8 Salgw release used Model Version 2.0.0.3.
Page 1 of 11
Supported Products
Avaya Aura Conferencing

Standard
Supported Product
Versions
Release 6
Alarm handling?
No - Alarms
managed by
System
Manager
Port Direction (SAL --- AC)

HTTPS/WebGUIAccess-443 --->
CRSAPP/TCP/NSM-5405 <--->
RDP/TCP/RemoteDeskTop-3389 --->
supported by SAL?
Future version
Auto-Onboarding
supported?
Not Applicable
Additional Comments
- Each application/server of Aura Conferencing (Client

Registration Server, Conference Bridge, Avaya Web
Conferencing, Web Portal) must be added to the SAL
Gateway as individual devices.
SAL Model Name
Aura_Conferencing
- "VSP" and "VSPU" models are also needed when running on

System Platform.
Assigned SECODES
Current Model
Version
ACSCRV
ACSWCV
ACSCBV
ACSWPV
AACAS
AACMS
AACCO
AACWC
ACCMA
ACCMM
ACCMMO
ACCMMW
ACCSCE
ACCT
ACCNCC
2.0.0.2
Avaya Aura Contact Center
Release 6.X
No
Port Direction (SAL --- ACC)

HTTPS/WebGUIAccess-443 --- >
RDP/TCP/RemoteDeskTop-3389 ->
Not applicable
No
Aura_Contact_Center
Avaya Aura Experience Portal
6_0 n 6_x
Yes
Port Direction (SAL --- EP)

HTTPS/TCP/WebGUIAccess-443 -->
RDP/TCP/RemoteDeskTop-3389 ---->
SSH/TCP/Secure Access-22 --->
FTP/TCP/FileTransfer-21 <--->
No
No
Experience_Portal
EPMSWB
EPMPLS
EPMPLB
EPMSWS
EPICR
EPSLB
EPSSLS
EPMSLB
2.0.0.1
Future version
No
- "VSP" and "VSPU" models are also needed if Aura

Messaging is managed by a SAL Gateway running on System
Platform.
Aura_Messaging
VAAM
2.0.0.5 & 3001
No
No
- "VSP" and "VSPU" models are also needed if Avaya Aura

Session Border Controller is managed by a SAL Gateway
running on System Platform.
Session_Border_Controller
AASBC
SBCMSL
SBCEL
2.0.0.2
No
No
Once connected to an Branch Gateway B5800 device via SAL, Branch_Gateway

you can invoke any Management tools as applicable, except
System Monitor and remote upgrade via Manager as (UDP)
protocol is not supported by SAL. Therefore, when
performing System Monitor tracing or Control unit upgrades
(bin file firmware) remotely, you must access a server on
which System Monitor/IPO Manager can be invoked locally.
B5800
ABGVM
2.0.0.2
No
Not applicable
ACCCM
2.0.0.0
Alarming Port Direction (SAL ---- EP)

Avaya Aura Messaging
Release 6
Yes - INADS
Port Direction (SAL --- AM)

HTTPS/WebGUIAccess-443 -->
SSH/Secure Access-22 -->
LDAP/TCP/LDAP-389 --->
2.0.0.0
##
Alarming Port Direction (SAL ---- AM)

SNMP/AlarmTraps-162 <--->
Avaya Aura Session Border
Controller
Release 6
Yes - SNMP
Trap
Port Direction
(SAL --- SBC)
HTTPS/TCP/WebGuiAccess-443 ---->
Alarming Port Direction (SAL ---- SBC)
Avaya Branch Gateway B5800
Release 6.1
Yes - SNMP
Trap
Avaya Contact Center Control

Manager
Release 6.0
No
Port Direction
(SAL --- B5800)
HTTPS/TCP/WebGuiAccess-443 ---->
RDP/TCP/RemoteDeskTop--3389 ---->
UDP/Sysmon-50794,50791,69 -->
UDP/Sysmon53248-53251,48620-48623,
5032-5035 <----UDP/NetViewer- 53252--53255, 48624-48627,5036-5039, <-----SSH/TCP/SSH-22 ----->
IPO/TCP/IPOClient--50813,50812,50808,
50805,50804,50802,50814,50794 --->
Alarming Port Direction (SAL ---- B5800)
Port Direction (SAL ---- CCCM)

Contact_Center_Control_Mgr
Page 2 of 11
Supported Products
Supported Product
Versions
Alarm handling?
supported by SAL?
Auto-Onboarding
supported?
Additional Comments
SAL Model Name
Assigned SECODES
Current Model
Version
Avaya Integrated Management Release 3 and No

(AIM)
later
Port Direction (SAL --- AIM)

Future version
Not applicable
With Avaya Fault and Performance Manager (FPM) R6, SAL

AIM
and FPM are interoperable in 2 ways:
1. FPM as a managed device of SAL so remote engineer can
remote access FPM
2. FPM as a NMS destination for SAL and SAL as an element
(voice adjunct) in FPM, so SAL can forward alarms from other
SAL managed devices to FPM. Please consult the
Administering Avaya Fault and Performance Manager
(https://support.avaya.com/css/P8/documents/100089484)
for configuration details.
VMM
FPM
NMC
DOCMV1
AIM
1.1.1.2 &
2.0.0.2
Avaya IQ
Release 4.2
and later
Yes
Port Direction (SAL --- AIQ)

HTTPS/IQOAM- 28443,28080---->
HTTPS/IQReporting 18443 ---->
HTTP/Apache- 80 --->
SRTD/SecRealTimeDashBorad- 38443 -->
Alarming Port Direction (SAL ---- AIQ)
SAL Gateway R1.8

or later w/ Model
2.x.x.x or later
required
No
IQ does not resolve alarms using automated services tools

IQ
(expert systems) as some other products do. IQ alarms could
be sent to a customers Network Management System (NMS).
See PSN002739.
IQSW
IQTEH
IQTAD
IQTDH
IQTF
IQTD
IQTE
IQSRVS
1.2.0.1 &
2.0.0.7
Avaya One-X Agent Central

Management
Release 2
No - Alarms
managed by
System
Manager
Port Direction (SAL --- CentralManagment)

HTTPS/TCP/WebGuiAccess-8443,443,8080,8309,8643 --->
SSH/TCP/SSH-22 --->
Future version
Not applicable
CentralManagement
CMGTPS
CMGT
1.1.1.2 &
2.0.0.2
Yes -Native
SNMP
Port Direction (SAL ---- 1XCES)

HTTPS/TCP/WebAccess-9443 -->
SSH/TCP/SSH-22 --->
No
No
OneXClient_Enablement_Services
1XPRES
1XCES
2.0.0.1
Avaya one-X Client Enablement Release 6.1

Services
Alarming Port Direction (SAL ---- 1XCES)

Avaya One-X Mobile
Release 5.2
No
Port Direction (SAL ---- 1XM)

HTTPS/TCP/GuiAcc-443,8443,8080 -->
SSH/TCP/SSH-22 --->
Future version
Not applicable
OneXMobile
1XMOBL
1.1.1.1 &
2.0.0.2
Avaya one-X Portal
Release 5.2
No
Port Direction (SAL ---- 1XP)

HTTPS/TCP/WebGuiAccess-80,443,8443,9443,9080 ---->
SSH/TCP/SSH-22 --->
Future version
Not Applicable
OneXPortal
1XPRTL
1.1.1.1 &
2.0.0.3
Avaya Video Conferencing

Solutions
Avaya 1030,
Avaya 1040
and Avaya
1050
No
Port Direction
(SAL --- VC)
HTTPS/TCP/Webccess-443 --->
Future version
Not Applicable
Video_Conferencing
AV1030
AV1040
AV1050
2.0.0.0
Remote access to the CODEC devices only.
Page 3 of 11
Supported Products
Avaya Web Alive
Supported Product
Versions
2.5
Alarm handling?
supported by SAL?
Auto-Onboarding
supported?
Additional Comments
SAL Model Name
Assigned SECODES
Current Model
Version
No
Port Direction
(SAL --- WA)
HTTPS/TCP/WebGUIAccess-443 --->
SpatialVPort/UDP/EndUserClient- 2379<--->
SpatialVPort/TCP/UserClient- 21002<--->
UnrealPt/UDP/UserClientSprt-7878 <--->
No
No
Web_Alive
WACPD
2.0.0.2
Avaya Workforce Optimization Release 10

and later.
No
Port Direction
(SAL --- AWO)
HTTPS/TCP/WebGuiAcc-8080,443 --->
Telnet/TCP/Access/23 --->
FTP/TCP/File Transfer/21 --->
SSH/TCP/SSH-22 --->
Future version
Not Applicable
Avaya_Workforce_Optimization
ACR
WFOP
QM
WFMP
2.0.0.4
Call Management System

(CMS)
Yes INADS Port Direction (SAL --- CMS)

NIU Required - SSH/TCP/SSH-22 --->
See Additional TELNET/TCP/Telnet-23 -->
Comments.
Alarming Port Direction (SAL ---- NIU)
SAL Gateway R1.8

or later w/ Model
2.x.x.x or later
required
No
CMS
CMS
CMSCVA
CMSEXP
CMSLX
1.1.0.0 &
2.0.0.3
No - Alarms
Port Direction (SAL ---- CMB)
continue to be HTTPS/TCP/WebGuiAccess-443 ---->
forwarded by SSH/TCP/SSH-22 --->
SEAC
Future version
Not Applicable
Secodes DOCMV1 and DOCRB are supported by SAL Models

"AIM" and "SIP_Server" respectively.
CM_Branch
2.0.0.1
Future Version
No
- "VSP" and "VSPU" models are also needed if CM Messaging CM_Messaging

is managed by a SAL Gateway running on System Platform.
DOAES
DOFS
DOSES
DOI120
DOI40
DOCRA
DOVM
DOG450
CMM
VCMM
S88VM
SAL Gateway R1.8

or later w/ Model
2.x.x.x or later
required
Yes with Model

V3 and later
- Platforms that are using SAMP (S84xx & S85xx) should not CM_Media_Server
replace the modem with SAL Gateway as the "server down"
alarm cannot be forwarded to Avaya without a modem. This
is addressed by the heartbeat monitoring capability in CM
Release 5.2.1 S8800 server and SAL Gateway 1.8.
Release 11
and later
Communication Manager
Branch
All Releases
Communication Manager
Messaging, Embedded and
Standalone
Releases 5 and Yes

6
Port Direction (SAL --- CMM)

HTTPS/TCP/WebGUIAccess-443 -->
SSH/TCP/Secure Access-22 -->
LDAP/TCP/LDAP-636 -->
- "Network Interface Unit" model need to be registered with

SAL Gateway also in order to process alarms from the CMS.
TCP Port 5108 for CMS needs to be open between the NIU
and the SALGW. The NIU will also need to be added as a
Managed Element in the SAL Gateway in order for alarm
handling to work correctly.
1.0.0.1 &
2.0.0.1
Alarming Port Direction (SAL ---- CMM)

Communication Manager on
S8300, S8400, S8500, S8700series, etc. Servers
Release 2 and Yes INADS

later
Port Direction (SAL --- CM)

HTTPS/TCP/WebGUIAccess-443 --->
SSH/TCP/ Secure Access-22 --->
DSAT/SystemAccessTerminal-5022 --->
DSAT/SystemAccessTerminal-5023 --->
Alarming Port Direction (SAL ---- CM)
SNMP/AlarmTraps-162 <--->
- "VSP" and "VSPU" models are also needed

if Communication Manager is managed by a SAL Gateway
running on System Platform.
S8500 S85IPA S8700 700MS S87IPA S87IPB

1.1.0.2 2.1.0.3,
S87MCA S87MCB S8710M S8710P
& 3.0.0.5
S87M1A S87M1B G350MS S8300 S8500B S85IPB
S87B1P S87P1A S87P1B S8400 S84IPA S8720A
8720B S85IPC S8500C S8300B S8710 S8720 s8730
s8730a s8730b S85P1A S8400B S84IPB SES83 VCM
S88IPA S88IPA S8800 S88IPB
- The SAL Gateway R1.8 provides operational status

monitoring of Communication Manager 5.2.1 on S8800
servers. These servers generate a periodic SNMP heartbeat.
To support "Monitor Health" capability, (1) turn on SNMP
Heartbeat in Communication Manager and (2) select
"Communication Manager with Heartbeat Enabled" as the
product when adding Communication Manager 5.2.1 on
S8800 server to SAL Gateway.
- Communication Manager R6 does not support SNMP
Heartbeat.
Page 4 of 11
Supported Products
Supported Product
Versions
Alarm handling?
supported by SAL?
Auto-Onboarding
supported?
- The SAL Gateway R1.8 provides operational status

monitoring of Communication Manager 5.2.1 on S8800
servers. These servers generate a periodic SNMP heartbeat.
To support "Monitor Health" capability, (1) turn on SNMP
Heartbeat in Communication Manager and (2) select
"Communication Manager with Heartbeat Enabled" as the
product when adding Communication
Manager 5.2.1 on
Additional Comments
S8800 server to SAL Gateway.
SAL Model Name
Assigned SECODES
Current Model
Version
- Communication Manager R6 does not support SNMP

Heartbeat.
Contact Center Express (CCE)
Release 3 and No
later
Port Direction (SAL --- CCE)

Not feasible - No
SNMP Support
Not applicable
Contact_Center_Express
CCEIVR
CCEMMA
CCEVA
2.0.0.2
Coomunication Server 1000

CS1K R7.5
(CS1K)
*Call Server
*SIP Line Gateway
*Terminal Proxy Server
*Personal Directory, Callers List
and Redial List
*Media Application Server
*SIP/H.323 Signaling Gateway
*Signaling Server Base
Manager
*Unified Communication
Manager (UCM)
*Element Manager
*IM/Presence Server
*Telephony Manager
*Network Routing Service
Manager
*Subscriber Manager
No
Port Direction
(SAL --- CS1K)
HTTPS/TCP/WebGuiAcc-80,8443 --->
SSH,SCP,SFTP,/TCP/-22 --->
TELNET/TCP/Telnet-23 --- >
RLOGIN/TCP/Rlogin-513 --->
FTP/TCP/FileTransfer-21 --->
No
No
Additional Comments
Communication_Server
For UCM running on a different server than an
EM/NRSM/MAS, a Reverse Proxy Server needs to be installed
and configured on the server running UCM. For the installer
and documentation, please go to support.avaya.com, login,
then Downloads and Documents -> Communication Server
1000E -> Release 7.5. Video demonstration is available on
Avaya
Mentorhttp://www.youtube.com/user/AvayaMentor?feature
=watch search term Reverse Proxy.
CS1KCPPM CS1KCPMG CS1KCPPIV CS1KCPDC

CS1KCOTS1 CS1KCOTS2 CS1KCOTS3 CS1KMGCX
CS1KMIRAN CS1KMICB CS1KMIPCD CS1KMICA
CS1KMC32 CS1KMGC CS1KMGPRI CS1KMIVS
CS1KTS
2.0.0.1
G860 Media Gateway
Release 2
Yes - SNMP
Trap
Port Direction (SAL --- G860)

HTTPS/TCP/WebGUIAccess-80,443 --->
RMI/TCP/EMSClient- 21044,21616,21615,22001 <-->
TELNET/TCP/Telnet-23 -->
SSH/TCP/SSH-22 ---->
Alarming Port Direction (SAL ---- G860)
Future version
No
Customers running G860 R1 should upgrade to G860 R2 in

order to be managed by SAL.
G860
G86EMS G86EMS G86SCA G86MGT G86SCB

G86SCG G86SCG G86TPA G86SPS G86SCR
G86TPR G86HDA G86HDR
2.0.0.3
IA770 Messaging Application
With CM
Release 2 &
later
Yes INADS IA770 Alarms

continue to be
forwarded to
CM.
Port Direction (SAL --- IA77)

HTTPS/TCP/WebGUIAccess- 443 -->
SSH/TCP/SSH-22 --->
Future version
No
Intuity_Audix_Lx
1.1.0.0 &
2.0.0.1
Future version
No
G700MA
G250MV
G350MV
G700MV
S84MV
LXAUDR
G450MV
G430MV
S85VM
TENPBX
TENI55
Alarming Port Direction (SAL ---- IA77)

Integral Enterprise (aka I55)
Version L06
Yes - SNMP
Trap
SSH-22; ISM Client20,21,22,23,80,111,123,139,161,443,2049,5801,5802,6022,6080,6551

Through 6555,9001,9002,9003,64000 Through 64011
All versions L05 and L04 should be upgraded to L06 in order

to be supported by SAL.
Integral_Enterprise
2.0.0.0
Page 5 of 11
Supported Products
Supported Product
Versions
Alarm handling?
supported by SAL?
Auto-Onboarding
supported?
Integral Solution Applications: All Releases

*Avaya easy Management.
*Avaya Voice Priority
Processor.
*Branchen Communications
Server.
*Central Data Management.
*Com4Tel 2.
*ConneCTIon.
*Contact Center TIVA.
*Customer Interaction Express.
*DialIt.
*Fehler- und Performance
Managementl.
*HotCom PMS.
*IDS Win GebuehrendatenManagement.
* See Additional Comments for
Rest of Application List
No
Port Direction (SAL --- IA)

Future version
Not Applicable
Interaction Center
Release 6.1.5
& later
No
Port Direction (SAL --- IC)

HTTPS/TCP/WebGUIAccess- 443 --->
TELNET/TCP/Telnet-23 --->
Future version
Not applicable
Interactive Response (IR)
Release 2 and Yes INADS later

NIU Required
Port Direction (SAL --- IR)

SSH/TCP/SSH-22 --->
SAL Gateway R1.8

or later w/ Model
2.x.x.x or later
required
No
Future version
No
Future version
Future Version
Additional Comments
*Integral easy Management

*Integral Message Server
*Internet Access Manager*
*MAS Accounting
*MedCom Medial
*Mobility Manager
*Multifunctional Alarming- and Communication-Server
*PUMA
*Qserver TAPI
*Satin
*SeCom
*Snapware
*TIMA
*Thetacom
*Unified Messaging System C300
*Unified Messaging System C3000
*VoIPManager
*Business Call Center
*Enterprise Directory System
SAL Model Name
Assigned SECODES
Current Model
Version
Integral_Applications
TENOVS
TENBCC
2.0.0.0
Interaction_Center
IC ICDEV ICEC ICECON ICOA ICVC

ICWC
1.2.0.0 &
2.0.0.1
- Also requires "Network Interface Unit" model.
InteractiveResponse
AIR
AIRSW
AIRO
1.1.0.0 &
2.0.0.1
- Also requires "Network Interface Unit" model.
Intuity_Audix
INAUD
1.1.0.1 &
2.0.0.1
No
Intuity_Audix_Lx
G700MA G250MV G350MV G700MV

S84MV LXAUDR G450MV G430MV
S85VM
1.1.0.0 &
2.0.0.1
Not Applicable
IPDECT
DECTAS
2.0.0.2
Alarming Port Direction (SAL ---- IR)

Intuity Audix
Releases 4.4
and 5.1
Yes INADS NIU Required
Port Direction (SAL --- IA)

SSH/TCP/SSH-22 --->
Alarming Port Direction (SAL ---- IA)
Intuity Audix LX
IP DECT Solution
Release 2
Release 4
Yes INADS Intuity Audix LX

only and "Ping
Surround"
must be set on
Configure
Alarms menu.
Port Direction (SAL --- IALX)

SSH/TCP/SSH-22 --->
No
Port Direction
(SAL --- IPD)
HTTPS/TCP/WebGUIAccess-80,443 --->
LDAP/TCP/LDAP-636 -->
Alarming Port Direction (SAL ---- IALX)

Page 6 of 11
Supported Products
Supported Product
Versions
Alarm handling?
IP Office
Release 6 and Yes -Native

later
SNMP
Media Gateway, e.g. G250,

G350, G430, G450, G700, etc.
All Releases
No - Alarms
continue to be
forwarded to
CM
Media Services
All releases
Mediant 3000
Release 1.0
supported by SAL?
Auto-Onboarding
supported?
SAL Model Name
Assigned SECODES
Current Model
Version
No
Once connected to an IP Office device via SAL, you can invoke IP_Office
any IPO Management tools as applicable, except System
Monitor and remote upgrade via Manager as (UDP) protocol
is not supported by SAL. Therefore, when performing System
Monitor tracing or IPO Control unit upgrades (bin file
firmware) remotely, you must access a server on which
System Monitor/IPO Manager can be invoked locally.
IP403 IP406 IP412 IPCCC IPCRM IPOHP

VMPRO IP500 IP5XV2 IPOCCR IPO1XP
2.0.0.3
Port Direction (SAL ---- CMG)

HTTPS/TCP/WebGuiAccess- 443 ---->
SSH/TCP/SSH-22 --->
SAL Gateway R1.8

or later w/ Model
2.x.x.x or later
required
Not Applicable
Gateway G700 needs to be registered at the time of onboarding.
G700 G700MG G350 G250AG G250BG G250BS

G250DS G250B4 G250D4 G250DG
G250T4 G350P4 JNTGM G250TG G450
G430
1.1.0.1 &
2.1.0.4
No - Alarms
through CM
Port Direction (SAL --- Cobar)

SSH/TCP/SSH-22 --->
Future version
Not Applicable
- "VSP" and "VSPU" models are also needed if Media Services Cobar
is managed by a SAL Gateway running on System Platform.
VCOB
1.1.0.0 &
2.0.0.0
Yes -Native
SNMP
Port Direction (SAL --- MEDIANT)

No
No
Only the active TP board will generate SNMP traps and only
Module 1 (M3KTP) & Module 3 (M3KHD) requires remote
access. As a result, Platform/Chassis (M3KP) and
Synchronization and Alarming module (M3KSA) do not need
to be added to the SAL Gateway as a managed device.
Mediant
M3KTP
M3KHD
2.0.0.0
Future version
No
Meeting_Exchange_Server
S6200
MXU41X
MX5S62
MX50HW
MXHW68
mx51hw
MX5S68
MX51SW
1.1.0.2 &
2.0.0.5
Client_Reservation_Server
CRSWEB
CRSFWP
1.1.0.0 &
2.0.0.1
Alarming Port Direction (SAL ---- IPO)
Alarming Port Direction (SAL ---- MEDIANT)

Meeting Exchange Server (MX) Release 4,5,6
Additional Comments
Future version
Port Direction
(SAL --- IPO)
HTTPS/TCP/WebGuiAccess-80,443 ---->
UDP/Sysmon-50794,50791,69 --->
UDP/Sysmon53248-53251,48620-48623,
5032-5035 <----UDP/NetViewer- 53252--53255, 48624-48627,5036-5039, <-----SSH/TCP/SSH-22 ----->
IPO/TCP/IPOClient--50813,50812,50808,
50805,50804,50802,50814,50794 --->
Yes - R5 and
Higher
Port Direction (SAL ---- MES)

CRSAPP/TCP/NSM-5405 <-->
SSH/TCP/SSH-22 --->
CM_Media_Gateway
Alarming Port Direction (SAL ---- MES)

Meeting Exchange Client

Reservation Server (CRS)
Release 4 and No
5
Port Direction (SAL ---- CRS)

CRSAPP/TCP/NSM-5405 <--->
SSH/TCP/SSH-22 --->
Future version
Not applicable
Message Networking
Release 3.0
Yes
and later, SP1
is
recommended
for R5.2
Port Direction (SAL ---- MMN)

SSH/TCP/SSH-22 --->
Future version
No
To work with SAL Gateway, MN alarming should follow the

MM_Message_Networking
configuration setup described for SSG but use the SAL
Gateway ip address as the destination. When MN R5.2 SP1 is
available (target June 2010), embedded SPIRIT/SAL agent in
MN R5.2 could be disabled. Applying SP1 will not change the
current alarming and NMS setup.
AMNR
1.1.0.0 &
2.0.0.1
Release 3.0
and later,
Release 4.0
requires SP4
or later,
Release 5.2
requires SP6
or later
Port Direction (SAL ---- MAS)

SAL Gateway R1.8

or later w/ Model
2.x.x.x or later
required
No
- "VSP" and "VSPU" models are also needed if Message

Application Server is managed by a SAL Gateway running on
System Platform.
MAS Server 5.2 requires SP6 or later in order to fix MAS
alarm floods to Avaya Core Server.
AMMAS
MMDO
MMEX
MMEXSV
MMDOSV
SMMAS
VMMAS
1.1.0.1 &
2.0.0.1
Modular Messaging (MM)

Message Application Server
(MAS)
Yes
Alarming Port Direction (SAL ---- MMN)

Alarming Port Direction (SAL ---- MAS)

MM_Application_Server
Page 7 of 11
Supported Products
Supported Product
Versions
Modular Messaging (MM)

Release 3.0
Message Storage Server (MSS) and later
Alarm handling?
Yes INADS
Port Direction (SAL --- MSS)

supported by SAL?
Auto-Onboarding
supported?
SAL Gateway R1.8

or later w/ Model
2.x.x.x or later
required
Yes with Model

V3 and later
- "VSP" and "VSPU" models are also needed if Message

Storage Server is managed by a SAL Gateway running on
System Platform.
Not Applicable
Not applicable
If using SAL Gateway R2.0, please see

NIU
PSN003068u,https://support.avaya.com/css/P8/documents/
100113994.
Additional Comments
SAL Model Name
MM_Storage_Server
Assigned SECODES
Current Model
Version
AMMSSR
SMMSSR
VMMSSR
1.2.0.0 &
3.0.0.0
NIU
APCLTX
1.1.0.0 &
2.0.0.1
Alarming Port Direction (SAL ---- MSS)

Network Interface Unit

(Lantronix SCS400 and
Lantronix SLC-8)
Yes/ NIU
converts
product alarms
to INADS
Alarms
Port Direction (SAL --- NIU)

SSH/TCP/SSH-22 --->
Alarming Port Direction (SAL ---- NIU)
NIU/UDP/NIUAlarms- 5107,5108 <-->
NICE
Release 8.9 & No

later
Port Direction (SAL ---- NICE)

SSH/TCP/SSH-22 --->
Not feasible - No
SNMP Support
Not applicable
NICE
NCLOG
NCLS
2.0.0.0
NICE Perform
Release 3 &
later
No
Port Direction (SAL ---- NICEP)

SSH/TCP/SSH-22 --->
Not feasible - No
SNMP Support
Not applicable
NICE
NCLOG
NCLS
2.0.0.0
Octel 200 Message Server
Release 4.1.x
Yes SNMP Trap

- LAN board
and
LANPatch09
required
Port Direction (SAL --- OCTEL)

Future version
No
OCTEL
SER200
2.0.0.1
Yes
Port Direction
(SAL --- OSM)
HTTPS/TCP/WebGuiAccess- 4511,443 ---->
No
No
OIS_SLA_Mon
SLAMON
3.0.0.0
OIS - SAL Mon Server
R1.0
Alarming Port Direction (SAL ---- OCTEL)

Alarming Port Direction (SAL ---- OSM)

OIS SAL Mon is not supported on System Platform due to its

high RAM requirments.
OIS SAL Mon Servere model is support from SAL 2.1 GW
onwards.
Implementation guide is documented under Compas ID
150422.
OSPC
Releases 2.5.1 No
Avaya One-X Attendant
and 3
(formerly OSPC)
Predictive Dialing System (PDS) Release 12
No
Port Direction (SAL ---- OSPC)

Future version
Not applicable
OSPC
1XATTD
2.0.0.3
Port Direction
(SAL --- PDS)
Future version
Not applicable
Predictive_Dialing_System
PDSYS
PDS
1.1.0.0 &
2.0.0.1
Presence Services
Port Direction
(SAL --- PresenceSvr)
HTTPS/TCP/WebGuiAccess- 443,7300,8009,8080,8443 ---->
Future version
No
IPS
PSCMGT
VPSB
1.1.0.1 &
2.0.0.2
Release
5.2 and later
Yes with model

version 2.0.0.2
& later, PS R6.1
or later
required (See
Addiitonal
Comments)
Alarming Port Direction (SAL ---- PS)

- Device with secode "SALIPS" does not need to be added to Presence_Server

the SAL Gateway as a managed element.
- For Presence Services releases before 6.1, only remote
access is supported by SAL Gateway. Alarms are managed by
System Manager. Starting Presence Services release 6.1,
alarms are forwarded to Avaya via SAL Gateway instead of
System Manager. Model version 2.0.0.2 is required.
- You may need to re-configure the Presence Services device
on the SAL Gateway if upgraded Presence Services from R6.0
or prior.
Page 8 of 11
Presence Services
Supported Products
Proactive Contact
Release
5.2 and later
Supported Product
Versions
Yes with model

version 2.0.0.2
& later, PS R6.1
or later
required (See
Alarm handling?
Addiitonal
Comments)
Release 4 & 5 Yes
Port Direction
(SAL --- PresenceSvr)
HTTPS/TCP/WebGuiAccess- 443,7300,8009,8080,8443 ---->
Alarming Port DirectionRemote
(SAL ---PS)
Access Port Requirements
Port Direction
(SAL --- PCC)
Future version
supported by SAL?
No
Auto-Onboarding
supported?
Future version
No
Yes INADS &

Port Direction (SAL --- POM)
native SNMP - HTTP/TCP/WebGUIAcc- 443 --->
Alarming
SSH/TCP/SecureAcc-22 --->
through VPMS
Alarming Port Direction (SAL ---- POM)
SNMP/AlarmTraps-162<--->
SAL Gateway R1.8

or later w/ Model
2.x.x.x or later
required
Planned
- Device with secode "SALIPS" does not need to be added to Presence_Server

the SAL Gateway as a managed element.
- For Presence Services releases before 6.1, only remote
access is supported by SAL Gateway. Alarms are managed by
System Manager. Starting Presence Services release 6.1,
Additional Comments
SAL Model Name
alarms are forwarded to
Avaya via SAL Gateway instead of
System Manager. Model version 2.0.0.2 is required.
- You may need to re-configure the Presence Services device
on the SAL Gateway if upgraded Presence Services from R6.0
or prior.
IPS
PSCMGT
VPSB
1.1.0.1 &
2.0.0.2
Product currently utilizes manual registration.

Proactive_Contact_Center
Alarm/Product ID need to be registered at the time of SAL onboarding.
PG230
APC
1.1.0.0 &
2.0.0.2
POM
1.1.0.0 &
3.1.0.0
Assigned SECODES
Current Model
Version
Alarming Port Direction (SAL ---- PCC)

Proactive Outreach Manager
Release 2
VoicePortal
Secure Access Link

Concentrator Core Server
Release 1.8
and later
No
Port Direction (SAL --- CSS)

HTTPS/TCP/WebGUIAccess-8443,443 -->
Future version
Not applicable
Core_SiteServer
SALCCS
2.0.0.3
Secure Access Link

Concentrator Remote Server
Release 1.8
and later
No
Port Direction
(SAL --- RSS)
HTTPS/TCP/WebGuiAcc-443,8443 ---->
Future version
Not applicable
Remote_SiteServer
SALCRS
2.0.0.2
Secure Access Link Policy

Server
Release 1.5
and later
No
Port Direction
(SAL --- PS)
HTTPS/TCP/WebGuiAccess- 443.8443---->
Future Version
Not Applicable
Policy_Server
SALPOL
2.0.0.1
Session Manager
All releases
Yes with model

version 2.0.0.2
& later, Session
Manager R6.1
Service Pack 1
or later
required (See
Addiitonal
Comments)
Port Direction
(SAL --- SM)
Future version
Not applicable
- "VSP" and "VSPU" models are also needed if Session

SessionMgr
Manager is managed by a SAL Gateway running on System
Platform.
- For Session Manager release before 6.1 Service Pack 1, only
remote access is supported by SAL Gateway. Alarms are
managed by System Manager. Device with secode "SALASM"
is not required to be added to the SAL Gateway as separate
managed element.
- For Session Manager release 6.1 Service Pack 1 and later,
alarms are forwarded to Avaya via SAL Gateway instead of
System Manager. "SALASM" must be added to the SAL
Gateway as separate managed element for alarming support.
- You may need to re-configure the Session Manager device
on the SAL Gateway if upgraded Session Manager from R6.0
or prior.
ASM
SALASM
VASM
1.1.0.0 &
2.0.0.6
Yes SNMP
Port Direction
(SAL --- SIPSvr)
SAL Gateway R1.8

or later w/ Model
2.x.x.x or later
required
Yes with Model

V3 and later
- "VSP" and "VSPU" models are also needed if SIP Enablement SIP_Server
Services is managed by a SAL Gateway running on System
Platform.
SESV3A SESV3B SESV1A SESV1B SESV2A

SESV2B DOCRB SESV4A SESV4B
VSES SESV5A SESV5B
1.1.0.1 &
3.0.0.0
SIP Enablement Services (SES)
Release 5
Alarming Port Direction (SAL ---- SM)

Alarming Port Direction (SAL ---- SIPSvr)

Page 9 of 11
Supported Products
System Manager
Supported Product
Versions
Alarm handling?
Release 1 and Yes with model

later
version 2.0.0.2
& later, System
Manager R6.1
or later
required (See
Addiitonal
Comments)
Port Direction
(SAL --- SysMgr)
supported by SAL?
Future version
Auto-Onboarding
supported?
No
Alarming Port Direction (SAL ---- SysMgr)

Additional Comments
SAL Model Name
- For System Manager release before 6.1, only remote access SystemMgr
is supported by SAL Gateway. Alarms are managed by
System Manager. Devices with secodes "SALSM" or
"SMELEM" are not required to be added to the SAL Gateway
as separate managed elements.
Assigned SECODES
Current Model
Version
SM
SALSM
SMELEM
1.1.0.0 &
2.0.0.5
VSP
1.1.0.0 &
2.0.0.0
VSPU
1.1.1.7 &
2.1.1.7
VUS
1.1.0.0 &
2.0.0.1
VPMSLB
VPMSLS
VPMPLB
VPMPLS
VPSSLB
VPSSLS
1.1.0.0 &
3.1.0.1
- For System Manager release 6.1 and later, alarms are

forwarded to Avaya via SAL Gateway instead of System
Manager. "SALSM" and "SMELEM" must be added to the SAL
Gateway as separate managed elements for alarming
support.
- You may need to re-configure the System Manager device
on the SAL Gateway if upgraded System Manager from R6.0
or prior.
System Platform Base

Operating System Domain
(Domain 0)
Releases 1 and Yes

6
Port Direction
(SAL --- VSP)
Future version
No
Alarming Port Direction (SAL ---- VSP)

System Platform Console

Domain
Releases 1 and Yes

6
Port Direction
(SAL --- VSPU)
HTTPS/TCP/WebGUIAcc-8443,7443,52233,443--->
- As a result, redundant SAL Gateway is not feasible
Future version
No
Alarming Port Direction (SAL ---- VSPU)

Utility Server on System

Platform
Release 1 and No
later
Voice Portal Management

System Server (VPMS).
Media Processing Platform
(MPP) Server.
Proactive Outreach Manager.
Release 4 and
later (VP)
Release 2
(POM)
Port Direction
(SAL --- VUS)
HTTPS/TCP/WebGUIAccess-443, 8443 --->
Yes INADS &

Port Direction (SAL --- VP)
native SNMP - HTTP/TCP/WebGUIAcc- 443 --->
Alarming
SSH/TCP/SecureAcc-22 --->
through VPMS
Alarming Port Direction (SAL ---- VP)
- System Platform R1 and R6 are deployed with a SAL

VSP
Gateway R1.5 and R1.8 respectively. They must be managed
by the SAL Gateway deployed with it.
- System Platform R1 and R6 are deployed with a SAL

VSPU
Gateway R1.5 and R1.8 respectively. They must be managed
by the SAL Gateway deployed with it.
- As a result, redundant SAL Gateway is not feasible.
- PSN# PSN002944u
Problem: Product alarm forwarding from the integrated SAL
Gateway on System Platform R6 fails.
Resolution:
Request and apply System Platform patch 6.0.0.1.11.
This problem will be fixed in a System Platform Service Pack
targeted for availability August 9, 2010.
Future version
Not applicable
SAL Gateway R1.8

or later w/ Model
2.x.x.x or later
required
Yes with Model

V3 and later
VUS
Voice Portal Model Version 3.1.0.1 and higher should only be VoicePortal
used with SALGW GA Build "2.1.0.0.40" or newer release.
Page 10 of 11
Supported Products
Witness ContactStore.
Witness Quality.
Witness Workforce
Optimization.
Supported Product
Versions
Release 7
Alarm handling?
No
Port Direction
(SAL --- Witness)
TELNET/TCP/RemoteAcc-23 --->
HTTP/TCP/WebGUIAcc-8080 --->
HTTPS/WebGUIAcc-443 --->
FTP/TCP/FileTransfer-21 --->
supported by SAL?
Future version ContactStore. Not

feasible - Witness
Quality and
Workforce, No
SNMP Support.
Auto-Onboarding
supported?
Not applicable
Additional Comments
SAL Model Name
Witness
Assigned SECODES
CSCMQ
CSCME
WFM
WFO
Current Model
Version
2.0.0.0
Page 11 of 11

Sal Supported Products

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Sal Supported Products

Caricato da

Copyright:

Formati disponibili

Secure Access Link Supported Products - September 20, 2012

SAL Production DNS / IP Destinations

Acme Packet NetNet 3800 &

3800 & 4500

Remote Access Port Requirements

SAL Gateway R1.8

Yes with Model

SAL Model Name

Alarming Port Direction (SAL ---- ANN)

Release 3 and Yes - See

Port Direction (SAL --- AES)

Secure Access Link Supported Products September 20, 2012

- Customer should NOT enable alarming before AES R4.2.2,

Avaya Aura Conferencing

Remote Access Port Requirements

Port Direction (SAL --- AC)

- Each application/server of Aura Conferencing (Client

SAL Model Name

- "VSP" and "VSPU" models are also needed when running on

Avaya Aura Contact Center

Port Direction (SAL --- ACC)

Avaya Aura Experience Portal

Port Direction (SAL --- EP)

- "VSP" and "VSPU" models are also needed if Aura

2.0.0.5 & 3001

- "VSP" and "VSPU" models are also needed if Avaya Aura

Once connected to an Branch Gateway B5800 device via SAL, Branch_Gateway

Alarming Port Direction (SAL ---- EP)

Port Direction (SAL --- AM)

Alarming Port Direction (SAL ---- AM)

Avaya Branch Gateway B5800

Avaya Contact Center Control

Port Direction (SAL ---- CCCM)

Secure Access Link Supported Products September 20, 2012

Remote Access Port Requirements

SAL Model Name

Avaya Integrated Management Release 3 and No

Port Direction (SAL --- AIM)

With Avaya Fault and Performance Manager (FPM) R6, SAL

Port Direction (SAL --- AIQ)

SAL Gateway R1.8

IQ does not resolve alarms using automated services tools

Avaya One-X Agent Central

Port Direction (SAL --- CentralManagment)

Port Direction (SAL ---- 1XCES)

Avaya one-X Client Enablement Release 6.1

Alarming Port Direction (SAL ---- 1XCES)

Port Direction (SAL ---- 1XM)

Avaya one-X Portal

Port Direction (SAL ---- 1XP)

Avaya Video Conferencing

Secure Access Link Supported Products September 20, 2012

Remote access to the CODEC devices only.

Avaya Web Alive

Remote Access Port Requirements

SAL Model Name

Avaya Workforce Optimization Release 10

Call Management System

Yes INADS Port Direction (SAL --- CMS)

SAL Gateway R1.8

Secodes DOCMV1 and DOCRB are supported by SAL Models

- "VSP" and "VSPU" models are also needed if CM Messaging CM_Messaging

SAL Gateway R1.8

Yes with Model