Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Include Page
Not_for_SWe
Not_for_SWe

Panel

In this section:

Table of Contents
maxLevel3

 

The Tenor can be used to provide FXS analog capability to the

Spacevars
0product
 (SBC), allowing for FAX connectivity. In this article, we describe the steps necessary to deploy a Tenor as an analog device in aSBC - Lync SBA topology. The overall configuration comprises three components: the Lync Server, the Tenor, and theSBC:

Note

In this article, G.711 voice codec is used and CNG Tone Detection is disabled:
 
When CNG detection is disabled, theSBC lets the Calling fax machine on either side, ISDN or SIP, to send CNG. However, theSBC is actively listening for and detecting the Fax Answer message that the Answering fax machine sends because Fax pass-thru is enabled.

 

The following diagrams depict the signaling and media flow of the Analog End Point of LYNC in this deployment.

Outbound Fax call flow using Lync call control (signaling and media)

Pagebreak

Inbound Fax call flow using Lync call control (signaling and media)

Related Information

In this deployment, following LYNC topology entities, PBX, and numbering plans are used:

 

Background Color
colorblue
FQDN
 

 

Background Color
colorblue
IP Address
 

 

Background Color
colorblue
Description
 

Background Color
colorblue
uxdemo.net

Background Color
colorblue
134.56.105.30

Background Color
colorblue
LYNC SBA Domain

Background Color
colorblue
rdc.uxdemo.net

Background Color
colorblue
134.56.105.30

Background Color
colorblue
DNS/AD/Ent. Root CA

Background Color
colorblue
sba247.uxdemo.net

Background Color
colorblue
134.56.105.247

Background Color
colorblue
FQDN of Lync SBA Pool

Background Color
colorblue
ux246.uxdemo.net

Background Color
colorblue
134.56.105.246

Background Color
colorblue
FQDN of the SBC GW

Background Color
colorblue
Tenor AF

Background Color
colorblue
134.56.105.41

Background Color
colorblue
Analog Device

Background Color
colorblue
Nortel Meridian

Background Color
colorblue
N/A

Background Color
colorblue
ISDN PBX

 

Background Color
colororange
LYNC SBA Users
 

 

Background Color
colororange
Line URI
 

Background Color
colororange
sip:SBAuser1@uxdemo.net

Background Color
colororange
tel:+15102461001

Background Color
colororange
sip:SBAuser2@uxdemo.net

Background Color
colororange
tel:+15102461002

 

Background Color
colorpurple
LYNC SBA ANALOG Users
 

 

Background Color
colorpurple
Line URI
 

Background Color
colorpurple
sip:ae11467d-d09d-4e78-ad2a-e4615b79ac57@Ribbon1000/2000DEMO.Ribbon (ANALOGph1)

Background Color
colorpurple
tel:+15102462001

Background Color
colorpurple
sip:80274280-9a22-43d9-b194-2640904c3e54@Ribbon SBC 1000/2000DEMO.Ribbon (ANALOGph2)

Background Color
colorpurple
tel:+15102462002

Background Color
colorpurple
sip:3f1e38d7-c8a3-425a-818c-bae3f2c28d62@Ribbon SBC 1000/2000DEMO.Ribbon (Fax1)

Background Color
colorpurple
tel:+15102462003

 

Background Color
colorgreen
Meridian Endpoints
 

 

Background Color
colorgreen
Extensions
 

Background Color
colorgreen
PBX Ph1

Background Color
colorgreen
ext: 6228

Background Color
colorgreen
PBX Ph2

Background Color
colorgreen
ext: 6222

Before You Begin

The SBC SBA must already be configured. If not, configure and deploy the Lync SBA following the instructions in Preparing for SBA Deployment - First Steps.

Lync Configuration

Creating analog End Point using the New-CsAnalogDevice Command

Analog Endpoints must be created from the Lync Management Shell using the New-CsAnalogDevice cmdlet.

  1. On the Lync Server, go to Start > Microsoft Lync Server 2010 > Lync Server Management Shell.
    Enter the command as shown below.

For Aanalog Phone Endpoints:

Code Block
New-CsAnalogDevice \-LineUri tel:+15102462001 \-DisplayName "Analogph1" \-RegistrarPool cspool.uxdemo.net \-AnalogFax $false \-Gateway ux246.uxdemo.net \-OU "ou=Analog,dc=uxdemo,dc=net"

