---

Overview

Sheet2
Main
Selection
CS1000
CS1000Confirmation
HELP_0
SAL New Registration
SAL Migration Initiation
SAL Registration Return
UI List
AES
Aura CM Registrations
CM Confirmation Page
AAC
MSG
SBC
SMGR
CS
UCS
UCSME62
UME
ME
ME62
ME622
CMM-FM
MBT
MBT LSP Registrations
MM
PS
NOTE
UI Product Reg Confirm
SAL New Registration 2
SAL Alarm Registration_2
Main2
SAL_2
SSG Data
Sheet1
SAL Alarm Registration

---

Sheet 1: Sheet2

Excel 2007 Security Issue

If you are using MS Excel 2007 you may receive an error message when trying to click on buttons, etc.

In this case you should see the following warning at the top of the screen

To enable macros you should select the bottom option (Enable this content)

Once they are selected you should click on "OK" at the bottom right corner

---

Sheet 2: Main

Introduction Page

Version:

2.3.3

Updated:

2012. April 11.

This form is to be used for registering NEW or EXISTING Customer Devices to a SAL Gateway (Stand-Alone or System Platform/UI) 1) NEW Installations of Non-UI/System Platform products to be connected to a SAL Gateway 2) NEW Installation of Universal Install Products (i.e. Products deployed on System Platform with SAL embedded) 3) MIGRATE Existing Customer Products (i.e. Products already present in a Customers Environment) from a Modem/VPN connection to SAL

---

Sheet 3: Selection

	Selection Menu
							Short Description
								5	3

---

Sheet 4: CS1000

Communication Server 1000 (CS1000) Registration

In order for the UI Product to function properly, you must register the elements with Avaya prior to installing the software. Please fill in the White cells below: customer name and Sold to Number, enter your contact info. In the product selection area, please note the number of items you have in each category in the Quantity field. Avaya will provide unique identifiers (SEIDs) for each that you will input into as Managed Elements into your SAL gateway.

Customer Information

Customer Name:

Submit request to

Customer Sold To where CS1K is or will be installed

Customer SOLD TO where the SAL GW is to be installed (if new SAL Gateway)

the Registration Team

SEID of existing SAL Gateways (if using existing)

Contact Information (this is the requestor's contact info, so the SEIDS can be sent)

Contact Name:

Contact E-mail address:

Contact Telephone Number (primary)

Contact Telephone Number (secondary)

Are "In Country" Citizenships required for this Project?

YES

NO

System Configuration:

For your CS 1000 System at this site, please check which SERVERS exist.

Each will correspond with the T-LAN IP address for the system.

Description

Quantity

Call Processor Pentium IV

CS1KCPPIV

Common Processor Pentium Mobile

CS1KCPPM

Common Processor Media Gateway

CS1KCPMG

Common Processor Dual Core

CS1KCPDC

IBM X306m

CS1KCOTS1

HP DL320-G4

CS1KCOTS1

Dell R300

CS1KCOTS2

IBM X3550

CS1KCOTS2

HP DL360-G7

CS1KCOTS3

Dell R610

CS1KCOTS3

For your CS 1000 System at this site, please check which PERIPHERALS exist.

Each line corresponds with specific IP address as noted in the table.

Description

Quantity

Media Gateway Controller - T-LAN IP Address

CS1KMGC

Media Gateway Extended Peripheral Equipment Controller - T-LAN IP Address

CS1KCPPM

Voice Gateway Media Card (32 or 32S) - T-LAN IP Address

CS1KMC32

Meridian Integrated Conference Bridge - Single IP address

CS1KMICB

Meridian Integrated Recorded Announcements - Single IP address

CS1KMIRAN

Meridian Integrated Personal Call Directory - Single IP address

CS1KMIPCD

Meridian Integrated Call Assistant - Single IP address

CS1KMICA

Meridian Integrated Voice Services - Single IP address

CS1KMIVS

High Density Primary Rate Interface - Two solution elements per quantity will be generated; each HD PRI has two IP addresses (one for T-LAN, one for IP-Web)

CS1KMGPRI

---

Sheet 5: CS1000Confirmation

Communication Server 1000 (CS1000) Confirmation
	Once you have entered the SEIDs listed here as Managed Elements into your SAL gateway, please resubmit the form using the "Email to Registration Team" button. Avaya will then confirm connectivity and proper setup.
Customer Information
	Customer Name:			0						Submit request
	Customer SOLD TO where the SAL GW is to be installed (if new SAL Gateway)			0						to the Registration Team
	SEID of existing SAL Gateways (if using existing)			0
Contact Information (this is the requestor's contact info, so the SEIDS can be sent)
	Contact Name:			0
	Contact E-mail address:			0
	Contact Telephone Number (primary)			0
	Contact Telephone Number (secondary)			0
Are "In Country" Citizenships required for this Project?						0		YES
								NO
System Information:
Each SEID here will correspond with the T-LAN IP address for the system.
	Description				Quantity	SEID	SEID	SEID	SEID	SEID	SEID
	Call Processor Pentium IV			CS1KCPPIV	0
	Common Processor Pentium Mobile			CS1KCPPM	0
	Common Processor Media Gateway			CS1KCPMG	0
	Common Processor Dual Core			CS1KCPDC	0
	IBM X306m			CS1KCOTS1	0
	HP DL320-G4			CS1KCOTS1	0
	Dell R300			CS1KCOTS2	0
	IBM X3550			CS1KCOTS2	0
	HP DL360-G7			CS1KCOTS3	0
	Dell R610			CS1KCOTS3	0
Each SEID corresponds with specific IP address as noted in the table.
	Description					SEID	SEID	SEID	SEID	SEID	SEID
	Media Gateway Controller - T-LAN IP Address			CS1KMGC	0
	Media Gateway Extended Peripheral Equipment Controller - T-LAN IP Address			CS1KCPPM	0
	Voice Gateway Media Card (32 or 32S) - T-LAN IP Address			CS1KMC32	0
	Meridian Integrated Conference Bridge - Single IP address			CS1KMICB	0
	Meridian Integrated Recorded Announcements - Single IP address			CS1KMIRAN	0
	Meridian Integrated Personal Call Directory - Single IP address			CS1KMIPCD	0
	Meridian Integrated Call Assistant - Single IP address			CS1KMICA	0
	Meridian Integrated Voice Services - Single IP address			CS1KMIVS	0
	High Density Primary Rate Interface - Two solution elements per quantity will be generated; each HD PRI has two IP addresses (one for T-LAN, one for IP-Web)			CS1KMGPRI	0

---

Sheet 6: HELP_0

Registration Instructions
Detailed Instructions:
On-Boarding is performed in 2 stages: 1st) Prior to the implementation in order to register your product and provide you with the data needed to perform the implementation; and 2nd) After the implementation is completed in order to set up alarming and to test it.
There are 5 corresponding pages with links to them (above). Normally, only 2 will be used by you and is determined by your SAL implementation requirements. You will need to click on the appropriate link(s) - please read the instructions carefully to ensure you use the correct pages, otherwise, the wrong Products will be registered and impede your installation.
1) NEW Installations of Non-UI/System Platform products then connect to a SAL Gateway
Product Registration: Complete this page if you are installing new (Non-UI/SP) products and then administering them to a new SAL GW. You will need to provide the Sold-To #'s and the Solution elements for all new products being installed. The Registration team will register the new SAL GW and all new Products. They will send you, via e-mail, all of the Solution Element IDs and Product IDs needed for the installation.
2) NEW Installations of Universal Install Registration on System Platform
Product Registration: For the New installation of UI products - The Before Implementation Registration (referred to as Product Registration) is intended to Register those new UI products that are being installed. This activity needs to be done BEFORE the solution is installed in order to provide the Solution Element IDs and Product IDs which are needed at the time of installation. Please complete the Product Registration request and submit at least 3 weeks prior to the Installation date.
3) MIGRATE Existing Customer Products to SAL
Complete this page if you are migrating an existing customer, with existing installed products, to connect through the Secure Access Link (SAL) Gateway from an existing Modem/VPN connection. You will be asked for the Sold-To #'s for all sites which are migrating to SAL. The Registration team will research the Sold-to(s) and identify all Products/SEIDs that can be moved to the SAL Gateway.
When all necessary information is completed, please click the email button in the bottom or right side of the respective page to send the completed page to the Registration team (if you are prompted asking to allow automatic email creation, please click "YES"). You will be contacted via email when the requested activity has been completed. A copy of the e-mail you sent will be in your Outbox addressed to [e-mail].
1) MIGRATE Existing Customer Products to SAL
Complete this page if you are migrating an existing customer, with existing installed products, to connect through the Secure Access Link (SAL) Gateway from an existing Modem/VPN connection. You will be asked for the Sold-To #'s for all sites which are migrating to SAL. The Registration team will research the Sold-to(s) and identify all Products/SEIDs that can be moved to the SAL Gateway.
Alarm Registration: Complete this page AFTER you have finished migrating the customers existing devices to the SALGW, have had the appropriate firewall rules open, are accessible to the SALGW and are ready for Avaya to configure and test the alarming through the SAL Gateway.

---

Sheet 7: SAL New Registration

