Amtelco 258A006 H.110 MC3 Interconnect & Conference Board User Manual

Amtelco (American Tel-A-Systems, Inc. H.110 MC3 Interconnect & Conference Board Users Manual

UserManual.wiki >

258A006 User Manual >

Contents

1. Users Manual
2. users manual

Users Manual

Infinity Series H.110 MC3 Multi-chassis Interconnect &Conference BoardTECHNICAL MANUALDocumentation Revision 0.3: February 14, 2000Copyright © 2000by American Tel-A-Systems, Inc.All rights reserved.258M000

This page left intentionally blank

• i •The H.110 MC3/Conference BoardContents1.0 INTRODUCTION ............................................. 1-11.1 Features and Capabilities .............................. 1-21.1.1 The H.110 Bus ............................... 1-21.1.2 The MC3 Bus Interface ......................... 1-31.1.3 Conferencing ................................. 1-41.1.4 DSP Functions ............................... 1-41.1.5 Analog Audio Port ............................. 1-41.1.6 Clock Modes ................................. 1-51.1.7 Hot Swap Capability ........................... 1-51.1.8 Message Passing .............................. 1-51.1.9 Flash EAROM for Firmware ..................... 1-61.2 How to Use This Manual .............................. 1-62.0 QUICK START .............................................. 2-13.0 INSTALLATION ............................................. 3-13.1 PCI Configuration ................................... 3-13.2 Jumpers & Headers .................................. 3-23.3 Connectors: P5, P6 and J1 ............................ 3-33.4 Installation ......................................... 3-33.5 Hot Swapping a Board ................................ 3-44.0 INITIALIZATION ............................................ 4-14.1 PCI Initialization .................................... 4-14.2 Initialization Commands .............................. 4-25.0 COMMUNICATING WITH THE HOST ............................... 5-15.1 Command and Response Protocol ....................... 5-25.1.1 Sending Commands to the Board ................. 5-25.1.2 Reading Messages From the Board ................ 5-25.1.3 Reading Board Information ...................... 5-3

• ii •The H.110 MC3/Conference Board5.0 COMMUNICATING WITH THE PC (CONTINUED):5.2 Interrupts .......................................... 5-35.2.1 Interrupt Initialization .......................... 5-45.2.2 Step-by-Step Summary ......................... 5-45.3 Commands and Responses ............................. 5-55.3.1 Characteristics of Command Strings ............... 5-55.3.2 Command Parameters .......................... 5-55.3.3 Commands to the H.110 MC3/Conference Board ..... 5-6< Conference Commands ....................... 5-6< MC3 Bus Commands ......................... 5-7< Analog Port Control .......................... 5-7< MVIP Compatibility Commands ................ 5-8< Interrupt Control Commands ................... 5-8< Reset Commands ............................ 5-8< Setup Commands ............................ 5-8< Version Requests ............................ 5-9< Download Commands ......................... 5-9< Diagnostics ................................. 5-9 5.4.4 Responses from the H.110 MC3/Conference Board .. 5-10< Acknowledgments ........................... 5-10< Error Messages ............................. 5-10< Query Responses ............................ 5-10< DTMF Detection Messages ................... 5-11< Diagnostic Responses ........................ 5-116.0 THE H.110 BUS, CLOCK MODES & MC3 BUS ..................... 6-16.1 The H.110 Bus ...................................... 6-16.2 Clock Modes ....................................... 6-26.2.1 Slave Mode .................................. 6-26.2.2 Primary Master Mode .......................... 6-36.2.3 Secondary Master Mode ........................ 6-46.2.4 Clock Fallback ................................ 6-56.2.5 Clock Errors .................................. 6-56.3 The MC3 Bus ....................................... 6-66.3.1 MC3 Ring Errors .............................. 6-66.3.2 Ring Status LEDs .............................. 6-76.4 MC3 Ring Configurations ............................. 6-8

• iii •The H.110 MC3/Conference Board6.0 THE H.110 BUS, CLOCK MODES & MC3 BUS (CONTINUED):6.5 Configuration Information ............................. 6-96.6 Hot Swap .......................................... 6-97.0 USING THE MC3 BUS ........................................ 7-17.1 Initialization ........................................ 7-17.2 MC3 Switching Commands ........................... 7-37.3 Ring Errors ......................................... 7-47.4 Ring Redundancy & Fallback .......................... 7-57.5 Loopback Modes .................................... 7-68.0 CT BUS BUS SWITCHING ..................................... 8-18.1 The H.110 Switching Hardware ......................... 8-18.2 MVIP-95 Compatibility Commands ..................... 8-18.3 The Analog Port ..................................... 8-39.0 CONFERENCING ............................................ 9-19.1 The Conferencing Hardware ........................... 9-19.1.1 Conference Handles ............................ 9-29.1.2 Command Set ................................. 9-29.1.3 Attenuation & Noise Threshold ................... 9-29.1.4 DSP Facilities ................................. 9-39.2 Controlling Conferences .............................. 9-49.3 Changing the Attenuation and Noise Threshold ............ 9-59.4 DTMF Detection .................................... 9-69.5 Energy Detection .................................... 9-79.6 2 kHz. Tone Generation and Detection ................... 9-79.7 Conferencing Examples ............................... 9-810.0 DIAGNOSTICS & ERROR MESSAGES ............................ 10-110.1 Diagnostic Commands ............................... 10-110.2 Error Messages ..................................... 10-310.3 QM Queries ....................................... 10-4

• iv •The H.110 MC3/Conference BoardAPPENDIXES:A. Environmental Specifications ......................... A-1B. Notes on H.110 MC3 Redundancy ......................B-1Infinity Series H.110 MC3 Multi-Chassis Interconnect &Conference Board Technical ManualCopyright © American Tel-A-Systems, Inc., February 2000Printed in U.S.A. All rights reserved.This document and the information herein is proprietary to American Tel-A-Systems, Inc.It is provided and accepted in confidence only for use in the installation, operation, repairand maintenance of Amtelco equipment by the original owner. It also may be used forevaluation purposes if submitted with the prospect of sale of equipment.This document is not transferable. No part of this document may be reproduced in wholeor in part, by any means, including chemical, electronic, digital, xerographic, facsimile,recording, or other, without the express written permission of American Tel-A-Systems,Inc.The following statement is in lieu of a trademark symbol with every occurrence oftrademarked names: trademarked names are used in this document only in an editorialfashion, and to the benefit of the trademark owner with no intention of infringement of thetrademark. "MVIP", “H-MVIP” and “MVIP-90” are registered trademarks of GO-MVIP. “SCSA” and “SCbus” are registered trademarks of the Dialogic Corportation.“CT bus” and “ECTF” are registered trademarks of the Enterprise Computer TelephonyForumAmerican Tel-A-System, Inc.800-356-9148• 4800 Curtin Drive • McFarland, WI 53558 •• 4145 North Service Road, Suite 200 • Burlington, Ontario L7L 6A3 •• 258M000 •

• v •The H.110 MC3/Conference BoardFCC Part 15 RequirementsWARNING: This equipment generates, uses, and can radiate radio frequency energy andif not installed and used in accordance with the instruction manual, may cause interferenceto radio communications. Operation of this equipment in a residential area is likely to causeinterference in which case the user at his own expense will be required to take whatevermeasures may be required to correct the interference.FCC Part 68 RegistrationThis equipment is registered with the FCC under Part 68 as a component device for usewith any generic PC Type computer or compatible. In order for FCC registration of thisproduct to be retained, all other products used in conjunction with this product to provideyour telephony function must also be FCC Part 68 registered for use with these hosts. Ifany of these components are not registered, then you are required to seek FCC Part 68registration of the assembled equipment prior to connection to the telephone network. Part68 registration specifies that you are required to maintain the approval and as such becomeresponsible for the following:-any component device added to your equipment, whether it bears componentregistration or not, will require that a Part 68 compliance evaluation is done andpossibly that you have testing performed and make a modification filing to the FCCbefore that new component can be used;-any modification/update made by a manufacturer to any component device withinyour equipment, will require that a Part 68 compliance evaluation is done andpossibly that you have testing performed and make a modification filing to the FCCbefore the new component can be used;-if you continue to assemble additional quantities of this compound equipment, youare required to comply with the FCC’s Continuing Compliance requirements.The telephone company has the right to request the registration information.The telephone company has the right to temporarily discontinue service. They are requiredto provide notification and advise of the right to file a complaint.In case of trouble, you may be required to disconnect the board from the telephone linesuntil the problem is resolved.

• vi •The H.110 MC3/Conference BoardThe authorized repair center is:American Tel-A-System, Inc.800-356-91484800 Curtin DriveMcFarland, WI 53558There are no user serviceable components on the board. All repairs should beaccomplished by returning the board to Amtelco with a description of the problem.Canadian CustomersCP-01, Issue 8, Part 1Section 14.1Notice: “The industry Canada label identifies certified equipment. Thiscertification means that the equipment meets certain telecommunications networkprotective, operational and safety requirements as prescribed in the appropriateTerminal Equipment Technical Requirements document(s). The Department doesnot guarantee the equipment will operate to the user’s satisfaction.Before installing this equipment, users should ensure that it is permissible to beconnected to the facilities of the local telecommunications company. Theequipment must also be installed using an acceptable method of connection. Thecustomer should be aware that compliance with the above conditions may notprevent degradation of service in some situations.Repairs of certified equipment should be coordinated by a representativedesignated by the supplier. Any repairs or alterations made by the user to thisequipment, or equipment malfunctions, may give the telecommunications companycause to request the user to disconnect the equipment.Users should ensure for their own protection that the electrical ground connectionsof the power utility, telephone lines and internal metallic water pipe system, irpresent, are connected together. This precaution may be particularly important inrural areas.CAUTION: Users should not attempt to make such connections themselves, butshould contact the appropriate electric inspection authority, or electrician, asappropriate.

Introduction • 1-1 •The H.110 MC3/Conference Board1.0 IntroductionThe Infinity Series H.110 MC3 Multi-chassis Interconnect & ConferenceBoard is designed to provide a high capacity interconnect path betweenmultiple computers using the H.110 bus to connect computer telephonyboards within a CompactPCI chassis. This path is provided by fiber-opticlinks conforming to the MC3 standard and operating at the OC3 bit rate of155 Mbps. Provisions are included for supporting dual counter rotatingrings for redundancy or higher capacity.In addition to the multi-chassis function, the board is equipped withenhanced conferencing facilities for up to 42 conferences with a total of128 participants. Enhanced features include individual DTMF detection foreach conference participant, a “clamping” function to prevent confereesfrom hearing DTMF tones generated by other conferees, and energydetection capabilities for conference inputs. A bidirectional analog port isalso provided for such functions as music on hold and monitoring.The H.110 bus was devised by the Enterprise Computer Telephony Forum(ECTF) to provide a single telecom bus for the entire industry. It isintended for add-in boards using the CompactPCI form factor. A varietyof boards are available from a number of different vendors. TheCompactPCI and H.110 specifications also provide for hot swapcapabilities for use in high availability applications. The MC3 bus is achassis interconnect standard promulgated by the GO-MVIP standardsbody.The board is equipped with a processor that can be used to control thelower level functions of the board. The host PC controls the board usingmessages passed through dual-ported RAM. The board shares a commonmessage passing and control scheme with other Infinity Series boards.

Introduction• 1-2 •The H.110 MC3/Conference BoardFigure 1: H.110 MC3/ConferenceBoard Functional Areas1.1 Features and CapabilitiesThis section presents an overview of the features and capabilities of theInfinity Series H.110 MC3 Multi-chassis Interconnect and ConferencingBoard.1.1.1 H.110 BusThe H.110 bus is a digital bus for transporting PCM (Pulse CodeModulation) signals between telephony boards. It was created by theECTF to provide a common bus structure for future development thatwould end the “bus wars” between the various legacy busses such as theSCbus and the MVIP bus.PCM is a standard method of digitizing phone signals. It involves encodingeach channel at an 8 kHz rate using eight bits. The signals from multiplechannels are then combined into a frame. On the H.110 bus, each frameconsists of 128 channels or timeslots. The bit rate of the H.110 bus is8.192 MHZ. Thirty-two wires, also called streams, each carrying 128

Introduction • 1-3 •The H.110 MC3/Conference Boardtimeslots, are combined to form the bus, and provide a total of 4096timeslots. Two timeslots are required for a full conversation, one for eachtalker.In addition to the streams, a number of other signals necessary to maintainsynchronization between all the boards in the system are carried on the bus.These signals provide the clocking and framing information. Redundantclocks are provided to aid in recovery if the primary clock should fail.The H.110 bus consists of backplane connections on a 6U CompactPCIbackplane that is used to interconnect the boards in the system. The CTBus connections are made through the J4/P4 connector. The electrical andmechanical requirements of H.110 boards are tightly specified to insure thereliability and consistent performance of the CT Bus in any validconfiguration of conforming boards.1.1.2 The MC3 Bus InterfaceThe MC3 bus was devised by GO-MVIP as a means of providing a largenumber of 64 kbps channels between PC chassis using the MVIP bus forintra-chassis connections. In the interest of minimizing cost and takingadvantage of existing hardware, the physical interface uses the samearchitecture as that used by the SONET standard operating at the OC3 bitrate of 155 Mbps.Each link consists of a full duplex fiber-optic cable that can support 2430channels. Seven of these channels are dedicated to framing purposes. TheMC3 standard arranges two of these fiber links in dual counter rotatingrings. The two rings can be used to provide redundancy against ring orchassis failure or they can be used to double the capacity. Each node ofthe MC3 structure provides bypass, drop and insert capabilities for each ofthe 64 kbps channels.The Infinity Series H.110 MC3/Conference Board provides up to 1024connections in each direction between the MC3 and H.110 busses.

Introduction• 1-4 •The H.110 MC3/Conference Board1.1.3 ConferencingIn addition to support for the MC3 bus, the H.110 MC3/Conference Boardalso includes enhanced conferencing facilities. Up to 42 simultaneousconferences can be supported with a total of 128 participants. The transmitand receive attenuation of each conferee can be controlled independentlyimproving audio quality and making larger conferences practical. As aseparate resource connected directly to the H.110 bus the conferencefacilities can connect to sources both within and external to the PC. Whenenabled, the conference facilities reduce the MC3 connectivity by 128.1.1.4 DSP FunctionsThe H.110 MC3/Conference Board is equipped with four DSP’s associatedwith the conferencing facilities. A DTMF detector is available for eachpotential conferee. The DSPs also provide a “clamping” feature whichwhen enabled will temporarily interrupt a connection when a DTMF digitis detected. This can be used to prevent other members of a conferencefrom hearing a DTMF tone generated by a conferee. There is also anenergy detection capability that can be used to detect the loudest talkers ina conference.In addition to DTMF tone detection, the DSPs can be used to generate anddetect 2 kHz. tones which are used for performing continuity checks forSignaling System 7.1.1.5 Analog Audio PortThe H.110 MC3/Conference Board also provides a bidirectional analog portthat can be used for such purposes as providing music on hold ormonitoring.

Introduction • 1-5 •The H.110 MC3/Conference Board1.1.6 Clock ModesThe H.110 MC3/Conference Board can operate in a variety of clockmodes. Modes are available so that the master clock can either be derivedfrom the H.110 bus, one of the MC3 rings, or be generated internally onthe MC3/Conference Board. The clock redundancy and clock fallbackfunctions of the H.110 bus are also supported so that the H.110 MC3Board can be set to provide a clock to the H.110 bus if the master clock onthat bus should fail.1.1.7 Hot Swap CapabilityThe H.110 Specification includes “hot swap” capability. This capabilityallows for the insertion and removal of boards from a live system. Notonly are there provisions for controlling the electrical signals to preventdisruption when inserting and removing boards, but also for informingdrivers and applications so that the board resources can be managed as theyare added or deleted. Each H.110 board is provided with a blue LED thatis used to inform an operator when it is safe to insert or remove a board.1.1.8 Message PassingThe board occupies 8K of memory space on the host PC. This 8K mayreside anywhere within the PC’s address space. As a CompactPCI board,the address and interrupt of the board is assigned at boot time. Themessage passing scheme used by the Infinity Series H.110MC3/Conference Board is identical to that of the other Infinity SeriesH.110 boards, allowing for the easy combination of a variety of InfinitySeries H.110 boards in a single system.The message passing scheme and message syntax of Infinity Series H.110boards is similar to that of the older XDS series of MVIP and SCbusboards. This facilitates the easy migration from ISA and PCI systems todesigns using CompactPCI boards.

Introduction• 1-6 •The H.110 MC3/Conference Board1.1.9 Flash EAROM for FirmwareThe firmware for both the main processor and for the DSP’s is containedin Flash EAROM. This allows for easy upgrades of the firmware on theboard in the field without requiring time consuming downloads every timea system boots. Once reprogrammed, the new firmware is retained evenwhen the power is removed. The original, factory programmed firmwareis also retained on board and can be accessed by installing a jumper.1.2 How to Use This ManualThe first five sections in this manual are organized in the order you shouldread and use them to get started with your H.110 MC3/Conference Board.We recommend that you begin with these three steps.1. Follow the instructions in section 2.0 (Quick Start) and 3.0(Installation). These sections will tell you if your board is operatingcorrectly within your system. You don’t need to be familiar with theboard’s command set to complete this step.2. Read section 4.0 (Initialization) to initialize the board within yoursystem. Your application must perform these initializationprocedures whenever the computer is powered-up in order for theboard to communicate with the application.3. Read section 5.0 (Communications with the Computer) for anoverview of how to communicate with the H.110 MC3/ConferenceBoard. Section 5.0 includes a summary of the commands forconstructing your application and details concerning systeminterrupts.Before you can actually build your application, read section 6.0 (The H.110bus, MC3 Bus and Clock Modes), 7.0 (Using the MC3 bus), 8.0 (H.110Bus Switching) and 9.0 (Conferencing). These sections explain, withpractical examples, how the H.110 MC3/Conference Board operates and

Introduction • 1-7 •The H.110 MC3/Conference Boardhow to use the command set to achieve the desired results. Section 10.0 explains diagnostic and error messages that may occur.The Appendix contains diagnostic information that will be helpful if youhave problems installing your H.110 MC3/Conference Board.

Introduction• 1-8 •The H.110 MC3/Conference Boardthis page intentionally left blank

Quick Start • 2-1 •The H.110 MC3/Conference Board2.0 Quick StartThis section describes the first steps you should perform to determine ifyour Infinity Series H.110 MC3 Multi-Chassis Interconnect & ConferenceBoard is communicating correctly with your CompactPCI system. You canperform this quick check without connecting any cables.The exact procedure will vary depending on which operating system youare running. For each operating systems, drivers are required to interfaceto the boards. The drivers supplied by Amtelco have tests built into themto verify communications with the boards. These drivers also comesupplied with utility programs that allow the developer to testcommunications with the board. Please consult the appropriatedocumentation for the driver and operating system you are using.Quick Start Procedure1. With the chassis power off, insert the board into a slot.2. Turn on the computer.3. If the Amtelco driver is not already installed, install it now,following the instructions supplied with the driver.4. Most Amtelco drivers will display a list of boards that areinstalled (see the documentation for the particular driver thatyou are using). If the H.110 MC3/Conference board is listed,skip to step 6.5. If the board is not listed, there may be a problem with theboard not being seated correctly in the backplane. There mayalso be a problem with a memory or interrupt conflict. Powerdown the chassis and check that the board is properly seated

Quick Start• 2-2 •The H.110 MC3/Conference Boardin the connector and repeat steps 1-4. If this does notremedy the problem, try removing any other computertelephony boards in the system. If your PC is unable to findthe board, consult the number at the end of this section.6. Run the program “xdsutil” supplied with the driver. Send themessage “IN” to the H.110 MC3/Conference board. Theboard should respond with the message “IA”.7. Send the message “VC” to the board. Verify that the ReceiveMessage reads: VCxxxxvvvvH03 (where xxxxvvvv isa variable indicating the firmware version).8. If the Communications screen shows the correct commandresponses, your H.110 MC3/Conference Board iscommunicating with the PC. You may now power down thecomputer and attach the necessary cables (see section 3.4)For technical assistance, call Amtelco at 1-608-838-4194 ext.168.

Installation • 3-1 •The H.110 MC3/Conference Board3.0 InstallationThis section describes how to install your Infinity Series H.110 MC3 Multi-Chassis Interconnect and Conference Board into your computer and howto set the switches, jumpers, and connectors. Before you begin theinstallation procedure, be sure to test the board as described in section 2.0(Quick Start).Figure 2: Location of JumpersHeaders, and Connectors3.1 PCI ConfigurationAs Infinity Series boards conform to the PCI standards, there are noswitches to set to configure the H.110 MC3/Conference Board's memoryaddress, I/O addresses, or interrupt. The host processor’s bios willautomatically configure the board at boot time to avoid conflicts with otherboards in the system.

Installation• 3-2 •The H.110 MC3/Conference Board3.2 Jumpers & HeadersThe following is a complete list of all jumpers for the H.110MC3/Conference Board:JW1-1 Firmware Select. If firmware has been downloaded to theboard, this jumper selects whether the downloaded firmwareor the factory default firmware is used. When this jumper isinstalled, the factory default firmware is executed wheneverthe board is reset. When the jumper is not installed, thedownloaded firmware will be executed after a reset if it ispresent. If no downloaded firmware is present, the factorydefault firmware is executed after reset. JW1-2 DSP Firmware Select. Two separate firmware programs areincluded in the EAROM, one for the board processor andone for the DSP. If JW1-2 is installed and downloaded DSPfirmware is present, the factory DSP firmware is executedafter reset. Otherwise, the downloaded firmware is executedif present. See JW1-1JW1-3 Undefined, reserved for future use.JW1-4 Undefined, reserved for future use..JW3 This jumper is used for factory testing and should not havejumpers installed.P3 Diagnostic port. Never install jumpers here.P4 This header is used for programming internal logic and shouldnever be jumpered.

Installation • 3-3 •The H.110 MC3/Conference Board3.3 Connectors: P5, P6 and J1 P5 Ring 0 RCV, Ring 1 XMT. This is one of the two fiber optictransceivers for the MC3 bus. In a normal counter rotatingring connection, the fibers from this transceiver are connectedto P6 in the next chassis in the ring. This connector is keyedto insure proper insertion.P6 Ring 1 RCV, Ring 0 XMT. This is one of the two fiber optictransceivers for the MC3 bus. In a normal counter rotatingring connection, the fibers from this transceiver are connectedto P5 in the previous chassis in the ring. This connector iskeyed to insure proper insertion.J1 Analog port. This port can be used to connect a music sourceor other device analog port for music on hold. Theconnector is a standard 1/8” headphone jack. The musicsource should be at standard line levels.J1A Analog input. This header is connected in parallel with J1.It will connect with the audio output of a PC CD-ROM drive.3.4 InstallationTo install the H.110 MC3/Conference Board in your system:1. Follow the quick check procedures described in section 2.0 to verifythe operation of the board.2. If the quick check is successful, turn off the chassis power andremove the board from the chassis.3. Install any necessary board jumpers. See section 3.2 for jumperconfigurations.

Installation• 3-4 •The H.110 MC3/Conference Board4. Insert the board into the chassis. Seat it properly in a slot in thechassis and secure it with the front panel handles.5. Connect the fiber optic cables to P5 and P6. See section 6.4 fordetails on the various ring configurations.6. If the analog port is to be used, connect the music source or othercompatible device.7. Power up the computer.3.5 Hot Swapping a BoardThe Infinity Series H.110 MC3/Conferencing Board can be “hot swapped,”that is it can be removed from a functioning system without turning thepower off or interrupting applications. However, to be able to do this, thehost processor must be equipped with suitable hot swap drivers as well asa hot swap manager which will alert applications when a board has beeninserted or removed from the system so that resources can be properlymanaged. It is beyond the scope of this manual to describe the operationof either the hot swap driver or hot swap manager.Each H.110 board is equipped with a switch linked to the lower ejector taband a blue LED. This combination is used to coordinate the actions of anoperator with the system software. When inserting a board, the board ispushed in part of the way until the blue LED is illuminated. The insertionmay then be completed. When the connection process is complete, theLED will go out. To remove a board, the lower ejector handle is depresseduntil it is in the unlatched position. When the blue LED comes on, theboard may be removed from the system.

Installation • 3-5 •The H.110 MC3/Conference BoardTo install the board in a system under power:1. Insert the board with the ejector tabs spread apart until partiallyengaged.2. Wait until the blue LED is illuminated.3. Finish inserting the board by pushing the ejector tabs towards eachother. The LED should then go out.To remove the front board from a system under power:1. Depress the lower ejector tab until it is in the unlatched position.2. Wait until the blue LED is illuminated.3. Finish removing the board by spreading the ejector tabs apart untilthe board is ejected.

Installation• 3-6 •The H.110 MC3/Conference BoardFigure 3: Front Panel with Status and Hot Swap LEDs, MC3 FiberConnectors, and Top and BottomEjector Handles

Initialization • 4-1 •The H.110 MC3/Conference Board4.0 InitializationThis section describes the procedures necessary to initialize the system andenable the host computer to communicate with the Infinity Series H.110MC3 Multi-Chassis Interconnect and Conference Board. XDS drivers willimplement some of these procedures.4.1 PCI Initialization The system BIOS is responsible for recognizing CompactPCI boards andmapping them into the I/O and memory spaces as required. It is alsoresponsible for assigning interrupts to the board. This is done through a setof on board registers which contain information specifying the memory,I/O, and interrupt needs of the board. A set of BIOS functions exist foraccessing this information. A detailed description of these functions can befound in the PCI BIOS Specification published by the PCI SIG, the PCISpecial Interest Group.Normally, the drivers supplied by Amtelco will take care of the process offinding Infinity Series boards and establishing communications. Theinformation in the rest of this subsection is for background only.The configuration registers of every CompactPCI board contain a vendorID and device ID code. These codes are unique to each board vendor. AllInfinity Series H.110 boards have the same vendor and device IDs. Thevendor ID is 14E3h and the device ID is 0101h. A BIOS function existsthat will find each instance of a particular vendor and device ID, and whichreturns with a bus and device number. The bus and device number is thenused in functions to read the configuration registers.The configuration registers contain information on the base address of thememory and I/O assigned to the board by the BIOS. A PCI board may

Initialization• 4-2 •The H.110 MC3/Conference Boardhave up to six different base addresses. On Infinity Series H.110 boards,the first two base addresses are used by the PCI bus interface logic. Thethird base address which is contained in registers 18-1Bh contains thememory location of the dual-ported memory that is used to pass messages.The interrupt information is contained in register 3C. The information inthese configuration registers can be used by a driver to address the board.4.2 Initialization CommandsThe H.110 MC3/Conference Board is initialized by sending a sequence ofcommand messages to the board. The process of sending messages isdescribed in detail in Section 5.0, but normally it is accomplished eitherwith a low-level driver XMT command or the API functionxds_msg_send. Response messages are read using the low-level driverRCV command or the API function xds_message_receive.To enable communications with the H.110 MC3/Conference Board, an INcommand message should be sent to the board. The board will respondwith an IA message.The board may be reset using the command message RA. The board willrespond with an RA message.Your application can now configure the H.110 MC3/Conference Boardusing these commandsCommand PurposeSCmsabb(c) Sets the clock mode for the board. The parameter mis the clock-mode. The parameter s is the clock sub-mode. The parameters a, bb, and c are used tospecify additional clock control information such ascompatibility modes, clock rates, local network, andCT_NETREF settings. The default mode on power-up or restart is mode 0. See section 6.0 of this manualfor details of clock mode arguments.

Initialization • 4-3 •The H.110 MC3/Conference BoardSEx Sets the encoding mode for the board. The parameterx can be either M for Mu-Law as used in NorthAmerica and Japan, or A for A-Law as used in Europeand Asia. The default value is for Mu-Law.SKa This command is used to enable or disableconferencing. If the parameter a is E, conferencingwill be enabled, if the parameter a is D, conferencingwill be disabled. When conferencing is enabled, themaximum number of connections between the MC3and H.110 bus is reduced from 1024 to 896.SMx Selects the ring mode. The parameter x is used tochoose between the extended mode where both ringsare available and the redundant modes where one ofthe rings acts as the primary ring and the other as abackup. The choices for x are:0 - extended mode, 4846 timeslots1 - redundant mode, primary ring is 0, 2423timeslots2 - redundant mode, primary ring is 1, 2423timeslotsSRx Selects ring failure mode. If the board is to beoperated with only a single ring due to a failure orconfiguration choice, this command is used to set theappropriate hardware. The choices for x are:0 - Both rings are operational1 - Ring 0 failure2 - Ring 1 failure3 - Both rings failed

Initialization• 4-4 •The H.110 MC3/Conference Boardthis page intentionally left blank

Communicating with the Host • 5-1 •The H.110 MC3/Conference Board5.0 Communicating with the HostThis section describes how the host computer communicates with theInfinity Series H.110 MC3 Multi-chassis Interconnect and ConferenceBoard. It includes the definitions for the H.110 MC3/Conference Boardcommands and responses along with a description of the mailboxes used formessaging.The board is controlled by the host computer through a system of twomailboxes. The messages consist of short NUL-terminated ASCII strings,which are easy for the host software to compose and parse. The board iscapable of buffering up to eight messages in either direction and can drivean interrupt line when it has a message for the host. Messages may notexceed 32 characters.There are two mailboxes, one for messages to the board and one formessages from the board, and two flags associated with them. A 00h in aflag byte indicates the mailbox is free, a non-zero value indicates that themailbox is occupied. The mailboxes and their flags are contained in an 8Kblock of dual-ported memory at the following offsets:receive mailbox 1F80htransmit mailbox 1FC0htransmit flag 1FFChreceive flag 1FFEhThe board's base address is determined by reading PCI ConfigurationSpace offset 18h. The 32-bit value at this location is the base address forthe dual-ported memory on the board.To send a message, the message is placed in the mailbox and the flag is setto 01h. To read a message, the message is removed from the mailbox andthe flag is cleared to 00h. This will clear the interrupt hardware.

Communicating with the Host• 5-2 •The H.110 MC3/Conference Board5.1 Command and Response ProtocolThis section describes the necessary step-by-step procedures for the hostto send a command to the board and to remove a response from the board.5.1.1 Sending Commands to the BoardThe basic steps to sending a command to the H.110 MC3/ConferenceBoard are:1. Build a command. Broadly speaking, a command is a string ofASCII characters with a NUL (00h) termination character.2. Check the transmit flag. If the flag is 0, continue with the next stepto put the command in memory. If the flag is not 0, wait until theflag is 0.3. Insert the command in transmit mailbox memory beginning at theaddress of the transmit mailbox.4. Write 01h to the transmit flag. This notifies the board that amessage is waiting.5.1.2 Reading Messages From the Board1. Check the receive flag. If the flag is 0, there is no message. If it isnon-zero, a message is waiting. Continue with the next step to readthe message.2. Remove the message from memory, starting at the address of thereceive mailbox. Messages are NUL-terminated ASCII strings. 3. Write 0h to the receive flag.

Communicating with the Host • 5-3 •The H.110 MC3/Conference Board5.1.3 Reading Board InformationA range of board information is included in memory so that it can bechecked without sending a message:Type of Information Offset AddressBoard ID 1F00-1F03Firmware Version 1F04-1F07Shelf and Slot ID 1F08-1F09Number of transmit timeslots 1F10-1F11Clock mode settings 1F18-1F1BBoard configuration 1F1C-1F1EClock status bits 1F1FThe board stores its identity upon power up or a hardware restart. Thephrase Restart cPCI MC3 © Amtelco 1999 appears in the receive mailbox. Thereceive flag is not set and no interrupt is generated.5.2 InterruptsThe H.110 MC3/Conferencing Board can generate an interrupt to the PCindicating that a message is available. The interrupt for PCI boards isassigned by the BIOS or Operating System at boot time. The assignmentis dependent on which PCI slot the board is in. The interrupt line is usuallyshared by more than one device. If multiple Infinity Series boards areinstalled they may or may not all share the same interrupt line.In order for an Infinity Series board to send interrupts to the PC, the PCIInterface circuit on the board must be programmed to enable interrupts.This is accomplished by setting bits 0 and 3 in the board's InterruptControl/Status Register. This is a byte-wide register located at an offset of69h from PCI Base Address 0. PCI Base Address 0 is contained in PCIConfiguration Space register 10h. The Base address is a 32-bit value andis mapped into memory. When an Infinity Series board sends a message, it generates a local

Communicating with the Host• 5-4 •The H.110 MC3/Conference Boardinterrupt to the PCI Interface circuit on the board. If the PCI Interfacecircuit has been programmed to generate interrupts to the PC, the localinterrupt is passed through to the PC. When the PC receives an interrupt,its Interrupt Service Routine (ISR) should check the Infinity board's receiveflag to see if a message is pending (i.e. the receive flag is non-zero). Itshould then process the message for the board and write a 0 to the board'sreceive flag.5.2.1 Interrupt Initialization1. Clear the board's receive flag.2. Read the PCI Base Address 0 from PCI Configuration Space offset10h (this must be a 32-bit access).3. Set bits 0 and 3 of PCI Base Address 0 + 69h. Do not modify anyother bits in this register. This register is a byte-wide memorymapped register.5.2.2 Step-by-Step Interrupt Processing Summary1. Check to see if the receive flag is non-zero.2. Remove the message from the receive mailbox.3. Write 0h to the receive flag.4. Re-enable the interrupt controller on the PC.

Communicating with the Host • 5-5 •The H.110 MC3/Conference Board5.3 Commands and ResponsesThis section gives a general overview of the H.110 MC3/Conference Boardcommands and responses. The commands are grouped by function andthen listed in alphabetical order by two-letter command. Refer to sections7.0 through 10.0 for examples and explanations of how to use thesecommands.5.3.1 Characteristics of Command Strings<All commands consist of null (00h) terminated ASCII strings.<There are no spaces or other delimiters between parameters in thecommands.<All letters in command strings must be UPPERCASE unlessotherwise noted.<Lowercase monospaced letters (such as xx ) in the followingcommand references represent parameters within commands. Eachletter represents one ASCII digit.<Numeric parameters are always hexadecimal numbers.5.3.2 Command ParametersThe following table documents the common parameters for many of thecommands listed in the next sections. Other less common parameters aredefined with individual commands.

Communicating with the Host• 5-6 •The H.110 MC3/Conference BoardCommon Command ParametersParameter Definition Valueshh Conference handle 01-2Ahcc Conference Control Address 00-7Fhpp Output pattern value 00-FFhiiii 1st & 2nd i, H.110 receive stream 00-1Fh2nd & 3rd i, H.110 receive timeslot 00-7Fhoooo 1st & 2nd o, H.110 transmit stream 00-1Fh 3rd & 4th o, H.110 transmit timeslot 00-7Fhyyyy 1st & 2nd y, MC3 transmit stream 00-4Bh3rd & 4th y, MC3 transmit timeslot 00-3Fhzzzz 1st & 2nd z, MC3 receive stream 00-4Bh3rd & 4th z, MC3 receive timeslot 00-3Fhbsstt MVIP-95 terminus, b - bus, C, H, L, Xss - stream, tt - timeslot 0000-4B7F5.3.3 Commands to the H.110 MC3/Conference BoardNote that sections 7.0-9.0 provide supplemental information and examplesfor the commands and messages documented here.Conference CommandsCAhhooooiiiian Conference H.110 timeslot iiii, output on timeslotoooo, conference hh, attenuation a, noise threshold nCDoooo Disable output to H.110 timeslot ooooCEiiii(cc) Enable DTMF detection on conferenced timeslot iiii,cc = clamping time .02 sec incrementsCEiiiiD Disable DTMF detection on conferenced timeslot iiii

Communicating with the Host • 5-7 •The H.110 MC3/Conference BoardCIhhiiiian Add H.110 input timeslot iiii to conference hhattenuation a, noise threshold nCLiiii Enable 2 kHz. tone detection on H.110 timeslot iiiiCLiiiiD Disable 2 kHz. tone detection on H.110 timeslot iiiiCMhhoooo Monitor conference hh on H.110 timeslot ooooCTooooE Enable 2 kHz. tone on H.110 timeslot ooooCTooooD Disable 2 kHz. tone on H.110 timeslot ooooCUhh Dissolve conference handle hhCXhhiiii Remove H.110 timeslot iiii as an input to conferencehhMC3 Bus CommandsXCooooiiiiyyyyzzzz Connect H.110 timeslot iiii to MC3 transmittimeslot yyyy and MC3 receive timeslot zzzz toH.110 timeslot ooooXDIoooo Disable output to H.110 timeslot oooo from MC3 busXDOyyyy Disable output to MC3 timeslot yyyyXLIoooozzzz One-way audio from MC3 timeslot zzzz to H.110timeslot ooooXLOyyyyiiii One-way audio from H.110 timeslot iiii to MC3timeslot yyyyXPIoooopp Output pattern pp on H.110 timeslot ooooXPOyyyypp Output pattern pp on MC3 timeslot yyyyAnalog Port Control (Music on Hold)AD Disable Music on Hold transmitAEoooo Enable Music on Hold output to H.110 timeslot ooooAGttrr Set transmit attenuation to tt and receive attenuation torr in .1 dB stepsARiiii Enable analog input from H.110 timeslot iiiiARX Disable analog input

Communicating with the Host• 5-8 •The H.110 MC3/Conference BoardMVIP Compatibility CommandsMAm Audio port control modem = D - disabled, m = E - enabledMDccmdd DTMF detection control, cc - CCA,m = D - disabled, m = E - enabled, dd - durationMKhhccman Conference control, hh - conference handle,cc - CCA,m = D - disabled, m = E - enableda - attenuation, n - noise thresholdMObssttD Set_output disable mode, bsstt - output terminusMObssttEbsstt Set_output enable mode, bsstt - output terminus, bsstt - input terminusMObssttPpp Set_output pattern mode, bsstt - output terminus, pp - pattern valueMTD Disable output to the CT Bus (tristate)MTE Enable output to the CT BusInterrupt Control CommandsIF Disable transmit interrupts and messagesIN Enable transmit interrupts and messagesReset CommandsRA Reset AllRD Reset DSP’sSetup CommandsSAhhan Set conference with handle hh to attenuation and noisethreshold nSCmsabb(c) Set clock mode m submode s, arguments a, bb, & cSDm Set energy detection mode, m = D - disabled, m = E - enabledSEm Set encoding mode, m = M - mu-Law, A - A-LawSKm Set Conference mode, m = E - enabled, D - disabledSLx Set Loopback Mode x = 0-F, 0 = no loopbackbit 0 - TLBB, 1 - FLBB, 2 - TLBA, 3 - FLBA

Communicating with the Host • 5-9 •The H.110 MC3/Conference BoardSMx Set Ring Mode, x = 0 - extended mode, both rings available1 - Redundant rings, Ring 0 primary ring2 - Redundant rings, Ring 1 primary ringSRx Select Ring Failure bits, x = 0, no failure, x = 1 ring 0,x = 2 ring 1, x = 3 both ringsVersion RequestsVA Checksum of alternate segment requestVC Version requestVD DSP version requestDownload Commands@xxxx Download 1K block to address xxxx@Es Erase segment sGA Jump to Alternate Program GM Jump to Main Program@Ws Write from RAM to segment sDiagnosticsQC Query Clock Mode informationQHcrrrr Query CT812, c = CT812, rrrr = registerQL Query geographical information (shelf & slot)QMRx0zzz Query MC3 Receive, x = MT90840, zzz = internalstream & timeslotQMTxyyyy Query MC3 Transmit, x = MT90840, yyyy = MC3stream & timeslotQObsstt Query Output for terminus bssttQPd(cmnd) Send command to DSP dQS Query MC3 bus status

Communicating with the Host• 5-10 •The H.110 MC3/Conference Board5.4.4 Responses from the H.110 MC3/Conferencing BoardAcknowledgementsIA Interrupt On acknowledgeRA Reset all acknowledgeError MessagesECxx Clock error bits xx EFr Ring r failureEG01 Conflict while enabling 2 kHz. generatorEKhhxx Conference error for conference handle hh, error xx01 - illegal handle02 - no free conference inputs03 - not an input to conferenceEPoooo Path error for H.110 output timeslot ooooERr Ring r restoredESrxx Ring r status error, status xxQuery ResponsesQCmsabrrttkkrsmxsy Reply to Query Clock Modem - mode, s - submode, a, b - argumentsrr - stream rate byte, tt, kk - enable flagsrs - reset byte, mx - mux byte, sy - SYN-155 byteQH0rrrrdddddd Reply to CT812 query, dddddd is register dataQLaabb Reply to location query, shelf aa, slot bbQMRx0zzzhhlldd Reply to Query MC3 Receive, hh = receive path connection memory highll = receive path connection memory lowdd = transmit path data memoryQMTxyyyyhhlldd Reply to Query MC3 Transmithh = transmit path connection memory highll = transmit path connection memory lowdd = receive path data memoryQObssttm(bsstt) Query_output reply, bsstt - output terminus, m - mode(bsstt) input terminusQPd(string) Response from DSP dQSsstt MC3 bus status ss for ring 0, tt for ring 1

Communicating with the Host • 5-11 •The H.110 MC3/Conference BoardDTMF Detection MessagesSTiiiit DTMF tone t detected on H.110 stream & timeslot iiiiSTX0cct DTMF tone t detected on CCA cc Diagnostic ResponsesVAcccc Alternate segment checksum, cccc - checksumVCccccvvvviiix Version request response, cccc - checksumvvvv - version, iii - board identifierHO3 - cPCI MC3 board, x - population levelVDxxxx DSP version numberU(msg) undefined or unparseable message

Communicating with the Host• 5-12 •The H.110 MC3/Conference Boardthis page intentionally left blank

The H.110 Bus, Clock Modes & MC3 Bus • 6-1 •The H.110 MC3/Conference Board6.0 The H.110 Bus, Clock Modes& MC3 BusThe Infinity Series H.110 MC3 Multi-Chassis Interconnect and ConferenceBoard provides a means of connecting the fiber-optic MC3 interchassis busto the H.110 bus. Through this bus, the MC3 channels can be connectedto other H.110 compatible boards. The H.110 MC3/Conference Boardalso has facilities for conferencing and an analog port for music on hold ormonitoring. It is capable of operating in a variety of clock modescompatible with H.110 and MC3 operation.6.1 The H.110 BusThe H.110 bus consists of 32 Pulse Code Modulation (PCM) streamsoperating at an 8.192 MHZ. clock rate. Each stream contains 128timeslots, for a total of 4096 timeslots. In addition to the PCM data signals,there are a number of bit, frame, and network reference signals that areused to synchronize the operation of multiple boards.For the purposes of commands, a particular H.110 timeslot is referred toby a four digit hexadecimal number. The first two digits are the streamnumber, while the last two digits are the timeslot within the stream.Streams range from 00h to 1Fh, and timeslots from 00-7Fh.The physical H.110 bus is a backplane connection using the J4/P4connector. The H.110 specification defines allowable impedance and signallengths on each board so that additional bus termination is not needed toinsure the proper operation of the bus. The maximum length of the bus(24.8 in.) and the maximum number of slots (21) are also specified.Different length pins are also used on the various connectors. This is doneso that the various signals are staged in the correct order.

The H.110 Bus, Clock Modes & MC3 Bus• 6-2 •The H.110 MC3/Conference Board6.2 Clock ModesThe H.110 bus specification defines a variety of clock signals. Two clocksignals CT bus A and CT bus B are provided for redundancy. In addition,two signals called CT_NETREF_1 and CT_NETREF_2 are defined whichmay be referenced to an external clock source such as a T1 or E1 span.These signals exist to aid in recovery if the primary clock source should fail.The clock mode must be set before any connections can be made withother boards. The clock mode is set using the Set Clock command“SCmsabbc”, where m is the clock mode, s is the sub-mode, and a, bb, andc are additional arguments used to select clock sources and specifycompatibility modes. The default clock mode on a power up is to providea local clock, but to neither source clock signals to the bus or derive theclock from the bus. The possible clock modes are:0no clocks to or from the bus1clocks slaved to the CT bus2the board is clock master CT bus clock A3the board is clock master CT bus clock B4the board is secondary master for CT bus clock A5the board is secondary master for CT bus clock BConnections are possible only when all boards within a system aresynchronized to the same clock. Only one board in a system can providethe H.110 bus clock. The other boards in the system must slave theirinternal clocks to the master. If the H.110 MC3/Conference Board is touse the H.110 bus clock, this clock must be provided by another boardbefore switching can be accomplished.6.2.1 Slave ModeIn the Slave Mode, the H.110 MC3/Conference board derives its clocksfrom one of the clock signals on the CT bus. The clock signal is selectedwith the submode argument in the SC command. The possible clock

The H.110 Bus, Clock Modes & MC3 Bus • 6-3 •The H.110 MC3/Conference Boardsignals are:0 - CT bus clock A1 - CT bus clock B6 - CT bus clock A, auto-fallback mode7 - CT bus clock B, auto-fallback modeArgument a is used to set the CT_NETREF mode, while argument bb isused to select the source of CT_NETREF. The choices for argument a are:0 - No CT_NETREF output1 - CT_NETREF_1 output is enabled2 - CT_NETREF_2 output is enabledIt should be noted that CT_NETREF_2 is defined only for the H.110 busand not the H.100 bus. The CT_NETREF source can be either MC3 Ring0 if argument bb is 00 or MC3 Ring 1 if argument bb is 01.6.2.2 Primary Master ModeIn modes 2 or 3, the board supplies the CT master clocks A or Brespectively. Other boards on the H.110 bus will synchronize to one ofthese clocks. The source of the clock is selected by the submode arguments. The choices are:0 - freerun, the board’s internal clock1 - CT_NETREF_12 - CT_NETREF_23 - a local network, either Ring 0 or Ring 14 - a local network with auto-fallback to CT_NETREF_15 - a local network with auto-fallback to CT_NETREF_2For submode 1 and 2, argument bb will select the frequency of theCT_NETREF signal. The choices are:

The H.110 Bus, Clock Modes & MC3 Bus• 6-4 •The H.110 MC3/Conference Board00 - 8 kHz. (frame rate)01 - 1.536 MHZ. (T1 rate)02 - 1.544 MHZ. (T1 extended superframe rate)03 - 2.048 MHZ. (E1 rate)For submodes 3-5, argument bb will select either the MC3 Ring 0 if 00 orRing 1 if 01. For submodes 4 and 5, the optional argument c will specifythe frequency of the selected CT_NETREF source.For all modes, argument a should be set to 0. On H.100 boards, thisargument is used to select the legacy bus compatible clocks that the boardwill supply. As the H.110 bus is not compatible with the SC or MVIP bus,the only valid option is 0, no compatibility clocks provided.6.2.3 Secondary Master ModesWhen a board is operating as a secondary master, it uses the other clocksignal as a source, i.e. if a board is the secondary master for CT clock B,it uses CT clock A as a source and provides CT clock B. If the primaryclock fails, the secondary master then becomes the clock master.Typically, one board will be set as the master for clock A and anotherboard as the secondary master for clock B, or vice versa. If the clocksource specified by the submode is either of the CT_NETREF signals ora local network, the board will automatically fall-back on that source if theprimary clock should fail. If set to free-run, it will fall back to a PLL thatwas locked to the primary master clock.In all secondary master modes, if the primary master fails, the board willautomatically become the new primary master. If the original primarymaster is restored, the clock mode for the original secondary master mustbe resetWhen operating in secondary master mode, submodes 0-3 are valid and thearguments a, and bb are the same as when operating as a primary master.

The H.110 Bus, Clock Modes & MC3 Bus • 6-5 •The H.110 MC3/Conference Board6.2.4 Clock FallbackThe H.110 Specification details a scheme for automatically recovering froma clock failure. One of the CT bus clocks, either A or B is designated themaster clock. The other clock is the secondary master and is generated bya different board than the primary clock. While the primary clock is valid,the secondary clock is locked to it. If the primary clock should fail, thesecondary clock takes over using a local oscillator, CT_NETREF_1,CT_NETREF_2, or a local network as the source. Boards that are slavesshould automatically fall back to the secondary clock. After a failure of themaster clock, system software should designate new primary and secondaryclocks. The new primary may be the previous secondary clock master.For Infinity Series H.110 boards, this will involve sending a set clockcommand with the new primary clock information.When an Infinity Series board is set for automatic fallback, the board willautomatically switch to the secondary clock if the primary clock fails.When this occurs, the board will send an “EC” message indicating thefailure. When the application designates a new primary master, it shouldsend a new clock mode command to the board even though auto-fallbackmay have occurred.6.2.5 Clock ErrorsIf the board detects a problem with the clocks, it will generate a clock error,which notifies the application that it should take appropriate action. Clockerrors are reported in the Clock Error Bit message, ECxx where the xx isa hexadecimal value in which each bit identifies the specific error. A valueof 1 indicates an error condition. The bits are as follows:bit Error Description0CT bus clock A1CT bus clock B2SCbus clocks3MVIP bus clocks4Master PLL error

The H.110 Bus, Clock Modes & MC3 Bus• 6-6 •The H.110 MC3/Conference Board5Frame BoundaryAs the SC and MVIP bus signals are not present, bits 2 and 3 can beignored.6.3 The MC3 BusThe MC3 bus is an interchassis connection mechanism that was defined bythe GO-MVIP Technical Committee. It uses many of the same conceptsand physical standards as the OC3 SONET specification, but is unique andnot intended for direct interconnection with SONET equipment.The MC3 bus consists of two full-duplex fiber-optic connections operatingat a 155 Mbps bit rate. This gives 2430 64 kbps channels on each ring, ofwhich seven are required for framing. The remaining 2423 channels areavailable for use in transporting 64 kbps information between chassis. Theseparation between chassis can be as great as 2000 meters. The MC3 buscan be operated in two modes. In the first mode, the two rings can becombined to give a total of 4846 channels or timeslots. In the secondmode, the two rings can be arranged as redundant counter rotating rings.In this mode signals can be routed around any one break between chassis.For the purposes of compatibility with the XDS MC1 Multi-Chassis board,the MC3 bus is divided up into logical streams of 64 timeslots each. Eachring has 38 of these logical streams, though the last stream does not havea full 64 timeslots. Timeslots are referenced using a four digit hexadecimalnumber where the first two digits indicate the stream and the last two thetimeslot. It should be noted that this arrangement is merely a logicalconvention and each frame on a ring actually consists of 2430 timeslots.6.3.1 MC3 Ring ErrorsThe MC3 rings are also a possible source of errors. If a ring failure isdetected, it will be reported with a message of the form EFr where r is thering. Restoration will be reported with a message of the form ERr. If the

The H.110 Bus, Clock Modes & MC3 Bus • 6-7 •The H.110 MC3/Conference Boardfailed ring was being used to provide a reference for the chassis, it may benecessary to change clock modes. Other error conditions may also bedetected. These are reported with a message of the form ESrxx where ris the ring and xx is the value of the ring status register. The bits in thisregister are:bit description 0 LOS - loss of signal 1 LOF - loss of frame 2 OOF - out of frame 3 RFE - receive frame error 4 B1ERR - bit error6.3.2 Ring Status LEDsThe board is equipped with two front panel LEDs to indicate the status ofthe MC3 rings. When a ring is operating normally, the LED for that ringwill be green. If the ring fails, the LED will be yellow. If an error occursthat causes an “ES” message the LED for that ring will switch to yellow fora second before returning to green. A third status LED indicates the stateof the main processor and should normally blink green at a one second rate.6.4 MC3 Ring ConfigurationsThe standard MC3 configuration takes the form of two counter rotatingrings. That is, signals in one ring move between the chassis in one directionand the signals in the other ring move in the opposite direction. To makethis configuration, the fiber plugged into P5 in one chassis is plugged intoP6 of the next chassis in the system. This pattern is repeated until the fiberfinally wraps around itself and is plugged into P6 of the first chassis in thecircle. As each connector consists of the receive fiber for one ring and thetransmit fiber for the other ring, this configuration completes the two ringsrotating in opposite directions.If the fiber should be interrupted between two chassis, or if there should be

The H.110 Bus, Clock Modes & MC3 Bus• 6-8 •The H.110 MC3/Conference BoardFigure 4: Three Node MC3 Ringa chassis failure, the boards on either side of the break can be set so thatsignals loop back on themselves. Received signals, instead of beingtransmitted on the same ring, are transmitted on the other ring in theopposite direction. This forms a completed loop avoiding the brokensegment or off-line chassis. The ability to avoid a segment or chassisallows maintenance to be performed while keeping the rest of the systemrunning.It is also possible with a two chassis system to connect the chassis usingonly one fiber pair. This may be desirable in some small configurations forthe sake of simplicity or to keep the cost down.

The H.110 Bus, Clock Modes & MC3 Bus • 6-9 •The H.110 MC3/Conference Board6.5 Configuration InformationInformation on the clock mode setting, stream rates, and otherconfiguration settings is available in the dual-ported memory in an eightbyte block beginning at an offset of 1F18h. The first four bytes are theclock mode, the submode, and the a and bb arguments from the set clockcommand SC. On H.100 boards the sixth byte is used to indicate the stateof the H.110 and MVIP termination and can be ignored on H.110 boards.Bits 0 and 1 of the seventh byte indicate whether conferencing and theaudio port have been enable. The eighth byte contains the clock errorstatus bits. These are in the same order as in the EC clock error message(Sec. 6.2.5)6.6 Hot SwapHot swapping is the capability of being able to insert or remove a boardfrom a live system without having to power down or interrupt the operationof the system. The H.110 specification provides for hot swap capabilities,and these are implemented on the H.110 MC3/Conferencing Board.Each board has a switch that is linked to the ejector tab. This switch isused to assert a signal called ENUM# when a board is inserted or about tobe removed. Each board also has a blue LED which is used to indicate thestatus of the board. Upon insertion, this LED is illuminated until thehardware connection process is complete. The LED is then turned off.When removing the board, the ejector tab is partially depressed to signalthat the board is to be removed. The blue LED will then be illuminatedindicating that it the board may be fully removed.The ENUM# signal is used to notify a Hot Swap Driver of the impendinginsertion or removal of the board. It is the responsibility of the driver totake what ever steps are necessary to connect or disconnect the hardware.

The H.110 Bus, Clock Modes & MC3 Bus• 6-10 •The H.110 MC3/Conference Boardthis page intentionally left blank

Using the MC3 Bus • 7-1 •The H.110 MC3/Conference Board7.0 Using the MC3 BusThis section describes the operation and use of the MC3 Bus. It willexplain the steps required for initialization, how to make and breakconnections, how to take advantage of the redundancy the MC3architecture provides, how to handle errors, and some of the diagnosticmodes.7.1 InitializationThe most important consideration in properly initializing a system is theconfiguration of the clocks. Before connections can be established, auniform set of clocks must be set up and synchronized. This is necessaryso that a particular timeslot in a frame can be identified.One and only one board in the system can serve as the master clock. Thisclock can be derived from an external digital circuit such as a T1, E1 orISDN interface or it can be generated by a local on board oscillator. Ifthere is one or more T1 or E1 circuits coming from the public switchednetwork, one of these must be the master clock source. This clock is thenplaced on the H.110 bus for the other boards in that chassis to use as areference. In the case of an MC3 board, this clock is used to generate theframing on the MC3 rings. Other MC3 boards in the system then referencetheir clocks from the MC3 framing and use these clocks to drive the CTbus clocks in all the other chassis in the system. If there are no externaldigital circuits to serve as the ultimate clock reference, one of the MC3boards may be selected to derive its clock from the local oscillator on thatboard. This board then drives the clock for both the H.110 and MC3busses.Before connections can be made, the clock configuration of all boards inthe system must be set. On the H.110 MC3/Conference Board, this is

Using the MC3 Bus• 7-2 •The H.110 MC3/Conference Boarddone using the Set Clock command. This command takes the formSCmsabb(c), where m is the clock mode, s is the clock sub-mode, and a,bb, and c specify reference frequency and which local network (MC3 Ring)is the clock source if the board is a clock master. Note that all but one ofthe MC3 Boards must be a clock master deriving it’s clock from one of thetwo rings. This means that for all but one of the H.110 MC3 boards theclock mode must be “2” or “3”, the clock submode must be “3”, “4” or“5” (clock source is the local network), and the local network bb must beeither Ring 0 or Ring 1. The remaining board must either be running inslave mode or be running as a bus master in clock mode “2” or “3” withthe clock submode set to “0” (freerun). If there are digital networkconnections in one of the chassis, that is a T1, E1, Primary Rate ISDN orBasic Rate ISDN board, that board must be the clock master in that chassisand the MC3 board in that chassis must be slaved to the bus and providingthe clocking to the MC3 bus. If more than one chassis has such a board,then one chassis should be picked as the master (a T1, E1, or Primary RateISDN is preferred over a Basic Rate ISDN board).For interoperability with chassis using the XDS MVIP MC3 Board, theXDS MVIP MC3 boards should be running in clock mode “3” unless thatchassis contains the ultimate clock source, in which case the XDSMC3/Conferencing Board clock mode will be “0” or “1” if the MVIP busin that chassis is the source of the clock reference, or “2” if the clock isbeing derived from the local oscillator on the board.With the clock mode selected, it may be necessary to select the ring mode.The default is the extended mode where timeslots on both rings areavailable for use. To select the redundant mode, the Set Ring Modecommand must be used. This command takes the form SMx where x isthe mode. If x is “1”, Ring 0 is the primary ring with ring 1 reserved forfallback in case of a failure. If x is “2”, Ring 1 is the primary ring. An xvalue of “0” selects the extended mode.If the MC3 configuration is anything other than an extended counterrotating ring, it will also be necessary to set the ring failure bits. This isdone using the “SR” or Set Ring Failure command. This command takesthe form SRx where x selects the ring failure mode. If x is “0”, there is no

Using the MC3 Bus • 7-3 •The H.110 MC3/Conference Boardfailure, if x is “1”, ring 0 has failed, and if x is “2”, ring 1 has failed. Thedefault mode is 0 where full counter rotating rings are assumed to befunctioning. If only one fiber pair is functioning, or one of the redundantmodes is selected, then one of the failure modes must be selected. If theworking fiber is connected to P5, or Ring 0 is the primary ring, then thefailure mode should be “2”, if the working fiber is connected to P6, or Ring1 is the primary ring, the failure mode selected should be “1”.7.2 MC3 Switching CommandsConnections between the MC3 and H.110 busses are controlled using the“X” commands. These commands consist of the letter “X” followed byone or two additional letters specifying the command. There will also beone to four arguments indicating the MC3 and H.110 timeslots involved inthe command. The timeslot arguments are four hexadecimal digits for theH.110 bus and four hexadecimal digits for the MC3 bus. The first twodigits indicate the stream and the last two digits indicate the timeslot withinthe stream. H.110 streams have 128 timeslots while the MC3 streams have64 (See section 6.1 and 6.3). In the extended mode, MC3 streams have arange of 00-4Bh and in the redundant mode the range is 00-25h. Note thatbecause of framing signals, streams 25h and 4Bh have only 55 timeslots,or timeslots in the range 00-36h. “Inward” connections are from the MC3bus to the H.110 bus and “outward” connections are from the H.110 toMC3 bus.A full-duplex connection between the H.110 bus and the MC3 bus is madeusing a command of the form XCooooiiiiyyyyzzzz where oooo specifiesthe H.110 transmit timeslot, iiii specifies the H.110 receive timeslot, yyyyspecifies the MC3 transmit timeslot and zzzz specifies the MC3 receivetimeslot.Half duplex connections can be made using the “XLI” and “XLO”commands which make connections to and from the H.110 busrespectively. The “XLI” command takes the form XLIoooozzzz whereoooo is the H.110 transmit timeslot and zzzz is the MC3 receive timeslot.The “XLO” command takes the form XLOyyyyiiii where yyyy is the MC3

Using the MC3 Bus• 7-4 •The H.110 MC3/Conference Boardtransmit timeslot and iiii is the H.110 receive timeslot. An “XLI” and an“XLO” command can be combined to form a full duplex connection.To disable a connection, the “XDI” and “XDO” commands are used todisable output to the H.110 and MC3 bus respectively. These commandstake the form XDIoooo and XDOyyyy where oooo is an H.110 timeslotand yyyy is an MC3 timeslot.As an example, to make a connection from H.110 timeslot 1 stream 0 tothe 131st timeslot on the MC3 bus, and from the 196th timeslot on theMC3 bus to H.110 timeslot 35 on stream 1, the command would beXC0123000102020303 where 0123 is timeslot 35 (23h) on H.110 stream1, 0001 is timeslot 1 on H.110 stream 0, 0202 is timeslot 131, and 0303 istimeslot 196 on the MC3 bus. Note that timeslot numbers begin with 0.The same connection could be made with the commands XLI01230303and XLO02020001. To disable the output to the H.110 bus the commandwould be XDI0123, while the output to the MC3 bus would be disabled bythe command XDO0202.There may be occasions when it is necessary to output a fixed pattern onthe H.110 or MC3 bus. This can be for diagnostic purposes or foroutputting a “silence” pattern. This can be done with a command of theform XPIoooopp where oooo is the H.110 timeslot and pp is the patternvalue or XPOyyyypp where yyyy is the MC3 timeslot and pp is thehexadecimal value of the byte to be output.7.3 Ring ErrorsA number of factors can cause errors. These are signaled in a message ofthe form ESrxx where r is the ring and xx is a status byte indicating theerror type. The bits in this byte are as follows:

Using the MC3 Bus • 7-5 •The H.110 MC3/Conference Boardbit description0 LOS - loss of signal1LOF - loss of frame2OOF - out of frame3RFE - receive frame error4B1ERR - a parity error detected6FSA - frame slip alarm7 TXPPA - transmit phase alignment alarmAny of these errors may indicate a problem with the fiber connection orclocking.If the errors on bits 0-3 persist for more than 150 msec. then a ring failurehas occurred. This will be signaled by a message of the form EFr wherer is the ring number. A recovery occurs when none of these bits indicatesan error condition for 1.5 seconds. This will be signaled by a message ofthe form ERr where r is the ring.7.4 Ring Redundancy & FallbackThe dual counter rotating ring architecture of the MC3 bus allows forredundancy and dynamic fallback in case of a failure in a ring. To takeadvantage of the redundancy, the MC3 bus must be operated in one of thetwo redundant modes, with either Ring 0 or Ring 1 as the primary ring.When in the redundant mode, signals are transmitted on the primary ringand the corresponding timeslot on the secondary ring is set to bypass.Signals from the primary ring are connected to the H.110 bus while thesecondary ring remains in reserve.To set up an H.110 MC3/Conference Board to operate in the redundantmode, it is necessary to set up both the ring mode with an “SM” command,and the ring failure mode with an “SR” command. For example, if theprimary ring is Ring 0, then the commands would be SM1 and SR0. If theprimary ring is Ring 1, then the commands would be SM2 and SR0. If theboard is a clock master and the clock submode of the board is “3”, “4" or“5", then it will be necessary to select the primary ring as the clock source.

Using the MC3 Bus• 7-6 •The H.110 MC3/Conference BoardA ring failure is signaled by an error message of the form EFr where r is thefailed ring. When a ring interruption occurs, the boards on either side ofthe break will indicate errors. If the error is in the primary ring, it will benecessary to change both the ring mode and the ring failure mode. Forexample, if Ring 0 is the primary ring, and a failure in the primary ring isdetected, then the ring mode must be changed so that Ring 1 is the primaryring by issuing an SM2 command. It will also be necessary to change thefailure mode by issuing an SR1 command. If the board is a clock masterand the source is the local network, it must be changed so that the clocksource is Ring 1. This is done by issuing an SC23001 command if theboard is clock master A or SC33001 if clock master B. If the failure is inthe secondary ring, only the ring failure mode must be changed. Forexample, if Ring 1 fails, an SR2 should be issued.Note that the “SR” command is used to set any required loopbacks forredundancy. The “SL” command is not used for this purpose and is onlyused for testing purposes.A ring recovery is signaled by an ERr message where r is the recoveredring. If the recovery is for the ring that had originally been the primaryring, the “SM”, “SR”, and “SC” commands to reestablish the primary ringshould be issued. For example, if Ring 0 is restored, the commands wouldbe SM1, SR0, and SC23000 or SC33000. If the recovery is for thesecondary ring, only an SR0 command should be issued.Under some circumstances, a ring failure may also require changes to theclock modes of other boards on the affected ring. For a more completediscussion see Appendix B.7.5 Loopback ModesThe rings can be placed into several loopback modes for diagnosticpurposes. This is done by setting one or more of the loopback bits usingthe Set Loopback command. This command has the form SLx where x isthe value of the loopback nibble. The bits in this nibble are

Using the MC3 Bus • 7-7 •The H.110 MC3/Conference Boardbit description0TLBB - Terminal Loopback B1FLBB - Facilities Loopback B2TLBA - Terminal Loopback A3 FLBA - Facilities Loopback AA Facilities Loopback will send data coming in on one ring out the otherring. FLBA will cause data from Ring 0 to be output on Ring 1, and FLBBwill cause data from Ring 1 to be output on Ring 0.A Terminal Loopback will take data to be output on one ring and loop itback as an input on the corresponding timeslot on the other ring. TLBAwill take data to be output on Ring 1 and loop it back as incoming data onRing 0. TLBB will take data to be output on Ring 0 and loop it back asincoming data on Ring 1.

Using the MC3 Bus• 7-8 •The H.110 MC3/Conference Boardthis page intentionally left blank

CT Bus Switching • 8-1 •The H.110 MC3/Conference Board8.0 CT Bus SwitchingThis section describes the operation of the Computer Telephony busswitching capabilities of the Infinity Series H.110 MC3 Multi-ChassisInterconnect and Conference Board. Topics include the H.110 bus, MVIP-95 compatible commands, and the operation of the analog port. 8.1 The H.110 Switching HardwareThe H.110 MC3/Conference Board consists of two separate switch blocks.One of these is dedicated to switching between the MC3 bus and the CTbus. The other switch block is used for switching between computertelephony bus and the conferencing facilities. The two switch blocks usedifferent hardware components and can be treated as completelyindependent entities.A total of 1024 inputs from and 1024 outputs to the CT bus are availableon the board. If conferencing is enabled, 128 of these are used by theconference hardware. Because of this, when conferencing is enabled, only896 inputs and outputs are available between the CT bus and the MC3 bus.If the analog port is in use, the number of MC3 connections is reduced byone more.8.2 MVIP-95 Compatibility CommandsSeveral commands exist for compatibility with the MVIP-95 driverspecification. This specification uses the concept of a “terminus” to definean input or output timeslot. The terminus argument consists of three parts,a bus, a stream within the bus, and a timeslot on that stream. In MVIPcompatibility messages, a terminus is represented by a five character string.The first character indicates the bus. Valid bus selections are “C” for the

CT Bus Switching• 8-2 •The H.110 MC3/Conference Boardconference inputs and outputs, “H” for the H.110 CT bus, “L” for the localbus connected to the audio port, and “X” for the MC3 bus.In the MVIP compatibility mode, connections are controlled using the SetOutput command MO. This command takes the form MObssttm, where“bsstt” is the output terminus being controlled, and m is the mode. Validmodes are “D” for disable, “E” for enable, and “P” for pattern output. Inthe enabled mode, the input terminus follows the mode character, and inthe pattern mode, a two digit hexadecimal number representing the valueof the byte to be output follows the mode. As an example, the message“MOH0123EX0000” would enable a connection from the MC3 bustimeslot 0, stream 0 to the H.110 timeslot 23h, stream 1.A query command QObsstt is also available to query the state of theoutput terminus “bsstt”. This command corresponds to the Query_Outputcommand in the MVIP-95 specification. The response takes the formQObssttm(bsstt) where “bsstt” is the output terminus, “m” is the mode,and if the mode is enable, the second “bsstt” is the input terminus.The audio port is timeslot 0 of stream 0 of the “Local” bus. No othertimeslots exist on this bus. To access the audio port, it must be enabledusing a command of the form MAm where m is the mode, either “E” forenabled, or “D” for disabled. To make a connection from the port to thebus, the port must be enabled, and the connection made using the SetOutput command “MO”. Gain can be controlled as described in thefollowing section.In the MVIP compatibility mode, the conference function consists of asingle stream of 128 timeslots which correspond to the Conference ControlAddresses or CCAs. Input and output connections are made between theH.110 CT bus and the conference bus using the “MO” command. Eachconference input/output pair, or CCA is controlled with a command of theform MKhhccman where hh is the conference handle, cc is the CCA, mis the mode, either “E” for enable or “D” for disable, and a and n are theattenuation and noise threshold parameters. See section 9.1 for a moredetailed description of the operation of the conferencing hardware.

CT Bus Switching • 8-3 •The H.110 MC3/Conference BoardTo add a party to a conference, connections need to be made to theconference input and output using the “MO” command, and the CCAcontrolled using the “MK” command. As an example the commands:MOC0001EH0123 connection to the input of CCA 1MOH0555EC0001 connection from the output of CCA 1MK0201E00 enable CCA 1 for conference 2The previous commands add a party to the conference with a handle of 02using CCA 01. The input stream 1 timeslot 23, and the output is stream 5timeslot 55 on the H.110 bus. To remove the party from the conferencethe commands would be:MOC0001D disable input to CCA 1MOH0555D disable output to the H.110 busMK0201D disable CCA 1When using the MVIP compatibility commands, it is the responsibility ofthe application to allocate the CCAs.8.3 The Analog PortAn analog port is provided for use either as a music on hold source or formonitoring timeslots on the H.110 bus. The external connection to this portcan be made through either the J1 or J1A connectors. The signal levels atthis port are assumed to be at line levels compatible with most electronicequipment. An attenuation command is provided to make adjustments.When enabled, the analog port will use one of the 1024 possibleconnections between the board and the H.110 bus.The command to enable the music on hold feature is of the form AEoooowhere oooo is the H.110 timeslot the port will transmit on. The port maybe disabled with a command of the form AD.To use the port to monitor a timeslot, the command is of the form ARiiiiwhere iiii is the H.110 timeslot. The monitor can be disabled using the

CT Bus Switching• 8-4 •The H.110 MC3/Conference Boardcommand ARX.The input or output level can be attenuated using the gain command. Thistakes the form AGttrr where tt is the attenuation in the transmit directionand rr is the attenuation in the receive direction. The attenuation can bespecified in steps of .1 dB.Though the port is bi-directional, it is not recommended that it be used forboth transmitting to the H.110 bus and receiving from the H.110 bus at thesame time because it is a 2-wire circuit and there is no isolation between theinput and the output.

Conferencing • 9-1 •The H.110 MC3/Conference Board9.0 ConferencingThis section describes the conferencing facilities available on the InfinitySeries H.110 MC3 Multi-Chassis Interconnect and Conference Board.This description will include an overview of the conferencing hardware, thecommands for conferencing, the DTMF capabilities associated withconferencing and examples of how to establish and dissolve a conference.9.1 The Conferencing HardwareThe conferencing hardware on the H.110 MC3/Conference Board isarranged into two blocks. Each block consists of 21 conferences and 64inputs and outputs. Conferences can be of any size up to the maximumlimit of 64, but the total number of parties for all the conferences withinone block can not exceed 64. Conferences can not cross block boundaries.The two conferencing blocks are connected to the last 4 local streams ofthe last CT812 H.110 bus switch block. The first two streams areconnected to the first block and the third and fourth streams are connectedto the second conferencing block. Four DSPs, one for each local streamare connected in line between the CT812 and the conference inputs.When conferencing is enabled using the “SK”command, 128 H.110 inputsand outputs are removed from the MC3 hardware. Because of this, thetotal number of MC3 to H.110 connections is reduced from 1024 to 896.

Conferencing• 9-2 •The H.110 MC3/Conference Board9.1.1 Conference HandlesEach conference is identified with a handle. The value of this handleranges from 1-21 for the first block and 22-42 for the second conferenceblock. The handle is selected by the application. The handle is used in theconferencing commands to identify which conference the command appliesto. Each conference input and output is defined by a Conference ControlAddress, or CCA. These range from 0-127 with the first 64 CCAs beingassociated with the first conference block and the second 64 with thesecond conference block. Conference Control Addresses are associatedwith fixed timeslots on the local conferencing streams. CCAs 0-31 areassociated with the 32 timeslots of the first local stream, CCAs 32-63 withthe second local stream, and so on. On the H.110 MC3/Conference Board, the CCAs are hidden from the user,and they are assigned dynamically.9.1.2 Command SetThe Conferencing command set consists of commands that begin with theletter “C”. Each of these commands performs all of the switching andconference control for the command function. When using thesecommands, the on board processor manages the allocation of the CCAswhich are hidden from the application. Commands exist for adding orremoving a party from a conference, dissolving a conference, monitoringa conference or adding an input to a conference.9.1.3 Attenuation & Noise ThresholdEach conference input and output can have its attenuation controlled. Thiscan be done individually or globally for all members of a conference. Theattenuation is set with an attenuation parameter that is part of variousconferencing commands. The following table gives the amount ofattenuation the parameter selects:

Conferencing • 9-3 •The H.110 MC3/Conference BoardValue of a Input Attenuation Output Attenuation00 dB 0 dB10 dB 3 dB23 dB 0 dB33 dB 3 dB46 dB 0 dB56 dB 3 dB69 dB 0 dB79 dB 3 dBThe amount of attenuation required to maintain the desired level of audioquality depends on a number of factors such as the type and quality of theincoming lines. It also depends on the number of parties beingconferenced, with larger conferences requiring more attenuation. Typically,no attenuation is needed for conferences of four or fewer parties.A noise threshold can also be set for each conference input. When thisfunction is enabled, signals below a threshold will be suppressed. Thesetting “0” disables the function, while settings of “1” to “3” raise thethreshold to progressively higher values. It should be noted that highthreshold levels may introduce distortion and so should be used withdiscretion.9.1.4 DSP FacilitiesThe H.110 MC3/Conference Board is equipped with four DSPs which areconnected in the conference input streams between the H.110 bus and theconference blocks. The DSPs can be used to detect DTMF tones from theconference inputs. A “clamping” function can be enabled which isolatesDTMF tones by temporarily interrupting the input connection to theconferencing hardware when a tone is detected. This can be used to

Conferencing• 9-4 •The H.110 MC3/Conference Boardprevent the other parties of a conference from hearing the DTMF signals.Because a finite amount of time is required to detect the presence of aDTMF signal, a short burst of tone of approximately 20 msec. will getthrough before the tone is clamped.An energy detection feature is also available. This feature can be used todetermine the “loudest talker” in a conference. If this feature is enabled,the energy of each input to a conference is periodically placed in a table inthe dual-ported memory. This table is arranged by H.110 timeslot.9.2 Controlling ConferencesA party can be added to a conference using the conference add command.This command takes the form CAhhooooiiiian where hh is the conferencehandle, iiii is the H.110 timeslot of the input, oooo is the H.110 timeslot ofthe output, and a and n are optional parameters for attenuation and noisethreshold. If these parameters are left off, the default values of noattenuation and no noise threshold are used. If the timeslot was involved inanother conference at the time the command is issued, that connection willbe broken. Each party to a conference must be added using the sameconference handle.A party can be removed from a conference using the disconnect command.This command is of the form CDoooo where oooo is the H.110 timeslot.All parties to a conference can be disconnected at once using theunconference command. This command takes the form CUhh where hhis the conference handle.A conference can be monitored, that is, an output from the conference iscreated for which there is no associated input. This is done using theconference monitor command which is of the form CMhhoooo, where hhis the conference handle and oooo is the H.110 output timeslot. Theconference monitor function uses up a CCA just as does a full party to aconference, therefore, if more than one party is monitoring a conference,they should use the same timeslot. The monitor path is disabled by usingeither the “CD” or “CU” commands.

Conferencing • 9-5 •The H.110 MC3/Conference BoardA timeslot can serve as an input to a conference without there being acorresponding output. This is done using the conference input command“CI”. This command takes the form CIhhiiiian where hh is theconference handle, iiii is the conference input timeslot, and a and n are theattenuation and noise parameters. The same timeslot can serve as an inputto multiple conferences. Note, however, that if a “CA” command is issuedfor that timeslot after it is defined as an input for another conference, theinput will be disabled. However, subsequent “CI” commands can be usedto reestablish the inputs if desired. A “CD” will remove the timeslot fromall conferences. The timeslot can be removed as an input to a conferenceby using the “CX” command. This command takes the form CXhhiiiiwhere hh is the conference handle and iiii is the timeslot. Participation bythat timeslot in other conferences will be unaffected. A “CU” commandwill dissolve all inputs and outputs for a particular conference handle, butwill leave inputs to other conferences unaffected.9.3 Changing the Attenuation and NoiseThresholdOnce a conference is established, the attenuation and noise threshold canbe changed in one of two ways. To change the parameters for a singlemember of a conference, the “CA” command can be reissued with the newparameters. It is not necessary to remove the party from the conferencefirst. However, if a party is an input only, it must first be removed fromthe conference before changing parameters. Otherwise, there will be twooccurrences of that party.The parameters of all members of a conference can also be changed atonce using the Set Attenuation command “SA”. This command takes theform SAhhan where hh is the conference handle and a and n are theattenuation and noise threshold parameters.

Conferencing• 9-6 •The H.110 MC3/Conference Board9.4 DTMF DetectionThe H.110 MC3/Conference Board is equipped with four DSPs for DTMFdetection. The DSPs are connected between the H.110 bus and theconference inputs, and there is one detector for each input. This meansthat DTMF digits can be detected simultaneously on all the parties to all theconferences.To enable DTMF detection in conferences established using the “C”commands, the detection enable command “CE” is used. This takes theform CEiiii where iiii is the input timeslot of the conferee. Detected digitsare reported in a message of the form STiiiid where iiii is the timeslot andd is the digit detected. Detection is disabled with a command of the formCEiiiiD. It is also disabled when a “CD” or “CU” command is issued.One of the problems that can arise is that if detection is enabled for oneparty of a conference, a DTMF digit generated by another party to thatconference may also be detected. This can pose problems if the intentionis to determine which party has generated a DTMF digit, for instance whenthese digits are being used to control the conference.To resolve this problem, a feature called “clamping” has been added. Withthis feature enabled, the input from a party is interrupted for a short periodwhen a DTMF digit is detected. This allows the DSP to determine whichparty is generating the digit. It also prevents the tone from being passed tothe other members of the conference eliminating an annoying blast ofsound. Because it takes a short amount of time to determine if a tone ispresent, the first 20 msec. of tone will pass through.To enable this feature, an optional argument is added to the “CE”command. The command now takes the form CEiiiidd where dd is theduration of the interruption interval in 20 msec. increments. For example,CE00305 would interrupt the signal for 100 msec. The range of theinterruption interval is 01-CFh or between 20 and 4140 msec.

Conferencing • 9-7 •The H.110 MC3/Conference Board9.5 Energy DetectionThe DSPs on the H.110 MC3/Conference Board can provide an energydetection function. In this function, the energy of each conference input isaveraged over a period of 100 msec. This information is then placed in atable in the dual-ported memory where it can be accessed by an application.The table begins at an offset of 0 bytes and consists of 4096 (1000h) bytesarranged in order to correspond to H.110 timeslots. The values in thesetables will run from 00h to 1Fh with each step corresponding toapproximately 3 dB. A flag at an offset of 7934 (1EFEh) from the baseaddress of dual-ported memory is set to 01h every time the tables areupdated. The flag should be cleared by the application after it reads theenergy tables.The energy detection feature is enabled by sending an SDE command.This will enable energy detection for all conferences. An SDD commandwill disable energy detection.9.6 2 kHz. Tone Generation and DetectionSignaling System 7 uses a 2 kHz. tone for performing continuity checks toverify the operation of speech circuits. The H.110 MC3/ConferencingBoard is capable of generating and detecting this tone. A single generatoris provided to play a 2 kHz. tone to an H.110 bus timeslot. From there, itmay be routed to multiple MC3 bus timeslots. Up to 128 detectors areavailable for the detection of the 2 kHz. tones. The DSP resources for 2kHz. detection are shared with those used for DTMF detection andclamping of conferenced inputs. Conferencing must be enabled for the 2kHz. detection and generation to be available. Note, that at most, 128detectors, generators and conference parties can be assigned at a time.Because the DSP facilities are located in the input leg of the conferencingfacility, each detector and generator utilize one of the 128 ConferenceControl Addresses (CCA). The assignment of CCAs is done dynamically.

Conferencing• 9-8 •The H.110 MC3/Conference BoardTo minimize conflicts between conferencing and the 2 kHz. detection, theassignment of CCAs for the 2 kHz. detection is done from the highestnumbered CCA on down. The 2 kHz. generator, when enabled, uses thehighest numbered CCA, 127.The generator is enabled using a command of the form CToooo whereoooo is the H.110 bus stream and timeslot that the tone will be output on.The generator should not be enabled if any of the 2 kHz. detectors areenabled as this may result in a possible CCA assignment conflict. If aconflict occurs, an error message of the form EG01 will be reported. Thegenerator may be disabled with a command of the form CTooooD whereoooo is the H.110 bus stream and timeslot. In practice, it is best to enablethe generator at start up time and leave it connected to the H.110 bus. To output the tone to an MC3 timeslot, the command takes the formXLOyyyyiiii where yyyy is the MC3 stream and timeslot and iiii is theH.110 stream and timeslot of the tone. The tone is disconnected from theMC3 bus using the command XDOyyyy. The 2 kHz. tone may be outputto multiple MC3 timeslots by issuing multiple commands within theswitching limitations of the board. (i.e., a total of 896 connections areallowed in either direction with conferencing enabled.)To enable tone detection, a one-way path is created from the MC3 bus tothe H.110 bus using the command XLIoooozzzz and enabling the detectorwith a command CLoooo where oooo is the H.110 stream and timeslotand zzzz is the MC3 stream and timeslot. Detection of the tone is reportedwith a message of the form STooooA where oooo is the H.110 stream andtimeslot used by the detector. Detection is disabled with a command of theform CLooooD to disable the detector and a command of the formXDIoooo to disable the audio path.9.7 Conferencing ExamplesThis section will give examples of how to create and dissolve conferences,set up inputs and monitors, and detect DTMF digits.

Conferencing • 9-9 •The H.110 MC3/Conference BoardIn the first example, three input timeslots, 0110, 0112, and 0114 areconferenced together using conference handle 03 with the outputs at 0000,0001, and 0002 respectively:CA030000011000CA030001011200CA030002011400To enable DTMF detection with 80 msec. of clamping:CE011004CE011204CE011404To add an input to this conference and conference 05 from timeslot 0205:CI03020500CI05020500And to monitor the conference on timeslot 0917CM030917Timeslot 0001 and the corresponding input at 0112 could be removed fromthe conference by:CD0001Or the conference could be dissolved with the command:CU03

Conferencing• 9-10 •The H.110 MC3/Conference Boardthis page intentionally left blank

Diagnostics & Error Messages • 10-1 •The H.110 MC3/Conference Board10.0 Diagnostics & ErrorMessages10.1 Diagnostic CommandsSeveral diagnostic commands are available:VA Used to request the checksum of the firmware in the alternatesegment of the board. This is returned in a message of theform VAxxxx where xxxx is the checksum of the firmwarein the alternate segment of ROM.VC Used to request the version of the firmware on the board.The version information is returned in a message of the formVCxxxxyyyyHO3, where xxxx is the checksum of thefirmware stored in the main segment of ROM, yyyy is afour-digit version number and HO3 indicates the board type.This message takes the same form with all Infinity Seriesboards, and can be used to determine the configuration of thesystem.VD Used to request the version of the DSP software. Theversion is returned in a message of the form VDxxxx, wherexxxx is the version number. All DSP’s on the board use thesame software version.QHcrrrr Queries the contents of the CT812 chip c, for register rrrr.The contents are returned as the 24 bit value ddddddvalues in the message QHcrrrrdddddd. This commandrefers to the details of the internal switching circuitry, and isordinarily of limited use to the application.QL This message queries the geographical shelf and slot

Diagnostics & Error Messages• 10-2 •The H.110 MC3/Conference Boardinformation. Each slot and chassis in a CompactPCI has aunique address allowing the identification of the physicallocation of any board. The information is returned in amessage of the form QLaabb where aa is hexadecimalvalue of the shelf address bits and bb is the value of the slotaddress bits.QMRx0zzz This command queries the MC3 90840 interface chip x forthe contents of the receive path connection memory andtransmit path data memory for the internal timeslot zzz.The results are returned in a message of the formQMRx0zzzhhlldd where hh and ll are the high and lowbyte contents of the receive path connection memory and ddis the contents of the transmit path data memory. Thiscommand refers to the details of the internal switchingcircuitry, and is ordinarily of limited use to the application.QMTxyyyy This command queries the MC3 90840 interface chip x forthe contents of the transmit path connection memory andreceive path data memory for MC3 timeslot yyyy. Theresults are returned in a message of the formQMTxyyyyhhlldd where hh and ll are the high and lowbyte contents of the transmit path connection memory and ddis the contents of the receive path data memory. Thiscommand refers to the details of the internal switchingcircuitry, and is ordinarily of limited use to the application,though it may be used to look for a pattern byte on the MC3bus.

Diagnostics & Error Messages • 10-3 •The H.110 MC3/Conference Board10.2 Error MessagesThe board will detect a number of error conditions and respond withappropriate error messages. These messages are:ECxx A clock error bit event xx has occurred. The value xx is ahexadecimal number where the bits are (a bit value of 1 is an error)bit description0CT bus clock A1CT bus clock B2SCbus clocks3MVIP bus clocks4Master PLL error5Frame BoundaryEFr A failure of ring r has been detected.EG01 A conflict has occurred when attempting to enable the 2 kHz.tone generator.EKhhxx An error has occurred while attempting to make a conferenceusing handle hh. If xx equals 01, a handle outside the rangeof 01-2Ah was used. If xx equals 02, all conference facilitiesavailable for that handle are in use.EPxxxx An attempt at switching has failed because all connectionsbetween the MC3 and H.110 bus are used. The commandwas for stream and timeslot xxxx.ERr Restoration of ring r has been detected.

Diagnostics & Error Messages• 10-4 •The H.110 MC3/Conference BoardESrxx A change in the ring status error bits has been detected forring r. The status bits are reported in xx. The bit values arebit description 0 LOS - loss of signal 1 LOF - loss of frame 2 OOF - out of frame 3 RFE - receive frame error 4 B1ERR - bit error 6 FSA - frame slip alarm 7 TXPPA - transmit phase alignment alarmU[cmnd] If the board does not recognize a command message, or if itdoes not have the appropriate number of arguments, the samemessage will be returned by the board preceded by a U toindicate an undefined message.10.3 QM QueriesThe QMT and QMR commands can be used to query the contents of theconnection and data memories of the chips used to interface to the MC3rings. Four MT90840 chips control the switching between the MC3 ringsand an internal bus, with two chips used for each ring. This internal bushas 1024 timeslots and is used to connect the MT90840 chips with theCT812 chips used to interface to the H.110 bus. These internal timeslotsare assigned dynamically with the first connection established using the firsttimeslot, the second connection the next timeslot and so on. When aconnection is disabled, the internal timeslot is released for use.The QMT command can be used to read the connection memory and dataassociated with the MC3 bus. The command takes the form QMTxyyyywhere x specifies the chip and yyyy specify the MC3 stream and timeslot.Each “stream” has 64 timeslots and the range runs from 0000 to 2536.The chips 0 and 1 are associated with Ring 0 and chips 2 and 3 areassociated with Ring 1.

Diagnostics & Error Messages • 10-5 •The H.110 MC3/Conference BoardThe response takes the form QMTxyyyyhhlldd where xyyyy are as in thequery, hh is the high byte of the connection memory, ll the low byte, anddd the contents of the data memory. The top three bits of the high byte arecontrol bits. The value of the high byte will be C0h or 00h when output isdisabled, 8xh when enabled, and A0h when outputting a pattern. The lowbyte and bit 0 of the high byte contain the internal bus timeslot address.When outputting a pattern, the low byte will be the value of the pattern.The data byte will contain the value on the MC3 bus timeslot.The QMR command can be used to read the connection memory and dataassociated with the internal bus. The command takes the form QMRx0zzzwhere x specifies the chip and 0zzz specifies the internal stream andtimeslot. Each “stream” has 64 timeslots and the range runs from 0000 to073F. Chips 0 and 1 are associated with Ring 0 and chips 2 and 3 areassociated with Ring 1.The response takes the form QMRx0zzzyhhlldd where x0zzz are as in thequery, hh is the high byte of the connection memory, ll the low byte, anddd the contents of the data memory. The top four bits of the high byte arecontrol bits. The value of the high byte will be 0xh when output is disabledand 3xh when enabled. The remaining bits of the connection memory arethe MC3 bus timeslot address. This command reads the actual contents ofthe MT90840. Because several timeslots are used for framing purposes,the address bits do not contain the MC3 stream and timeslot value as usedin commands. For timeslots 0000-0407, the address bits are incrementedby 1 over the command timeslot and for timeslots 0408-2536 the addressbits are incremented by 2. For example, if the address bits read 011h, thisindicates stream 00, timeslot 10, and if the address bits read 142, thismeans stream 5, timeslot 0. The data bits are the value present on the localtimeslot.

Diagnostics & Error Messages• 10-6 •The H.110 MC3/Conference Boardthis page intentionally left blank

Appendix A: Environmental Specifications • A-1 •The H.110 MC3/Conference BoardAppendix A:Environmental SpecificationsThe Infinity Series H.110 MC3 Multi-Chassis Interconnect and ConferenceBoard meets the following environmental specifications:TEMPERATURE EXTREMES:Operating: 0EC (+32EF) to +50EC (+122EF).Storage: –40EC (–40EF) to +70EC (+158EF).AMBIENT HUMIDITY:All boards will withstand ambient relative humidity from 0% to 95% non-condensing in both operating and storage conditions.MECHANICAL:All Infinity Series H.110 boards conform to PCI-SIG mechanicalspecifications for 6U CompactPCI cards.MTBF:150,000 hours.ELECTRICAL REQUIREMENTS:+5 volts ±5% @ 4.0 amps maximum.-12 volts @ 15 mA. maximum+3.3 volts, - volts, and +12 volts are not required.

Appendix A: Environmental Specifications• A-2 •The H.110 MC3/Conference Boardthis page intentionally left blank

Appendix B: Notes on H.110 MC3 Redundancy • B-1 •The H.110 MC3/Conference BoardAppendix B:Notes on H.110 MC3 RedundancyB.1 IntroductionMC3 is designed to provide for fault tolerance in systems by allowing usersto implement redundant operation. This document describes theprocedures that may be used to implement the fault tolerant design and howto recover from a ring failure.B.2 Term DefinitionFirst, some terms need to be defined. In some failure modes, it isnecessary to know the arrangement of chassis in a ring. For purposes ofthis document, the terms upstream and downstream will be used whendiscussing the topology of the ring. Let's say there are three chassis in asystem, labeled Chassis A, Chassis B, and Chassis C. Chassis A transmitsto Chassis B on ring 0, Chassis B transmits to Chassis C on ring 0, andChassis C transmits to Chassis A on ring 0. Since the rings counter-rotate,Chassis A therefore transmits to Chassis C on ring 1, Chassis C transmitsto B on ring 1, and B to A on ring 1. Given this topology, we can considerthe locations of Chassis A and C with respect to B. By definition, ChassisA is upstream of Chassis B on ring 0 and downstream of Chassis B on ring1 (because Chassis B is receiving data from Chassis A on ring 0 andtransmitting to Chassis A on ring 1). Likewise, Chassis C is downstreamof Chassis B on ring 0 and upstream of Chassis B on ring 1.This terminology works well when describing adjacent chassis. However,it is sometimes necessary to consider all chassis in the system. Since a ringtopology is used, it could be argued that a given chassis is downstream ofall other chassis. When a ring break occurs, it will be necessary to considerwhat happens to the clocking for the system. In order to do this rationally,the chassis that is providing the master clock for the system will beconsidered the origin of the ring.

Appendix B: Notes on H.110 MC3 Redundancy• B-2 •The H.110 MC3/Conference BoardIf we consider the three chassis example above, with chassis A providingthe master clock for the system, and assume a break occurs betweenchassis B and C, we can consider chassis A and B to be upstream of thebreak on ring 0. Chassis C and A are upstream of the break on ring 1.B.3 Setting up Redundant OperationBefore setting up redundant operation, the clock configuration for thesystem must be established and a primary and secondary ring must bedefined. The clock configuration requires that one chassis provide themaster clock for the system. Generally, this clock is derived from a digitalnetwork trunk, although the MC3 board is capable of providing afree-running clock. All other chassis will be set up to derive their clockfrom the designated primary ring.Once the clocks have been configured for all chassis, redundant mode isenabled by issuing an "SMx" command, where "x" is '1' if ring 0 is theprimary ring or '2' if ring 1 is the primary ring. At this point, redundantoperation is enabled. Note that in commands dealing with connections, allcommands must use streams on ring 0. It is not valid to use a stream onring 1. Thus, the command "XC0000000126002601" is not valid. Instead,"XC0000000100000001" would establish a connection. B.4 Responding to a Ring BreakThe main actions necessary to respond to a ring break are to loop back dataon each side of the break so that all chassis can still access all data and toreconfigure clock modes as appropriate. The required actions for a givenchassis will depend on its location in the ring with respect to the break. Thefollowing paragraphs describe the specifics.1. A chassis detects a failure in the secondary ring. This chassis simplyneeds to issue an "SRx" command to appropriately reroute the data. If theprimary ring was 0, the chassis will issue an "SR2". If the primary ring was1, the chassis will issue an "SR1".

Appendix B: Notes on H.110 MC3 Redundancy • B-3 •The H.110 MC3/Conference Board2. A chassis detects a failure in the primary ring. This chassis mustimplement several procedures. First, it will need to issue an "SMx"command to make the secondary ring primary for as long as the breakexists. If ring 0 was primary, an "SM2" command will be issued. If ring1 was primary, an "SM1" will be issued.Next, an "SRx" command will be issued to appropriately reroute the data.If ring 0 was primary, an "SR1" will be issued. If ring 1 was primary, an"SR2" will be issued.Third, the clocks for the system will need to be reconfigured. This iswhere the application must know the physical ring topology. Basically, allchassis from the failed chassis downstream to the clock master on theprimary ring must switch clock modes to derive their clock from thesecondary ring.3. A chassis detects failures in both rings. This would generally occur in amaintenance situation and will require recovery procedures that combinethe two failures. Usually, the chassis next to it in one direction would geta failure in one ring and the chassis next to it in the other direction wouldget a failure in the other ring. A brief example is given below.If one of the rings is restored, the appropriate "SRx" command should beissued for the remaining failed ring. Thus, if ring 1 is restored and ring 0is still failed (with ring 0 the primary ring), an SR1 should be issued. Whenthe second ring is restored, an "SR0" should be issued.4. Multiple failures are detected in a single ring. Generally, these can bedealt with as the failures are received as though no other failures occurred.However, when recovering from a multiple failure condition, theappropriate clock modes must be retained. For example, if ring 0 is primaryand two chassis detect a ring 0 failure, both will issue "SR1" commands and"SM2" commands. Both will also reconfigure clocks on all ring 0downstream chassis to derive their clocks from ring 1. However, if one ofthe rings recovers, all chassis downstream of the other failed chassis willstill need to continue deriving their clocks from ring 1. Thus, if the chassisthat recovers first is downstream of the other, the clock mode should not

Appendix B: Notes on H.110 MC3 Redundancy• B-4 •The H.110 MC3/Conference Boardbe changed. If the chassis that recovers first is upstream of the other, onlythose chassis from the recovered one to the failed one will have their clockreconfigured.B.5 Examples of Some Specific CasesA. Assume the three chassis configuration described in the Term Definitionsection. Chassis A is providing the master clock, chassis B and C arederiving their clock from ring 0. Ring 0 has been designated as primary byissuing "SM1" commands to all three chassis.Chassis A detects a failure on ring 0. It will issue an "SM2" and an "SR1"command. Since it is the master clock, it does not need to change clockmodes. Furthermore, since chassis B and C are downstream on ring 0,their clock modes do not need to change.Typically, if chassis A detects a failure on ring 0, chassis B will detect afailure on ring 1. It will therefore issue an "SR2" command.B. The system is setup as described in Example A. Chassis B detects afailure on ring 0. It will issue an "SM2" command and an "SR1" command.Neither chassis B nor chassis C can derive their clock from ring 0 any morebecause both are downstream of the break on ring 0. Thus, both ChassisB and Chassis C will change their clock modes so that they are derivingtheir clock from ring 1.C. The system is setup as described in Example A. Chassis C detects afailure on ring 0. It will issue an "SM2" command and an "SR1" command.Since chassis B is upstream of the break on ring 0, it does not need tochange its clock mode. However, chassis C will need to change clockmodes so that it will begin deriving its clock from ring 1.D. The system is setup as described in Example A. Chassis B detectsfailures on both rings. Generally, this means that chassis A will detect aring failure on ring 1 and chassis C will detect a failure on ring 0. Assumingthis to be the case, chassis B is simply no longer in the loop and cannotrecover.

Appendix B: Notes on H.110 MC3 Redundancy • B-5 •The H.110 MC3/Conference BoardIf, for some reason, chassis A and C do not get ring failures, chassis Bshould notify chassis A that there was a failure on ring 1 (as though chassisA did get a ring failure on ring 1). Chassis A will then issue an "SR2"command. Likewise, chassis B should notify chassis C that there was afailure on ring 0 (as though Chassis C did get a ring failure on ring 0).Chassis C will then issue an "SM2" command and an "SR1" command, aswell as changing clock modes so that it is deriving its clock from ring 1.B.6 Recovering from a Ring BreakWhen a ring is restored after a break, recovery is basically reversing whatwas done when the break occurred. If a chassis detects a recovery on thesecondary ring, it will issue an "SR0" command. If a chassis detectsrecovery on the primary ring, it will issue an "SR0" command, an "SMx"command, where "x" is '1' if ring 0 is primary and '2' if ring 1 is primary,and will set all clocks back to their original configuration. (Clockreconfiguration may be complicated if multiple chassis detected a failure onthe primary ring. This situation was described in failure mode 4 above.)If errors had occurred on both rings, the application must deal with therecovery of one ring by acting as though the remaining ring had just failed.Thus, the application will not issue an "SR0" command if only one ringrecovers. Instead, it will issue an "SR" command appropriate for the ringthat is still failed. Clock modes will have to be dealt with similarly. B.7 Combining Redundant and Extended Operation ModesIn some cases, customers may desire to run with the total MC3 bandwidthavailable. However, if there is a break, they would like to recover asgracefully as possible, although some connections may be lost. This can bedone using the XDS MC3 board if some basic guidelines are followed.First, the application should select a primary ring. This ring should be usedfor all connections until its bandwidth is used up. The secondary ring maythen be used for overflow connections.

Appendix B: Notes on H.110 MC3 Redundancy• B-6 •The H.110 MC3/Conference BoardIf a ring failure is detected, the application should issue "SMx" commandsto all chassis, where "x" is '1' if ring 0 was primary, or '2' if ring 1 wasprimary. This will automatically disconnect all connections on both rings,and will enter the redundant mode. The application will then need toreestablish all connections, as appropriate, given the remaining bandwidth.After the connections have been restored, the system is treated as astandard redundant configuration.The application may return to extended mode operation at any time byissuing "SM0" and "SR0" commands. ("SR0" commands are only neededif a chassis was in mode "SR1" or "SR2".) When it does so, allconnections will again be terminated by the board and will need to bere-established via software control.B.8 Determining System TopologyIn order to implement appropriate fallback techniques, the location of eachchassis in the ring must be known. This could be handled manually byhaving the user enter configuration data. However, it is also possible to usepatterns on the MC3 bus to determine where chassis are with respect toeach other.The manual method requires keeping track of where each fiber optic cableis connected. On a given board, there are two duplex fiber connectors.With the board mounted vertically in a cPCI chassis, the bottom positionof the bottom connector is the Ring 0 input. The top position of thisconnector is the Ring 1 output. Similarly, the bottom position in the topconnector is the Ring 1 input and the top position of the top connector isthe Ring 0 output. When cabling multiple chassis, the ring 0 output of onechassis goes to the Ring 0 input of the next chassis. The Ring 1 output ofthis second chassis goes back to the Ring 1 input of the first chassis. Thisconfiguration is continued around the ring until all chassis are in the ring.The application software can also determine the ring topology by applyingpatterns appropriately to the MC3 bus. The procedure is essentially thesame whether extended mode or redundant mode is being used. However,in redundant mode, the procedure will determine the ordering of chassis on

Appendix B: Notes on H.110 MC3 Redundancy • B-7 •The H.110 MC3/Conference Boardthe primary ring, whereas in extended mode, the ordering of chassis can bedetermined on either ring based on the commands that are issued.To enable chassis identification, every chassis should output a unique IDcode in the range 00h - 0FFh on a timeslot on one of the rings. All chassisshould use the same timeslot and the same ring. This may be accomplishedwith the "XPO" command. For example, if timeslot 0 on ring 0 is to havethe ID code, the application would issue "XPO0000pp", where 'pp' is thepattern to output. Next, each chassis must query the selected ID timeslot to determine whichchassis is transmitting to it. This can be done with the "QMT" command.For the given example, the command issued would be "QMT00000". Theboard would respond with "QMT00000xxxxpp", where the 'x' argumentsmay be ignored and 'pp' is the value of the pattern on ring 0 timeslot 0.This pattern is the ID of the board immediately upstream of the chassis onring 0. It also indicates the downstream chassis on ring 1. Generally, it isprobably best to configure all patterns in all chassis first. Then, after anominal delay to ensure that the pattern is available in all chassis, the"QMT" commands may be issued.If ring 1 is used for the pattern, the "QMT" command will have the format"QMT2sstt", where 'ss' will be the stream number minus 26h and 'tt' is thetimeslot used.Once the IDs have been determined, the patterns may be disconnected.For the example, the command "XDO0000" could be used in all chassis.The topology derived from the ID codes may be saved and used todetermine how to configure clock modes when a ring failure occurs.B.9 Maximum Timeslot UtilizationWhen the multi-chassis system is used for simple full-duplex connections,each party in the connection can use the same MC3 timeslot for maximumcapacity. Thus, if two parties are involved in a full duplex conversation andone is transmitting on ring 0 timeslot 0, the other can also transmit on ring

Appendix B: Notes on H.110 MC3 Redundancy• B-8 •The H.110 MC3/Conference Board0 timeslot 0. Each would therefore listen to ring 0 timeslot 0. This modeof operation provides for a total of 4846 full-duplex conversations inextended mode and 2423 full-duplex conversations in redundant mode.In broadcast configurations, where multiple devices listen to the sametransmitter, the transmitting device must use a unique timeslot. No otherdevices can transmit on this timeslot, but as many devices as necessary(depending on the switching capacity of the system), can listen to thistimeslot.