For Analog FAX Endpoints:

Code Block
New-CsAnalogDevice \-LineUri tel:+15102462003 \-DisplayName "Fax1" \-RegistrarPool cspool.uxdemo.net \-AnalogFax $true \-Gateway ux246.uxdemo.net \-OU "ou=Analog,dc=uxdemo,dc=net"
Note

Before running the commands above, make sure that the relevant Organizational Unit(OU) (in this example it is named Analog) exists in Active Directory. On a machine that can access the Active Directory Users and Computers snap-in, launch the Active Directory Users and Computers snap-in and verify that OU is present as shown in below screenshot:

Panel
borderStylenone

Caption
0Figure
1Verify OU Is Present

  • Launch the Lync Management Shell and run the relevant commands to create both Analog Phone and Analog Fax Endpoints as shown in below screenshot:
Panel
borderStylenone

Caption
0Figure
1Launch Lync Management Shell

 

  • Verify in Active Directory Users and Computers snap-in that relevant users are created successfully in Analog Organizational Unit as shown below:
Panel
borderStylenone

Caption
0Figure
1Verify Users

Explanation of New-CsAnalogDevice

The New-CsAnalogDevice cmdlet instructs Lync to route calls from the analog device to the gateway specified in the -Gateway switch of the cmdlet; thus, ensuring that Fax calls will safely be transmitted over PSTN.

Tenor configuration

Requirements for Tenor

These instructions assume that:

  • The Tenor gateway is running P108-09-10 or newer software release.
  • The Tenor Configuration Manager is CM108-19-00 or newer.

Run the Tenor Wizard

  • Launch the Quintum Configuration Manager and connect to your Tenor Device
  • Upon connecting to the device, Configuration Wizard will run automatically
  • Follow the Wizard Steps and enter the relevant IP addresses, Analog Endpoint numbers..etc. as shown below
Panel
borderStylenone

Caption
0Figure
1Wizard Steps

  • For this exercise we are using DHCP for the Tenor IP address configuration
Panel
borderStylenone

Caption
0Figure
1IP Address Configuration - DHCP

  • Enter the DNS IP address which is used in LYNC SBA Deployment Topology
Panel
borderStylenone

Caption
0Figure
1IP Address Configuration - DNS

Panel
borderStylenone

Caption
0Figure
1Enter DNS IP Address

  • Verify that IP Address Configuration is completed as shown below
Panel
borderStylenone

Caption
0Figure
1Verify IP Address Configuration

  • Continue the wizard steps for Dial Plan Configuration
Panel
borderStylenone

Caption
0Figure
1Dial Plan Country

Panel
borderStylenone

Caption
0Figure
1Progress Tone Country

  • Verify that Dial Plan Configuration is completed as shown below
Panel
borderStylenone

Caption
0Figure
1Verify Dial Plan Configuration

  • Continue the wizard steps for Phone Port Configuration
Panel
borderStylenone

Caption
0Figure
1Phone Port Configuration

  • Enter the relevant Phone Number/Extension (in this example we are using 2001 and 2002 users for the Analog phone endpoints)
Panel
borderStylenone

Caption
0Figure
1Enter Phone Number/Extension - 2001

Panel
borderStylenone

Caption
0Figure
1Enter Phone Number/Extension - 2002

  • Click "Save/OK" and then the "Done" buttons
Panel
borderStylenone

Caption
0Figure
1Add Phone Number/Extension

 

Panel
borderStylenone

Caption
0Figure
1Configured Phone Number/Extension

 

  • Verify that Phone Port Configuration is completed as shown below
Panel
borderStylenone

Caption
0Figure
1Verify Phone Port Configuration

  • Continue the wizard steps for Multi Path Configuration
Panel
borderStylenone

Caption
0Figure
1Enable Pass Through Calls

Panel

Caption
0Figure
1Add Bypass Number

Panel
borderStylenone

Caption
0Figure
1Add Next Bypass Number

Panel
borderStylenone

Caption
0Figure
1Configure Bypass Number

  • Verify that Multi Path Configuration is completed as shown below
Panel
borderStylenone

