Creating the Hunt Groups
The default hunt group
that is created with the UM IP gateway does not contain a pilot number.
To have the system handle incoming calls correctly, the default hunt
group should be deleted and new ones created for the caller and
subscriber hunt groups.
To accomplish the creation of the hunt groups, execute the following steps:
1. | Launch the Exchange Management Console.
|
2. | Under the Organization Configuration folder, select the Unified Messaging container.
|
3. | Select the UM IP Gateway tab.
|
4. | Select the Default Hunt Group in the results pane.
|
5. | In the actions pane, under the section for the selected hunt group, click Remove.
|
6. | At the prompt, click Yes.
|
7. | Select the UM IP gateway, such as SFO IP Gateway.
|
8. | In the actions pane, click New UM Hunt Group.
|
9. | Enter the caller hunt group name, such as SFO Caller Hunt Group.
|
10. | Click Browse.
|
11. | Select the dial plan to associate, such as SFO Dial Plan.
|
12. | Click OK.
|
13. | Enter the hunt group pilot number, such as 222.
|
14. | Click New.
|
15. | Click Finish.
|
16. | Repeat steps 7 through 14, using SFO Subscriber Hunt Group as the name and 333 as the hunt group pilot.
|
The result of the configuration is shown in Figure 7, including the new hunt groups.
The
system is now configured and ready for the final configuration step in
the basic configuration—the enabling of a user for unified messaging.
Enabling Mailboxes for UM
The last task is to
enable a user’s mailbox. This associates the user with a mailbox policy
and, therefore, to the rest of the unified messaging infrastructure.
To enable a user, execute the following steps:
1. | Launch the Exchange Management Console.
|
2. | Under the Recipient Configuration folder, select the Mailbox folder.
|
3. | In the results pane, select the user to be enabled.
|
4. | In the actions pane, select Enable Unified Messaging.
|
5. | Click Browse.
|
6. | Select the UM policy, such as the SFO Dial Plan Default Policy.
|
7. | Click OK.
|
8. | Click Next.
|
9. | Enter the extension, such as 100, shown in Figure 8.
|
10. | |
11. | Click Enable.
|
12. | Click Finish to close the wizard.
|
A simple welcome email
message with the extension and their confidential PIN will be
automatically sent to their Exchange Server mailbox.
Testing Functionality
The final step is to
make sure that it is all working. This could be the most difficult
testing tasks for an average Exchange Server administrator, as they will
be the least familiar with the telephony elements of the
infrastructure.
It is important to make sure that these critical functions be tested:
The UM server is operating.
The UM server can connect to the gateway and PBX.
The UM server can be reached from an internal phone.
The UM server can be reached from an external phone.
Figure 9 shows the paths of the critical tests.
The specific commands and steps for testing are discussed in the following sections.
Testing Unified Messaging Server Operation
The
Unified Messaging server operations test needs to run on the local UM
server in the Exchange Management Shell. The shell command is:
This command attempts a diagnostic SIP call and reports back on the success. Figure 10 shows the result of a successful test. Specifically, the value of EntireOperationSuccess is True.
Testing Unified Messaging Server Connectivity
This test shows if the UM
server can communicate with the PBX and access a phone. Specifically, it
causes the internal phone to ring.
The command needs to be run from the Exchange Management Shell. The command syntax is:
Test-UMConnectivity –IPGateway "IP Gateway Name" –Phone extension
For example, the command might be:
Test-UMConnectivity –IPGateway "SFO IP Gateway" –Phone 102
The results for a successful test are shown in Figure 11. The phone at the extension should ring. If the test is successful, it will show that "The call was disconnected by the other party" at the end of the test.
To show the results of an unsuccessful test, enter the command:
Test-UMConnectivity –IPGateway "SFO IP Gateway" –Phone 104
This command specifies a nonexistent extension. The results are shown in Figure 12. It shows that the requested operation failed.
Testing Unified Messaging Server with an Internal Phone
To test the Unified Messaging server from a phone, pick up a phone from within the dial plan and dial the pilot number.
For example, from the
phone at extension 102, dial the pilot number 222. The Auto Attendant
should pick up and prompt the caller.
Leave a message for a test user and then hang up.
Dial the pilot number
for subscriber access (for example, extension 333) and check the
message. Alternatively, check the message using Outlook or Outlook Web
App.
Testing Unified Messaging Server with an External Phone
Use an outside line to
call the company number that the PBX routes to the caller hunt group.
Say the user’s name. Press # to leave a message and leave a message for
the user.
To verify the
message was received, dial the external number for subscriber access and
check the message. Alternatively, check the message using Outlook or
Outlook Web App.
Data Storage in Unified Messaging
Unified messaging stores data
in a variety of locations and formats. The different types of data
include custom audio prompts, incoming calls, configuration, and setup.
It is important to
understand where the data is stored, the relative importance of backing
it up, and the method of restoring the data. Tables 1, 2, 3, and 4 list the relevant data storage information for each type of data.
Table 1. Custom Audio Prompt Data
| Data Type | Custom audio files (.wav) for UM dial plans and UM Auto Attendants
Custom audio files (.wav) for telephone user interface (TUI) and Outlook Voice Access |
| Storage | File system in \UnifiedMessaging\Prompts |
| Backup | File-level backup is only needed on the prompt publishing server |
| Restore | File-level restore is only needed on the prompt publishing server |
| Data Type | Custom audio files (.wav) for UM dial plans and UM Auto Attendants
Custom audio files (.wav) for telephone user interface (TUI) and Outlook Voice Access |
| Storage | File system in \UnifiedMessaging\Prompts |
Table 2. Incoming Call Data
| Critical Data | Incoming calls: .eml and .wma files for each voice mail |
| Storage | File system \UnifiedMessaging\temp |
| Backup | None |
| Restore | None |
Table 3. Server Configuration Data
| Critical Data | Server configuration data, including all objects and settings |
| Storage | Active Directory configuration container |
| Backup | Backup method is domain controller replication or Active Directory backup |
| Restore | This data is reapplied to the server during a setup /m:recoverserver restore |
Table 4. Setup Data
| Critical Data | Limited information is stored in the Registry by Setup that is not essential to server restore |
| Storage | HKLM\SOFTWARE\Microsoft\Exchange |
| | HKLM\SYSTEM\currentcontrolset\Services |
| Backup | Backup method is System State backup or Registry export |
| Restore | Restore method is System State restore or Registry import |
