Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
bulk add in AAM using SITES wth ASA
- Thread starter Veloce67
- Start date
avayaguy23
Systems Engineer
Administering a MM/AAM system.
This procedure describes how to administer an MM/AAM system. You must perform this procedure before you can connect to an MM/AAM system through Site Administration.
1. Access your MM.AAM system through the web administration screen, and log in as craft.
The system displays the Messaging Administration page.
2. Click Global Administration.
The Global Administration page appears.
3. Click Trusted Server Management.
The Manage Trusted Servers page appears.
4. Click Add a New Trusted Server.
The Add Trusted Server page appears.
5. In the Trusted Server Name box, enter the login name that you want Site Administration to use to connect to the MM/AAM system.
6. In the Password box, enter the password for the login that you want Site Administration to use to connect to the MM/AAM system.
7. In the IP Address box, enter the fixed IP address of the PC that is running Site Administration.
8. In the Service Name box, enter a descriptive name that will be displayed in the Manage Trusted Servers page in Messaging Administration.
9. Use the default settings for the other boxes.
10. Click Save.
11. Click Return to Main.
12. Log off from the MM/AAM system.
13. Configure Site Administration to connect to this MM/AAM system.
Adding an MM/AAM system
This procedure describes how to configure Site Administration to connect to an MM/AAM system. Before you can connect to an MM/AAM system through Site Administration, see Administering a Release 2 system.
Configure Site Administration to connect to an MM/AAM system by completing the following steps:
1. From the toolbar at the top of the screen, click , or select File > New > Messaging System.
The system displays the Add Messaging System dialog box.
2. In the Messaging System Name field, enter a name for this connection.
3. Select the MM/AAM check box.
4. In the Shared Systems area, specify whether this MM/AAM system is a local system or a shared system.
5. In the Add Messaging System dialog box, select the appropriate Version from the drop down menu.
6. Click Next.
The system displays the next Add Messaging System dialog box.
7. Click Next.
The system displays the Network Connection dialog box.
8. Either enter the fully-qualified domain name of the MM/AAM system, or enter the IP address of the MM/AAM system.
9. Click Next.
The system displays the default setting (389) of the TCP/IP Port Number box.
10. Click Next.
11. In the Timeout for sustaining an idle connection box, enter a value other than 0 to make sure the connection to the MM/AAM system is not active permanently.
12. Click Next.
13. Click Next.
14. In the Login ID field, enter the trusted-server name you configured in the MM/AAM system.
15. In the Base DN field, enter the Base DN for all subscriber entries. ( ou=people,dc=Avaya ).
16. Click Next.
17. In the Password field, enter the password you configured for the trusted server in the MM/AAM system.
18. In the Password (again) field, re-enter the password you configured for the trusted server in the MM/AAM system.
Bulk Import mailboxes into Aura Messaging.
This procedure describes how to bulk import mailboxes into MM/AAM system.
1. Click Tree.
2. Right click AAM profile in work place.
3. Select connect using.
4. Click Task.
5. Click Import.
The system displays New import Data and Select add command.
6. Click OK.
The system displays excel sheet format.
7. Here I have attached the AAM user template.
8. Fill the mandatory field in the template.
9. Save the file as .csv format
10. Click open option browse the file.
11. Click to OK.
12. Click to Save
13. Click to run.
This procedure describes how to administer an MM/AAM system. You must perform this procedure before you can connect to an MM/AAM system through Site Administration.
1. Access your MM.AAM system through the web administration screen, and log in as craft.
The system displays the Messaging Administration page.
2. Click Global Administration.
The Global Administration page appears.
3. Click Trusted Server Management.
The Manage Trusted Servers page appears.
4. Click Add a New Trusted Server.
The Add Trusted Server page appears.
5. In the Trusted Server Name box, enter the login name that you want Site Administration to use to connect to the MM/AAM system.
6. In the Password box, enter the password for the login that you want Site Administration to use to connect to the MM/AAM system.
7. In the IP Address box, enter the fixed IP address of the PC that is running Site Administration.
8. In the Service Name box, enter a descriptive name that will be displayed in the Manage Trusted Servers page in Messaging Administration.
9. Use the default settings for the other boxes.
10. Click Save.
11. Click Return to Main.
12. Log off from the MM/AAM system.
13. Configure Site Administration to connect to this MM/AAM system.
Adding an MM/AAM system
This procedure describes how to configure Site Administration to connect to an MM/AAM system. Before you can connect to an MM/AAM system through Site Administration, see Administering a Release 2 system.
Configure Site Administration to connect to an MM/AAM system by completing the following steps:
1. From the toolbar at the top of the screen, click , or select File > New > Messaging System.
The system displays the Add Messaging System dialog box.
2. In the Messaging System Name field, enter a name for this connection.
3. Select the MM/AAM check box.
4. In the Shared Systems area, specify whether this MM/AAM system is a local system or a shared system.
5. In the Add Messaging System dialog box, select the appropriate Version from the drop down menu.
6. Click Next.
The system displays the next Add Messaging System dialog box.
7. Click Next.
The system displays the Network Connection dialog box.
8. Either enter the fully-qualified domain name of the MM/AAM system, or enter the IP address of the MM/AAM system.
9. Click Next.
The system displays the default setting (389) of the TCP/IP Port Number box.
10. Click Next.
11. In the Timeout for sustaining an idle connection box, enter a value other than 0 to make sure the connection to the MM/AAM system is not active permanently.
12. Click Next.
13. Click Next.
14. In the Login ID field, enter the trusted-server name you configured in the MM/AAM system.
15. In the Base DN field, enter the Base DN for all subscriber entries. ( ou=people,dc=Avaya ).
16. Click Next.
17. In the Password field, enter the password you configured for the trusted server in the MM/AAM system.
18. In the Password (again) field, re-enter the password you configured for the trusted server in the MM/AAM system.
Bulk Import mailboxes into Aura Messaging.
This procedure describes how to bulk import mailboxes into MM/AAM system.
1. Click Tree.
2. Right click AAM profile in work place.
3. Select connect using.
4. Click Task.
5. Click Import.
The system displays New import Data and Select add command.
6. Click OK.
The system displays excel sheet format.
7. Here I have attached the AAM user template.
8. Fill the mandatory field in the template.
9. Save the file as .csv format
10. Click open option browse the file.
11. Click to OK.
12. Click to Save
13. Click to run.
- Thread starter
- #3
avayaguy23
Systems Engineer
field you are looking for is msgSiteID
- Thread starter
- #5
This field "msgSiteID" does not show up on the import screen in ASA. It's also not on the spreadsheet you shared. I also ran an export for Subscribers in my ASA and these are the fields that exported.
Account Code
Additional Extension1
Additional Extension2
Address Before Record
ascii Name
avUmLastTUIPasswordChange
avUmPersonalOperatorScheduleGUID
BucketNum
Call Type
Class of Service
Common Name
Community ID
Email-Address
Exchange email
Failed Login Count
FAX Auto Delete
FAX Auto Print
FAX Print Number
First Name
Include in Auto Attendant directory
Machine id number(Node ID)
MailBox Number
Manual
Miscellaneous 1
Miscellaneous 2
Miscellaneous 3
Miscellaneous 4
MWI enabled
Number Of Nodes
Numeric Address
Password
Personal Attendant
Personal Directory Exist
Preferred Media Type
Pronounceable name
Second Extension
Storage Destination
Sub Sequence Number
SubCategory
Subscriber ID
SubType
SurName
System Sub
Tandem Subscriber ID
Telephone Number
Time Zone
TimeOut
Touch Tone Name
Transfer Authority
Transfer Extension
TUI Message Order
umIntercomPaging
umVoiceMailboxExtension
umVoiceMailEnabled
Universal Address
User Name
Voice System Number
Account Code
Additional Extension1
Additional Extension2
Address Before Record
ascii Name
avUmLastTUIPasswordChange
avUmPersonalOperatorScheduleGUID
BucketNum
Call Type
Class of Service
Common Name
Community ID
Email-Address
Exchange email
Failed Login Count
FAX Auto Delete
FAX Auto Print
FAX Print Number
First Name
Include in Auto Attendant directory
Machine id number(Node ID)
MailBox Number
Manual
Miscellaneous 1
Miscellaneous 2
Miscellaneous 3
Miscellaneous 4
MWI enabled
Number Of Nodes
Numeric Address
Password
Personal Attendant
Personal Directory Exist
Preferred Media Type
Pronounceable name
Second Extension
Storage Destination
Sub Sequence Number
SubCategory
Subscriber ID
SubType
SurName
System Sub
Tandem Subscriber ID
Telephone Number
Time Zone
TimeOut
Touch Tone Name
Transfer Authority
Transfer Extension
TUI Message Order
umIntercomPaging
umVoiceMailboxExtension
umVoiceMailEnabled
Universal Address
User Name
Voice System Number
avayaguy23
Systems Engineer
The field msgSiteID was pulled directly from the database. I’m guessing asa doesn’t support it.
- Status
Similar threads
- Locked
- Question