Applies to: Exchange Server 2013
Topic Last Modified: 2012-11-18
You can allow the Microsoft Exchange Unified Messaging service on a Mailbox server to answer new calls or prevent it from doing so. By default, a Mailbox server is in an enabled state after it’s installed. When you’re setting the Mailbox server to accept incoming voice, fax, auto attendant and Outlook Voice Access calls, you use the Set-ServerComponentState cmdlet.
Configuring Maintenance Mode for a Mailbox server lets you take the server out of service. For a Mailbox server, out-of-service means that the server won’t host any active databases, all transport queues are empty, and the server won’t accept any incoming calls from Client Access servers, VoIP gateways, IP PBXs, SIP-enabled PBXs, or session border controllers (SBCs).
In Exchange 2007 and Exchange 2010, there was a status parameter that could be used to control the operational status of a Unified Messaging server. In Exchange 2013, no status parameter is available for that purpose on the Set-UMService cmdlet for a Mailbox server.
 Important: |
|---|
| It’s not required that Client Access and Mailbox servers be added to a UM dial plan before they can process calls for Unified Messaging, except when you’re integrating UM and Microsoft Office Communications Server 2007 R2 or Microsoft Lync Server. By default, all Client Access and Mailbox servers in an organization are available to answer incoming calls. |
For additional management tasks related to Mailbox servers, see UM Services Procedures.
What do you need to know before you begin?
- Estimated time to complete: 3 minutes.
- You need to be assigned permissions before you can perform this
procedure or procedures. To see what permissions you need, see the
"Exchange Server Configuration Settings" entry in the Unified Messaging
Permissions topic.
- Verify that the Mailbox server is installed, either on the same
computer as the Client Access server or on a separate computer.
- If you’re putting a Mailbox server into Maintenance Mode,
verify that there’s enough redundancy of all database copies to
allow the server to go out of service.
- Before taking a server out of Maintenance Mode, verify the
health of the server and make sure it’s ready to go into
service.
- For information about keyboard shortcuts that may apply to the
procedures in this topic, see Keyboard Shortcuts in
the Exchange Admin Center.
 Tip: |
|---|
| Having problems? Ask for help in the Exchange forums. Visit the forums at: Exchange Server, Exchange Online, or Exchange Online Protection. |
Use the Shell to allow or prevent call answering on a Mailbox server
This example enables a Mailbox server
UMMBXr-05x.contoso.com to answer incoming voice, fax,
auto attendant, and Outlook Voice Access calls from VoIP gateways,
IP PBXs, SIP-enabled PBXs, and SBCs, and writes the change to the
registry on the UMMBX-05x server.
 Copy Code |
|
|---|---|
Set-ServerComponentState -Component UnifiedMessaging -Identity UMMBX-05x.contoso.com -Requester Maintenance -State Active -LocalOnly |
|
This example prevents a Mailbox server
UMMBX-05x.contoso.com from answering incoming voice,
fax, auto attendant, and Outlook Voice Access calls from VoIP
gateways, IP PBXs, SIP-enabled PBXs, and SBCs, and writes the
change only to Active Directory.
| Copy Code |
|
|---|---|
Set-ServerComponentState -Component UnifiedMessaging -Identity UMMBX-05x.contoso.com -Requester Maintenance -State Inactive -RemoteOnly |
|