CG 6565 Installation and Developer's Manual

Transcription

1 CG 6565 Installation and Developer's Manual Crossing Boulevard Framingham, MA USA

2 CG 6565 Installation and Developer's Manual No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of NMS Communications Corporation NMS Communications Corporation. All Rights Reserved. Alliance Generation is a registered trademark of NMS Communications Corporation or its subsidiaries. NMS Communications, Natural MicroSystems, AG, CG, CX, QX, Convergence Generation, Natural Access, Natural Access MX, CT Access, Natural Call Control, Natural Media, NaturalFax, NaturalRecognition, NaturalText, Fusion, Open Telecommunications, Natural Platforms, NMS HearSay, AccessGate, MyCaller, and HMIC are trademarks or service marks of NMS Communications Corporation or its subsidiaries. Multi- Vendor Integration Protocol (MVIP) is a registered trademark of GO-MVIP, Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. Windows NT, MS-DOS, MS Word, Windows 2000, and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Clarent and Clarent ThroughPacket are trademarks of Clarent Corporation. Sun, Sun Microsystems, Solaris, Netra, and the Sun logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and/or other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the United States and/or other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. Linux is a registered trademark of Linus Torvalds. Red Hat is a registered trademark of Red Hat, Inc. All other marks referenced herein are trademarks or service marks of the respective owner(s) of such marks. All other products used as components within this product are the trademarks, service marks, registered trademarks, or registered service marks of their respective owners. Every effort has been made to ensure the accuracy of this manual. However, due to the ongoing improvements and revisions to our products, NMS Communications cannot guarantee the accuracy of the printed material after the date of publication or accept responsibility for errors or omissions. Revised manuals and update sheets may be published when deemed necessary by NMS Communications. P/N Revision history Revision Release date Notes 1.0 May 2005 SRR 1.1 July 2005 LBG/MVH 1.2 October 2005 LBG, Natural Access , SP July 2006 LBG, Natural Access , SP December 2006 LBZ, Natural Access , SP June 2007 LBZ, Natural Access , SP 4 Last modified: June 13, 2007 Refer to the NMS Communications web site ( for product updates and for information about support policies, warranty information, and service offerings. 2 NMS Communications

3 Table Of Contents Chapter 1: Introduction...9 Chapter 2: Overview of the CG 6565 board...11 Migration information...11 Hardware differences...11 Software differences...12 CG 6565 board features...16 Software components...20 NMS OAM...20 Configuration files...21 Runtime software...22 Trunk control programs (TCPs)...23 Natural Access...23 NMS Fusion and the CG 6565 board...24 Ethernet interfaces...24 Temperature monitoring system...25 Warning error message...25 Critical error message...25 Chapter 3: Installing the hardware...27 System requirements...27 CG driver software...27 Installation summary...27 Configuring the hardware...28 Configuring H.100 bus termination...29 Configuring the DIP switches...29 Configuring the board without trunk interfaces...30 Configuring the T1 or E1 interface...30 Configuring hardware echo cancellation...31 Installing the board...32 Connecting to the network...32 Chapter 4: Establishing network connections...33 Connectors and cables...33 Ethernet connectors...33 Four-trunk board...33 Eight-trunk board...37 Connecting to a T1 network...40 Connecting to an E1 network...41 Connecting a four-trunk CG 6565 to an E1 120 ohm...42 Connecting a four-trunk CG 6565 to an E1 75 ohm...42 Connecting an eight-trunk CG 6565 to an E1 120 ohm...42 Connecting an eight-trunk CG 6565 to an E1 75 ohm...42 Grounding the conductor...43 Testing in loopback mode...43 Testing with four trunks...43 Testing with eight trunks...44 Connecting to an Ethernet network...45 NMS Communications 3

4 Table of Contents CG 6565 Installation and Developer's Manual Chapter 5: Configuring the board...47 Configuring and starting the system with oamsys...47 Creating a system configuration file for oamsys...48 Running oamsys...49 Using board keyword files...50 Changing configuration parameters...50 Specifying configuration file locations...51 Configuring board clocking...51 CG 6565 clocking capabilities...52 Configuring clocking...55 Configuring CG 6565 board clocking using keywords...55 Multiple board system example...57 Managing board DSP resources...59 Setting up a single resource pool...60 Setting up multiple resource pools...60 Using multiple resource pools...61 Sample board keyword file...61 Chapter 6: Configuring Ethernet interfaces...63 Configuring IPv4 Ethernet connections...63 Using IPv4 Ethernet interface keywords...63 Setting up the IPv4 Ethernet connections...63 Configuring IPv6 Ethernet connections...65 IPv6 Ethernet interface keywords...65 IPv6 addresses and routing...65 IPv6 and neighbor discovery...66 IP security and IPv IPv6 path redundancy...67 Example configuration...67 IPv6 standards...68 Running in IPv4/IPv6 dual stack mode...68 Setting up multi-homed configurations...69 Load balancing in dual subnet configurations...69 UDP port numbers in multi-homed configurations...71 Configuring the board in redundant Ethernet mode...72 Configuring the board in dual subnet mode...73 Monitoring Ethernet link status events...74 Chapter 7: Verifying the installation...75 Status indicator LEDs...75 Trunk LEDs...75 Ethernet LEDs...77 Board LEDs...78 Verifying the board installation...79 Verifying trunk connections...79 Demonstration programs...80 Chapter 8: CG 6565 switching...81 Switch blocking...81 CG 6565 switch models...81 CAS mode switching...82 CAS switching limitations...82 CAS mode switch model NMS Communications

