Skip to end of metadata
Go to start of metadata

This article describes the process of configuring an SBC Edge (SBC) to be deployed Upstream in a PSTN - SBC - Microsoft Exchange 2007/2010 Unified Messaging Server environment. In this example the SBC serves as a gateway between the PBX, Exchange Unified Messaging Server, and the PSTN; none of which are directly connected to the other:

The diagram below illustrates the topology and a typical call scenario:

Figure : Topology

 

Before You Begin

Launch the WebUI and verify the node level settings:

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to System > Node Level Settings
  3. Verify that all the fields have been populated as indicated in the image below.

    Use the IP address from YOUR Primary Domain Server, not the sample IP address in the image.

Configuration Overview

The SBC integration with the MS Exchange 2007/2010 Unified Messaging Server requires specific configuration steps to be completed using the WebUI:

  • Default Tone Table. A factory default SBC configuration contains the "Default Tone Table" entry.
  • Default Media Profile(s). The default G.711A/Mu-Law profile is used in this example.
  • Default Media List. The Default Media List is used in this example.
  • Create a SIP Server Table. Add a SIP Server table entry for the Exchange 2007/2010 Server.
  • Create a SIP Profile. Create a custom SIP Profile or use the default.
  • Create a Transformation Table. Create this table to relate Call Routing tables and for Called/Calling Number transformations.
  • Create a Call Routing Table. Create two table entries: ISDN and SIP. These are required in the relevant Signaling Groups.
  • Configure a DS1 Port. The port is associated with the Physical PRI (T1/E1) connection.
  • Create two Signaling Groups. One Signaling Group is designated for SIP and the other for ISDN.
  • Set the System Timing. Configure the Clock Source to use the SBC system clock or a network source, depending on the PBX.

 

Configuring the SBC

SIP Server Table

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to SIP > SIP Server Tables.
  3. Create a new IP Server Table.

  4. Configure the new SIP Server Table. Refer to Creating and Modifying Entries in SIP Server Tables.

Transformation Table

For detailed configuration, refer to Creating and Modifying Entries to Transformation Tables.

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to Transformation
  3. Add a new Transformation Table.

  4. In the left navigation pane, click the Transformation table created in the previous step.

  5. Add Calling / Called Party Number transformation rules for each:
    1. PBX Endpoint
    2. PSTN Phone.
    3. SA/AA
    4. Called party's voicemail (VM) box

Call Routing Table

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to Call Routing Table.
  3. Add an entry to the Call Routing Table (for example, Calls from ISDN (PBX)). Refer to Creating and Modifying Entries to Call Routing Tables.
  4. Create two entries (for example, Calls from Exch and Calls From PSTN).

    In this deployment, three call route table entries are required for the relevant Signaling Groups.

Route Table for Calls from PBX phones

This table requires two entries:

  • Routing calls to Redirected party's VM boxes in Exchange 20xx Unified Messaging Server (eUMS).
  • Routing calls to 5xxx PSTN phones.

Route Table for Calls from Exchange Server

This table requires two entries:

  • Routing calls to 622x PBX phones via eUMS Auto Attendant or Subscriber Access prompts.
  • Routing calls to 5xxx PSTN phones via eUMS Auto Attendant or Subscriber Access prompts.

Route Table for Calls from PSTN phones

This table requires two entries:

  • Routing calls to 622x PBX phones.
  • Routing calls to 625x eUMS Auto Attendant or Subscriber Access numbers.

Port Configuration

For detailed configuration, refer to Configuring T1 Ports

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to Node Interfaces > Ports
  3. Click the expand () icon in the table next to the port used to connect the physical PRI line.
  4. Configure two Ports: T1 connection to PBX and T1 connection to PSTN (which will eventually be used in the relevant ISDN Signaling Groups.)

Signaling Groups

ISDN Signaling Group for PBX Connection

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to Signaling Groups.
  3. Click the Add ISDN SG text at the top of the Signaling Group Table.
  4. Configure the fields. Refer to Creating and Modifying ISDN Signaling Groups.
  5. Click OK.

SIP Signaling Group for Exchange 20xx Unified Messaging Server Connection

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to Signaling Groups.
  3. Click the Add SIP SG text at the top of the Signaling Group Table.
  4. Configure the fields. Refer to Creating and Modifying SIP Signaling Groups.
  5. Click OK.

ISDN Signaling Group for PSTN Connection

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to Signaling Groups.
  3. Click the Add ISDN SG text at the top of the Signaling Group Table.
  4. Configure the fields. Refer to Creating and Modifying ISDN Signaling Groups.
  5. Click OK.

System Timing Configuration

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to System > System Timing.
  3. Configure the Clock Source either as System or the Network, depending on your PBX timing settings. Refer to Configuring the System Clock Source

     

    In this exercise, the SBC node is reading the system time from the network therefore the configuration is done as shown below:
    For more information about system timing see, Configuring the System Clock Source.

SBC Signaling Group Status Verification

After completing the configuration steps, and the relevant configuration on Exchange 20xx Unified Messaging Server, verify the signaling group status:

  1. In the WebUI, click the Monitor tab.
  2. Verify that all three Ports are visible.