Associating Subscriber Access Numbers
For subscribers to
access their mailbox, one or more subscriber access numbers must be
specified in the dial plan. This should be the pilot number for the PBX
hunt group that the subscribers will use.
To associate a subscriber access extension to the dial plan, 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 Dial Plan tab.
|
4. | Select the dial plan in the results pane, such as SFO Dial Plan.
|
5. | In the Action menu, select Properties.
|
6. | Select the Subscriber Access tab.
|
7. | Enter the extension that subscribers will use to access their mailboxes, such as 333.
|
8. | Click Add.
|
9. | Click OK to close the window.
|
The UM server will now recognize that subscribers will use the extension to access their mailboxes.
Creating a UM IP Gateway
The next task is to create an UM IP gateway to link the dial plan with the IP/VoIP gateway and the PBX. This is shown in Figure 4.
To create the UM IP gateway, 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. | In the Action pane, click New UM IP Gateway.
|
5. | Enter the IP gateway name, such as SFO IP Gateway.
|
6. | Enter the IP address for the IP gateway, such as 192.168.1.4 shown in Figure 5.
|
7. | Click Browse.
|
8. | Select a dial plan to associate the IP gateway with, such as the SFO Dial Plan.
|
9. | This also creates a default hunt group (which will be deleted later).
|
10. | |
11. | Click New to create the UM IP gateway.
|
12. | Click Finish to close the wizard.
|
The newly created UM IP
gateway should be shown in the results pane. The default hunt group will
be removed and a new one created in a later task.
Associating the UM Server with the Dial Plan
The dial plan needs to be
associated with the UM server that was installed in the first task.
This eventually causes the UM server to register with the IP/VoIP
gateway to receive calls.
To associate the UM server with the new dial plan, execute the following steps:
1. | Launch the Exchange Management Console.
|
2. | Under the Server Configuration folder, select the Unified Messaging container.
|
3. | Select the Unified Messaging server.
|
4. | In the actions pane, click Properties.
|
5. | Select the UM Settings tab.
|
6. | Click Add.
|
7. | Select the dial plan to associate, such as the SFO Dial Plan.
|
8. | Click OK.
|
9. | Click OK to close the Properties dialog box.
|
The pilot number will now be associated to the dial plan for subscriber access.
Create a Unified Messaging Auto Attendant
For the UM server to
answer callers, a UM Auto Attendant must be created and associated with a
dial plan. This allows incoming calls to be answered and directed to
the appropriate voice mailbox.
To create an Auto Attendant and associate it with a dial plan, execute the following tasks:
1. | Launch the Exchange Management Console.
|
2. | Under the Organization Configuration folder, select the Unified Messaging container.
|
3. | Select the UM Auto Attendants tab.
|
4. | In the actions pane, click New UM Auto Attendant.
|
5. | Enter the name of the Auto Attendant, such as SFO Auto Attendant.
|
6. | Click Browse.
|
7. | Select a dial plan, such as the SFO Dial Plan.
|
8. | |
9. | Enter the pilot extension number, such as 222, and click Add.
|
10. | Check the Create Auto Attendant as Enabled check box.
|
11. | Check the Create Auto Attendant as Speech-Enabled check box, shown in Figure 6, if you want the Auto Attendant to accept voice commands.
|
12. | Click New.
|
13. | Click Finish to close the wizard.
|
The newly created auto attendant should be shown in the results pane.
Note
If the Auto Attendant
is created as speech-enabled, a secondary fallback Auto Attendant that
is not speech-enabled should be created and that option configured on
the primary Auto Attendant. If a user cannot use voice commands, he can
use DTMF commands on the secondary Auto Attendant. Although the
speech-enabled Auto Attendant accepts DTMF commands, the user is not
notified this is possible unless a DTMF fallback Auto Attendant is
configured.