5 CG 6565 Installation and Developer's Manual Table of Contents H.100 and local streams...84 Voice and signaling information routing on T1 trunks (CAS mode)...85 Voice and signaling information routing on E1 trunks (CAS mode)...86 Default connections (CAS mode)...87 PRI mode switching...89 PRI mode switch model...90 H.100 and local streams...90 Voice information routing on T1 trunks (PRI mode)...92 Voice information routing on E1 trunks (PRI mode)...93 T1/E1 signaling information routing (PRI mode)...93 Default connections (PRI mode)...94 RAW mode switching...94 RAW mode switch model...95 H.100 and local streams...95 Voice information routing on T1 trunks (RAW mode)...97 Voice information routing on E1 trunks (RAW mode)...98 T1/E1 signaling information routing (RAW mode)...98 Default connections (RAW mode)...98 Chapter 9: Echo cancellation control Using echo cancellation control Syntax Setting or retrieving the echo cancellation bypass state Setting the bypass state example Retrieving the bypass state example Setting or retrieving the nonlinear processing state Setting the NLP state example Retrieving the NLP state example Setting or retrieving the acoustic echo control state Setting the acoustic echo control state example Retrieving the acoustic echo control state example Chapter 10: Keyword summary Keyword types Setting keyword values Retrieving keyword values Editable keywords Informational keywords Retrieving board information Retrieving driver information Retrieving miscellaneous information Retrieving EEPROM information Plug-in keywords Chapter 11: Keyword reference Using the keyword reference AutoStart AutoStop Boards[x] BootDiagnosticLevel Buffers[x].Size Clocking.HBus.AutoFallBack Clocking.HBus.ClockMode NMS Communications 5

6 Table of Contents CG 6565 Installation and Developer's Manual Clocking.HBus.ClockSource Clocking.HBus.ClockSourceNetwork Clocking.HBus.FallBackClockSource Clocking.HBus.FallBackNetwork Clocking.HBus.NetRefSource Clocking.HBus.NetRefSourceNetwork Clocking.HBus.NetRefSpeed Clocking.HBus.SClockSpeed Clocking.HBus.Segment ConferencingStream.Enable ConferencingStream.SlotCount DebugMask DetectedBoards[x] DLMFiles[x] DSP.C5x[x].Image DSP.C5x[x].Libs[y] DSP.C5x[x].NumRxTimeSlots DSP.C5x[x].NumTxTimeSlots DSP.C5x[x].OS DSP.C5x[x].XLaw DSPStream.SignalIdleCode[x] DSPStream.SlotCount DSPStream.VoiceIdleCode[x] DynamicRecordBuffers Echo.AutoSwitchingRefSource Echo.EnableExternalPins EnableMonitor HardwareEcho.EchoChipEnabled HardwareEcho.Trunk[x].OnOffTimeslots HardwareEcho.XLaw Hdlc[x].Boot Hdlc[x].RxTimeSlot Hdlc[x].TxTimeSlot IPC.AddRoute[x].DestinationAddress IPC.AddRoute[x].GatewayAddress IPC.AddRoute[x].Interface IPC.AddRoute[x].Mask IPv6.Link[x].Enable IPv6.Link[x].EnablePing IPv6.Link[x].HopLimit IPv6.Link[x].ICMPRateLimit IPv6.Link[x].IPSec IPv6.Link[x].MTU IPv6.Link[x].NDAttempts IPv6.Link[x].NDReachabilityTimer IPv6.Link[x].NDRetranTimer Location.PCI.Bus Location.PCI.Slot MaxChannels Name NetworkInterface.Ethernet[x].MAC_Address NetworkInterface.T1E1[x].AlarmMode NetworkInterface.T1E1[x].CRCMFMode NMS Communications

7 CG 6565 Installation and Developer's Manual Table of Contents NetworkInterface.T1E1[x].D_Channel NetworkInterface.T1E1[x].FrameType NetworkInterface.T1E1[x].Impedance NetworkInterface.T1E1[x].ISDN.D_Channel_Backup_Trunk NetworkInterface.T1E1[x].ISDN.NFAS_Member[y].Board NetworkInterface.T1E1[x].ISDN.NFAS_Member[y].NAI NetworkInterface.T1E1[x].ISDN.NFAS_Member[y].Trunk NetworkInterface.T1E1[x].ISDN.NFASGroup NetworkInterface.T1E1[x].Length NetworkInterface.T1E1[x].LineCode NetworkInterface.T1E1[x].SignalingType NetworkInterface.T1E1[x].Type Number Products[x] Resource[x].Definitions Resource[x].DSPs Resource[x].Name Resource[x].Size Resource[x].StartTimeSlot Resource[x].TCPs SwitchConnections SwitchConnectMode TPKT.ComplexForward.Count TPKT.ComplexForward[x].DestinationPacketSize TPKT.ComplexForward[x].LifeTimeTicks TPKT.ComplexRxPort TPKT.ComplexTxPort TPKT.Enable TPKT.NumberOfComplexForwardConditions TPKT.SimpleRxPort TPKT.SimpleTxPort Version.Major Version.Minor Chapter 12: Hardware specifications General hardware specifications Physical Media stream DSP processing IP network connectivity PSTN network connectivity Software environment Host interface H.100 compliant interface Environment Power requirements CEPT E1 G.703 telephony interface DSX-1 telephony interface Compliance and regulatory certification EMC Safety Telecom EU R&TTE statement NMS Communications 7

8 Table of Contents CG 6565 Installation and Developer's Manual Chapter 13: DSP resource management Managed DSP resources DSPs, DPMs, and DPFs DSP resources Worst-case resource management calculation Example Resource calculations Determining the maximum number of ports available DSP resource management keywords Resource definition string syntax DSP image and resource definitions Resource definitions Input and output slots Resource definition examples Conditional relationships between DPFs Natural Access media masks and call progress masks Software echo cancellation restriction Trunk control program resource usage Debugging resource management Using CG board debug masks Resource management board errors Debugging resource management with cgtrace DSP files and MIPS requirements Software echo cancellation MIPS DSP files Chapter 14: T1 and E1 trunk channels Channels and transmission rates Signaling Channel associated signaling (CAS) Common channel signaling (CCS) Framing T1 framing E1 framing Voice encoding Companding AMI, ones density, and zero code suppression Chapter 15: Utilities Utility summary f41info - Displaying DPF file resource usage cg6kcon - Displaying statistics about CG board activity cg6ktool - Displaying EEPROM and RAM cgroute - Setting up CG board IPv4 routing tables cgsetkey - Configuring IPv6 security keys and policies cgtrace - Performing CG board debugging cgv6if - Adding, printing, and deleting IPv6 addresses NMS Communications

