Configuration for 25 to 48 Ports | Cisco Systems guide

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0

Integration Description

Configuration for 25 to 48 Ports

Avaya Definity/PBXLink integrations with 25 to 48 ports can use one of the following configurations (others are possible):

•(Recommended) A single PBXLink-48 box with Ports A and B set for calls only.

•Two PBXLink-24 boxes with Port A of both set for calls only.

Configuration for 49 to 72 Ports

Avaya Definity/PBXLink integrations with 49 to 72 ports can use one of the following configurations (others are possible):

•(Recommended) One PBXLink-24 box with Port A set for calls only, and one PBXLink-48 box with Ports A and B set for calls only.

•Two PBXLink-48 boxes with Ports A and Port B of both set for calls only.

•Three PBXLink-24 boxes with Port A of all three set for calls only.

PBXLink Box Connections

A single PBXLink box is connected to the phone system with one or two digital phone lines and connected to the Cisco Unity server with an RS-232 serial cable. The voice messaging lines from the phone system connect to the analog voice cards in the Cisco Unity server. Figure 1 shows the required connections.

Figure 1

Serial Connections Between a Single PBXLink Box and Cisco Unity

PBXLink box

Phone system

Cisco Unity server

Digital lines RS-232 serial cable Analog lines

55419

Multiple PBXLink boxes are connected to the Cisco Unity server by using an RS-232 cable to connect the SMDI port from the last PBXLink box to the Management port of the first PBXLink box. Another RS-232 cable is then used to connect the SMDI port of the first PBXLink box to the Cisco Unity server. The voice messaging lines from the phone system connect to the analog voice cards in the Cisco Unity server. Figure 2 shows the required connections.

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0

4	OL-3105-15

Image 4

Cisco Systems manual Configuration for 25 to 48 Ports, Configuration for 49 to 72 Ports, PBXLink Box Connections

Contents

Integration Tasks Task List to Create the Integration Requirements Task List to Make Changes to an IntegrationTask List to Delete an Existing Integration Phone System Integration Description Configuration for 24 or Fewer PortsCisco Unity Server Configuration for 49 to 72 Ports Configuration for 25 to 48 PortsPBXLink Box Connections Integration Functionality Integrations with Multiple Phone Systems Number of Voice Messaging Ports to Install Field Considerations Preparing for Programming the Phone System Number of Voice Messaging Ports That Will Answer Calls Programming the Avaya Definity/PBXLink Phone System Option SettingTo Program the Phone System Button Assignment Setting Call-appr Normal Feature Button Number Setting Call-appr 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 Setting Up the PBXLink Box To Update the PBXLink Box Firmware 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 Field Setting To Create an Integration Settings for the Enter MWI Codes Selection Control Effect Click Save To Enable MWI Extensions That Begin with Zero Testing the IntegrationTo Set Up the Test Configuration Select New Exchange Subscriber To Test an External Call with Release Transfer To Test Listening to Messages To Test Supervised Transfer To Set Up Supervised Transfer on Cisco UnityTo Delete the Test Subscriber Requirements Integrating a Secondary Server for Cisco Unity FailoverIntegration Description Setting Up the Secondary Server for Failover To Set Up the Secondary Server for Failover Click Programs Cisco Unity Edit Switch Utility Changing the Settings for an Existing Integration To Change the Settings for an Integration Deleting an Existing Integration Alternate ExtensionsTo Delete an Existing Integration Reasons to Use Alternate Extensions Setting Up Alternate Extensions How Alternate Extensions Work Alternate MWIs To Add Administrator-Defined Alternate ExtensionsTo Modify or Delete Alternate Extensions To Set Up Alternate MWIs for Extensions Setting Up Alternate MWIsTo Modify or Delete Alternate MWIs Conventions Convention Description Obtaining Documentation Cisco.comProduct Documentation DVD Ordering Documentation Documentation Feedback Reporting Security Problems in Cisco ProductsCisco Product Security Overview Obtaining Technical Assistance Cisco Technical Support & Documentation Website Submitting a Service Request Definitions of Service Request Severity Obtaining Additional Publications and Information Page OL-3105-15