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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

AAM 7.0 Subscriber info

Status
Not open for further replies.
Feb 8, 2018
2
US
Recently migrated from MM 4 to AAM 7.0 . I use to be able to export subscribers to look for secondary extensions using Site Administration. Is there anyway to pull a report of current subscribers and any additional extensions they may have associated with them? I tried to connect using Site Administration but I am either missing some setting or it just doesn't work on AAM 7. Any help would be greatly appreciated.
 
You can use ASA to do the same thing as you did in MM. It should be the same type of setup. What error are you getting ?

Ken Means

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
 
ASA returns back 2 errors first is "Command Failed: No Ports Available" the second is "The task could not be executed on any configured connection
 
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.

Ken Means

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
 
For what it's worth, I worked backwards wiresharking ASA connecting on the open port 389, and...
This'll get it in a nasty flat text file :)


ldapsearch -D "cn=TRUSTEDSERVERNAME,dc=avaya" -w TRUSTEDSERVERPASSWORD -p 389 -h MSS-IPADDRESS -b "ou=people,dc=avaya" -s sub "(objectclass=*)" MailboxNumber SecondExt
 
Not sure why. I have this working on hundreds of AAM 6.x and 7.0 AAM systems.

Ken Means

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
 
Oh, it works fine in ASA, I was just trying to find a way to script it :)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top