9 1 Introduction The CG 6565 Installation and Developer's Manual explains how to perform the following tasks: Install and configure a CG 6565 board. Verify that the board is installed and operating correctly. Use the CG 6565 board keywords to configure the board. Use the CG 6565 board utilities. This manual is for programmers and system integrators who develop media server applications. This manual defines telephony terms where applicable, but assumes that the reader is familiar with basic telephony and Internet data communication concepts, switching, and the C programming language. NMS Communications 9

10

11 2 Overview of the CG 6565 board Migration information The CG 6565 board is based on the CG 6000/C, CG 6100C, and CG 6500C boards. Although the boards are very similar, be aware of the following hardware and software differences as you migrate from one of these boards to the CG 6565 board. Hardware differences CG 6000/C, CG 6100C, or CG 6500C board DSP C MIPS each. Each chip has two cores. 10/100Base-T Ethernet Ethernet SPEED LED: 10Base-T Ethernet (off) 100Base-T Ethernet (on) No echo cancellation hardware Status LEDs for each trunk: CG 6000 red and yellow CG 6000C red, yellow, and green CG 6100C green CG 6500C - green CAS signaling processed in the DSP Agere T81xx As many as 8 DSP cores per HMIC stream Each HMIC stream is 8 MHz with 128 timeslots Supports a 32-bit 33 MHz PCI bus Board status LEDs - none CG 6565 board DSP C MIPs each. Each chip has four cores. 10/100/1000Base-T Ethernet Ethernet SPEED LED: 10Base-T Ethernet (off) 100Base-T Ethernet (on) 1000Base-T Ethernet (blinking) NMS proprietary echo cancellation chip Red and yellow status LEDs for each trunk. For more information, refer to Trunk LEDs on page 75. CAS signaling processed in the framer NMS proprietary TSI 4 DSP cores per TSI stream Each TSI stream is 8 MHz with 128 timeslots Supports 32-bit or 64-bit, 66 MHz or MHz PCI X bus, or 33 MHz or 66 MHz PCI bus. For more information, refer to Configuring the DIP switches on page 29. Board status LEDs were added. For more information, refer to Board LEDs on page 78. NMS Communications 11

12 Overview of the CG 6565 board CG 6565 Installation and Developer's Manual Software differences The software differences between the CG 6000/C, CG 6100C, CG 6500C boards and the CG 6565 board include changes to the following: System configuration file Board keyword file Booting sequence Board information System configuration file The CG 6565 board product names that appear in the system configuration file depend on the number of trunks: Product name CG_6565 CG_6565_4 CG_6565_8 Trunks No trunks 4 trunks 8 trunks The following system configuration file excerpt describes a CG 6565 board configured using no call control: [CG 6565] Product = CG_6565 Number = 0 Bus = 2 Slot = 9 File = c6565nocc.cfg For more information, refer to Creating a system configuration file for oamsys on page 48. Board keyword file The CG 6565 board keyword file differs from the board keyword files of the CG 6000/C, CG 6100C, or CG 6500C boards in the following ways: The CG 6565 board uses framers instead of DSPs for signaling. You must configure the trunks to perform signaling. Once you configure the trunks, use only channel associated signaling (CAS) to convey signaling information: NetworkInterface.T1E1[x].SignalingType = CAS The CG 6565 board does not require DSPs to do signaling. Do not set the following DSP values: DSP.C5x[0].Files = qtsignal DSP.C5x[0..1].Files = 8tsignal The CG 6565 board merges the core file and the run module to create a file named cg6565core.ulm. The CG 6565 board does not require the following DLMFiles[x] settings: DLMFiles[x] = cg6krun DLMFiles[x] = cg6500run 12 NMS Communications

13 CG 6565 Installation and Developer's Manual Overview of the CG 6565 board In the CG 6565 configuration file, only set the DLMFiles[x] keyword when using the board with the following software: Software Generic ISDN Fusion ISDN management DPNSS NaturalFax Setting DLMFiles[x] = c6565igen DLMFiles[x] = cg6565fusion DLMFiles[x] = c6565imgt.dlm DLMFiles[x] = c6565.dlm DLMFiles[x] = cg6565fax.dlm When you use only one DLM file, x is always 0 (zero). If using more than one DLM file, number them sequentially starting with 0 (zero). They can appear in any order. For example: DLMFiles[0] = cg6565fusion DLMFiles[1] = c6565igen The following keywords are available to set hardware echo cancellation values: HardwareEcho.EchoChipEnabled HardwareEcho.Trunk[x].OnOffTimeslots HardwareEcho.XLaw Note: Do not use hardware echo cancellation in conjunction with software echo cancellation (that is, echo cancellation implemented through programs running on CG board DSPs). For more information about hardware echo cancellation, refer to Configuring hardware echo cancellation on page 31. All DSP resources must be managed by the CG 6565C resource management scheme. Use the following keywords to set up appropriate resource management: Resource[x].Definitions and Resource[x].DSPs instead of DSP.C5x[x].Files to specify DSPs and DSP functions. Resource[x].TCPs instead of TCPFiles[x] to specify TCPs. The NMS Conferencing service implements resource management differently than other Natural Access services. For more information, refer to the NaturalConference Service Developer's Reference Manual. NMS Communications 13

