Conventions used

This information product uses the text conventions explained below. In addition, hexadecimal numbers are preceded by a zero and small "x." For example, the decimal number 15 is represented in hexadecimal as 0x0F.

Convention	Description
®	In documentation related to a graphical user interface (GUI), the right arrow indicates you must click for another menu choice. Example: Go to the Configuration menu and select Card->Span Configuration.
. . .	In documentation related to GUI, a horizontal ellipsis in the description of a title bar of a dialog box denotes that the remaining part of the title bar is created dynamically. A horizontal ellipsis in an API message indicates fields of variable length.
. . .	A horizontal ellipsis in an API message indicates fields of variable length.
:	A vertical ellipsis in an API message indicates that a block of information is repeated or is variable.
n	The letter n is a generic placeholder for a number.
Sans serif mono space	Indicates a command name, option, input, output, non-GUI error, and system messages.
Sans serif monospace italic	Indicates a parameter name in an input message. Example: move *.dot a: c: -s The -s is the parameter.
Serif italic	Indicates the name of a book, chapter, path, file, or API message. Example: UserDirectory/Config.exe
Boldface	Indicates keyboard keys, key combinations, and command buttons Example: Ctrl+Alt+Del
Sans serif boldface	Identifies text that is part of a graphical user interface (GUI). Example: Go to the Configuration menu and select Card®Span Configuration

Industry Standards

This documentation contains many references to ITU-T standards. Originally, the CCITT made international standards for modulation, data transfer, and data compression protocols. The CCITT later became the ITU-T, or International Telecommunications Union Telecommunication Standardization Sector. CCITT standards are synonymous with ITU-T standards. For more details on these standards, go to www.itu.org.

This documentation also refers to American National Standards Institute (ANSI) standards. ANSI administers and coordinates the U.S. voluntary standardization and conformity assessment system for the telecommunications industry. More details on these standards may be viewed at www.ansi.org.

Related Training

Cantata Technology offers a variety of training courses for the Excel CSP. Instructors present a comprehensive description of hardware and software components and their interaction. Laboratory sessions provide hands-on experience for developing efficient, robust telecommunication.

For information, call 1-508-862-3000 and ask for a Training representative.

Contacting Technical Support for Hardware Failures

To expedite the process of returning defective hardware, please provide the serial number of the card and a shipping address.

Technical Support investigate to determine whether a card may be defective, or if it is instead exhibiting a software issue that can be confused as a hardware problem. An example of an indication of a hardware defect would be an LED that fails to display any status. Examples of problems that do not indicate hardware defects include the following:

• Software faults (probably a software defect issue)

• A card that arrives "dead" (probably a dip switch set incorrectly)

• A card not coming into service during software downloading
(probably a TFTP issue)

• Spans not framing (probably a wiring issue)

• Power card LEDs blink when no other cards are in the chassis. This is normal.

Recommendations for System Supportability

The following are key elements we have identified across our customer base that have made them successful in their development and deployment of solutions incorporating Cantata Technology products. We are passing these onto you as suggestions to consider when designing and building solutions. Not all of these suggestions are appropriate for all customers, but we hope you consider them carefully.

If Your Solution Requires High Availability:

• Order redundant configurations

• Purchase onsite spares

• Follow the limitations for power, cards, and configurations as noted in the Cantata Product Documentation

• Have your developers and technicians trained on the Cantata CSP platform

• Enable logging in your application so that problems can be diagnosed and corrected

• Develop test scripts, environments, and systems that best simulate the environment of intended use for each release and each fix you deliver to your customers

• Implement Software Configuration Management to track every revision and change that you release to your customers

• Review your call flows and APIs with Cantata Technical Support to identify opportunities to optimize your solution with regard to our product capabilities

• Purchase a support agreement from Cantata Technology

If you are running a network with Cantata Products in them, in addition to the above suggestions, also:

• Have backup systems for power

• Review your network design with Cantata Technical Support to identify opportunities to optimize your solution with respect to our product capabilities

• Design your network to allow for alternative routes and logical assignments to more quickly address any service affecting issues.

• Control your system environment and configuration changes

• Plan your network management and monitoring strategy

• Ensure that your technicians are trained in all network elements and interfaces

• Monitor your network every day, around the clock.

• Have the ability to get someone to every site without delay

• Have a complete list of contact information for the support arm of each network element you deploy

• Provide for supplier remote access if required to diagnose and resolve an issue

All of us at Cantata Technology want you, our valued customer, to be successful. For additional information regarding our support services and how we can work more closely together for our mutual success, contact us at our support website at http://www.cantata.com/support or contact a sales representative at sales@cantata.com.