Conventions, Convention Description | Cisco Systems 4 manual

Appendix: Documentation and Technical Assistance

Conventions

Appendix: Documentation and Technical

Assistance

Conventions

The Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0 uses the following conventions.

Table 38	Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0 Conventions

Convention		Description

boldfaced text		Boldfaced text is used for:
		• Key and button names. (Example: Click OK.)
		• Information that you enter. (Example: Enter Administrator in the User
		Name box.)

< >		Angle brackets are used around parameters for which you supply a value.
(angle brackets)		(Example: In the Command Prompt window, enter ping <IP address>.)
(angle brackets)

-		Hyphens separate keys that must be pressed simultaneously. (Example: Press
(hyphen)		Ctrl-Alt-Delete.)
(hyphen)

>		A right angle bracket is used to separate selections that you make:
(right angle		• On menus. (Example: On the Windows Start menu, click Settings > Control
bracket)		Panel > Phone and Modem Options.)
		• In the navigation bar of the Cisco Unity Administrator. (Example: Go to the
		System > Configuration > Settings page.)

[x]		Square brackets enclose an optional element (keyword or argument). (Example:
(square brackets)		[reg-e164])
(square brackets)

[x y]		Square brackets enclosing keywords or arguments separated by a vertical line
(vertical line)		indicate an optional choice. (Example: [transport tcp transport udp])
(vertical line)

{x y}		Braces enclosing keywords or arguments separated by a vertical line indicate a
(braces)		required choice. (Example: {tcp udp})
(braces)

The Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0 also uses the following conventions:

Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the document.

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0

	OL-3105-15	45

Image 45

Cisco Systems 4 manual Conventions, Convention Description

Contents

Task List to Create the Integration Integration Tasks Task List to Make Changes to an Integration RequirementsTask List to Delete an Existing Integration Phone System Configuration for 24 or Fewer Ports Integration DescriptionCisco Unity Server Configuration for 25 to 48 Ports Configuration for 49 to 72 PortsPBXLink Box Connections Integrations with Multiple Phone Systems Integration Functionality Field Considerations Number of Voice Messaging Ports to Install Number of Voice Messaging Ports That Will Answer Calls Preparing for Programming the Phone System Option Setting Programming the Avaya Definity/PBXLink Phone SystemTo Program the Phone System Call-appr Normal Button Assignment Setting Call-appr Feature Button Number Setting Abrdg-appr Extn 4th voice mail extension Abrdg-appr Extn 6th voice mail extension Vector Definition Options for a Single Digital Port Option Setting Route to number 2010 if unconditionally To Set Up User Phones To Update the PBXLink Box Firmware Setting Up the PBXLink Box To Set Up the PBXLink Box Page LTN Number Voice Messaging Port Value Following substeps LTN Number Voice Messaging Port Value 0007 0009 LTN Number Voice Messaging Port Value LTN Number Voice Messaging Port Value LTN Number Voice Messaging Port Value 0002 To Create an Integration Field Setting Settings for the Enter MWI Codes Selection Control Effect Click Save Testing the Integration To Enable MWI Extensions That Begin with ZeroTo Set Up the Test Configuration Select New Exchange Subscriber To Test Listening to Messages To Test an External Call with Release Transfer To Set Up Supervised Transfer on Cisco Unity To Test Supervised TransferTo Delete the Test Subscriber Integrating a Secondary Server for Cisco Unity Failover RequirementsIntegration Description To Set Up the Secondary Server for Failover Setting Up the Secondary Server for Failover Click Programs Cisco Unity Edit Switch Utility To Change the Settings for an Integration Changing the Settings for an Existing Integration Alternate Extensions Deleting an Existing IntegrationTo Delete an Existing Integration Reasons to Use Alternate Extensions How Alternate Extensions Work Setting Up Alternate Extensions To Add Administrator-Defined Alternate Extensions Alternate MWIsTo Modify or Delete Alternate Extensions Setting Up Alternate MWIs To Set Up Alternate MWIs for ExtensionsTo Modify or Delete Alternate MWIs Convention Description Conventions Cisco.com Obtaining DocumentationProduct Documentation DVD Ordering Documentation Reporting Security Problems in Cisco Products Documentation FeedbackCisco Product Security Overview Cisco Technical Support & Documentation Website Obtaining Technical Assistance Definitions of Service Request Severity Submitting a Service Request Obtaining Additional Publications and Information Page OL-3105-15