Guest

Telephony Signaling

Integrate the Cisco IOS Gateway to the MX/Alliance Turret via T1-CAS

Hierarchical Navigation

Document ID: 71708

Updated: Jan 23, 2007

   Download PDF
   Print

Introduction

This document contains the solution for how to integrate a Cisco IOS® Gateway with an MX/Alliance Turret System using T1-Channel Associated Signaling (CAS).

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

  • T1-CAS

  • How to configure the Cisco IOS Gateway for voice

Components Used

This document is not restricted to specific software and hardware versions.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Problem

Consider this topology:

  • IP Phone-->Cisco CallManager--H.323-->2851--T1CAS-->MX/Alliance Turret System

The MX/Alliance T1 is configured for Foreign Exchange Station (FXS) loopstart and Super Frame (SF)/Alternate Mark Inversion (AMI). When the T1 controller on the Cisco 2851 Integrated Services Router is configured for Foreign Exchange Office (FXO) loopstart and SF/AMI, calls from the IP phone to the turret work fine. But the 2851 never sees an incoming seizure from the MX/Alliance due to non-standard signaling used by the MX/Alliance.

Solution

The solution is to insert an RAD Vmux 2100 Circuit Emulator/Transport Device between the Cisco IOS Gateway T1 Controller and the MX/Alliance Turret System. Because the Vmux 2100 converts time-division multiplex (TDM)-to-IP and back to TDM, the Cisco IOS Gateway T1 Controller can be configured for E&M Immediate-Start, ESF/B8Zs while the MZ/Alliance remains configured as T1 FXS loopstart, SF/AMI.

Complete these steps:

  1. Connect the Vmux 2100 to the Cisco IOS Gateway T1 Controller and the MX/Alliance Turret System according to the instructions provided by the manufacturer.

  2. Configure the Cisco IOS Gateway using the steps outlined in Private Line Automatic Ringdown for Trading Turrets.

Related Information

Updated: Jan 23, 2007
Document ID: 71708