Cisco Systems 4 manual Deleting an Existing Integration, Alternate Extensions

Page 41

Appendix: Using Alternate Extensions and MWIs

Deleting an Existing Integration

Step 8 If prompted, restart the Cisco Unity services.

Deleting an Existing Integration

If you want to delete an existing integration (for example, you have replaced the phone system with which Cisco Unity originally integrated), do the following procedure.

To Delete an Existing Integration

Step 1 On the Cisco Unity server, on the Windows Start menu, click Programs > Cisco Unity > Manage Integrations. The UTIM window appears.

Step 2 In the left pane, double-click Unity Server. The existing integrations appear.

Step 3 Click the integration that you want to delete.

Step 4 On the Integration menu, click Delete.

Step 5 Follow the on-screen instructions to assign the subscribers of the deleted phone system integration to another phone system integration.

Step 6 At the prompt to restart the Cisco Unity services, click Yes. The Cisco Unity services restart.

Alternatively, you can restart the Cisco Unity services in UTIM on the Tools menu by clicking Restart

Cisco Unity.

Step 7 If the integration you deleted used voice cards, remove the voice cards from the Cisco Unity server.

Appendix: Using Alternate Extensions and MWIs

Alternate Extensions

In addition to the “primary” extension that you specify for subscribers, you can assign subscribers up to nine alternate extensions. (The primary extension is the one that you assign to each subscriber when you create his or her subscriber account; it is listed on the Subscribers > Subscribers > Profile page.)

Reasons to Use Alternate Extensions

There are several reasons that you may want to specify alternate extensions for subscribers. For example, if you have more than one Cisco Unity server that accesses a single, corporate-wide directory, you may want to use alternate extensions to simplify addressing messages to subscribers at the different locations. With alternate extensions, the number that a subscriber uses when addressing a message to someone at another location can be the same number that the subscriber dials when calling. You may also want to use alternate extensions to:

•Handle multiple line appearances on subscriber phones.

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0

 

OL-3105-15

41

 

 

 

Page 40 Page 42
Image 41
Page 40 Page 42
Contents
Task List to Create the Integration Integration TasksTask List to Make Changes to an Integration RequirementsTask List to Delete an Existing Integration Phone SystemCisco Unity Server Configuration for 24 or Fewer PortsIntegration Description PBXLink Box Connections Configuration for 25 to 48 PortsConfiguration for 49 to 72 Ports Integrations with Multiple Phone Systems Integration FunctionalityField Considerations Number of Voice Messaging Ports to InstallNumber of Voice Messaging Ports That Will Answer Calls Preparing for Programming the Phone SystemTo Program the Phone System Option SettingProgramming the Avaya Definity/PBXLink Phone System Call-appr Normal Button Assignment SettingCall-appr Feature Button Number SettingAbrdg-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 BoxTo 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 SettingSettings for the Enter MWI Codes Selection Control Effect Click Save To Set Up the Test Configuration Testing the IntegrationTo Enable MWI Extensions That Begin with Zero Select New Exchange Subscriber To Test Listening to Messages To Test an External Call with Release TransferTo Delete the Test Subscriber To Set Up Supervised Transfer on Cisco UnityTo Test Supervised Transfer Integration Description Integrating a Secondary Server for Cisco Unity FailoverRequirements To Set Up the Secondary Server for Failover Setting Up the Secondary Server for FailoverClick Programs Cisco Unity Edit Switch Utility To Change the Settings for an Integration Changing the Settings for an Existing IntegrationAlternate Extensions Deleting an Existing IntegrationTo Delete an Existing Integration Reasons to Use Alternate ExtensionsHow Alternate Extensions Work Setting Up Alternate ExtensionsTo Modify or Delete Alternate Extensions To Add Administrator-Defined Alternate ExtensionsAlternate MWIs To Modify or Delete Alternate MWIs Setting Up Alternate MWIsTo Set Up Alternate MWIs for Extensions Convention Description ConventionsCisco.com Obtaining DocumentationProduct Documentation DVD Ordering DocumentationCisco Product Security Overview Reporting Security Problems in Cisco ProductsDocumentation Feedback Cisco Technical Support & Documentation Website Obtaining Technical AssistanceDefinitions of Service Request Severity Submitting a Service RequestObtaining Additional Publications and Information Page OL-3105-15
Top Page Image Contents