14 Overview of the CG 6565 board CG 6565 Installation and Developer's Manual Booting sequence The CG 6565 board booting sequence differs from the booting sequence of the CG 6000/C, CG 6100C, and CG 6500C boards in the following ways: CG 6565 boards do not require that you run the burnall script to update the flash memory on any CG 6565 boards in the chassis. CG 6565 boards download the run file, cg6565core.ulm, directly into SDRAM when the boards boot up using NMS OAM. This file is installed in the \nms\cg\load directory. On CG 6565 boards, the NMS OAM utility, oammon, logs boot-specific information to cg6x6xboot_bus_slot.txt. For information about using the oammon utility and generating log files, refer to the NMS OAM System User's Manual. The following example shows oammon output: Fri Feb 11 11:51:01 - OAMEVN_ALERT ERROR Board 1 "Name1" 1:9 - log cg6x6x boot info to file C:\WINNT\system32\CG_6565boot_1_9.txt Fri Feb 11 11:51:01 - OAMEVN_ALERT ERROR Board 1 "Name1" Writing at SDRAM 0xfa2c580 for bytes... Fri Feb 11 11:51:01 - OAMEVN_ALERT ERROR Board 1 "Name1" cg6565core.ulm loaded, version , built Feb Board information The NMS ID for the CG 6565 board is 0x6565. For example, pciscan displays the following information: NMS PCI Boards Scanner Bus Slot NMS ID x6565 CG_ x6565 CG_6565 There were 2 NMS PCI board(s) detected The NMS OAM product number is 0x635 and is included in the \nms\include\nmshw.h file: #define OAM_PRODUCT_NO_CG6565 0x635 CG 6565 boards use the CG 6500C switching model with MVIP-95 DSP streams of 64 to 67 as shown in the following boardinf example: Natural Access Board Information Demo V.13 (Jan ) MVIP-95 Board Addr Type MIPS Free memory Ports DSP Slots streams , 7 CG , 9 CG Total port count = 248 The subsystem ID for a CG board is 0x6565 as shown in the following cg6ktool example (use the -A option when you run cg6ktool): CG family command line tool, V3.00 (Dec ) (c) NMS Communications Board SubSysID Bus:Slot Shelf-Slot Temp DSP Cores Trunks CG : C 48 0 CG : C NMS Communications

15 CG 6565 Installation and Developer's Manual Overview of the CG 6565 board CG 6565 boards use C5441 DSPs and not C5420 DSPs for applications. The DSP files have.f41 extensions instead of.f54 extensions. For example, CG 6000/C, CG 6100C, and CG 6500C boards use dtmf.f54, but CG 6565 boards use dtmf.f41. The.f41 files are in the \nms\cg\load directory (or /nms/cg/load for UNIX), which is the same directory that contains.f54 files. Use f41info to display file resource usage instead of the f54info utility. The Fusion msppsamp and tpktsamp demonstration programs include the E option to disable software echo cancellation running on the DSPs. Set this option when using hardware echo cancellation on the CG 6565 board. For information on using msppsamp, refer to the Fusion Developer s Manual. The CG 6565 daughterboard includes an echo chip for providing hardware echo cancellation capabilities and to free up DSP resources. For more information, refer to Configuring hardware echo cancellation on page 31. To control hardware echo cancellation on a per-timeslot basis, refer to Using echo cancellation control on page 101. Trunk impedance on the CG 6565 board applies to two trunks and must be identical for trunk pairs. For information about the pairings, refer to NetworkInterface.T1E1[x].Impedance on page 181. CG 6565 boards include a temperature monitoring system. If the board temperature becomes too high, oammon generates either a warning or a critical error message. For more information, refer to Temperature monitoring system on page 25. CG 6565 boards do not support the following Switching service functions: swiconfigstreamspeed swigetstreamsbyspeed All 32 H.100 streams are automatically configured for maximum capacity (8 Mbit/s or 128 timeslots). NMS Communications 15

16 Overview of the CG 6565 board CG 6565 Installation and Developer's Manual CG 6565 board features The CG 6565 board is an NMS Communications PCI board. It is a high-density platform for IVR, fax, VoIP, and media server applications. The board uses a high performance PowerPC processor. Configurations with a main board and attached daughterboard provide up to eight T1 or E1 digital trunk interfaces and two Ethernet 10/100/1000Base-T interfaces. Refer to the NMS Communications web site ( for a list of available CG 6565 board configurations, for a list of countries where NMS has obtained approval for the CG 6565 board, and for product updates. CG 6565 boards include the following features: DSP resources The CG 6565 board has up to 6384 MIPS of media processing DSPs. PCI bus connectivity Each CG 6565 board is designed to reside in a single PCI bus slot. Each board contains a universal (5 V or 3.3 V signaling) PCI bus interface compliant with the PCI Local Bus Specification, Revision 2.2. The PCI interface is a 33 or 66 MHz 32/64-bit device. The PCI-X interface is a 66 or MHz 32/64-bit device and complies with the PCI-X Addendum to the PCI Local Bus Specification, Revision 1.0. Trunk connectivity Board configurations provide up to eight T1 or E1 network interfaces for digital trunk connectivity. You must configure the board for either T1 or E1. For more information, refer to Configuring the T1 or E1 interface on page 30 and to NetworkInterface.T1E1[x].Type on page 192. H.100 bus connectivity The CG 6565 board fully supports the H.100 bus specification. The H.100 bus enables multiple boards to share data. For example, you can connect two or more CG 6565 boards for applications that perform trunk-to-trunk switching. You can use H.100 compatible products from other manufacturers with the CG 6565 board. The H.100 interface supports the following stream configurations on the H.100 bus: Full mode: 32 streams at 8 MHz each, which provides 128 timeslots each for a total of 4096 timeslots. Backward compatibility mode: 16 8-MHz streams, 16 2-MHz streams (total of 2560 timeslots). The H.100 interface can operate with MVIP-90 boards on the same bus. In this configuration, an H.100 board in the system must be the bus master. 16 NMS Communications

