Configuring SBC Edge with Exchange 2013

Prerequisites

Interoperation Notes

The following instructions detail configuring both Exchange 2013 and Ribbon SBC Edge to interoperate via TCP.  It is suggested that any integration attempt begin with TCP and move to TLS, if required, only after ensuring the Exchange <> SBC connection is fully functional.

• Exchange = demo4.sbc.net  (10.1.1.4)
• SBC = sbc2000.sbc.net (10.1.1.74)

Exchange 2013 Configuration

Use the following to configure Exchange 2013 to accept and process calls sent directly from SBC Edge.

1. Connect to the Exchange Admin interface via your web browser.

   Connect to Exchange Admin

   

2. Select Unified Messaging.

   Unified Messaging

   

3. Select UM dial plans.

   UM Dial Plans

   

4. Add a new UM dial plan.  Add a dial plan to support the Exchange <> SBC connection. 

   Lync and PBX dial plans are different.  You should not attempt to use a Lync dial plan to support the Exchange <> SBC connection.

   Add New UM Dial Plan

   

   New UM Dial Plan

    

5. Create a UM IP gateway.  Create an entry in Exchange for the SBC gateway.

   UM IP Gateway

    

   Add New UM IP Gateway

   

   New UM IP Gateway

   

6. Modify the newly created UM dial plan.

   UM Dial Plan

   

   Modify New UM Dial Plan

   

7. Configure/verify Outlook Voice Access.

   Configure Dial Plan

   

   Outlook Voice Access

    

   Dialing Rules

   

   Dialing Authorization

   

   Transfer and Search

   

8. Add a UM Mailbox Policy to the dial plan.

   Add UM Mailbox Policy

    

   New UM Mailbox Policy

    

9. Modify/verify the newly created UM Mailbox Policy.

   Modify New UM Mailbox Policy

   

   General

   

   Dialing Authorization

   

10. Add a UM Auto Attendant.

    Add UM Auto Attendant

    

    New UM Auto Attendant

    

11. Modify/verify the newly created UM Auto Attendant.

    Modify New UM Auto Attendant

    

    Address Book and Operator Access

    

    Dialing Authorization

    

12. If a UM Hunt Group if a default does not already exist.

    UM Hunt Group

    

13. Add users to the newly created SBC dial plan.  Adding extensions is accomplished via a user's Unified Messaging configuration.

    Add Users

    

    Other Extensions

    

    Add Another Extension

    

Configure the SBC Edge

The next section covers configuring the SBC Edge to interface to the Exchange server.

1. Access the Ribbon SBC Edge WebUI.
   
   

2. Create/verify SIP Profile. Refer to Creating and Modifying SIP Profiles.
   
   

3. Create a SIP Server Table for the Exchange Server. Refer to Creating and Modifying Entries in SIP Server Tables.
   
   

4. Add the Exchange Server to the newly created SIP Server Table.
   
   

5. Create a Transformation Table and Transformation Entries to be used to process calls sent from Exchange's Subscriber Access (SA) and Automated Attendant (AA) to the SBC. Adjust your configuration according to your specific needs. Refer to Creating and Modifying Entries to Transformation Tables.
   
   

6. Create a Call Routing Table to process incoming calls from the Exchange SA and AA. Creating and Modifying Entries to Call Routing Tables.
   
   

7. Create a SIP Signaling Group to process incoming SIP calls from the Exchange Subscriber Access and Automated Attendant. Refer to Managing Signaling Groups.
   
   

8. Create entries in the Call Route Table. Refer to Managing Call Routing Tables. These call route entries process incoming calls from the Exchange Subscriber Access and Auto Attendant.  Create a call route for every possible destination for Exchange SA/AA calls.
   
   

9. In addition to the above configuration that supports incoming calls from Exchange, you will need to create corresponding configurations to route calls to Exchange from other sources (such as PSTN and PBXs).  It is strongly recommended that transformations for Exchange SA/AA appear at the top any transformation table. These entries not only handle the initial calls to Exchange, but also the 302 from Exchange (used during the call setup).
   
   

   Not placing the Exchange transformations at the top of the transformation table may cause the 302 to fail, which will cause the calls to Exchange to fail.