Caption
0Figure
1Verify Multi Path Configuration

 

  • Continue the wizard steps for Line Port Configuration
Panel
borderStylenone

Caption
0Figure
1Line Port Configuration

  • Verify that Line Port Configuration is completed as shown below
Panel
borderStylenone

Caption
0Figure
1Verify Line Port Configuration

  • Continue the wizard steps for VoIP Routing Configuration
Panel
borderStylenone

Caption
0Figure
1VoIP Routing Configuration

  • Enter the SBC 2000 Gateway IP address in the Primary SIP Server IP/Domain Name field and the relevant Port (5060 in this case)
Panel
borderStylenone

Caption
0Figure
1Enter IP Address

 

  • Enter the SIP user information for the related 2001 and 2002 users
Panel
borderStylenone

Caption
0Figure
1Enter SIP User Information - 2001

Panel
borderStylenone

Caption
0Figure
1Enter SIP User Information - 2002

Panel
borderStylenone

Caption
0Figure
1SIP User Configuration

  • Verify that VoIP Routing Configuration is completed as shown below
Panel
borderStylenone

Caption
0Figure
1Verify VoIP Routing Configuration

  • Continue the wizard steps for Idle Channel Configuration
Panel
borderStylenone

Caption
0Figure
1Idle Channel Configuration

  • Verify that Idle Channel Configuration is completed as shown below
Panel
borderStylenone

Caption
0Figure
1Verify Idle Channel Configuration

  • Click the Accept button on Configuration Summary to complete the wizard run
Panel
borderStylenone

Caption
0Figure
1Complete Wizard Run

  • Click OK to restart the Tenor device as shown below
Panel
borderStylenone

Caption
0Figure
1Restart Tenor Device

Pagebreak

Additional Post-wizard Settings and Configuration Verification

Verifying the SIP Signaling Group Options

  • Reconnect to Tenor Device using the Configuration Manager and Verify that SIP Signaling Group is configured In General Tab as shown below
Panel
borderStylenone

Caption
0Figure
1Reconnect to Tenor Device

  • Verify that SIP Signaling Group is configured in Advanced Tab as shown below
Warning

The Transport Type must be set to UDP.

Panel
borderStylenone

Caption
0Figure
1Verify SIP Signaling Group Is Configured

Pagebreak

Verify that the Silence Suppression parameter in the IP Routing Group is disabled

Panel
borderStylenone

Caption
0Figure
1Disable Silence Suppression

Verify the Tx/Rx Gain Values in the CAS Signaling Groups

Verify the following settings in Tenor:

CAS Signaling Group

Rx Gain

Tx Gain

CAS Signaling Group - Phone:

-6

0

CAS Signaling Group - Line:

6

0

  • Verify Tx/Rx gain values in the CAS signaling groups - Phone
Panel
borderStylenone

Caption
0Figure
1CAS Signaling Group - Phone

  • Verify Tx/Rx gain values in the CAS signaling groups - Line
Panel
borderStylenone

Caption
0Figure
1CAS Signaling Group - Line

Pagebreak

Creating a Route For Calls From Tenor to Lync

  • In Configuration Manager, right click on Number Tables in left pane and select New as shown below
Panel
borderStylenone

Caption
0Figure
1Create New Number Table

 

  • Create a new Number Tables to allow Analog Endpoints to be able to make calls to LYNC endpoints as wells as to PBX endpoints as shown below
Panel
borderStylenone

Caption
0Figure
1Enter Number Table Information

  • Create an entry in the Routing Table as shown below
Panel
borderStylenone

Caption
0Figure
1Routing Table Entry

  • Modify the default Number Table to allow incoming calls to Tenor Device as shown below
Panel
borderStylenone

Caption
0Figure
1Modify Default Number Table

  • Verify that "Use Routing Table" option is selected in Gateway configuration field as shown below
Panel
borderStylenone

Caption
0Figure
1Select Use Routing Table

Verifying Codec Selection

Info

Ensure that the codec settings are identical with the matching codec in SBC.
Use only G.711U and/or G.711A.

  • Verify that Voice Codec settings are configured correctly as shown below
Panel
borderStylenone

Caption
0Figure
1Verify Voice Codec - 1

Panel
borderStylenone