17 CG 6565 Installation and Developer's Manual Overview of the CG 6565 board Telephony bus switching Switching for the CG 6565 board offers support for the H.100 bus within the H.100 architecture. On the CG 6565 board, switch connections are allowed for a total of 512 full duplex connections between local devices and the H.100 bus. Ethernet connectivity The CG 6565 board contains two 10/100/1000Base-T Ethernet connections for fast Ethernet connectivity and support of both IPv4 and IPv6. For more information, refer to Connecting to an Ethernet network on page 45. Echo cancellation CG 6565 boards support up to 480 ports of line echo cancellation with 64 ms tails. NMS Communications 17

18 Overview of the CG 6565 board CG 6565 Installation and Developer's Manual The following illustration shows where various components are located on a CG 6565 board: Ethernet connectors Ethernet interfaces Daughterboard connector PCI to PCI bridge SDRAM PowerPC processor with fan Digital signal processors (DSPs) H.100 bus connector 18 NMS Communications

19 CG 6565 Installation and Developer's Manual Overview of the CG 6565 board The following illustration shows the location of components on a 4-port CG 6565 daughterboard: Trunk status LEDs Trunk RJ-45 connectors Transformers Main board connector T1/E1 framer Echo chip NMS Communications 19

20 Overview of the CG 6565 board CG 6565 Installation and Developer's Manual Software components Natural Access is a development environment that provides such services as call control, system configuration, and voice store and forward. CG 6565 boards require the following software components that are available with Natural Access: NMS OAM (Operations, Administration, and Maintenance) software and related utilities. Configuration files that describe how the board is set up and initialized. Runtime software and drivers that control the CG 6565 board. One or more trunk control programs (TCPs) that enable applications to communicate with the telephone network using the signaling schemes (protocols) on the trunk. NMS OAM NMS OAM manages and maintains the telephony resources in a system. These resources include hardware components (including CG boards) and low-level board management software modules (such as clock management). Using NMS OAM, you can: Create, delete, and query the configuration of a component. Start (boot), stop (shut down), and test a component. Receive notifications from components. NMS OAM maintains a database containing records of configuration information for each component as shown in the following illustration. This information consists of parameters and values. NMS OAM Configuration database Board plug-in Board A Board B OAM Supv. Clock mgmt. Board plug-in Software components A B Boards 20 NMS Communications

21 CG 6565 Installation and Developer's Manual Overview of the CG 6565 board Each NMS OAM database parameter and value is expressed as a keyword name and value pair (for example, Clocking.HBus.ClockMode = MASTER_A). You can query the NMS OAM database for keyword values in any component. Keywords and values can be added, modified, or deleted. Before using NMS OAM or any related utility, verify that the Natural Access server (ctdaemon) is running. For more information about ctdaemon, refer to the Natural Access Developer's Reference Manual. For general information about NMS OAM and its utilities, refer to the NMS OAM System User's Manual. CG board plug-in NMS OAM uses the CG board plug-in module to communicate with CG boards. The name of the CG plug-in is cg6kpi.bpi. This file must reside in the \nms\bin directory (or /opt/nms/lib for UNIX) for NMS OAM to load it when it starts up. Configuration files NMS OAM uses two types of configuration files: File type System configuration Board keyword Description Contains a list of boards in the system and the names of one or more board keyword files for each board. Contains parameters to configure the board. These settings are expressed as keyword name and value pairs. NMS Communications 21

22 Overview of the CG 6565 board CG 6565 Installation and Developer's Manual Several sample board keyword files are installed with Natural Access. You can reference these files in your system configuration file or modify them. Board keyword file filea.cfg NetworkInterface.T1E1[0..15].Type = T1 Resource[0].Name = RSC1 Resource[0].Size = Board keyword file fileb.cfg NetworkInterface.T1E1[0..15].Type = T1 Resource[0].Name = RSC1 Resource[0].Size = System configuration file oamsys.cfg [Board A] Product = CG_6565 Number = 1 Bus = 0 Slot = 20 File = filea.cfg [Board B] Product = CG_6565 Number = 2 Bus = 0 Slot = 21 File = fileb.cfg [Supervisor] AutoStartEnabled = Yes AutoStopEnabled = Yes oamsys NMS OAM configuration database When you run oamsys, it creates NMS OAM database records based on the contents of the specified system configuration file and board keyword files. It then directs the OAM service to start the boards, configured as specified. Refer to Configuring and starting the system with oamsys on page 47 for more information. Runtime software The runtime software is stored in a run file on the host computer. CG 6565 boards download the run file, cg6565core.ulm, directly into SDRAM when the boards boot up using NMS OAM. This file is installed in the \nms\cg\load directory. DSP files enable the CG 6565 on-board DSPs to perform certain tasks, such as DTMF signaling, voice recording, and playback. Several run files and DSP files are installed with Natural Access. Specify the files to use for your configuration in the board keyword file. Refer to Using board keyword files on page 50 for more information. 22 NMS Communications

23 CG 6565 Installation and Developer's Manual Overview of the CG 6565 board Trunk control programs (TCPs) CG 6565 boards are compatible with a variety of PSTN signaling schemes, called protocols. A trunk control program (TCP) performs all of the signaling tasks to interface with the protocol used on a channel. TCPs run on the board, relieving the host computer of the task of processing the protocol directly. Several different protocol standards are in use throughout the world. For this reason, different TCPs are supplied with Natural Access. Each TCP supports various countryspecific variations. For applications that support multiple protocols simultaneously, you can load more than one TCP at a time. Specify the TCPs in the configuration file. NMS OAM downloads the specified TCPs to the board. For more information about TCPs, refer to the NMS CAS for Natural Call Control Developer's Manual. Natural Access Natural Access is a complete software development environment for voice applications. It provides a standard set of functions grouped into logical services. Each service has a standard programming interface. For more information about standard and optional Natural Access services, refer to the Natural Access Developer's Reference Manual. The following illustration shows the Natural Access software environment as it relates to NMS OAM software and CG 6565 hardware: Host Application (Other services) ADI service Natural Access NCC service OAM service NMS OAM configuration database Natural Call Control ADI commands commands and and board events board events API commands and board events CG 6565 board driver NMS OAM configuration commands, information, and board events NMS Communications 23

