You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

 

This article describes how to configure the 

Unable to show "metadata-from": No such page "_space_variables"
such that it can be deployed downstream in a PBX - 
Unable to show "metadata-from": No such page "_space_variables"
- MS Exchange 2007/2010 Unified Messaging Server
topology.

Configuring the 

Unable to show "metadata-from": No such page "_space_variables"
for this type of deployment requires specific configuration steps to be completed in the following order:

Topology

Configuration Overview

The configuration process comprises the following 10 steps, each of which is explained in detail in the body of this article.

Configuration Overview

  1. Default Tone Table: A factory default 
    Unable to show "metadata-from": No such page "_space_variables"
    configuration contains the "Default Tone Table" entry. This article's configuration requires it, ensure its presence in your configuration.
  2. Default Media Profile(s): the default G.711A/Mu-Law profile is used in this example.
  3. Default Media List: the Default Media List is used in this example.
  4. Create a SIP Server Table: In this example we add a SIP Server table entry for the Exchange 2007/2010 Server.
  5. Create a SIP Profile: you can create a custom SIP Profile or use the default. The default is used in this example.
  6. Create a Transformation Table: this table is used in the relate Call Routing tables and for Called/Calling Number transformations.
  7. Create a Call Routing Table: in this example we create two table entries, one for ISDN and another for SIP. They are required in the relevant Signaling Groups.
  8. Configure a DS1 Port: this port is associated with the Physical PRI (T1/E1) connection.
  9. Create two Signaling Groups: One Signaling Group will be designated for for SIP and the other is for ISDN.
  10. Set the System Timing: you can configure the Clock Source to use the 
    Unable to show "metadata-from": No such page "_space_variables"
    system clock or a network source, depending on your PBX.

Configuring SBC Edge

SIP WebUI Login and verification of the Node Level Settings:

  1. In the WebUI, click on Settings.

  2. In the left navigation pane, go to System > Node-Level Settings.

  3. Verify that the settings are configured correctly as indicated below.

    Node-Level Settings

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. Click on the Create () icon.
    (info) The SIP Server Tables page is a table of SIP Server Tables.

  4. Configure the new SIP Server Table as shown in the illustration below.

    Create SIP Server Table


     

  5. In the left navigation pane, go to SIP > SIP Server Tables > (The table you created in the previous step).

  6. Click the Create SIP Server > IP/FQDN.

  7. Enter the IP address of the eUM Server in the Host as shown below.

  8. Click OK.

    Create SIP Server Entry

Transformation Table

  1. In the WebUI, click the Settings tab.

  2. In the left navigation pane, go to Transformation.

  3. Click the Create () icon.

  4. Create a new Transformation Table.

    Create Transformation Table



  5. In the left navigation pane, go to Transformation >(the table created in the previous step).

  6. Add an entry as shown below.

    Add Entry

Call Routing Table

  1. In the WebUI, click the Settings tab.

  2. In the left navigation pane, go to Call Routing Table.

  3. Create two entries (Calls from ISDN, Calls to ISDN) as shown below.

    Create Two Entries

Port Configuration

  1. In the WebUI, click the Settings tab.

  2. In the left navigation pane, go to Node Interfaces > Ports.

  3. Click the port that you wish to connect to the physical PRI line.

  4. Fill in the fields as shown below.

    Port Configuration

Signaling Groups

  1. In the WebUI, click the Settings tab.

  2. In the left navigation pane, go to Signaling Groups.
    Click Create Signaling Group and select ISDN Signaling Group text at the top of the table.

  3. Fill in the fields as shown below.

    Create ISDN Signaling Group

     
     

     

  1. In the WebUI, click the Settings tab.

  2. In the left navigation pane, go to Signaling Groups.

  3. Click Create Signaling Group and select SIP Signaling Group.

  4. Fill in the fields as shown below.

    Create SIP Signaling Group

The Signaling Groups should appear like the following after adding the ISDN and SIP Signaling Groups:

Signaling Group Table

Call Routing Table Entries

  1. In the WebUI, click the Settings tab.

  2. In the left navigation pane, go to Call Routing Table > (call route entry for ISDN).

  3. Fill in the fields as shown below.

    Call Route Entry For ISDN

     

  1. In the WebUI, click the Settings tab.

  2. In the left navigation pane, go to Call Routing Table > (call route entry for SIP)

  3. Fill in the fields as shown below.

    Call Route Entry For SIP

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.
    (info) In this exercise, the Sonus SBC 1000/2000 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.

    System Timing Configuration

Exchange 20xx UM Server Configuration Steps

Exchange 20xx UM Server and Sonus SBC 2000 Gateway integration requires the following items to be configured on Exchange Management Console:

  1. A Dial Plan configuration with:
    • Subscriber Access Number
    • UM Mailbox Policy
    • UM IP Gateway
    • UM Auto Attendant

  2. UM Dial Plan association

Dial Plan Configuration

  • Logon to Exchange / UM Server PC
  • Launch Exchange Management Console
  • Create a New Dial Plan using the following information:

Subscriber Access Number

Subscriber Access Number

Dialing Rule Group for 4 digit dialing used in this example:

Dialing Rule Group

Dialing Restriction

Dialing Restriction

UM Mailbox Policy

UM Mailbox Policy

UM IP Gateway

UM IP Gateway

UM Auto Attendants

UM Auto Attendants

Dialing Restriction

Associating Dial Plan to UM Server

  • Logon to Exchange / UM Server PC.
  • Launch Exchange Management Console.
  • Associate the relevant dial plan with the UM Server as shown below:

    Associate Dial Plan

SBC Edge Signaling Group Status Verification

After having completed both 

Unable to show "metadata-from": No such page "_space_variables"
and Exchange 20xx Unified Messaging Server configuration steps, using the monitor view, ensure both PRI and SIP ports are up and in idle as shown below:

Monitor View

Common Use Case

In a PBX – 

Unable to show "metadata-from": No such page "_space_variables"
– eUM Server scenario the following configuration steps allow PBX users to have UM voice mail boxes:

  1. On the PBX, a user must be configured with a diversion number as the Subscriber Access Number (i.e: 6255).
    (info) This number is configured in the Exchange Management Console >> Organization Configuration >> Unified Messaging >> UM Dial Plan >> Subscriber Access tab.

  2. On the eUM, the relevant user entry must be enabled for Unified Messaging as shown below:

    eUM



  3. When a PBX user-1 receives a call (i.e., from PBX user-2) and does not answer, the call is diverted by the PBX to the diversion number (6225). The call arrives at the
    Unable to show "metadata-from": No such page "_space_variables"
    , and the 
    Unable to show "metadata-from": No such page "_space_variables"
    sends an INVITE to the UM Server. Once the call reaches the UM Server, the Calling Party can leave a message in PBX user-1's voice mail box.

  4. In addition, PBX user(s) can call a Subscriber Access (SA) Number (6255) and an Auto Attendant (AA) Number (6256) via 4 digit dialing in above setup to navigate UM prompts via DTMF or voice commands

 

  • No labels