Caption
0Figure
1Verify Voice Codec - 2

Pagebreak

Verify Supplementary Services Enabled

Tenor supports the following supplementary services - Hold/Unhold, Unattended (Blind) Transfer, and Attended (Consultative) Transfer. These features can be enabled and configured using either a Line Circuit Routing Group (LCRG) or Trunk Circuit Routing Group (TCRG). Follow the configuration steps below:

  • Verify that "Detect Flash Hook Signal" option is selected in CAS Signaling Group-phone > Signaling Tab
Panel
borderStylenone

Caption
0Figure
1Select Detect Flash Hook Signal

  • Verify that "Generate Flash Hook Signal" option is selected in CAS Signaling Group-line > Signaling Tab
Panel
borderStylenone

Caption
0Figure
1Select Generate Flash Hook Signal

  • Verify that Call Services are selected in Line Circuit Routing Group-phone > Call Services Tab
Panel
borderStylenone

Caption
0Figure
1Select Call Services

Change Fax Relay from T.38 without Fallback to G.711

  • Make sure that Fax Relay is set to G.711.

    Info

    The codec should be either G.711U or G.711A depending on your particular environment.

  • Enable both, Fax Relay and Fax Modem Coding:
    • Fax Relay: This command configures how the Tenor signals the other end to tell the peer how to switch over to the correct protocol for a fax call. When FaxRelay is set to anything other than 0, there will be a short delay in training as the Tenor determines whether the device at the other end is a fax machine or a modem
    • Fax Modem Coding: Enable the Fax Modem Coding configuration option if the Tenor will be used to make modem calls (remote door/elevator control).
      When the Tenor is configured for modem over IP calls, FaxModemCoding allows you to select which codec will be used.
      When FaxRelay is set to 0 (Disabled), Modem over IP (MoIP) takes over, and all fax calls will be sent as MoIP passthrough with the codec specified by the FaxModemCoding setting.
      When FaxRelay is set to anything other than 0, there will be a short delay in training as the Tenor determines whether the device at the other end is a fax machine or a modem.
Panel
borderStylenone

Caption
0Figure
1Change Fax Relay

Configuring the Relay of Calling Name (CNAM)

The configuration of the Calling Name (CNAM) is optional. Tenor can relay CNAM in both directions Analog to SIP and SIP to Analog.

Div
classpdf6pttext

Caption
0Table
1Relay of Calling Name

 

Analog to SIP

SIP to Analog

Not send CNAM

VoIP Configuration > IP Routing Groups > IP Routing Group-default > ANI > Relay Calling Name - Disabled

Circuit Configuration > Signaling Config > CAS Signaling Groups > CAS Signaling Group-phone > Relay Calling name - Disabled

Send the CNAM

Send the CNAM of each analog line as configured in the DN Channel Map:

  1. First add the Calling Name in the channel mapping for each channel.
    VoIP Configuration > DN Channel Map > Calling Name - Free text
  2. Secondly select the global default behavior.
    VoIP Configuration > IP Routing Group > IP Routing Group-default > ANI > Relay Calling name - Relay CNAM in INVITE

Send the CNAM from the SIP call leg.
Circuit Configuration > Signaling Config > CAS Signaling Groups > CAS Signaling Group-phone > Signaling > Relay Calling Name - Relay CNAM

Send default CNAM

Send a default CNAM for all calls regardless of the Calling Name of the originating channel.
VoIP Configuration > IP Routing Group > IP Routing Group-default > ANI > Relay Calling name > Relay Default CNAM > Default Calling Name - Free text

Send a default CNAM for all calls regardless of the Calling Name of the originating channel.
Circuit Configuration > Signaling Config > CAS Signaling Groups > CAS Signaling Group-phone > Signaling > Relay Calling Name > Relay Default CNAM > Default Calling Name - Free text

Sample Tenor AF Configuration File - P108-09-10

Noprint

Click to see Tenor AF DB file Software version P108-09-10...

Toggle Cloak

Cloak
titleClick to read more...
none

Sample Tenor AF Configuration File - P107-09-10

Noprint

Click to see Tenor AF DB file Software version P107-09-10...

Toggle Cloak

Cloak
titleClick to read more...
none

Ribbon SBC 1000/2000 configuration