24 Overview of the CG 6565 board CG 6565 Installation and Developer's Manual NMS Fusion and the CG 6565 board Gateway applications provide a way of transferring data between telephone network and packet network interfaces. NMS Fusion provides software for developing IP telephony gateway applications that run on CG boards. For more information about Fusion software and Fusion CG 6565 board configurations, refer to the Fusion Developer's Manual. Fusion 4.0 (or later) configurations use CG 6565 boards to receive and transmit data to PSTN and to IP networks. Fusion applications use NCC (Natural Call Control) service functions to place and receive PSTN calls, and MSPP (media stream protocol processing) service functions to create and configure media channels between PSTN and IP networks. For more information about MSPP service functions, refer to the MSPP Service Developer's Reference Manual. Ethernet interfaces CG 6565 board Ethernet interfaces support IPv4 as well as IPv6 implementations of the Internet protocol. For information about implementing IPv4 and IPv6 Ethernet interface support on CG 6565 boards, refer to the following topics: For information about... Configuring IPv4 Ethernet interfaces Configuring IPv6 Ethernet interfaces Running the board in dual IPv4/IPv6 stack mode Gathering statistics from IPv4 and IPv6 Ethernet interfaces (ping also supported) Adding, printing, and deleting IPv6 addresses without editing individual board keyword files Refer to... Configuring IPv4 Ethernet connections on page 63 Configuring IPv6 Ethernet connections on page 65 Running in IPv4/IPv6 dual stack mode on page 68 cg6kcon - Displaying statistics about CG board activity on page 277 cgv6if - Adding, printing, and deleting IPv6 addresses on page NMS Communications

25 CG 6565 Installation and Developer's Manual Overview of the CG 6565 board Temperature monitoring system CG 6565 boards include a temperature monitoring system. If the board temperature becomes too high, oammon generates either a warning or a critical error message. Warning error message A warning error message displays when the board temperature reaches 70 C. The following example shows a warning error message: Mon Jun 20 09:54:52 - OAMEVN_ALERT INFO Board 0 "Name0" Temperature (70.0C) has reached the warning level (70.0C) for sensor PowerPC (0x92) If you receive a warning error message, no action is required. Critical error message A critical error message displays when the board temperature reaches 75 C. The following example shows a critical error message: Thu Jun 16 14:44:52 - OAMEVN_ALERT ERROR Board 0 "Name0" Board Error 0x40f2: Temperature (75.0C) has reached the critical level (75.0C) for sensor PowerPC (0x92) If you receive this error message, locate the cause of the problem and ensure that airflow to the board is sufficient. If no action is taken, the board's temperature may continue to climb. When the board temperature reaches 85 C, the board automatically shuts down to prevent damage. NMS Communications 25

26

27 3 Installing the hardware System requirements To install and use CG 6565 boards, your system must have: A chassis with an available PCI bus slot with 5.0 V and 3.3 V of supplied power. Natural Access installed. NMS recommends that you use an uninterruptible power supply (UPS) for increased system reliability. The UPS does not need to power the PC video monitor except in areas prone to severe lightning storms. CG driver software NMS recommends that you install the CG 6565 hardware before you install the CG 6565 driver software. The following drivers for operating CG boards are installed with Natural Access software: Operating system Windows UNIX Red Hat Linux Driver name cg6kwin2k.sys cg6k cg6ksw cg6k.o cg6ksw.o Installation summary The following table summarizes the procedure for installing the hardware and software components: Step Description 1 Ensure that your PC system meets the system requirements. 2 Power down the system if it is running. 3 If necessary, configure the CG 6565 board for H.100 bus termination. 4 Install the CG 6565 board in a PCI bus slot. 5 Power up the system. 6 Install Natural Access, which also installs the CG board driver and runtime software. The hardware interface drivers are installed with Natural Access software. 7 Create or edit an NMS OAM system configuration file and board keyword file describing your setup. For more information, refer to Configuring and starting the system with oamsys on page 47 and the NMS OAM System User's Manual. NMS Communications 27

28 Installing the hardware CG 6565 Installation and Developer's Manual Step Description 8 Configure the CG 6565 board either without trunk interfaces or with T1 or E1 interfaces. 9 Configure an Ethernet connection. For more information, refer to the Configuring Ethernet interfaces section. 10 Run oamsys to configure the boards as specified in the configuration files. 11 Connect the board interfaces to T1 or E1 trunks (if enabled) and Ethernet connections. 12 Verify that your installation is operational. Configuring the hardware This topic describes the following procedures for configuring the CG 6565 board: Configuring H.100 bus termination Configuring the DIP switches Configuring the board without trunk connectors Configuring the T1 or E1 interface Configuring hardware echo cancellation The procedures you follow depend on the CG 6565 board configuration you are installing. Configurations with a main board and attached daughterboard provide up to eight T1 or E1 digital trunk interfaces and two Ethernet interfaces. Configurations without a daughterboard provide no trunk interfaces. Caution: The CG 6565 board is shipped in a protective anti-static container. Leave the board in its container until you are ready to install it. Handle the board carefully and hold it only by its handles. NMS recommends that you wear an anti-static wrist strap connected to a good earth ground whenever you handle the board. 28 NMS Communications