New SAL Gateway & Device Registrations Page
	For NEW SAL Gateway and Device installation
	This form is to be used to register a NEW Secure Access Link (SAL) Gateway (SAL GW). Instructions: You will need to provide to the Registration Team the customer name, the SOLD TO where the SAL GW is to be installed. Please fill out the White Boxes below with the needed information, providing the Sold TO needing to be newly registered for this customer. You will be contacted via email when the Registration Team completed the registration of the Gateway.
Customer Information:
	Customer Name :
	Sold To # where the SAL Gateway is to be installed:
	Existing SALGW SEID which should be used (if applicable)
	Redundant SALGW SEID (if applicable)
Contact Information (this is the requestors contact info, so the SE ID's can be sent):
	Name :
	Email Address :														NONE
	Telephone Number Primary :														US CITIZEN
	Telephone Number Secondary :														JAPANESE CITIZEN
	Are "In-Country" Citizenships required for this Project?
List all Solution Elements needing to be registered and the associated Sold TO for the SE's:
	SEIDs and Product IDs will be returned for all products listed below
	Sold TO	Select each Product being install for each FL (if multiple copies of the same Product need to be registered, list the Product multiple times)…..																		0
1		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
2		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
3		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
4		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
5		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
6		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
7		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
8		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
9		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
10		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
11		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
12		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
13		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
14		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
15		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
16		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
17		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
18		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
19		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
20		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
21		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
22		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
23		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
24		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
25		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
26		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
27		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
28		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
29		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
30		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0

---

Sheet 8: SAL Migration Initiation

SAL Migration Initiation Page

For products existing on a customer system that are needing to be identified for migration to SAL

This form is to be used to initiate the Migration of an existing customer product(s) to be rerouted to connect/alarm through Secure Access Link (SAL). You will need to provide to the Registration Team all of the Sold To's for this customer that are going to be migrated. Please fill out the White Boxes below with the needed information. You will be contacted via email when the Registration Team has completed their query of all Avaya products on those Sold To's. The email will provide you with all of the Solution Elements, Solution Element ID (SE ID) and Product ID that are on those systems. Once the appropriate products are added to the SAL Server, you will need to complete the SAL ALARM Registration page to notify the Registration team to setup/test the alarms through the SAL GW.

Customer Information:

Customer Name :

Sold To Number where SAL GW is registered:

SAL GW Solution Element ID:

CAVIOT Ticket Nr.

No

Are "In-Country" Citizenships required for this Project?

Yes

Contact Information (this is the requestors contact info, so the SE ID's can be sent):

NONE

US CITIZEN

Name

JAPANESE CITIZEN

Email Address

Telephone Number Primary

Telephone Number Secondary

List all Sold-To's for sites for this customer which need to be migrated to SAL:

Please use 8 digit Sold-To's!

Site 1

\,\

Site 2

Site 3

Site 4

Site 5

Site 6

Site 7

Site 8

Site 9

Site 10

Site 11

US CITIZEN

Site 12

JAPAN

Site 13

Site 14

Site 15

---

Sheet 9: SAL Registration Return

SAL Gateway and Device Registration Confirmation Page

This Form is the confirmation that the request has been completed and the SAL GW has been succesfully registered.

Customer Information

Customer Name:

0

CAVIOT Ticket Nr.

Avaya associate should enter the CAVIOT Number as a reference for this request

before sending it back to requestor!

SAL Gateway Registration Information

Sold to/FL #

SE ID

Product ID

0

List Devices that have been added to SALGW

NO

YES

Note to Requestor - List those devices here that have been added to the SALGW and are ready to be ALARM Registered.

NO

(You can copy this data from the FL Report that was sent to you from the Registration Team)

Sold TO

Product (SE) Code

Model

Solution Element ID

Product ID

Remote Access

Transport Alarms

Administered in SALGW [Y/N]

---

Sheet 10: UI List

	Selection Menu
							SAP Bundle Material Code & Name
														225132
						1
											1
1	AES	Application Enablement Sercvices
2	CM	Avaya communication Manager
3	AAC	Avaya Aura Conferencing
4	MSG	Avaya Aura Messaging
5	SBC	Avaya Aura System Border Control
6	SMGR	Avaya Aura System Manager
7	CS	Collaboration Evaluation Server
8	CMM-FM	Communications Manager Messaging - Federal Market
9	MBT	Midsize Business Template
10	MM	Modular Messaging
11	PS	Presence Services
12	ME	Midsize Enterprise Registration (ME 6.1)
13	UCS	Upgrade Collaboration Server 6.1 to ME 6.1 template
14	UME	Upgrade MBT to ME
	225135
	225136
	225137
	225138
	225139
	225141
	225143
	225144
	225149
	225150
	225151
	225152
	225153
	225154
	225155
	225156
	225157
	225158
	225159
	225161
	225162
	225163
	225164
	225165
	225166
	225167
	225168
	225169
	225170
	225171
	225172
	229580
	229581
	229582
	229583
	229584
	229585

---

Sheet 11: AES

AES Registration for System Platform/UI

Solution Element Registrations for products being installed on System Platform

In order for the UI Product to function properly, you must register the elements with Avaya prior to installing the software. Please fill in the White cells below: customer name and Sold to Number, enter your contact info

Yes

S8300D

G250A4

G250A4

G250AS

No

S8510

G250B4

G250B4

G250BS

Customer Information:

S8800

G250D4

G250D4

G250DS

G250T4

G250T4

G250TS

Customer Name

G350P4

G350P4

G350MS

Avaya Sold-to (Customer) Number

G430

G430

G430MS

G450

G450

G450MS

Contact Information (this is the requestors contact info, so the SE ID's can be sent):

G650

NA

NA

G700

G700

G700MS

Name

YES

NONE

Standard

S8510

S85P1A

Email Address

NO

US CITIZEN

Enterprise

S8800

S88IPA

Telephone Number Primary

JAPANESE CITIZEN

Telephone Number Secondary

Are "In-Country" Citizenships required for this Implementation?

Is this a High Availability Installation?

0

Please note: Standalone SAL gateways must be registered separately and in advance of registering any Solution Template that it will support!

Will a Standalone SAL Gateway be used to support the solution?

0

2

Solution Element ID (SEID) of the existing standalone SAL GW

If you need to add comments to clarify your needs, check here:

0

---

Sheet 12: Aura CM Registrations

Avaya Aura Registration

Registering of Avaya Aura Communication Manager

NOTE: This is not the product configurator - it is strictly meant to be used as a communication tool to the Registration team of those elements which are needing to be registered based on the configuration already established. DO NOT use this as a tool to determine configuration rules. In order to properly Register your Avaya Aura Communications Manager, you need to provide some information about the solution you are installing at the customer site as there are numerous options and it is imperative we the right information. You may need to have the AVAYA sales contract in front of you with the details of the solution. APPLICATIONs You need to 1st select the correct CM Solution Template that will be installed. You may need to answer another question depending on the solution type selected. Next, review the list of eligible Solution Elements below in the Applications Registrations section. If the row indicates you are eligible for those elements (highlighted in Green), you will need to select if you are going to install those elements. You will also need to identify the type of server and gateway for each application group. If you are not planning to install the elements at this time, please select "NO" - you still are eligible to install them at a later date if your needs change. ESS @&LSPs If you are installing Enterprise Survivable Server (ESS), scroll down to the ESS section and provide the needed additional information about the location and naming convention for those server(s). If you have a preferred MID #, please enter it, otherwise, it will be set up sequentially, starting at 2 (1 is always assigned to the Main Server). If you are registering a Local Survivable Processors (LSPs), scroll down to the LSP section as additional information is needed to be able to Register those items. Please fill in ALL white areas in that section. If you have a preferred MID #, please enter it, otherwise, it will be set up sequentially, starting at 2 (1 is always assigned to the Main Server). To e-mail this data to the Registration team, please use the e-mail button below.

PARENT

Eligibility

YES

Application

CMM Requirements

Servers

Gateways

S8300D

Gateway

SE1

SE2

Customer Name:

225132

STD

NO

Embedded CM Main

1

No CMM will be used

A

S8300D

S8300D

G250

Yes

S8510

G250A4

G250A4

G250AS

Customer Sold To/FL#:

225133

STD

Simplex CM Main w/ Survivable Core

2

CMM will be co-resident on main server template

B

S8510

S85P1A

S8500

G350

No

S8800

G250B4

G250B4

G250BS

System ID (SID)

(Used for upgrades from pre-CM 6 to CM 6.x.)

225134

STD

Duplex CM Main w/ Survivable Core

3

CMM will reside on a separate Server

C

S8800

S88IPA

S8510

G430

HP DL360G7

G250D4

G250D4

G250DS

Eligibility:

STD

225135

STD

Embedded CM Server w/ Survivable Remote

4

S8710

G450

Dell R610

G250T4

G250T4

G250TS

Aura 6 CM Contract Code:

225132

(Selected in the UI List)

Avaya Registration Team only

225136

ENT

Simplex CM Server w/ Survivable Remote

5

S8720

G700

None

G350P4

G350P4

G350MS

Select the CM Solution Template:

Simplex CM Main w/ Survivable Core

2

225137

ENT

S8730

G430

G430

G430MS

Select the CMM configuration:

CMM will be co-resident on main server template

B

225138

ENT

S8800

G450

G450

G450MS

List the Number of LSPs to be installed:

0

225139

ENT

Customer Provided

G650

NA

NA

225141

ENT

G700

G700

G700MS

Main Application Registrations

225143

ENT

Register Now?

Select Server

Select Gateway

Eligible

Eligible Applications

If any of the applications are to be installed outside of main site, list the SOLD To's where installing:

Software Solution Elements

Duplex Server = S8800

225144

ENT

YES

Communication Manager

VSP

VSPU

VSALGW

VCM

VUS

VCMM

ASM is co-resident on main server if either Survivable Remote is chosen

225149

STD

NO

Duplicate Communication Manager (for DUPLEX core)

VSP

VSPU

VSALGW

VCM

Session Manager - up to 6 may be added

225150

STD

YES

Avaya Aura System Manager

VSP

VSPU

VSALGW

SM

SMELEM

SALSM

AIM - multiple AIMs should be registered for Duplex

225151

STD

YES

Application Enablement Services

VSP

VSPU

VSALGW

AESSP

NMC - multiple NMCs should be registered for Duplex

225152

ENT

YES

Avaya Aura Presence Services QTY:

1

VSP

VSPU

VSALGW

VPSB

VCMM Rules: Embedded or Simplex Main only and choose where to put it

225153

ENT

YES

IM Site Admin QTY:

1

AIM

VUS Rules: Does not work with Duplex, but is needed for everything else

225154

ENT

YES

IM Network Management QTY:

1

NMC

225155

STD

NO

Session Manager QTY:

1

SALASM

VASM

225156

STD

NO

One-X Portal (SW)

1XPRTL

225157

STD

NO

One-X Mobile

1XMOBL

225158

STD

NO

Communication Manager Messaging

VSP

VSPU

VSALGW

VCM

VCMM

225159

STD

225160

STD

Enterprise Survivable Server (ESS)

225161

ENT

ESS

Location Sold To:

Select Server

Alarm Origination (Y/N)

Preferred Nickname

Preferred MID #

System Solution Elements

Hardware Solution Element

225162

ENT

1

VSP

VSPU

VSALGW

VCM

VASM

SALASM

225163

ENT

2

VSP

VSPU

VSALGW

VCM

VASM

SALASM

225164

ENT

3

VSP

VSPU

VSALGW

VCM

VASM

SALASM

225165

ENT

4

VSP

VSPU

VSALGW

VCM

VASM

SALASM

225166

ENT

5

VSP

VSPU

VSALGW

VCM

VASM

SALASM

225167

STD

225168

STD

Standalone Gateways/Local Survivable Processors (LSP) Registrations

225169

STD

Gateway#

Location Sold To:

Select Server

Select Gateway

Preferred Nickname

Preferred MID #

Alarm Origination (Y/N)

System Solution Elements

Hardware Solution Elements

225170

ENT

1

VSP

VSPU

VSALGW

VCM

VASM

SALASM

225171

ENT

2

VSP

VSPU

VSALGW

VCM

VASM

SALASM

225172

ENT

3

VSP

VSPU

VSALGW

VCM

VASM

SALASM

229580

STD

4

VSP

VSPU

VSALGW

VCM

VASM

SALASM

229581

ENT

5

VSP

VSPU

VSALGW

VCM

VASM

SALASM

229582

STD

6

VSP

VSPU

VSALGW

VCM

VASM

SALASM

229583

ENT

7

VSP

VSPU

VSALGW

VCM

VASM

SALASM

229584

STD

8

VSP

VSPU

VSALGW

VCM

VASM

SALASM

229585

ENT

9

VSP

VSPU

VSALGW

VCM

VASM

SALASM

10

VSP

VSPU

VSALGW

VCM

VASM

SALASM

11

VSP

VSPU

VSALGW

VCM

VASM

SALASM

12

VSP

VSPU

VSALGW

VCM

VASM

SALASM

13

VSP

VSPU

VSALGW

VCM

VASM

SALASM

14

VSP

VSPU

VSALGW

VCM

VASM

SALASM

15

VSP

VSPU

VSALGW

VCM

VASM

SALASM

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

76

77

78

79

80

81

82

83

84

85

86

87

88

89

90

91

92

93

94

95

96

97

98

99

100

If you need to add comments to clarify your needs, check here:

0

K

---

Sheet 13: CM Confirmation Page

1

0

1

0

0

For products installed on the Aura CM Registrations

This form is for requesting the ALARM Registration of the UI product/Onboarding of the customer (setting up alarming/alarm monitoring by Avaya for this customer). The installation of the UI products MUST be completed prior to submitting this form. INSTRUCTIONS: You must fill out the New UI/SP Product Registration form to ensure that information caries over to this page, including the UI products being registered, as that will populate the needed information below. The cells in Yellow, below, automatically populate from the Pre-Registrations (Product) page and do not need any further input from you. The cells in White may have been filled in by the Registration team during Product Registration, if not, please provide this information. Please verify the accuracy of the data, then Click the "Final Registration Button" and send this request to the Registration team (if you are prompted asking to allow automatic email creation, please click "YES". This will create a new CAVIOT request case, so this information is not readily known by the registering person.

Customer Information:

Customer Name

Customer Sold-to Number

Contact Information (this is the requestors contact info, so that alarming confirmation can be sent):

Name

Email Address

NONE

Telephone Number Primary

US CITIZEN

Telephone Number Secondary

JAPAN

ALARMS REGISTRATION INFORMATION (Alarming is to be set up for the following products:)

Please enter the SE ID and Product ID for the Solution Elements highlighted in Yellow below:

Sold To

Solution Element

SE ID

Product ID

---

Sheet 14: AAC

AAC Registration for System Platform/UI

Solution Element Registrations for products being installed on System Platform

In order for the UI Product to function properly, you must register the elements with Avaya prior to installing the software. Please fill in the White cells below: customer name and Sold to Number, enter your contact info

Yes

S8300D

G250A4

G250A4

G250AS

No

S8510

G250B4

G250B4

G250BS

Customer Information:

S8800

G250D4

G250D4

G250DS

S8800

G250T4

G250T4

G250TS

Customer Name

G350P4

G350P4

G350MS

Avaya Sold-to (Customer) Number

G430

G430

G430MS

G450

G450

G450MS

Contact Information (this is the requestors contact info, so the SE ID's can be sent):

G650

NA

NA

G700

G700

G700MS

Name

YES

NONE

Standard

S8510

S85P1A

Email Address

NO

US CITIZEN

Enterprise

S8800

S88IPA

Telephone Number Primary

JAPANESE CITIZEN

Telephone Number Secondary

Are "In-Country" Citizenships required for this Implementation?

Standard or Enterprise Conferencing Edition?

1

Please note: Standalone SAL gateways must be registered separately and in advance of registering any Solution Template that it will support!

Will a Standalone SAL Gateway be used to support the solution?

0

Solution Element ID (SEID) of the existing standalone SAL GW

If you need to add comments to clarify your needs, check here:

0

Gateway

SE1

SE2

S8300D

G250A4

G250A4

G250AS

S8510

G250B4

G250B4

G250BS

S8800

G250D4

G250D4

G250DS

G250T4

G250T4

G250TS

G350P4

G350P4

G350MS

G430

G430

G430MS

G450

G450

G450MS

G650

NA

NA

G700

G700

G700MS

---

Sheet 15: MSG

MSG Registration for System Platform/UI

Solution Element Registrations for products being installed on System Platform

In order for the UI Product to function properly, you must register the elements with Avaya prior to installing the software. Please fill in the White cells below: customer name and Sold to Number, enter your contact info

Yes

S8300D

G250A4

G250A4

G250AS

Please note that some templates, as indicated, require the registration team to "push" a model file for SAL 1.8 if you are using System Platform 6.0, Service Pack 1. This effort is not required if you are using System Platform 6.0, Service Pack 2. Please add a comment below that explains which System Platform Service Pack will be used at cutover for this server

No

S8510

G250B4

G250B4

G250BS

Customer Information:

S8800

G250D4

G250D4

G250DS

G250T4

G250T4

G250TS

Customer Name

G350P4

G350P4

G350MS

Avaya Sold-to (Customer) Number

G430

G430

G430MS

G450

G450

G450MS

Contact Information (this is the requestors contact info, so the SE ID's can be sent):

G650

NA

NA

G700

G700

G700MS

Name

YES

NONE

Standard

S8510

S85P1A

Email Address

NO

US CITIZEN

Enterprise

S8800

S88IPA

Telephone Number Primary

JAPANESE CITIZEN

Telephone Number Secondary

Pick Configuration Type

Please add preferred nickname

Are "In-Country" Citizenships required for this Implementation?

Please note: Standalone SAL gateways must be registered separately and in advance of registering any Solution Template that it will support!

Will a Standalone SAL Gateway be used to support the solution?

0

Solution Element ID (SEID) of the existing standalone SAL GW

If you need to add comments to clarify your needs, check here:

0

---

Sheet 16: SBC

SBC Registration for System Platform/UI

Solution Element Registrations for products being installed on System Platform

In order for the UI Product to function properly, you must register the elements with Avaya prior to installing the software. Please fill in the White cells below: customer name and Sold to Number, enter your contact info

Yes

S8300D

G250A4

G250A4

G250AS

Please note that some templates, as indicated, require the registration team to "push" a model file for SAL 1.8 if you are using System Platform 6.0, Service Pack 1. This effort is not required if you are using System Platform 6.0, Service Pack 2. or later but you should always manually request updated models files be downloaded to your System Platform machine. Please add a comment below that explains which System Platform Service Pack will be used at cutover for this server.

No

S8510

G250B4

G250B4

G250BS

Customer Information:

S8800

G250D4

G250D4

G250DS

G250T4

G250T4

G250TS

Customer Name

G350P4

G350P4

G350MS

Avaya Sold-to (Customer) Number

G430

G430

G430MS

G450

G450

G450MS

Contact Information (this is the requestors contact info, so the SE ID's can be sent):

G650

NA

NA

G700

G700

G700MS

Name

YES

NONE

Standard

S8510

S85P1A

Email Address

NO

US CITIZEN

Enterprise

S8800

S88IPA

Telephone Number Primary

JAPANESE CITIZEN

Telephone Number Secondary

Are "In-Country" Citizenships required for this Implementation?

Please note: Standalone SAL gateways must be registered separately and in advance of registering any Solution Template that it will support!

Will a Standalone SAL Gateway be used to support the solution?

0

Solution Element ID (SEID) of the existing standalone SAL GW

If you need to add comments to clarify your needs, check here:

0

---

Sheet 17: SMGR

SMGR Registration for System Platform/UI

Solution Element Registrations for products being installed on System Platform

In order for the UI Product to function properly, you must register the elements with Avaya prior to installing the software. Please fill in the White cells below: customer name and Sold to Number, enter your contact info

Yes

S8300D

G250A4

G250A4

G250AS

No

S8510

G250B4

G250B4

G250BS

Customer Information:

S8800

G250D4

G250D4

G250DS

G250T4

G250T4

G250TS

Customer Name

G350P4

G350P4

G350MS

Avaya Sold-to (Customer) Number

G430

G430

G430MS

G450

G450

G450MS

Contact Information (this is the requestors contact info, so the SE ID's can be sent):

G650

NA

NA

G700

G700

G700MS

Name

YES

NONE

Standard

S8510

S85P1A

Email Address

NO

US CITIZEN

Enterprise

S8800

S88IPA

Telephone Number Primary

JAPANESE CITIZEN

Telephone Number Secondary

Are "In-Country" Citizenships required for this Implementation?

Will you be installing Session Manager?

0

If yes, how many?

Please note: Standalone SAL gateways must be registered separately and in advance of registering any Solution Template that it will support!

Will a Standalone SAL Gateway be used to support the solution?

0

1

Solution Element ID (SEID) of the existing standalone SAL GW

If you need to add comments to clarify your needs, check here:

0

---

Sheet 18: CS

CS Registration for System Platform/UI

Solution Element Registrations for products being installed on System Platform

In order for the UI Product to function properly, you must register the elements with Avaya prior to installing the software. Please fill in the White cells below: customer name and Sold to Number, enter your contact info

Yes

S8300D

G250A4

G250A4

G250AS

No

S8510

G250B4

G250B4

G250BS

Customer Information:

S8800

G250D4

G250D4

G250DS

G250T4

G250T4

G250TS

Customer Name

G350P4

G350P4

G350MS

Avaya Sold-to (Customer) Number

G430

G430

G430MS

G450

G450

G450MS

Contact Information (this is the requestors contact info, so the SE ID's can be sent):

G650

NA

NA

G700

G700

G700MS

Name

YES

NONE

Standard

S8510

S85P1A

Email Address

NO

US CITIZEN

Enterprise

S8800

S88IPA

Telephone Number Primary

JAPANESE CITIZEN

Telephone Number Secondary

Are "In-Country" Citizenships required for this Implementation?

Pick which gateway will be used?

Please note: Standalone SAL gateways must be registered separately and in advance of registering any Solution Template that it will support!

Will a Standalone SAL Gateway be used to support the solution?

0

Solution Element ID (SEID) of the existing standalone SAL GW

If you need to add comments to clarify your needs, check here:

0

G250A4

1

G250B4

2

G250D4

3

G250T4

4

G350P4

5

G430

6

G450

7

G650

8

G700

9

NONE

---

Sheet 19: UCS

Upgrade From Collaboration Server 6.1 template to ME 6.1 template

Solution Element Registrations for products being installed on System Platform

In order for the UI Product to function properly, you must register the elements with Avaya prior to installing the software. Please fill in the White cells below: customer name and Sold to Number, enter your contact info

Yes

S8300D

G250A4

G250A4

G250AS

No

S8510

G250B4

G250B4

G250BS

Customer Information:

S8800

G250D4

G250D4

G250DS

G250T4

G250T4

G250TS

Customer Name

G350P4

G350P4

G350MS

Avaya Sold-to (Customer) Number

G430

G430

G430MS

G450

G450

G450MS

Contact Information (this is the requestors contact info, so the SE ID's can be sent):

G650

NA

NA

G700

G700

G700MS

Name

YES

NONE

Standard

S8510

S85P1A

Email Address

NO

US CITIZEN

Enterprise

S8800

S88IPA

Telephone Number Primary

JAPANESE CITIZEN

Telephone Number Secondary

Are "In-Country" Citizenships required for this Implementation?

Pick which gateway will be used?

Please note: Standalone SAL gateways must be registered separately and in advance of registering any Solution Template that it will support!

Will a Standalone SAL Gateway be used to support the solution?

0

Solution Element ID (SEID) of the existing standalone SAL GW

If you need to add comments to clarify your needs, check here:

0

G250B4

G250D4

G250T4

G350P4

G430

G450

G650

G700

NONE

---

Sheet 20: UCSME62

Upgrade From Collaboration Server 6.1 template to ME 6.2 template

Solution Element Registrations for products being installed on System Platform

In order for the UI Product to function properly, you must register the elements with Avaya prior to installing the software. Please fill in the White cells below: customer name and Sold to Number, enter your contact info

Yes

S8300D

G250A4

G250A4

G250AS

No

S8510

G250B4

G250B4

G250BS

Customer Information:

S8800

G250D4

G250D4

G250DS

G250T4

G250T4

G250TS

Customer Name

G350P4

G350P4

G350MS

Avaya Sold-to (Customer) Number

G430

G430

G430MS

G450

G450

G450MS

Contact Information (this is the requestors contact info, so the SE ID's can be sent):

G650

NA

NA

G700

G700

G700MS

Name

YES

NONE

Standard

S8510

S85P1A

Email Address

NO

US CITIZEN

Enterprise

S8800

S88IPA

Telephone Number Primary

JAPANESE CITIZEN

Telephone Number Secondary

Are "In-Country" Citizenships required for this Implementation?

Does ME 6.2 use HA?

Please note: Standalone SAL gateways must be registered separately and in advance of registering any Solution Template that it will support!

Will a Standalone SAL Gateway be used to support the solution?

0

Solution Element ID (SEID) of the existing standalone SAL GW

If you need to add comments to clarify your needs, check here:

0

G250B4

G250D4

G250T4

G350P4

G430

G450

G650

G700

NONE

---

Sheet 21: UME

Upgrade MBT to ME

Solution Element Registrations for products being installed on System Platform

In order for the UI Product to function properly, you must register the elements with Avaya prior to installing the software. Please fill in the White cells below: customer name and Sold to Number, enter your contact info

Yes

S8300D

G250A4

G250A4

G250AS

S8300D

Gateway

No

S8510

G250B4

G250B4

G250BS

S8510

G250A4

Customer Information:

S8800

G250D4

G250D4

G250DS

S8800

G250B4

G250T4

G250T4

G250TS

HP DL360G7

G250D4

Customer Name

G350P4

G350P4

G350MS

Dell R610

G250T4

Avaya Sold-to (Customer) Number

G430

G430

G430MS

None

G350P4

G450

G450

G450MS

G430

Contact Information (this is the requestors contact info, so the SE ID's can be sent):

G650

NA

NA

G450

G700

G700

G700MS

G650

Name

YES

NONE

Standard

S8510

S85P1A

G700

Email Address

NO

US CITIZEN

Enterprise

S8800

S88IPA

Telephone Number Primary

JAPANESE CITIZEN

Telephone Number Secondary

Are "In-Country" Citizenships required for this Implementation?

Pick which gateway will be used?

Please note: Standalone SAL gateways must be registered separately and in advance of registering any Solution Template that it will support!

Will a Standalone SAL Gateway be used to support the solution?

0

Solution Element ID (SEID) of the existing standalone SAL GW

If you need to add comments to clarify your needs, check here:

0

Standalone Gateways/Local Survivable Processors (LSP) Registrations

Location Sold To:

Select Server

Select Gateway

Preferred Nickname

Preferred MID #

---

Sheet 22: ME

Midsize Enterpise (ME) Registration for System Platform/UI

Solution Element Registrations for products being installed on System Platform

In order for the UI Product to function properly, you must register the elements with Avaya prior to installing the software. Please fill in the White cells below: customer name and Sold to Number, enter your contact info

Yes

S8300D

G250A4

G250A4

G250AS

No

S8510

G250B4

G250B4

G250BS

Customer Information:

S8800

G250D4

G250D4

G250DS

G250T4

G250T4

G250TS

Customer Name

G350P4

G350P4

G350MS

Avaya Sold-to (Customer) Number

G430

G430

G430MS

G450

G450

G450MS

Contact Information (this is the requestors contact info, so the SE ID's can be sent):

G650

NA

NA

G700

G700

G700MS

Name

YES

NONE

Standard

S8510

S85P1A

Email Address

NO

US CITIZEN

Enterprise

S8800

S88IPA

Telephone Number Primary

JAPANESE CITIZEN

Telephone Number Secondary

Are "In-Country" Citizenships required for this Implementation?

Please note: Standalone SAL gateways must be registered separately and in advance of registering any Solution Template that it will support!

Will a Standalone SAL Gateway be used to support the solution?

0

Solution Element ID (SEID) of the existing standalone SAL GW

If you need to add comments to clarify your needs, check here:

0

---

Sheet 23: ME62

Midsize Enterpise (ME) 6.2 Template Registration for System Platform/UI

Solution Element Registrations for products being installed on System Platform

In order for the UI Product to function properly, you must register the elements with Avaya prior to installing the software. Please fill in the White cells below: customer name and Sold to Number, enter your contact info

Yes

S8300D

G250A4

G250A4

G250AS

No

S8510

G250B4

G250B4

G250BS

Customer Information:

S8800

G250D4

G250D4

G250DS

G250T4

G250T4

G250TS

Customer Name

G350P4

G350P4

G350MS

Avaya Sold-to (Customer) Number

G430

G430

G430MS

G450

G450

G450MS

Contact Information (this is the requestors contact info, so the SE ID's can be sent):

G650

NA

NA

G700

G700

G700MS

Name

YES

NONE

Standard

S8510

S85P1A

Email Address

NO

US CITIZEN

Enterprise

S8800

S88IPA

Telephone Number Primary

JAPANESE CITIZEN

Telephone Number Secondary

Are "In-Country" Citizenships required for this Implementation?

Does ME 6.2 use HA?

1

Please note: Standalone SAL gateways must be registered separately and in advance of registering any Solution Template that it will support!

Will a Standalone SAL Gateway be used to support the solution?

0

Solution Element ID (SEID) of the existing standalone SAL GW

If you need to add comments to clarify your needs, check here:

0

---

Sheet 24: ME622

Upgrade from ME 6.1 template to ME 6.2 template

Solution Element Registrations for products being installed on System Platform

In order for the UI Product to function properly, you must register the elements with Avaya prior to installing the software. Please fill in the White cells below: customer name and Sold to Number, enter your contact info

Yes

S8300D

G250A4

G250A4

G250AS

No

S8510

G250B4

G250B4

G250BS

Customer Information:

S8800

G250D4

G250D4

G250DS

G250T4

G250T4

G250TS

Customer Name

G350P4

G350P4

G350MS

Avaya Sold-to (Customer) Number

G430

G430

G430MS

G450

G450

G450MS

Contact Information (this is the requestors contact info, so the SE ID's can be sent):

G650

NA

NA

G700

G700

G700MS

Name

YES

NONE

Standard

S8510

S85P1A

Email Address

NO

US CITIZEN

Enterprise

S8800

S88IPA

Telephone Number Primary

JAPANESE CITIZEN

Telephone Number Secondary

Are "In-Country" Citizenships required for this Implementation?

Does ME 6.2 use HA?

2

Please note: Standalone SAL gateways must be registered separately and in advance of registering any Solution Template that it will support!

Will a Standalone SAL Gateway be used to support the solution?

0

Solution Element ID (SEID) of the existing standalone SAL GW

If you need to add comments to clarify your needs, check here:

0

---

Sheet 25: CMM-FM

CMM-FM Registration for System Platform/UI

Solution Element Registrations for products being installed on System Platform

In order for the UI Product to function properly, you must register the elements with Avaya prior to installing the software. Please fill in the White cells below: customer name and Sold to Number, enter your contact info

Yes

S8300D

G250A4

G250A4

G250AS

No

S8510

G250B4

G250B4

G250BS

Customer Information:

S8800

G250D4

G250D4

G250DS

G250T4

G250T4

G250TS

Customer Name

G350P4

G350P4

G350MS

Avaya Sold-to (Customer) Number

G430

G430

G430MS

G450

G450

G450MS

Contact Information (this is the requestors contact info, so the SE ID's can be sent):

G650

NA

NA

G700

G700

G700MS

Name

YES

NONE

Standard

S8510

S85P1A

Email Address

NO

US CITIZEN

Enterprise

S8800

S88IPA

Telephone Number Primary

JAPANESE CITIZEN

Telephone Number Secondary

Are "In-Country" Citizenships required for this Implementation?

Please note: Standalone SAL gateways must be registered separately and in advance of registering any Solution Template that it will support!

Will a Standalone SAL Gateway be used to support the solution?

0

Solution Element ID (SEID) of the existing standalone SAL GW

If you need to add comments to clarify your needs, check here:

0

---

Sheet 26: MBT

MBT Registration for System Platform/UI

Solution Element Registrations for products being installed on System Platform

In order for the UI Product to function properly, you must register the elements with Avaya prior to installing the software. Please fill in the White cells below: customer name and Sold to Number, enter your contact info

Yes

S8300D

G250A4

G250A4

G250AS

No

S8510

G250B4

G250B4

G250BS

Customer Information:

S8800

G250D4

G250D4

G250DS

G250T4

G250T4

G250TS

Customer Name

G350P4

G350P4

G350MS

Avaya Sold-to (Customer) Number

G430

G430

G430MS

G450

G450

G450MS

Contact Information (this is the requestors contact info, so the SE ID's can be sent):

G650

NA

NA

G700

G700

G700MS

Name

YES

NONE

Standard

S8510

S85P1A

Email Address

NO

US CITIZEN

Enterprise

S8800

S88IPA

Telephone Number Primary

JAPANESE CITIZEN

Telephone Number Secondary

Are "In-Country" Citizenships required for this Implementation?

Will Media Services be installed on this system?

Is this a High Availability Installation?

0

Pick which Server will be used

Please note: Standalone SAL gateways must be registered separately and in advance of registering any Solution Template that it will support!

Will a Standalone SAL Gateway be used to support the solution?

0

Solution Element ID (SEID) of the existing standalone SAL GW

If you need to add comments to clarify your needs, check here:

0

---

Sheet 27: MBT LSP Registrations

MBT LSP Registration
	Registering of single/multiple LSP(s) for MBT
	In order to properly register the Local Survivable Processors (LSPs), the information below is needed by the Registration team for each LSP being installed . The MID is only necessary if you have a preference, otherwise, it will be assigned sequentially starting at 2 (the main CM system will be assigned "1"). The number of LSPs listed here should match the quantity listed on the Product Registration page. To e-mail this data to the Registration team, please use the e-mail button on the Product Registration page (use the green button to return to the Product Registration page).
				You will need to provide information on this many LSPs:	0
														S8300	G250	5.2.1
LSP #	Sold To:	Select Server Type	Select Gateway Type	Modem Dial In # (If SAL, leave blank)	Alarm Origination (Y/N)	Preferred Nickname	CM Version	Preferred MID #						S8500	G350	6
1														S8510	G430
2														S8710	G450
3														S8720	G550
4														S8730	G700
5														S8800 Simplex
6														S8800 Duplex
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100

---

Sheet 28: MM

MM Registration for System Platform/UI

Solution Element Registrations for products being installed on System Platform

In order for the UI Product to function properly, you must register the elements with Avaya prior to installing the software. Please fill in the White cells below: customer name and Sold to Number, enter your contact info

Yes

S8300D

G250A4

G250A4

G250AS

No

S8510

G250B4

G250B4

G250BS

Customer Information:

S8800

G250D4

G250D4

G250DS

G250T4

G250T4

G250TS

Customer Name

G350P4

G350P4

G350MS

Avaya Sold-to (Customer) Number

G430

G430

G430MS

G450

G450

G450MS

Contact Information (this is the requestors contact info, so the SE ID's can be sent):

G650

NA

NA

G700

G700

G700MS

Name

YES

NONE

Standard

S8510

S85P1A

Email Address

NO

US CITIZEN

Enterprise

S8800

S88IPA

Telephone Number Primary

JAPANESE CITIZEN

Telephone Number Secondary

Are "In-Country" Citizenships required for this Implementation?

Is this a High Availability Installation?

Will a Standalone SAL Gateway be used to support the solution?

0

Solution Element ID (SEID) of the existing standalone SAL GW

0

---

Sheet 29: PS

PS Registration for System Platform/UI

Solution Element Registrations for products being installed on System Platform

In order for the UI Product to function properly, you must register the elements with Avaya prior to installing the software. Please fill in the White cells below: customer name and Sold to Number, enter your contact info

Yes

S8300D

G250A4

G250A4

G250AS

No

S8510

G250B4

G250B4

G250BS

Customer Information:

S8800

G250D4

G250D4

G250DS

G250T4

G250T4

G250TS

Customer Name

G350P4

G350P4

G350MS

Avaya Sold-to (Customer) Number

G430

G430

G430MS

G450

G450

G450MS

Contact Information (this is the requestors contact info, so the SE ID's can be sent):

G650

NA

NA

G700

G700

G700MS

Name

YES

NONE

Standard

S8510

S85P1A

Email Address

NO

US CITIZEN

Enterprise

S8800

S88IPA

Telephone Number Primary

JAPANESE CITIZEN

Telephone Number Secondary

Are "In-Country" Citizenships required for this Implementation?

Please note: Standalone SAL gateways must be registered separately and in advance of registering any Solution Template that it will support!

Will a Standalone SAL Gateway be used to support the solution?

0

Solution Element ID (SEID) of the existing standalone SAL GW

If you need to add comments to clarify your needs, check here:

0

---

Sheet 30: NOTE

Additional Information From Customer
Will a Standalone SAL Gateway be used to support the solution?

---

Sheet 31: UI Product Reg Confirm

1

1

0

1

0

0

For products installed on System Platform and are ready to have the Alarms Registered and Tested

This form is for requesting the ALARM Registration of the UI product/Onboarding of the customer (setting up alarming/alarm monitoring by Avaya for this customer). The installation of the UI products MUST be completed prior to submitting this form. INSTRUCTIONS: You must fill out the New UI/SP Product Registration form to ensure that information caries over to this page, including the UI products being registered, as that will populate the needed information below. The cells in Yellow, below, automatically populate from the Pre-Registrations (Product) page and do not need any further input from you. The cells in White may have been filled in by the Registration team during Product Registration, if not, please provide this information. Please verify the accuracy of the data, then Click the "Final Registration Button" and send this request to the Registration team (if you are prompted asking to allow automatic email creation, please click "YES". This will create a new CAVIOT request case, so this information is not readily known by the registering person.

Customer Information:

Customer Name

Customer Sold-to Number

Contact Information (this is the requestors contact info, so that alarming confirmation can be sent):

Name

Email Address

NONE

Telephone Number Primary

US CITIZEN

Telephone Number Secondary

JAPAN

ALARMS REGISTRATION INFORMATION (Alarming is to be set up for the following products:)

Please enter the SE ID and Product ID for the Solution Elements highlighted in Yellow below:

Product

Element

SE ID

Product ID

Application Enablement Sercvices

SP (DOM 0)

VSP

HA (DOM 0)

VSP

SP (CDOM)

VSPU

SAL

VSALGW

AES

AESSP

---

Sheet 32: SAL New Registration 2

New SAL Gateway & Device Registrations Page
	For NEW SAL Gateway and Device installation
	This form is to be used to register a NEW Secure Access Link (SAL) Gateway (SAL GW). Instructions: You will need to provide to the Registration Team the customer name, the SOLD TO where the SAL GW is to be installed. Please fill out the White Boxes below with the needed information, providing the Sold TO needing to be newly registered for this customer. You will be contacted via email when the Registration Team completed the registration of the Gateway.
Customer Information:
	Customer Name :
	Sold To # where the SAL Gateway is to be installed:
	Existing SALGW SEID which should be used (if applicable)
	Redundant SALGW SEID (if applicable)
Contact Information (this is the requestors contact info, so the SE ID's can be sent):
	Name :
	Email Address :														NONE
	Telephone Number Primary :														US CITIZEN
	Telephone Number Secondary :														JAPANESE CITIZEN
	Are "In-Country" Citizenships required for this Project?
List all Solution Elements needing to be registered and the associated Sold TO for the SE's:
	SEIDs and Product IDs will be returned for all products listed below
	Sold TO	Select each Product being install for each FL (if multiple copies of the same Product need to be registered, list the Product multiple times)…..																		0
1		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
2		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
3		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
4		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
5		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
6		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
7		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
8		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
9		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
10		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
11		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
12		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
13		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
14		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
15		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
16		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
17		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
18		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
19		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
20		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
21		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
22		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
23		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
24		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
25		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
26		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
27		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
28		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
29		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0
30		1
					0	0	0	0	0	0	0	0	0	0	0	0	0			0

---

Sheet 33: SAL Alarm Registration_2

SAL ALARM Registration Page
For products migrated to connect through SAL and are ready to be ALARM Registered and Tested
	This form is to be used to request the Alarm Registration of those Solution Elements connected to Secure Access Link (SAL) and have the Alarms tested. Instructions: Please provide the contact information so that once the alarming is set up and tested, a confirmation e-mail will be sent. List all of the SE IDs that were administered to the SAL Server. You can either paste the information from the FL Report that was sent to you or you can manually type in the information below.
Customer Information
	Customer Name:																										YES
																											NO
Contact Information (this is the requestors contact info, so alarming confirmation can be sent):
	Name
	Email Address
	Telephone Number Primary
	Telephone Number Secondary
	Are "In-Country" Citizenships required for this Project?
SAL Gateway Registration Information
			Sold to/FL #	SE ID	Product ID
			0	0
	List Devices that have been added to SALGW
	Note to Requestor - List those devices here that have been added to the SALGW and are ready to be ALARM Registered.
	(You can copy this data from the FL Report that was sent to you from the Registration Team)
			Sold TO Number	Product (SE) Code	Model	Solution Element ID	Product ID	Remote Access	Transport Alarms	Administered in SALGW [Yes/No]
	0
	0
	0
	0
	0
	0
	0
	0
	0
	0
	0
	0
	0
	0		,	,\
	0		,,	,,\
			1111111111111110	1111111111111110

---

Sheet 34: Main2

Selection Menu

1

3

---

Sheet 35: SAL_2

SSG/SIG to SAL Migration Page

For NEW installations of products being installed on a non-UI/System Platform version of SAL

SSG/SIG Information

Customer Name :

Sold To # where the SSG/SIG is installed:

SE ID of SSG/SIG

SAL Information

1

Customer Name :

Sold To # where the SAL is (to be) installed:

1

Contact Information (this is the requestors contact info, so the SE ID's can be sent):

Name :

Email Address :

NONE

Telephone Number Primary :

US CITIZEN

Telephone Number Secondary :

JAPAN

Are "In-Country" Citizenships required for this Project?

Version:

e.g. R15

1

---

Sheet 36: SSG Data

		From				To
		Customer Name:	0			Customer Name:	0
		Sold To #:	0			Sold To #:	0
		SE ID of SSG/SIG:	0			SE ID of SAL:	Please Enter SE ID
CET	Date and Time								EST
MST	Avaya Engineer
EST	Avaya Engineer E-mail
PST	Avaya Engineer Phone
	Customer/BP Engineer
	Customer/BP Engineer E-mail
	Customer/BP Engineer Phone
	FL Name
	FL Number
	#	Product	SE ID	Product ID	Local IP	Data admin	Connectivity	Alarming	Roll back	Comments
	1					OK	OK			X
	2
	3
	4
	5
	6
	7
	8
	9
	10
	Date and Time				24.11.2010		15:00		EST
	Avaya Engineer
	Avaya Engineer E-mail
	Avaya Engineer Phone
	Customer/BP Engineer
	Customer/BP Engineer E-mail
	Customer/BP Engineer Phone
	FL Name
	FL Number
	#	Product	SE ID	Product ID	Local IP	Data admin	Connectivity	Alarming	Roll Back	Comments
	1					OK	OK			X
	2
	3
	4
	5
	6
	7
	8
	9
	10
	Date and Time				24.11.2010		15:00		EST
	Avaya Engineer
	Avaya Engineer E-mail
	Avaya Engineer Phone
	Customer/BP Engineer
	Customer/BP Engineer E-mail
	Customer/BP Engineer Phone
	FL Name
	FL Number
	#	Product	SE ID	Product ID	Local IP	Data admin	Connectivity	Alarming	Roll Back	Comments
	1					OK	OK			X
	2
	3
	4
	5
	6
	7
	8
	9
	10
	Date and Time				24.11.2010		15:00		EST
	Avaya Engineer
	Avaya Engineer E-mail
	Avaya Engineer Phone
	Customer/BP Engineer
	Customer/BP Engineer E-mail
	Customer/BP Engineer Phone
	FL Name
	FL Number
	#	Product	SE ID	Product ID	Local IP	Data admin	Connectivity	Alarming	Roll Back	Comments
	1					OK	OK			X
	2
	3
	4
	5
	6
	7
	8
	9
	10
	Date and Time				24.11.2010		15:00		EST
	Avaya Engineer
	Avaya Engineer E-mail
	Avaya Engineer Phone
	Customer/BP Engineer
	Customer/BP Engineer E-mail
	Customer/BP Engineer Phone
	FL Name
	FL Number
	#	Product	SE ID	Product ID	Local IP	Data admin	Connectivity	Alarming	Roll Back	Comments
	1					OK	OK			X
	2
	3
	4
	5
	6
	7
	8
	9
	10
	Date and Time				24.11.2010		15:00		EST
	Avaya Engineer
	Avaya Engineer E-mail
	Avaya Engineer Phone
	Customer/BP Engineer
	Customer/BP Engineer E-mail
	Customer/BP Engineer Phone
	FL Name
	FL Number
	#	Product	SE ID	Product ID	Local IP	Data admin	Connectivity	Alarming	Roll Back	Comments
	1					OK	OK			X
	2
	3
	4
	5
	6
	7
	8
	9
	10
	Date and Time				24.11.2010		15:00		EST
	Avaya Engineer
	Avaya Engineer E-mail
	Avaya Engineer Phone
	Customer/BP Engineer
	Customer/BP Engineer E-mail
	Customer/BP Engineer Phone
	FL Name
	FL Number
	#	Product	SE ID	Product ID	Local IP	Data admin	Connectivity	Alarming	Roll back	Comments
	1					OK	OK			X
	2
	3
	4
	5
	6
	7
	8
	9
	10
	Date and Time				24.11.2010		15:00		EST
	Avaya Engineer
	Avaya Engineer E-mail
	Avaya Engineer Phone
	Customer/BP Engineer
	Customer/BP Engineer E-mail
	Customer/BP Engineer Phone
	FL Name
	FL Number
	#	Product	SE ID	Product ID	Local IP	Data admin	Connectivity	Alarming	Roll Back	Comments
	1					OK	OK			X
	2
	3
	4
	5
	6
	7
	8
	9
	10
	Date and Time				24.11.2010		15:00		EST
	Avaya Engineer
	Avaya Engineer E-mail
	Avaya Engineer Phone
	Customer/BP Engineer
	Customer/BP Engineer E-mail
	Customer/BP Engineer Phone
	FL Name
	FL Number
	#	Product	SE ID	Product ID	Local IP	Data admin	Connectivity	Alarming	Roll Back	Comments
	1					OK	OK			X
	2
	3
	4
	5
	6
	7
	8
	9
	10
	Date and Time				24.11.2010		15:00		EST
	Avaya Engineer
	Avaya Engineer E-mail
	Avaya Engineer Phone
	Customer/BP Engineer
	Customer/BP Engineer E-mail
	Customer/BP Engineer Phone
	FL Name
	FL Number
	#	Product	SE ID	Product ID	Local IP	Data admin	Connectivity	Alarming	Roll Back	Comments
	1					OK	OK			X
	2
	3
	4
	5
	6
	7
	8
	9
	10
	Date and Time				24.11.2010		15:00		EST
	Avaya Engineer
	Avaya Engineer E-mail
	Avaya Engineer Phone
	Customer/BP Engineer
	Customer/BP Engineer E-mail
	Customer/BP Engineer Phone
	FL Name
	FL Number
	#	Product	SE ID	Product ID	Local IP	Data admin	Connectivity	Alarming	Roll Back	Comments
	1					OK	OK			X
	2
	3
	4
	5
	6
	7
	8
	9
	10
	Date and Time				24.11.2010		15:00		EST
	Avaya Engineer
	Avaya Engineer E-mail
	Avaya Engineer Phone
	Customer/BP Engineer
	Customer/BP Engineer E-mail
	Customer/BP Engineer Phone
	FL Name
	FL Number
	#	Product	SE ID	Product ID	Local IP	Data admin	Connectivity	Alarming	Roll Back	Comments
	1					OK	OK			X
	2
	3
	4
	5
	6
	7
	8
	9
	10
	Date and Time				24.11.2010		15:00		EST
	Avaya Engineer
	Avaya Engineer E-mail
	Avaya Engineer Phone
	Customer/BP Engineer
	Customer/BP Engineer E-mail
	Customer/BP Engineer Phone
	FL Name
	FL Number
	#	Product	SE ID	Product ID	Local IP	Data admin	Connectivity	Alarming	Roll back	Comments
	1					OK	OK			X
	2
	3
	4
	5
	6
	7
	8
	9
	10
	Date and Time				24.11.2010		15:00		EST
	Avaya Engineer
	Avaya Engineer E-mail
	Avaya Engineer Phone
	Customer/BP Engineer
	Customer/BP Engineer E-mail
	Customer/BP Engineer Phone
	FL Name
	FL Number
	#	Product	SE ID	Product ID	Local IP	Data admin	Connectivity	Alarming	Roll Back	Comments
	1					OK	OK			X
	2
	3
	4
	5
	6
	7
	8
	9
	10
	Date and Time				24.11.2010		15:00		EST
	Avaya Engineer
	Avaya Engineer E-mail
	Avaya Engineer Phone
	Customer/BP Engineer
	Customer/BP Engineer E-mail
	Customer/BP Engineer Phone
	FL Name
	FL Number
	#	Product	SE ID	Product ID	Local IP	Data admin	Connectivity	Alarming	Roll Back	Comments
	1					OK	OK			X
	2
	3
	4
	5
	6
	7
	8
	9
	10
	Date and Time				24.11.2010		15:00		EST
	Avaya Engineer
	Avaya Engineer E-mail
	Avaya Engineer Phone
	Customer/BP Engineer
	Customer/BP Engineer E-mail
	Customer/BP Engineer Phone
	FL Name
	FL Number
	#	Product	SE ID	Product ID	Local IP	Data admin	Connectivity	Alarming	Roll Back	Comments
	1					OK	OK			X
	2
	3
	4
	5
	6
	7
	8
	9
	10
	Date and Time				24.11.2010		15:00		EST
	Avaya Engineer
	Avaya Engineer E-mail
	Avaya Engineer Phone
	Customer/BP Engineer
	Customer/BP Engineer E-mail
	Customer/BP Engineer Phone
	FL Name
	FL Number
	#	Product	SE ID	Product ID	Local IP	Data admin	Connectivity	Alarming	Roll Back	Comments
	1					OK	OK			X
	2
	3
	4
	5
	6
	7
	8
	9
	10
	Date and Time				24.11.2010		15:00		EST
	Avaya Engineer
	Avaya Engineer E-mail
	Avaya Engineer Phone
	Customer/BP Engineer
	Customer/BP Engineer E-mail
	Customer/BP Engineer Phone
	FL Name
	FL Number
	#	Product	SE ID	Product ID	Local IP	Data admin	Connectivity	Alarming	Roll Back	Comments
	1					OK	OK			X
	2
	3
	4
	5
	6
	7
	8
	9
	10

---

Sheet 37: Sheet1

Standard	No		1	AAC		Yes	S8510			1			G430		Application+Storage		1	225132	AURA STD ED R6 50 USER BUNDLE LIC	225132-AURA STD ED R6 50 USER BUNDLE LIC
Enterprise	1		2	AES		No	S8800 Simplex		CM-8300-G350	2			G450		Application Only		2	225133	AURA STD ED R6 100 USER BUNDLE LIC	225133-AURA STD ED R6 100 USER BUNDLE LIC
	2		3	CM			S8800 Duplex		CM-8300-G430	3			NONE		Storage Only		3	225134	AURA STD ED R6 150 USER BUNDLE LIC	225134-AURA STD ED R6 150 USER BUNDLE LIC
	3		4	CMM-FM					CM-8300-G450	4							4	225135	AURA STD ED R6 200 USER BUNDLE LIC	225135-AURA STD ED R6 200 USER BUNDLE LIC
	4		5	CS					CM-8300-G650	5							5	225136	AURA ENT ED R6 50 USER BUNDLE LIC	225136-AURA ENT ED R6 50 USER BUNDLE LIC
	5		6	MBT					CM-8300-G700	6							6	225137	AURA ENT ED R6 100 USER BUNDLE LIC	225137-AURA ENT ED R6 100 USER BUNDLE LIC
	6		7	MM					CM-S8500B	7							7	225138	AURA ENT ED R6 150 USER BUNDLE LIC	225138-AURA ENT ED R6 150 USER BUNDLE LIC
	7		8	MSG					CM-S8500C	8							8	225139	AURA ENT ED R6 200 USER BUNDLE LIC	225139-AURA ENT ED R6 200 USER BUNDLE LIC
	8		9	PS					CM-S8510	9				49			9	225141	AURA ENT ED UPLIFT PER EXT SFTW LIC	225141-AURA ENT ED UPLIFT PER EXT SFTW LIC
	9		10	SBC					CM-S8700IP	10							10	225143	AURA ENT ED R6 BP DEMO ONLY SW LICLIC	225143-AURA ENT ED R6 BP DEMO ONLY SW LICLIC
	10		11	SMGR					CM-S8700MC	11							11	225144	AURA ENT ED R6 INTERNAL LIC:10000TDM-NU	225144-AURA ENT ED R6 INTERNAL LIC:10000TDM-NU
	11								CM-S8710IP	12							12	225145	AURA STD ED R6 SW ENT LIC	225145-AURA STD ED R6 SW ENT LIC
	12								CM-S8710MC	13							13	225149	AURA STD ED R6 1-100 NEW LIC	225149-AURA STD ED R6 1-100 NEW LIC
	13								CM-S8720	14							14	225150	AURA STD ED R6 101-1000 NEW LIC	225150-AURA STD ED R6 101-1000 NEW LIC
	14								CM-S8730	15							15	225151	AURA STD ED R6 1001+ NEW LIC	225151-AURA STD ED R6 1001+ NEW LIC
	15								CM-S8800 Simplex	16							16	225152	AURA ENT ED R6 1-100 NEW LIC	225152-AURA ENT ED R6 1-100 NEW LIC
									CM-S8800 Duplex	17							17	225153	AURA ENT ED R6 101-1000 NEW LIC	225153-AURA ENT ED R6 101-1000 NEW LIC
									G350 Gateway Only	18							18	225155	AURA STD ED R6 1-100 SINGLE UPGRADE LIC	225155-AURA STD ED R6 1-100 SINGLE UPGRADE LIC
									G430 Gateway Only	19							19	225156	AURA STD ED R6 101-1000 SINGLE UPGRADE LIC	225156-AURA STD ED R6 101-1000 SINGLE UPGRADE LIC
					Version:				G450 Gateway Only	20							20	225157	AURA STD ED R6 1001+ SINGLE UPGRADE LIC	225157-AURA STD ED R6 1001+ SINGLE UPGRADE LIC
									G650 Gateway Only	21							21	225158	AURA STD ED R6 1-100 MULTI UPGRADE LIC	225158-AURA STD ED R6 1-100 MULTI UPGRADE LIC
					SID/MID:				G700 Gateway Only	22							22	225159	AURA STD ED R6 101-1000 MULTI UPGRADE LIC	225159-AURA STD ED R6 101-1000 MULTI UPGRADE LIC
									MM-MSS	23							23	225159	AURA STD ED R6 101-1000 MULTI UPGRADE LIC	225159-AURA STD ED R6 101-1000 MULTI UPGRADE LIC
					Root Pw:				MM-MAS	24							24	225160	AURA STD ED R6 1001+ MULTI UPGRADE LIC	225160-AURA STD ED R6 1001+ MULTI UPGRADE LIC
									Audix-Intuity	25							25	225161	AURA ENT ED R6 1-100 SNGL UPGRADE LIC	225161-AURA ENT ED R6 1-100 SNGL UPGRADE LIC
					OS (Win) Pw:				Audix-LX	26							26	225162	AURA ENT ED R6 101-1000 SINGLE UPGRADE LIC	225162-AURA ENT ED R6 101-1000 SINGLE UPGRADE LIC
									CMS	27							27	225163	AURA ENT ED R6 1001+ SINGLE UPGRADE LIC	225163-AURA ENT ED R6 1001+ SINGLE UPGRADE LIC
					RAS Pw:				AES	28							28	225164	AURA ENT ED R6 1-100 MULTI UPGRADE LIC	225164-AURA ENT ED R6 1-100 MULTI UPGRADE LIC
									SES	29							29	225165	AURA ENT ED R6 101-1000 MULTI UPGRADE LIC	225165-AURA ENT ED R6 101-1000 MULTI UPGRADE LIC
									AIR	30							30	225166	AURA ENT ED R6 1001+ MULTI UPGRADE LIC	225166-AURA ENT ED R6 1001+ MULTI UPGRADE LIC
									VP	31							31	225167	AURA STD ED R6 1-100 ADD LIC	225167-AURA STD ED R6 1-100 ADD LIC
									Other-AIC	32							32	225168	AURA STD ED R6 101-1000 ADD LIC	225168-AURA STD ED R6 101-1000 ADD LIC
									Other-AMN	33							33	225169	AURA STD ED R6 1001+ ADD LIC	225169-AURA STD ED R6 1001+ ADD LIC
									Other-PDS	34							34	225170	AURA ENT ED R6 1-100 ADD LIC	225170-AURA ENT ED R6 1-100 ADD LIC
									Other-CCE	35							35	225171	AURA ENT ED R6 101-1000 ADD LIC	225171-AURA ENT ED R6 101-1000 ADD LIC
									Other-AIM	36							36	225172	AURA ENT ED R6 1001+ ADD LIC	225172-AURA ENT ED R6 1001+ ADD LIC
									Other-Other	37							37	225173	AURA STD ED R6 1-100 SINGLE MOVE LIC	225173-AURA STD ED R6 1-100 SINGLE MOVE LIC
									Session Manager	38							38	225174	AURA STD ED R6 101-1000 SINGLE MOVE LIC	225174-AURA STD ED R6 101-1000 SINGLE MOVE LIC
									Avaya IQ	39							39	225175	AURA STD ED R6 1001+ SINGLE MOVE LIC	225175-AURA STD ED R6 1001+ SINGLE MOVE LIC
									ABG B8500 (B5800)	40							40	225176	AURA STD ED R6 1-100 MULTI MOVE LIC	225176-AURA STD ED R6 1-100 MULTI MOVE LIC
									ABG VMPRO (ABGVM)	41							41	225177	AURA STD ED R6 101-1000 MULTI MOVE LIC	225177-AURA STD ED R6 101-1000 MULTI MOVE LIC
									Avaya Easy Management	42							42	225178	AURA STD ED R6 1001+ MULTI MOVE LIC	225178-AURA STD ED R6 1001+ MULTI MOVE LIC
									Avaya Voice Priority Processor	43							43	225179	AURA ENT ED R6 1-100 SINGLE MOVE LIC	225179-AURA ENT ED R6 1-100 SINGLE MOVE LIC
									Branchen Communications Server	44							44	225180	AURA ENT ED R6 101-1000 SINGLE MOVE LIC	225180-AURA ENT ED R6 101-1000 SINGLE MOVE LIC
									Business Call Center	45							45	225181	AURA ENT ED R6 1001+ SINGLE MOVE LIC	225181-AURA ENT ED R6 1001+ SINGLE MOVE LIC
									Central Data Management	46							46	225182	AURA ENT ED R6 1-100 MULTI MOVE LIC	225182-AURA ENT ED R6 1-100 MULTI MOVE LIC
									Com4Tel 2	47							47	225183	AURA ENT ED R6 101-1000 MULTI MOVE LIC	225183-AURA ENT ED R6 101-1000 MULTI MOVE LIC
									ConneCTIon	48							48	225184	AURA ENT ED R6 1001+ MULTI MOVE LIC	225184-AURA ENT ED R6 1001+ MULTI MOVE LIC
									Contact Center TIVA	49							49	229580	AVAYA AURATM R6 STD ED NEW SFTW LIC	229580-AVAYA AURATM R6 STD ED NEW SFTW LIC
									Customer Interaction Express	50							50	229581	AVAYA AURATM R6 ENT ED NEW SFTW LIC	229581-AVAYA AURATM R6 ENT ED NEW SFTW LIC
									DiaIIt	51							51	229582	AVAYA AURATM R6 STD ED UPG SFTW LIC	229582-AVAYA AURATM R6 STD ED UPG SFTW LIC
									Enterprise Directory System	52							52	229583	AVAYA AURATM R6 ENT ED UPG SFTW LIC	229583-AVAYA AURATM R6 ENT ED UPG SFTW LIC
									Fehler- und Performance Management	53							53	229584	AVAYA AURATM R6 STD ED ADD SFTW LIC	229584-AVAYA AURATM R6 STD ED ADD SFTW LIC
									HotCom PMS	54							54	229585	AVAYA AURATM R6 ENT ED ADD SFTW LIC	229585-AVAYA AURATM R6 ENT ED ADD SFTW LIC
									IDS Win Gebuehrendaten Management	55
									Integral Easy Management	56
									Integral Message Server	57
									Internet Access Manager	58
									MAS Accounting	59
									MedCom Medial	60
									Mobility Manager	61
									Multifunctional Alarming- and Communication Server	62
									PUMA	63
									Observer TAPI	64
									Satin	65
									SeCom	66
									Snapware	67
									TIMA	68
									Thetacom	69
									Unified Messaging System C300	70
									Unified Messaging System C3000	71
									Gebuehrendaten-Management	72

---

Sheet 38: SAL Alarm Registration

SAL ALARM Registration Page
For products migrated to connect through SAL and are ready to be ALARM Registered and Tested
	This form is to be used to request the Alarm Registration of those Solution Elements connected to Secure Access Link (SAL) and have the Alarms tested. Instructions: Please provide the contact information so that once the alarming is set up and tested, a confirmation e-mail will be sent. List all of the SE IDs that were administered to the SAL Server. You can either paste the information from the FL Report that was sent to you or you can manually type in the information below.
Customer Information
	Customer Name:		0																								YES
																											NO
Contact Information (this is the requestors contact info, so alarming confirmation can be sent):
	Name		0
	Email Address		0
	Telephone Number Primary		0
	Telephone Number Secondary		0
	Are "In-Country" Citizenships required for this Project?			0
SAL Gateway Registration Information								NONE
							LINK: (You can copy and paste it into your browser to save the FL report)
			Sold to/FL #	SE ID	Product ID		http://gts.avaya.com:7777/pls/apex/f?p=102:9:493463653236882::NO::P9_SOLD_TO_ID:\
							http://gts.avaya.com:7777/pls/apex/f?p=102:9:493463653236882::NO::P9_SOLD_TO_ID:\,,\
	List Devices that have been added to SALGW													,,\
	Note to Requestor - List those devices here that have been added to the SALGW and are ready to be ALARM Registered.
	(You can copy this data from the FL Report that was sent to you from the Registration Team)
	If you saved your FL report into the C:\ root directory, you can upload data when clicking the button below		Sold TO Number	Product (SE) Code	Model	Solution Element ID	Product ID	Remote Access	Transport Alarms	Administered in SALGW [Yes/No]
	0
	0
	0
	0
	0
	0
	0
	0
	0
	0
	0
	0
	0
	0		,	,\
	0		,,	,,\
			1111111111111110	1111111111111110