Requirements and Prerequisites

  • This document assumes thatSBC Lync 2010 wizard was ran prior to the configuration
  • Running the Lync 2010 wizard will ensure SRTP towards Lync is set to Required
  • Media bypass must be enabled in Lync

SIP Registrar Table

  • Browse toSBC to SBC 2000 WebUI > Settings Tab > SIP / Local Registrars (in left pane)
  • Click on Add (plus) button and add a SIP Local Registrar Entry as shown below
Panel
borderStylenone

Caption
0Figure
1Add SIP Local Registrar Entry

Image Removed 

  • .

Media List Configuration

  • Browse to SBC 2000 WebUI > Settings Tab > Media List (in left pane)
  • Click on Add (plus) button and add a Media List Entry as shown below. For details, refer to Creating and Modifying Media Lists.

Make sure to have following settings are configured in Tenor Media List:

Background Color
colorblue
CNG

Background Color
colorblue
Disabled

Background Color
colorblue
Fax passthru

Background Color
colorblue
Enabled

Background Color
colorblue
Modem Passthru

Background Color
colorblue
Enabled

Background Color
colorblue
Silence Suppression

Background Color
colorblue
Enabled

Background Color
colorblue
Rx/Tx Gain

Background Color
colorblue
0

panel

 

borderStylenone

Caption
0Figure
1Add Media List

Image Removed

Translation Table

  • Browse to SBC

 

Translation Table

  • Browse to SBC 2000 WebUI > Settings Tab > Translation (in left pane)
  • Click on Add (plus) button and add a Translation Table with following entry as shown below
Panel
borderStylenone

 

Caption
0Figure
1Add Translation Table
Image Removed

Signaling Group (uses UDP only)

  • Browse to SBC 2000 WebUI > Settings Tab > Signaling Groups (in left pane).
  • Click on Add SIP SG button and add a SIP Signaling Group for Tenor Device connectivity as shown below
Panel
borderStylenone

 

Caption
0Figure
1Add SIP Signaling Group
Image Removed

Call Routing Table

  • Browse to SBC 2000 WebUI > Settings Tab > Call Routing Table (in left pane).
  • Click on SIP to ISDN Call Route Table and hit Add (plus) button to add an entry to route calls to Tenor (for those with 2xxx extension in this example)
Panel
borderStylenone

Caption
0Figure
1Add Entry to Route Calls

Image Removed

 

  • .
  • Re-sequence the Call Route entries in this table to make sure ensure that calls to 2xxx extensions (Analog Endpoints) will use the entry that you just created in previous step
Panel
borderStylenone
Caption
0Figure
1Re-sequence Call Route Entry
Image Removed
  • the entry created in previous step.

 

Troubleshooting Techniques

Troubleshooting FAX Calls Between the Tenor and PSTN

  • If you are getting comm errors on the Fax machine, check the following resources for solutions:
  • If faxes are failing, check the E1 port counters for slips and frame errors.

    Noprint

    Click here to see a screenshot of a "bad" E1 line...

    Toggle Cloak

    Cloak
    titleClick to read more...
    noneFigureScreenshot of E1 LineINLINE

    For details, refer to Viewing Port Counters and Channel Details.

  • The frame errors and the slips counters must not be increasing. You can check if they are increasing by resetting the counters. If the errors are increasing, the issue could be caused by one of the following:
    • System timing / clocking. Check the clock source (System -> System Timing) - it should be set to Network/T1/E1 port and not System/Free run. If the clock source is set to Network, but the Current Active Clock shows as Free run, click Apply and ensure that Current Active Clock is now set to Primary. This should resolve the clocking issue as long as the error counters do not increase.
    • If the Tenor is not configured to register with the SBC local SIP registrar and the SIP Signaling group in SBC constantly goes down, check the contents of the var_config.cfg file (from Tenor Config Manager -> Tools -> Var_config -> Edit) and delete the line specifying the transport protocol as in P108 it is obsolete.
    • Bad E1 cable. Replace the cable.
    • Faulty RJ45 jacks. Replace the cable or fix the Rj45 jacks.
    • Faulty RJ45 socket. Try configuring a different T1/E1 port. Visually check the pins in the E1/T1 ports for any differences.

Pagebreak