29 CG 6565 Installation and Developer's Manual Installing the hardware Configuring H.100 bus termination H.100 boards are connected to one another with an H.100 bus cable. The two boards located at either end of the H.100 bus must have bus termination enabled, as shown in the following illustration. Bus termination is controlled by a DIP switch as explained in Configuring the DIP switches. H.100 bus cable Enable bus termination Enable bus termination Configuring the DIP switches The CG 6565 DIP switches are located on the board, as shown in the following illustration: S3 DIP switch S2 DIP switch S1 DIP switch S3 DIP switch The S3 DIP switch controls the H.100 bus termination. By default, all S3 switches are set to OFF (H.100 bus termination disabled). Setting all S3 switches to ON enables H.100 bus termination. Set all S3 switches to ON only for the boards that are on the ends of the H.100 bus. Note: The switches in the S3 DIP switch must be set to either all ON or all OFF. NMS Communications 29

30 Installing the hardware CG 6565 Installation and Developer's Manual S2 DIP switch Switch 5 in the S2 DIP switch allows you to control if the board LEDs can be off or on. (This is known as the dark office feature.) By default, switch 5 is set to OFF (all LEDs can be on). Setting switch 5 to ON turns off all LEDs on the board unless there is an error. S1 DIP switch The S1 DIP switch sets the mode of the board. By default, the switches set the board to the PCI mode. Mode PCI PCI-X Settings Switch 1 is set to ON. Switch 2 is set to OFF. Switch 3 is set to ON for 33 MHz or to OFF for 66 MHz. Switch 4 is set to ON. Switch 1 is set to OFF. Switch 2 is set to ON for 66 MHz or to OFF for MHz. Switch 3 is set to OFF. Switch 4 is set to ON. Configuring the board without trunk interfaces If you are installing a CG 6565 board either without a daughterboard or without configuring the trunk interfaces, be sure that the NetworkInterface.T1E1[x].Type keyword is set to NONE, which is the default. Configuring the T1 or E1 interface If the CG 6565 board you are installing has an attached daughterboard, it is shipped to you configured as a T1/E1 120 ohm board. To configure the T1 or E1 interface, make sure the following keywords appear in the board keyword file and perform the following steps: Step Action 1 Set the NetworkInterface.T1E1[x].Type keyword in the board keyword file to T1 or E1. You must configure all trunks that are being used as either T1 or E1. Do not specify more than one trunk type per board. 2 Set the NetworkInterface.T1E1[x].Impedance keyword to one of the following values: DSX1 for T1 G703_75_OHM for E1 75 ohm G703_120_OHM for E1 120 ohm 3 Set the NetworkInterface.T1E1[x].FrameType, NetworkInterface.T1E1[x].LineCode, and NetworkInterface.T1E1[x].SignalingType keywords to values appropriate for your configuration. 4 Ensure that you use the correct I/O cables. Refer to Connecting to an E1 network on page 41 or Connecting to a T1 network on page NMS Communications

31 CG 6565 Installation and Developer's Manual Installing the hardware Sample T1 trunk configuration The following example shows a sample T1 configuration for eight trunks: NetworkInterface.T1E1[0..7].Type = T1 NetworkInterface.T1E1[0..7].Impedance = DSX1 NetworkInterface.T1E1[0..7].LineCode = B8ZS [other values possible] NetworkInterface.T1E1[0..7].FrameType = ESF [other values possible] NetworkInterface.T1E1[0..7].SignalingType = CAS [other values possible] DSP.C5x[0..47].XLaw = MU_LAW DSPStream.VoiceIdleCode[0..7] = 0x7F DSPStream.SignalIdleCode[0..7] = 0x00 Sample E1 trunk configuration The following example shows a sample E1 configuration for eight trunks: NetworkInterface.T1E1[0..7].Type = E1 NetworkInterface.T1E1[0..7].Impedance = G703_120_OHM NetworkInterface.T1E1[0..7].LineCode = HDB3 [other values possible] NetworkInterface.T1E1[0..7].FrameType = CEPT NetworkInterface.T1E1[0..7].SignalingType = CAS [other values possible] DSP.C5x[0..47].XLaw = A_LAW DSPStream.VoiceIdleCode[0..7] = 0xD5 DSPStream.SignalIdleCode[0..7] = 0x09 Note: The syntax [0..7] specifies that the configuration supports any valid number of trunks within the range of 0 through 7 trunks. Configuring hardware echo cancellation NMS recommends using the CG 6565 daugtherboard with the echo chip to provide hardware echo cancellation capabilities and free up DSP resources. When using the hardware echo cancellation capabilities, echo cancellation parameters are fixed. An application cannot change the parameters in the ADI_ECHOCANCEL_PARMS structure with the adimodifyechocanceller function. Use the HardwareEcho.EchoChipEnabled, HardwareEcho.Trunk[x].OnOffTimeslots, and HardwareEcho.XLaw keywords to set hardware echo cancellation. If the application requires flexibility and you must modify echo cancellation parameters, use DSP resources to provide software echo cancellation capabilities. For more information, refer to the ADI Service Developer's Reference Manual. Note: Do not use both hardware echo cancellation and software echo cancellation at the same time on a CG 6565 board. NMS Communications 31

32 Installing the hardware CG 6565 Installation and Developer's Manual Installing the board Warning: The CG 6565 board powers up and functions only in a PCI chassis that supplies the PCI bus slot with 5.0 V and 3.3 V of power. Complete the following steps to initially install the CG 6565 board: Step Action 1 If necessary, configure the board as described in Configuring the hardware on page Power down the chassis and disconnect it from the power source. 3 Remove the cover and set it aside. 4 Arrange the CG 6565 board and other H.100 boards in adjacent PCI bus slots. Make sure each board's PCI bus connector is seated securely in a slot. 5 Secure the end bracket on the board to the chassis. 6 If applicable, connect the H.100 bus cable to the board. If you have multiple H.100 boards, connect the H.100 bus cable to each of the H.100 boards. 7 Replace the cover and connect the computer to its power source. Connecting to the network After installing the CG 6565 board, perform the following tasks: Task Description 1 Install the CG 6565 software available with Natural Access. 2 Connect the CG 6565 board interfaces to PSTN trunks and Ethernet connections. For more information, refer to the Establishing network connections section, which includes the following topics: Connectors and cables on page 33 Connecting to a T1 network on page 40 Connecting to an E1 network on page 41 Testing in loopback mode on page 43 Connecting to an Ethernet network on page NMS Communications

33 4 Establishing network connections Connectors and cables A CG 6565 board has either four-trunks or eight-trunks. Warning: Important safety notes for telephony connections Allow only qualified technical personnel to install this board and its associated telephone wiring. Make sure the PC chassis is grounded through the power cord or by other means before connecting the telephone line. If your system requires an external power supply, make sure it is grounded through the power cord or by other means. Never install telephone wiring during a lightning storm. Never install telephone jacks in wet locations. Telephone companies provide primary lightning protection for their telephone lines. However, if a site connects to private lines that leave the building, make sure that external protection is provided. Ethernet connectors To connect the CG 6565 board to a 10Base-T, 100Base-T, or 1000Base-T network, use two shielded twisted pair (STP) Category 5 or better Ethernet cables. The two 10/100/1000Base-T Ethernet connectors provide the CG 6565 board with Ethernet connections supporting auto-negotiation for 10, 100, and 1000 Base-T full duplex and half duplex transmissions. The RJ-45 Ethernet connectors have pinouts as shown in the following illustration: Pin 1 Pin 8 Pin 1: MDI0P Pin 2: MDI0M Pin 4: MDI2P Pin 5: MDI2M Pin 3: MDI1P Pin 6: MDI1M Pin 7: MDI3P Pin 8: MDI3M M = minus P = plus For more information, refer to Connecting to an Ethernet network on page 45. NMS Communications 33

34 Establishing network connections CG 6565 Installation and Developer's Manual Four-trunk board The board with four trunks has: Four trunk status LEDs Two NMS RJ-45 interfaces Two RJ-45 Ethernet connectors The following illustration shows a CG 6565 board with four trunks: Trunk status LEDs for trunks 0-3 Trunk 0 (and Trunk 2, if applicable) Trunk 1 (and Trunk 3, if applicable) Two NMS RJ-45 interfaces When used as is, there is one trunk per interface. When used with a splitter cable, there are two trunks per interface. Ethernet 1 Ethernet 2 Board status LEDs NMS RJ-45 interface pin assignments Each of the NMS RJ-45 interfaces has the following pinouts: Pin 8: (Port 2) R - Receive from network Pin 7: (Port 2) T - Receive from network Pin 6: (Port 2) R1 - Transmit to network Pin 5: (Port 1) T1 - Transmit to network Pin 4: (Port 1) R1 - Transmit to network Pin 3: (Port 2) T1 - Transmit to network Pin 2: (Port 1) T - Receive from network Pin 1: (Port 1) R - Receive from network Pin 8 Pin 1 To access Trunk 0, Trunk 1, or both Trunk 0 and Trunk 1, connect a shielded RJ-48 cable to one or both of the NMS RJ-45 interfaces on the end bracket. 34 NMS Communications

35 CG 6565 Installation and Developer's Manual Establishing network connections T1 and E1 120 ohm splitter cables To access all four trunks configured as T1 trunks or as 120 ohm E1 trunks, use two dual T1/E1 120 ohm adapter cables (NMS P/N 32851). These cables can be ordered with the board at no extra charge. Each splitter cable separates each of the NMS RJ-45 interfaces on the end bracket out to two RJ-48C interfaces as shown in the following illustration: RJ-48C interfaces Each of the RJ-48C interfaces on the T1/E1 120 ohm adapter cable has the following pinouts: Pin 8: Optional shield, not used Pin 7: Optional shield, not used Pin 6: No connection Pin 5: T1 - Transmit to network Pin 4: R1 - Transmit to network Pin 3: No connection Pin 2: T - Receive from network Pin 1: R - Receive from network Pin 8 Pin 1 E1 75 ohm splitter cables To access all four trunks configured as 75 ohm E1 trunks, use two of the NMS RJ-45 to two 75 ohm BNC adapters cables. The following illustration shows this cable: NMS RJ ohm BNC female (transmit) Trunk 0 (2) 75 ohm BNC female (receive) Trunk 0 (2) 75 ohm BNC female (receive) Trunk 1 (3) 75 ohm BNC female (transmit) Trunk 1 (3) Some countries require different splitter cables. NMS provides three types of splitter cables. The cables differ in the shielding of the 75 ohm BNC connectors. NMS Communications 35

36 Establishing network connections CG 6565 Installation and Developer's Manual The following table describes each of the 75 ohm BNC adapter cables: Cable NMS P/N NMS P/N NMS P/N Description Shield is not connected to transmit and receive connectors. Shield is connected to transmit connector outer conductor. Shield is connected to transmit and receive outer conductors. The following illustrations show each of these splitter cables: Splitter cable NMS P/N J2 BNC 75 ohm BNC female (receive) Trunk 0 (2) Ring Tip J3 BNC NMS RJ-45 (shielded) Ring Tip 75 ohm BNC female (transmit) Trunk 0 (2) J RxR0 RxT0 TxT1 TxR0 TxT0 TxR1 RxT1 RxR1 Ring Tip J4 BNC 75 ohm BNC female (receive) Trunk 1 (3) J5 BNC Shield Ring Tip 75 ohm BNC female (transmit) Trunk 1 (3) Shield not connected to J2, J3, J4, or J5 36 NMS Communications