avaya aura communication manager change description release 6.0.1

Avaya Aura® Communication ManagerChange Description for Release 6.0.1

Release 6.0.103-603723

Issue 1November 2010

© 2011 Avaya Inc.

All Rights Reserved.

Notice

While reasonable efforts have been made to ensure that theinformation in this document is complete and accurate at the time ofprinting, Avaya assumes no liability for any errors. Avaya reserves theright to make changes and corrections to the information in thisdocument without the obligation to notify any person or organization ofsuch changes.

Documentation disclaimer

“Documentation” means information published by Avaya in varyingmediums which may include product information, operating instructionsand performance specifications that Avaya generally makes availableto users of its products. Documentation does not include marketingmaterials. Avaya shall not be responsible for any modifications,additions, or deletions to the original published version ofdocumentation unless such modifications, additions, or deletions wereperformed by Avaya. End User agrees to indemnify and hold harmlessAvaya, Avaya's agents, servants and employees against all claims,lawsuits, demands and judgments arising out of, or in connection with,subsequent modifications, additions or deletions to this documentation,to the extent made by End User.

Link disclaimer

Avaya is not responsible for the contents or reliability of any linked Websites referenced within this site or documentation provided by Avaya.Avaya is not responsible for the accuracy of any information, statementor content provided on these sites and does not necessarily endorsethe products, services, or information described or offered within them.Avaya does not guarantee that these links will work all the time and hasno control over the availability of the linked pages.

Warranty

Avaya provides a limited warranty on its Hardware and Software(“Product(s)”). Refer to your sales agreement to establish the terms ofthe limited warranty. In addition, Avaya’s standard warranty language,as well as information regarding support for this Product while underwarranty is available to Avaya customers and other parties through theAvaya Support Web site: http://support.avaya.com. Please note that ifyou acquired the Product(s) from an authorized Avaya reseller outsideof the United States and Canada, the warranty is provided to you bysaid Avaya reseller and not by Avaya.

Licenses

THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYAWEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ AREAPPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/ORINSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC.,ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER(AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITHAVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESSOTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOESNOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINEDFROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR ANAVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHTTO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSEUSING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BYINSTALLING, DOWNLOADING OR USING THE SOFTWARE, ORAUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OFYOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING,DOWNLOADING OR USING THE SOFTWARE (HEREINAFTERREFERRED TO INTERCHANGEABLY AS “YOU” AND “END USER”),AGREE TO THESE TERMS AND CONDITIONS AND CREATE ABINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THEAPPLICABLE AVAYA AFFILIATE ( “AVAYA”).

Avaya grants End User a license within the scope of the license typesdescribed below. The applicable number of licenses and units ofcapacity for which the license is granted will be one (1), unless a

different number of licenses or units of capacity is specified in theDocumentation or other materials available to End User. “DesignatedProcessor” means a single stand-alone computing device. “Server”means a Designated Processor that hosts a software application to beaccessed by multiple users. “Software” means the computer programsin object code, originally licensed by Avaya and ultimately utilized byEnd User, whether as stand-alone Products or pre-installed onHardware. “Hardware” means the standard hardware originally sold byAvaya and ultimately utilized by End User.

License types

• Designated System(s) License (DS). End User may install anduse each copy of the Software on only one DesignatedProcessor, unless a different number of Designated Processorsis indicated in the Documentation or other materials available toEnd User. Avaya may require the Designated Processor(s) tobe identified by type, serial number, feature key, location or otherspecific designation, or to be provided by End User to Avayathrough electronic means established by Avaya specifically forthis purpose.

• Concurrent User License (CU). End User may install and usethe Software on multiple Designated Processors or one or moreServers, so long as only the licensed number of Units areaccessing and using the Software at any given time. A “Unit”means the unit on which Avaya, at its sole discretion, bases thepricing of its licenses and can be, without limitation, an agent,port or user, an e-mail or voice mail account in the name of aperson or corporate function (e.g., webmaster or helpdesk), ora directory entry in the administrative database utilized by theSoftware that permits one user to interface with the Software.Units may be linked to a specific, identified Server.

• Named User License (NU). End User may: (i) install and use theSoftware on a single Designated Processor or Server perauthorized Named User (defined below); or (ii) install and usethe Software on a Server so long as only authorized NamedUsers access and use the Software. “Named User”, means auser or device that has been expressly authorized by Avaya toaccess and use the Software. At Avaya's sole discretion, a“Named User” may be, without limitation, designated by name,corporate function (e.g., webmaster or helpdesk), an e-mail orvoice mail account in the name of a person or corporate function,or a directory entry in the administrative database utilized by theSoftware that permits one user to interface with the Software.

• Shrinkwrap License (SR). Customer may install and use theSoftware in accordance with the terms and conditions of theapplicable license agreements, such as “shrinkwrap” or“clickthrough” license accompanying or applicable to theSoftware (“Shrinkwrap License”). (see “Third-partyComponents” for more information).

Copyright

Except where expressly stated otherwise, no use should be made ofmaterials on this site, the Documentation, Software, or Hardwareprovided by Avaya. All content on this site, the documentation and theProduct provided by Avaya including the selection, arrangement anddesign of the content is owned either by Avaya or its licensors and isprotected by copyright and other intellectual property laws including thesui generis rights relating to the protection of databases. You may notmodify, copy, reproduce, republish, upload, post, transmit or distributein any way any content, in whole or in part, including any code andsoftware unless expressly authorized by Avaya. Unauthorizedreproduction, transmission, dissemination, storage, and or use withoutthe express written consent of Avaya can be a criminal, as well as acivil offense under the applicable law.

Third-party components

Certain software programs or portions thereof included in the Productmay contain software distributed under third party agreements (“ThirdParty Components”), which may contain terms that expand or limitrights to use certain portions of the Product (“Third Party Terms”).Information regarding distributed Linux OS source code (for those

2 Avaya Aura® Communication Manager Change Description for Release 6.0.1 November 2010

http://support.avaya.com

http://www.avaya.com/support/LicenseInfo

Products that have distributed the Linux OS source code), andidentifying the copyright holders of the Third Party Components and theThird Party Terms that apply to them is available on the Avaya SupportWeb site: http://support.avaya.com/Copyright.

Preventing Toll Fraud

“Toll fraud” is the unauthorized use of your telecommunications systemby an unauthorized party (for example, a person who is not a corporateemployee, agent, subcontractor, or is not working on your company'sbehalf). Be aware that there can be a risk of Toll Fraud associated withyour system and that, if Toll Fraud occurs, it can result in substantialadditional charges for your telecommunications services.

Avaya Toll Fraud Intervention

If you suspect that you are being victimized by Toll Fraud and you needtechnical assistance or support, call Technical Service Center TollFraud Intervention Hotline at +1-800-643-2353 for the United Statesand Canada. For additional support telephone numbers, see the AvayaSupport Web site: http://support.avaya.com. Suspected securityvulnerabilities with Avaya products should be reported to Avaya bysending mail to: [email protected].

Trademarks

Avaya® and Avaya Aura® are trademarks of Avaya Inc.

The trademarks, logos and service marks (“Marks”) displayed in thissite, the documentation(s) and product(s) provided by Avaya are theregistered or unregistered Marks of Avaya, its affiliates, or other thirdparties. Users are not permitted to use such Marks without prior writtenconsent from Avaya or such third party which may own the Mark.Nothing contained in this site, the documentation(s) and product(s)should be construed as granting, by implication, estoppel, or otherwise,any license or right in and to the Marks without the express writtenpermission of Avaya or the applicable third party.

All non-Avaya trademarks are the property of their respective owners.

Linux® is the registered trademark of Linus Torvalds in the U.S. andother countries.

Downloading Documentation

For the most current versions of Documentation, see the AvayaSupport Web site: http://support.avaya.com.

Contact Avaya Support

Avaya provides a telephone number for you to use to report problemsor to ask questions about your Product. The support telephone numberis 1-800-242-2121 in the United States. For additional supporttelephone numbers, see the Avaya Web site: http://support.avaya.com.

Avaya Aura® Communication Manager Change Description for Release 6.0.1 November 2010 3

http://support.avaya.com/Copyright




Contents

Chapter 1: Introduction.............................................................................................................9

Chapter 2: Communication Manager changes.....................................................................11Clock Synchronization over IP.........................................................................................................................11

Detailed description of Clock Synchronization over IP...........................................................................11Clock Synchronization over IP administration........................................................................................12Interactions for Clock Synchronization over IP.......................................................................................15IP Network Region..................................................................................................................................15Feature-related system parameters.......................................................................................................16

Deluxe paging support for branch gateways...................................................................................................16Deluxe paging for analog trunks.............................................................................................................16Setting up Passive Signaling Station for deluxe paging.........................................................................17Assigning an Analog Trunk Port.............................................................................................................17End-user procedure for Call Park...........................................................................................................17Station....................................................................................................................................................18Loudspeaker Paging...............................................................................................................................18

Multiple signaling groups in one SIP trunk group............................................................................................19Detailed description of multiple signaling groups in one SIP trunk group...............................................19Multiple signaling groups in one SIP trunk group administration............................................................19

Number Display - Short Number Display on Inter Location Calls...................................................................21Display between Locations with these Display Parameters...................................................................21

Trunk Side XOIP Modem Support...................................................................................................................22XOIP Treatment......................................................................................................................................22

Maintenance objects.......................................................................................................................................23IP-SYNC.................................................................................................................................................23MG-SYNC...............................................................................................................................................23

Maintenance SAT Commands.........................................................................................................................24add media-gateway................................................................................................................................24change synchronization..........................................................................................................................25display synchronization..........................................................................................................................25list synchronization.................................................................................................................................25disable synchronization..........................................................................................................................26enable synchronization...........................................................................................................................26status ip-synchronization........................................................................................................................27

Installations.....................................................................................................................................................28Install Communication Manager on the Dell and HP servers.................................................................28Install System Platform Service Pack 2 on the Dell and HP servers......................................................29

Upgrades.........................................................................................................................................................29Upgrade paths........................................................................................................................................29

Special applications........................................................................................................................................29

Chapter 3: Avaya Branch Gateways changes.......................................................................31IPv6.................................................................................................................................................................31

Chapter 4: Communication Manager Session Manager interoperability...........................33Session Manager............................................................................................................................................33Desk-level SIP E911 location reporting...........................................................................................................33

Overview.................................................................................................................................................33Configuring Communication Manager for ELIN Server support.............................................................34


Call Admission Control....................................................................................................................................34Provisioning Session Manager and Communication Manager CAC together........................................35

Chapter 5: Communication Manager Messaging changes..................................................37Direct SIP integration between Communication Manager Messaging and Communication Manager............37

Overview.................................................................................................................................................37Adding node names for SIP integration..................................................................................................37Adding a signaling group for direct SIP integration................................................................................38Adding a trunk group for direct SIP integration.......................................................................................39Creating a hunt group for messaging.....................................................................................................40Changing private numbering..................................................................................................................41Changing a route pattern........................................................................................................................41Changing IP network region...................................................................................................................42Changing the IP Codec Set....................................................................................................................43Adding a coverage path for messaging..................................................................................................43Changing AAR analysis..........................................................................................................................44Adding a station......................................................................................................................................44Saving translations.................................................................................................................................45Administering the Switch Link.................................................................................................................45Restarting the messaging application.....................................................................................................46

Direct SIP integration between Communication Manager Messaging Federal and Communication Manager........................................................................................................................................................................47

Setting feature access codes for messaging..........................................................................................47Adding node names for SIP integration..................................................................................................48Creating a signaling group......................................................................................................................48Creating a trunk group............................................................................................................................50Creating a hunt group for messaging.....................................................................................................52Changing private numbering..................................................................................................................53Changing a route pattern........................................................................................................................54Changing IP network region...................................................................................................................55Changing the IP Codec Set....................................................................................................................55Adding a coverage path for messaging..................................................................................................56Changing AAR analysis..........................................................................................................................56Adding a station......................................................................................................................................57Saving translations.................................................................................................................................57Administering the Switch Link.................................................................................................................57Restarting the messaging application.....................................................................................................59

IPv6 implementation for Communication Manager Messaging.......................................................................59Overview.................................................................................................................................................59Adding node names IP...........................................................................................................................59Defining IP interfaces for Processor Ethernet........................................................................................60Creating a signaling group......................................................................................................................61Creating a trunk group............................................................................................................................63Administering gateway...........................................................................................................................65Creating a hunt group for messaging.....................................................................................................66Changing private numbering..................................................................................................................67Changing a route pattern........................................................................................................................68Changing the IP Network Region...........................................................................................................69Changing the IP Codec Set....................................................................................................................69Adding a coverage path for messaging..................................................................................................70Changing AAR analysis..........................................................................................................................70Adding a station......................................................................................................................................71


Saving translations.................................................................................................................................71Administering the Switch Link.................................................................................................................71Restarting the messaging application.....................................................................................................73

Subscribers.....................................................................................................................................................73Subscriber Management........................................................................................................................73Adding a subscriber................................................................................................................................73Editing a subscriber................................................................................................................................74Viewing a subscriber..............................................................................................................................74Deleting a subscriber..............................................................................................................................75Subscriber List........................................................................................................................................75Filtering subscribers...............................................................................................................................76Subscribers (CMM) field descriptions.....................................................................................................76

Upgrades.........................................................................................................................................................79Upgrade paths........................................................................................................................................79

Chapter 6: Hardware...............................................................................................................81Avaya A175 Desktop Video Device.................................................................................................................81Avaya 1000 Series Video Conferencing endpoint...........................................................................................82

Avaya 1010 Video Conferencing endpoint.............................................................................................82Avaya 1020 Video Conferencing endpoint.............................................................................................82Avaya 1030 Video Conferencing endpoint.............................................................................................83Avaya 1040 Video Conferencing endpoint.............................................................................................83Avaya 1050 Video Conferencing endpoint.............................................................................................83

HP ProLiant DL360 G7 1U server overview....................................................................................................84Introduction.............................................................................................................................................84Front of server........................................................................................................................................84Back of server.........................................................................................................................................85Server specifications..............................................................................................................................86Environmental specifications..................................................................................................................87Physical specifications............................................................................................................................87References.............................................................................................................................................88

Dell™ PowerEdge™ R610 1U server overview..............................................................................................88Introduction.............................................................................................................................................88Front of server........................................................................................................................................88Back of server.........................................................................................................................................89Server specifications..............................................................................................................................90Environmental specifications..................................................................................................................91Physical specifications............................................................................................................................92References.............................................................................................................................................92

Chapter 7: Documentation and procedure updates.............................................................93Adding New Hardware for Avaya Servers and Gateways...............................................................................93

Downloading Reliable Data Transport Tool............................................................................................93Administrator guide.........................................................................................................................................94

PE Interface configuration......................................................................................................................94Administering Network Connectivity................................................................................................................95

Reviewing the network region administration.........................................................................................95Conversion of servers and gateways..............................................................................................................95

Suppress alarming..................................................................................................................................96Feature Description and Implementation........................................................................................................96

Call detail record field descriptions.........................................................................................................96Call forward override..............................................................................................................................96


Call Park.................................................................................................................................................97Considerations for Administrable Language Displays............................................................................97Enhanced Redirection Notification.........................................................................................................97Interactions for Station Security Code....................................................................................................98System requirements for EMU...............................................................................................................98

Installing and Upgrading the Avaya G450 Gateway.......................................................................................99Installing and Upgrading the Avaya S8300 Server.........................................................................................99Maintenance Alarms.......................................................................................................................................99

CONFIG (System Configuration)............................................................................................................99disable synchronization-switch.............................................................................................................100enable synchronization-switch..............................................................................................................100IP Signaling Group Far-End Status Test (#1675).................................................................................100Media Path Status Test (#1374)...........................................................................................................100SIP-SGRP (SIP Signaling Group)........................................................................................................101

Maintenance Commands..............................................................................................................................101AAR and ARS Digit Analysis Table .......................................................................................................102disable synchronization-switch.............................................................................................................102enable synchronization-switch..............................................................................................................102list ars route-chosen.............................................................................................................................102pingall...................................................................................................................................................102

Reports..........................................................................................................................................................103AAR or ARS Route Chosen reports.....................................................................................................103Attendant and Maintenance Status report............................................................................................103

Screen Reference.........................................................................................................................................104Agent LoginID.......................................................................................................................................104Attendant Console................................................................................................................................104Dial Plan Analysis Table.......................................................................................................................104Dial Plan Parameters............................................................................................................................105Feature-Related System Parameters...................................................................................................105Hunt Group...........................................................................................................................................106Incoming Call Handling Treatment.......................................................................................................107IP Network Region................................................................................................................................107ISDN Numbering Calling Party Number Conversion for Tandem Calls................................................107Location................................................................................................................................................109Numbering-Public/Unknown Format and Numbering-Private Format..................................................110Percent Full...........................................................................................................................................110Personal CO Line Group......................................................................................................................110QSIG to DCS TSC Gateway.................................................................................................................111Station...................................................................................................................................................111System parameters customer options..................................................................................................112System Parameters Port Networks.......................................................................................................112Terminating Extension Group...............................................................................................................112Trunk Group: Protocol Variations..........................................................................................................113Uniform Dial Plan Table........................................................................................................................113Usage Allocation Enhancements..........................................................................................................113Vector Directory Number......................................................................................................................114

Upgrades.......................................................................................................................................................114disable synchronization-switch.............................................................................................................114enable synchronization-switch..............................................................................................................114

Index.......................................................................................................................................115


Chapter 1: Introduction

The Avaya Aura® Communication Manager Change Description document describes the features andchanges that were introduced with release 6.0.1 of Avaya Aura® Communication Manager, andCommunication Manager and Avaya Aura® Session Manager interoperability.

The Communication Manager documents (maintenance alarms, commands, procedures, hardware guide,administrator guide, and so on) are not being updated for this release.


Introduction


Chapter 2: Communication Managerchanges

This chapter describes the features and enhancements of Release 6.0.1 of Avaya Aura® CommunicationManager.

The enhancements for Call Center 6.0.1 are provided in Avaya Aura® Call Center 6.0 Overview,07-602633.

Clock Synchronization over IPWhere traditional synchronization is not available, you can use the Clock Synchronization overIP (CSoIP) feature on G450 and G430 Branch Gateways to provide system clocking acrossIP networks.

Detailed description of Clock Synchronization over IPCommunication Manager creates Inter-Gateway Connections (IGCs) to convey the IP streams.The G450 and G430 Branch Gateways provide both source ports and sync ports for the IGCs.CSoIP supports TDM-based devices, such as an H.320 video device to retain and transmitwithin an IP infrastructure. You administer Clock Synchronization over IP through theCommunication Manager's SAT Administration forms.

Instead of DS1 or BRI interface, you can use a local clock as the clocking source. You canchoose a primary and any other backup sources.

The Communication Manager maintenance object and connection manager create andmaintain the synchronization domains, also known as sync domains. A sync domain is a clocksource that emanates IGC streams to clock receivers. All gateways involved with the CSoIPfeature are referred to as members. A master domain is a clock source derived from a DS1 orBRI, which is used to emanate IGC streams to clock receivers. Other members that use theincoming IGC stream for internal clocking are known as slave clocks. The receiver is one hoplevel below the clock source. A secondary clock domain uses the incoming IGC stream, whichis used to clock outgoing IGC streams to other members.

Depending on the limitation of the fan-out, a single clock source cannot source a stream to themaximum number of gateways. As a result, some clock receivers also become clocking source,known as the secondary clock source. These, in turn, constitute sync domains.


When the first IGC source comes into service, it becomes the default system clock source. Allother IGC sources become slaves until the fan-out limit is reached. After the fan-out limit isreached, a slave is promoted to a secondary clock source, known as a tandem clock.Subsequent receivers are then clocked from the secondary source until its fan-out is reached.Then another slave from that sync domain is promoted to a tandem clock. This process takesplace as each clock source reaches its fan-out limit.

When a master clock board comes into service, it is used to create a master clock domain ifthere is an IGC source board already providing IGC streams. The highest level clock sourcethat was the default system clock source is demoted and becomes a receiver of a master clocksource and becomes a tandem clock. There can be as many master clock domains as thereare administered sync sources.

The CSoIP feature does not attempt to mitigate the reference board outages. If such a boardgoes out of service, the traditional sync feature raises an alarm and you need to rectify theproblem. Removing or adding any reference board from translations causes the CSoIP featureto adjust to move members to another source or begin adding members to the new source.

There can be several DS1s, BRIs, or other boards capable of providing a reference from thePSTN, and each can be used by the CSoIP feature to provide sync to a group of members.

Clock Synchronization over IP administrationThe following tasks are part of the administration process for the CSoIP feature:

• Setting up IP synchronization

• Setting up IP synchronization for the gateway

• Setting up IP synchronization for the network region

• Assigning synchronization reference for the gateway

• Setting up the DS1 board as a synch Source reference

• Setting up the BRI trunk board as a Synch Source reference

• Disabling synchronization

For information on how to administer the above tasks, see Administering Avaya Aura™

Communication Manager, 03-300509.

Screens for administering Clock Synchronization over IP

Screen name Purpose FieldsFeature-RelatedSystemParameters

Set up the ClockSynchronization over IPfeature.

Synchronization over IP

Communication Manager changes


Screen name Purpose FieldsMedia Gateway Set up IP

synchronization on thegateway.

Use for IP Sync

IP Network Region Set up IPsynchronization on thenetwork region.

Sync

IP SynchronizationSource MediaGateway

Assign synchronizationreference to the primaryand secondarygateway.

PrimarySecondary

DS1 Set up the DS1 boardas a Synch Source.

For information on fields, see theConfiguring a DS1 circuit pack examplesection of Administering Avaya Aura™

Communication Manager, 03-300509.

ISDN-BRI TrunkCircuit Pack

Set up the BRI trunkboard as a SynchSource.

Synch Source

Clock Synchronization over IP administrationListing all administered gateways

Enter list synchronization media-gateway to display the list of administeredgateways.

Setting up IP synchronization

1. Enter change system-parameters feature.

2. Click Next until you see the IP Parameters section.

3. Set the Synchronization over IP field to y.

4. Select Enter to save your changes.

Clock Synchronization over IP


Setting up IP synchronization for the gateway

1. Enter change media-gateway n, where n is the number of the gateway in whichyou want to enable IP synchronization.

2. Set the Use for IP Sync field to y.


Assigning synchronization reference for the gateway

1. Enter change synchronization media-gateway n, where n is the numberof the gateway that requires synchronization.

2. In the Primary field, enter a synchronization-source slot address location. Obtainthis location from the Circuit Packs Available for Synchronization list. Ensure thatyou choose a working synchronization source.

3. (Optional) Add another synchronization-source circuit pack location in theSecondary field. Obtain the location from the Circuit Packs Available forSynchronization lost.


Setting up the DS1 board as a sync Source reference

1. Enter change ds1 n, where n is the DS1 board location that you want to set upas a Sync Source.

2. Enter the necessary parameters to match the far end of the DS1 span.For information on Configuring a DS1 circuit pack example, see AdministeringAvaya Aura™ Communication Manager, 03-300509.


Setting up the BRI trunk board as a Synch Source reference

1. Enter change bri-trunk-board n, where n is the BRI trunk board location thatyou want to set up as a sync source.

2. Set the Synch Source field to y.




Setting up IP synchronization for the network region

1. Enter change ip-network-region n, where n is the network region number inwhich you want to enable IP synchronization.

2. Click Next until you see the Inter Network Region Connection Managementfields.

3. Set the Sync to y.


Disabling synchronization

Enter disable synchronization media-gateway n, where n is the number ofthe gateway.The command prevents switching between clock sources.

Interactions for Clock Synchronization over IPThis section provides information about how the Clock Synchronization over IP (CSoIP) featureinteracts with other features on the system. Use this information to ensure that you receive themaximum benefits of CSoIP in any feature configuration.

Survivable remote and survivable core serversIf a survivable remote and survivable core servers control the gateways with the primary andsecondary synchronization source, the elements under the control of that survivable serverhave clock synchronization. If the primary and secondary synchronization source is notcontrolled by the survivable server in a failover fragment:

• The segment performs as if it had no primary or secondary source for clocksynchronization.

• Any gateways with a DS1 or BRI interface in service takes its clock source from that DS1or BRI interface.

IP Network RegionReference Avaya Aura™ Communication Manager Screen Reference, 03-602878, 6.0 version,a new field is added on the IP Network Region screen.

Clock Synchronization over IP


Sync

Appears when the Synchronization over IP field is enabled.

Valid Entry Usage

y Timing IGC streams are allowed between the region pair that is beingadministered. The default value is y.

n Do not allow timing IGC streams between the region pair that is beingadministered.

Feature-related system parametersReference Avaya Aura™ Communication Manager Screen Reference, 03-602878, 6.0 version,a new field is added on the Feature-related system parameters screen.

Synchronization over IP

Enables or disables the Clock Synchronization over IP (CSoIP) feature to provide IP sync toa group of members.

Valid entries Usage

y Enables the CSoIP feature.

n Disables the CSoIP feature. This is the default value.

Deluxe paging support for branch gatewaysUsing the deluxe paging support for branch gateways feature you can use the deluxe pagingwith analog media modules (MM711 and MM714) and port networks (TN747 and TN797).

Deluxe paging for analog trunksTo use the deluxe paging feature with analog trunks, the analog trunk port must be connectedto an analog line port. The analog line ports are administered as passive signaling stations.Analog trunks need a line-end termination to remain in-service and close the circuit. Stationsadministered as passive signaling stations act as line-end terminations for analog loop starttrunk ports.



Setting up Passive Signaling Station for deluxe paging

1. Enter add station n, where n is the extension of the station.

2. In the Type field, type the model of analog station, such as 2500.

3. Set the Passive Signalling Station field to y.

4. Press Enter to save your changes.

Assigning an Analog Trunk Port

1. Enter change paging loudspeaker.

2. In the Port field, enter the port number of the analog trunk media module or circuitpack.

3. Press Enter to save your changes.

End-user procedure for Call Park

Parking a call using the trunk access code

1. Press the transfer button.

2. Dial the trunk access code with the extension for parking a call.

3. Press the transfer button.

Deluxe paging support for branch gateways


StationReference Avaya Aura™ Communication Manager Screen Reference, 03-602878, Release6.0, a new field is added to the Station screen. The field description is as follows:

Passive Signalling Station

The entries y and n indicate the call processing status of the analog trunk port user. This fieldis available only when you select an analog trunk port as the station type.

Valid Entry Usage

y The analog station port does not process calls when off hook.

n The analog station port processes and receives calls as an analogstation. This is the default value.

Loudspeaker PagingReference Avaya Aura™ Communication Manager Screen Reference, 03-602878, Release6.0, a new field is added to the Loudspeaker Paging screen. The field description is as follows:

Port

The Auxiliary and Analog ports assigned to the station are as follows.

Valid Entry Usage

01 to 64 The first and second numbers are the cabinet numbers.

A to E The third character is the carrier.

01 to 20 The fourth and fifth characters are the slot numbers. G650 has 14slots.

01 to 32 The sixth and seventh characters are the port numbers.

x or X Indicates that there is no hardware associated with the port assignmentsince the switch was set up, and the administrator expects that theextension has a non-IP set. Or, the extension had a non-IP set, and itdissociated. Use x for Administered WithOut Hardware (AWOH) andComputer Telephony (CTI) stations, as well as for SBS Extensions.

IP Indicates that there is no hardware associated with the port assignmentsince the switch was set up, and the administrator expects that theextension would have an IP set. This is automatically entered for certain



Valid Entry Usage

IP station set types, but you can enter for a DCP set with softphonepermissions. This changes to the s00000 type when the set registers.

xxxVmpp Specifies the Branch Gateway.

• xxx is the Branch Gateway number, which is in the range 001 to 250.

• m is the module number, which is in the range 1 to 9.

• pp is the port number, which is in the range 01 to 32.

Analog Trunkport

Analog trunk port is available with:

• MM711 and MM714 media modules

• TN747 and TN797 circuit packs

Multiple signaling groups in one SIP trunk groupBy assigning members from multiple SIP signaling groups to one SIP trunk group, you candirectly connect a SIP-integrated Avaya Aura® Messaging system with multiple MessagingApplication Servers (MASs) to Communication Manager. Using this connection,Communication Manager can handle the load balancing between MAS devices.

Detailed description of multiple signaling groups in one SIP trunkgroup

To assign members from more than one signaling group to one SIP trunk group, you must firstset up the signaling groups. After setting up the signaling groups you must assign membersfrom more than one signaling group to one SIP trunk group. You can have one signaling groupper MAS.

For example, if you have three MASs within the Messaging system, you must configure threesignaling groups, one for each MAS. A single SIP trunk group can then be created withmembers from the three signaling groups.

Multiple signaling groups in one SIP trunk group administrationThe following tasks are part of the administration process for assigning members from morethan one signaling group to one SIP trunk group:

• Setting up the signaling groups

• Assigning members from more than one signaling group to one SIP trunk group

Multiple signaling groups in one SIP trunk group


Screens for administering multiple signaling groups in one SIP trunk group

Screen name Purpose FieldsSignaling Group Set up the signaling group. • Group Type

• IMS Enabled

• Peer DetectionEnabled

• Peer Server

Trunk Group Assign members from one or moresignaling groups to one SIP trunkgroup.

• Member AssignmentMethod

• Port

• Sig Grp

Setting up the signaling groups

1. Enter add signaling-group n, where n is the signaling group number.

2. Ensure that the Group Type field is set to SIP.

3. Set the IMS Enabled field to n.

4. Set the Peer Detection Enabled field to y.

5. Set the Peer Server field to Others.

6. Ensure that the Q-SIP and Far-end Domain fields have the same values for allsignaling groups assigned to the SIP trunk group.

7. Set the Enable Layer 3 Test field to y.This ensures that Communication Manager maintenance detects a signaling groupoutage and enables trunk group member selection to bypass out-of-servicesignaling groups.




Assigning members from more than one signaling group to one SIP trunkgroup

1. Enter add trunk-group n, where n is the trunk group number.

2. Ensure that the Group Type field is set to SIP.

3. Set the Member Assignment Method field to manual.The Signaling Group and Number of Members fields disappear.

4. On the Group Member Assignments page:

a. Enter IP in the Port field.

b. (Optional) Enter the SIP signaling group name in the Name field.

c. Enter the SIP signaling group number in the Sig Grp field.You must assign different signaling groups in cyclical order for subsequentmembers of the trunk group. For example, if you have three signaling groups,such as 1, 2, and 3, assign the groups in the order 1, 2, 3, 1, 2, 3, 1, 2, 3, andso on for the subsequent members of the trunk group. This ensures that loadbalancing occurs amongst the different signaling groups.


Number Display - Short Number Display on Inter LocationCalls

The Display between Locations with these Display Parameters field is added on theDisplay Parameters screen to use the Number display - intra-locations internal calls feature.

Display between Locations with these Display ParametersThis field appears when you enable the Multiple Locations field. This field cannot be leftblank.

Valid Entry Usage

inter-location Communication Manager uses the inter-location display format for callsbetween designated locations. This is the default value.

Number Display - Short Number Display on Inter Location Calls


Valid Entry Usage

intra-location Communication Manager uses the intra-location display format for callswithin a location. You can use the intra-location format within a branch todisplay short extensions within that location. This Display Parameter letsyou display short extensions between two or more closely associatedlocations. For example, if you assign display parameter 3 to locations 7and 17, and set the field to intra-location, Communication Manager usesintra-location format for calls between locations 7 and 17, however usesinter-location calls from 7 to any other location other than 17, and for callsfrom 17 to any other location other than 7.

Trunk Side XOIP Modem SupportThe XOIP Treatment field is added on the Trunk Group screen to use the Trunk Side XOIPModem Support feature.

XOIP Treatment

Valid Entry Usage

automodemfaxtty

Identifies treatment of an incoming trunk call. When set to modem, fax,or tty, the serving digital signal processor algorithms is placed inimmediate pass-through mode. Use this field when the incoming trunk istransporting the XOIP traffic. By identifying this external equipmentthrough administration, VoIP firmware uses this field to determine if it isnecessary to immediately attempt to put a call in pass-through mode sothat the DSPs will not miss identification of the initial tone events. Defaultis auto.

Note:

• This feature does not apply to IP trunks (SIP and H.323 trunks).• This field is intended for exception cases only. For the majority of

trunk groups, use the default setting of auto.



Maintenance objects

IP-SYNC

MO Name in Log Alarm Level Initial Command to Run Full Name of MO

IP-SYNC None None IP Synchronization

The IP-SYNC handles the creation and maintenance of the sync domains. This maintenanceobject runs as a single instance maintenance object when the various IP sync operations arebeing executed. The IP-SYNC object indicates that gateways are coming in and out ofservice.

Demand tests descriptions and error codesThere are no demand tests for IP-SYNC.

MG-SYNC

MO Name in Log Alarm Level Initial Command toRun

Full Name of MO

MG-SYNC None None Branch gateway capable of IPsynchronization

The MG-SYNC handles the clock-related messaging to the branch gateways and interfaceswith IP Synchronization (IP-SYNC).

A branch gateway that is part of a Communication Manager system can use one of threesynchronization references: DS1, BRI, and VOIP. These resources derive synchronizationreference from a received IGC stream. The MG-SYNC maintenance object implements controlof the gateway clock synchronization and synchronization references. The MG-SYNC objectconfigures MG clocks, monitor clock synchronization status, log errors and raise alarms, andreports changes to IP-SYNC distribution for the system.

Maintenance objects


Error log entries and recommended actions

ErrorType

AuxData

AssociatedTest

AlarmLevel

On/OffBoard

Recommended Action

18 — Disable sync WRN OFF enable synchronization-switch

513 (3) — — MIN OFF None.When the gateway is a master clockmember, see DS1 or BRItroubleshooting section ofMaintenance Procedures for AvayaAura™ Communication Manager,Media Gateways and Servers ,03-300432.

Note:Error Type 18: The Clock Synchronization over IP feature is disabled. The recommendedaction is to run the enable synchronization-switch command.

Demand tests descriptions and error codesThere are no demand tests for MG-SYNC.

Maintenance SAT Commands

add media-gatewayReference Maintenance Commands for Avaya Aura™ Communication Manager, MediaGateways and Servers, 03-300431, 6.0 version, a new field is added to the Media Gatewayscreen. The field description is as follows:

add media-gateway field descriptions

Field Description

Use for IP Sync Appears when the Synchronization over IP field is enabled.Indicates whether or not the G430 and G450 branch gatewaysare exempted from IP sync. By default, this field is enabled.



change synchronizationReference Maintenance Commands for Avaya Aura™ Communication Manager, MediaGateways and Servers, 03-300431, 6.0 version, a new qualifier is added to the changesynchronization command. The description of the qualifier is as follows:

Action/Object Qualifier QualifierDescription

Login Feature Interaction

changesynchronization

media-gateway n

change thegatewaynumber

init,inads,craft,cust,rcust,bcms

DS1 interface or BRI trunk isselected as either a primaryor secondary sync sourcecannot be removed from theDS1 circuit packadministration screen or theregular circuit packadministration screen.

display synchronizationReference Maintenance Commands for Avaya Aura™ Communication Manager, MediaGateways and Servers, 03-300431, 6.0 version, a new qualifier is added to the displaysynchronization command. The description of the qualifier is as follows:



displaysynchronization

media-gateway n

display thegatewaynumber


No default.A DS1 interface is selected asa primary or secondarysynchronization sourcecannot be removed from theDS1 circuit packadministration screen or theregular circuit packadministration screen.

list synchronizationReference Maintenance Commands for Avaya Aura™ Communication Manager, MediaGateways and Servers, 03-300431, 6.0 version, media-gateway and port-network qualifiersare added to the list synchronization command.



Use list synchronization media-gateway to see all administered gateway referenceboards and the existing reference sources.

Use list synchronization port-network to see all administered port networkreference boards and the existing reference sources.



listsynchronization

media-gatewayport-network

list the gatewayreference boardslist the portnetworkreference boards


No default.A DS1 interface is selectedas a primary or secondarysynchronization sourcecannot be removed from theDS1 circuit packadministration screen or theregular circuit packadministration screen.

disable synchronizationReference Maintenance Commands for Avaya Aura™ Communication Manager, MediaGateways and Servers, 03-300431, 6.0 version, a new qualifier is added to the disablesynchronization command. The description of the qualifier is as follows:

Action/Object Qualifier Qualifier Description Login Default

disablesynchronization

media-gatewayn

disable the gatewaynumber

init, inads,craft

enable synchronizationReference Maintenance Commands for Avaya Aura™ Communication Manager, MediaGateways and Servers, 03-300431, 6.0 version, a new qualifier is added to the enablesynchronization command. The description of the qualifier is as follows:

Action/Object Qualifier Qualifier Description Login Default

enablesynchronization

media-gatewayn

enable the gatewaynumber

init, inads,craft



status ip-synchronizationstatus ip-synchronization [master | member media-gateway n | oos-members | source media-gateway n | system-information]Use status ip-synchronization to see the information about the status of the variousgateways that are part of IP synchronization.

Action/Object

Qualifier Qualifier Description Login FeatureInteraction

status ip-synchronization

master,member media-gateway n,oos-members,source media-gateway n,system-information

status of the master sync sourcesin the system.status of the timing source for agiven gateway.status of the members who are notsynchronized and their servicestates.status of the gateways whosesync is sourced by the givengateway.status of the global status of thesync over IP feature.


status ip-synchronization field descriptions

Field Description

Member Displays all master sources of the system.

Ref Stat Displays the health of the reference board, whether the memberis in service and setup to source IGC streams.

DSP Status Displays the status of the DSP.

Input Provides information about the incoming IGC stream.

Inp R: Receiving stream, N: No stream detected, D: Streamdetected.

Jit Jitter detected.

Bad Bad packets detected.

Ord Out of order packets detected.

Dup Duplicated packets detected.

Loss% Percentage loss of incoming stream.



Field Description

Output Lock Provides information about the outgoing IGC stream.

• Yes: Locked to input.

• No: Not locked, no output.

• Pnd: Pending lock.

• S: (sync) Indicates if the sync lead is connected.

Sync Ref Displays whether the clock is synchronized to the synch lead ofthe PN and MG.

Role Displays the role of the member.

Fail Reason Displays why the member is out of synch with other members.

Master Domain Count Number of master IP sync domain count.

Total Domain Count Number of overall IP sync system count.

Member Count Number of gateways in sync domains.

Max Level Highest hop count by any member.

Out of Sync Number of members not in sync.

Building domains Indicates whether the new sync domains are created after thefeature flag is turned on. When the field is set to n, the processis finished.

Removing Domains Indicates if the feature is removing the IGC streams and syncdomains when the feature is turned off.

Installations

Install Communication Manager on the Dell and HP serversFor Release 6.0.1, Communication Manager can be installed on the HP ProLiant DL360 G7and Dell™ PowerEdge™ R610 servers. Within Installing and Configuring Avaya Aura™

Communication Manager, 03-603558, all references to the Avaya S8800 Server apply to thesetwo servers also.



Install System Platform Service Pack 2 on the Dell and HP serversFor Release 6.0.1, when installing System Platform, ensure that you download and install theService Pack 2 version. This Service Pack allows System Platform and the CommunicationManager templates to be installed on the HP ProLiant DL360 G7 and Dell™ PowerEdge™ R610servers.

Upgrades

Upgrade pathsThe Upgrade paths to Communication Manager Release 6.0.1 are:

• Upgrading Communication Manager Release 4.0.5 to Release 6.0.1

• Upgrading Communication Manager Release 6.0 to Release 6.0.1

For more information, see the Upgrading to Avaya Aura® Communication Manager Release6.0.1, 03-603560.

Special applicationsSpecial applications, also known as green features, meet special requirements requested byone or more customer. Customers may activate the special applications by themselves usingtheir own super-user login. Although these special features are available to customers, theymay have not gone through extensive testing. So customers must use these features at theirown risk.

Some of the special features should not be set without the right configurations, and somefeatures should not be set together at the same time. Otherwise, the feature may not operateas expected, the system performance could be affected or both. To avoid users from settingthose features accidentally, Communication Manager has identified those features and markedthem as restricted. To activate the restricted features, contact Avaya Custom Developmentteam.

For a list of unrestricted special features and related information, see Avaya Aura®

Communication Manager Special Application Features at http://support.avaya.com.

Upgrades



The special applications features available for Release 6.0.1 are as follows:

• National/International numbers in CDR

• CDR Enhancements for Timezone, Location, and Country Support

• SIP Trunks for 3rd Party Make Call

• CDR Answering Party via Call-Pickup

• Modify Authorization code dial sequence

• EC500 Call Pickup and Bridge-on

• Attendant Camp-on

• Interaction with Conferencing



Chapter 3: Avaya Branch Gatewayschanges

This chapter summarizes the changes in functionality in Branch Gateways for Communication Manager6.0.1

IPv6Internet Protocol version 6 (IPv6) is the successor to IPv4. IPv6 supports 128–bit addressesand satisfies the rapidly growing demand for IP addresses. In contrast, IPv4 supported 32–bit.IPv6 also improves security, ease of configuration, and routing performance. IPv6 can coexistwith IPv4 networks, easing the transition process.

The IETF (Internet Engineering Task Force) published RFC 2460, the internet standardspecification that defines IPv6, in December 1998.

AddressingBy using 128-bit addresses, IPv6 has about 3.4x1038 unique IP addresses, more than enoughfor every network device. This eliminates the IPv4 mechanisms, such as NAT (network addresstransitions), that are used to relieve IP address exhaustion. IPv6 addresses are normallywritten as hexadecimal digits with colon separators, for example: 2005:af0c:168d::752e:375:4020. The double colon “::” represents a string of zeroes, according to RFC4291.

SimplicityIPv6 simplifies the routing process by changing the packet header and packet forwarding:

• Simplified packet header, despite enhanced functionality.• IPv6 routers do not perform fragmentation. This is carried out by IPv6 hosts.• IPv6 routers do not need to recompute a checksum when header fields change.• Routers no longer need to calculate the time a packet spent in a queue.• IPv6 supports stateless address configuration, so IPv6 hosts can be configured

automatically when connected to a routed IPv6 network through ICMPv6. Statefulconfiguration using DHCPv6 and static configuration are also available.

Deployment and transitionThere are several mechanisms that ease the deployment of IPv6 running alongside IPv4. Thekey to the transition is dual-stack hosts. Dual-stack hosts refers to the presence of two IPsoftware implementations in one operating system, one for IPv4 and one for IPv6. These dual-


stack hosts can run the protocols independently or as a Hybrid. The Hybrid is the commonform on recent server operating systems and computers.

When an IPv6 host or network must use the existing IPv4 infrastructure to carry IPv6 packets,Tunneling provides the solution. Tunneling encapsulates IPv6 packets within IPv4. Tunnelingcan be either automatic or configured, the latter being more suitable for large, well-administered networks.

Key differences between IPv4 and IPv6

IPv4 IPv6

Address space 32-bit, about 4.3x109 128-bit, about 3.4x1038

Security IPSec support is optional. IPSec support is required.

Configuration Requires DHCP or manualconfiguration.

Stateless auto-configuration.Does not require DHCP ormanual configuration.

Address format Decimal digits with colonseparators, for example:192.168.1.1

Hexadecimal digits withcolon separators. Forexample: 2005:af0c:168d::752e:375:4020. The doublecolon “::” represents fourzeros “0000”

Broadcast and Multicastsupport

Yes No Broadcast. Various formsof Multicast — better networkbandwidth efficiency

QoS support ToS using DIFFServ Flow labels and flow classes,more granular approach.

Feature Support in Avaya Branch GatewaysCertain Branch Gateway features are not supported in IPv6. See “Branch Gateway Features”in the Overview for the Avaya Branch Gateway G430 or Overview for the Avaya BranchGateway G450

Avaya Branch Gateways changes


Chapter 4: Communication ManagerSession Managerinteroperability

Session ManagerWithin an Avaya Aura® solution, Session Manager is at the core with one or more installationsof Communication Manager. For the Avaya Aura® solution to work optimally requires closemanagement of Communication Manager and Session Manager.

For what’s new for Session Manager in Release 6.1, see Avaya Aura® Session ManagerOverview, 03-603323.

Desk-level SIP E911 location reporting

OverviewE911 service (such as ELIN Server) enables emergency location lookups for emergency callsand helps in identifying the physical location of the emergency caller (a registered user onSession Manager) in the event of an emergency call. The ELIN is a number which providesspecific details about the location of the caller. This enables emergency services to:

• call back the emergency caller in case of need for additional information after ending theemergency call

• re-establish the emergency call if it gets disconnected for some reason

For information on basic concepts, scenario definition, and administration details regardingEmergency Calling, see Avaya Aura® Session Manager Case Studies, 03-603478.


Configuring Communication Manager for ELIN Server supportCommunication Manager should be able to route “911” calls to the PSAP and the required SIPsig groups and trunks needs to be configured for this purpose.

1. For incoming emergency calls to the Communication Manager, if the messagesignaling has the presence of an ELIN:

a. ELIN needs to be mapped to an existing extension via incoming callhandling (inc-call-handling-trmt of the SIP trunk group) to get theextension number.

b. Each shortened ELIN should be a valid station extension in order toenable callback for the phone making the emergency call. Similar is thecase if an unregistered phone makes an emergency call.

c. ELIN must be converted back to 10 digits via public-numbering beforebeing sent out to the public network (PSAP).

2. For incoming emergency calls to the Communication Manager, if the messagesignaling does not have the presence of an ELIN:

a. Communication Manager uses the ip-network-region mapping todetermine an ELIN based on the user’s IP address. If it maps the callinguser to an ELIN, it uses digit conversion to assign it to some station. Afterit finds the station, it reapplies the digit conversion to set the ELIN backto 10 digits format before forwarding it to the PSAP.

b. In case when the Communication Manager finds no match for the IPaddress to an ELIN, it includes the actual calling station’s extensionnumber as the calling party for the PSAP.

Following are some of the essential steps to ensure proper coverage in case of emergencycalls:

1. For every ELIN a paired station extension must be administered.2. Define digit pattern conversion for incoming and outgoing ELIN to station extension

mapping.3. Communication Manager must have an IP address mapping to ELIN for cases of

emergency calling from unregistered phones.

Call Admission ControlThe bandwidth needed for SIP and H.323 audio and video endpoints can be managed withina single logical location. SIP endpoints are managed using Locations administered through

Communication Manager Session Manager interoperability


System Manager, and H.323 endpoints are managed using Network Regions administeredthrough Communication Manager. Because Session Manager and Communication Managerare used simultaneously, provisioning them correctly is critical.

Provisioning Session Manager and Communication Manager CACtogether

For simultaneous use of Session Manager and Communication Manager CAC, followingconfigurations should be done:

1. Create 1-to-1 mapping of Session Manager Locations to Communication ManagerNetwork Regions, because Communication Manager uses Network Regions forCAC. This is limited by the fact that Communication Manager supports no morethan 250 Network Regions, while Session Manager supports thousands ofLocations.

2. As Session Manager maps IP addresses to Locations, Communication Managermaps IP addresses to Network Regions. These mappings must be synchronizedmanually.

3. As part of Communication Manager administration, the SIP trunk to CommunicationManager must be placed within a dummy Network Region for which no CAC limitsare set.

This enables the following changes:

• Calls terminated to non-SIP destinations (H.323 phones, non-SIP trunks) are counted byCommunication Manager CAC for the appropriate Network Regions.

• All calls terminated to SIP destinations (SIP phones, SIP trunks on Session Manager) arecounted by Session Manager CAC for the appropriate Locations.

• SIP trunks on Communication Manager that do not route to Session Manager (not arecommended configuration) are counted by Communication Manager.

Note:Communication Manager performs CAC in terms of bandwidth limits between two specificNetwork Regions, while Session Manager performs CAC as per limits covering all traffic intoor out of a Location, regardless of the far-end location.

Call Admission Control


Communication Manager Session Manager interoperability


Chapter 5: Communication ManagerMessaging changes

Direct SIP integration between Communication ManagerMessaging and Communication Manager

OverviewCommunication Manager Messaging R6.0.1 allows direct SIP integration with CommunicationManager R6.0.1. You need to administer Communication Manager screens andCommunication Manager Messaging Web pages to implement direct SIP integration betweenCommunication Manager and Communication Manager Messaging.

Adding node names for SIP integration

1. Using PuTTY, log in to the SAT screen.

2. Type change node-names ip.

3. In the Names column, add an entry for SIP.

4. Type procr.

5. In the IP Address column, enter the IP address of the processor Ethernet.

6. Type msgserver.

7. In the IP Address column, enter the same IP address that you entered for theprocessor Ethernet.

8. Submit the changes.


Adding a signaling group for direct SIP integration

1. On the SAT command prompt, type add signaling-group n, where n is thesignaling group used for SIP.

2. On Page 1 in the Group Type field, change the type to SIP.

3. In the Transport Method field, type either tls or tcp as the transport method.

4. In the Near-end Node Name field, type procr.

5. In the Far-end Node Name field, type msgserver.

6. In the Far-end Listen Port field, type a value that is different from the value enteredin the Near-end Listen Port field. You can use 5060/6060 (near-end listen port/far-end listen port) as the port numbers for TCP transport type and 5061/6061 (near-end listen port/far-end listen port) as the port numbers for TLS transport type.

7. In the Far-end Network Region field, type 1.

8. In the Far-end Domain field, type the SIP domain name.

Note:Ensure that you enter the same values on the Adding signaling group form andthe Switch Link Admin Web page of the Communication Manager MessagingWeb interface.


Add Signaling Group field descriptions

Field Setting

Group Type SIP

Transport Method tls or tcp

Near-end Node Name procr (IPv4 IP address) or procr6 (IPv6 IP address)or name of the CLAN, depending on which interfaceconnects to Communication Manager Messaging.

Far-end Node Name Name of the messaging server, in IPv4 or IPv6 IPaddress format, that is resident on the CommunicationManager Messaging server. This name is the samename that appears on the Node Names screen and hasthe Integrated Messaging IP address.

Communication Manager Messaging changes


Field Setting

Near-end Listen Port 5060 (TCP) / 5061(TLS)

Far-end Listen Port 6060 (TCP) / 6061(TLS)

Far-end Network Region 1 is usually assigned to procr. If this field is left blank,Communication Manager uses the network regionassociated with the near-end node name.

IMS Enabled? n

Far-end Domain Name of the SIP domain.

DTMF over IP out-of-band

Enable Layer 3 Test? y

Direct IP-IP AudioConnections?

y

IP Audio Hairpinning? n

Interworking Message PROGress

Note:The fields that must be left blank must not have any values entered at this time. The valuesare populated later in the administration process. The fields that need not be left blank cantake the default value.

The field, Far-end Network Region, defaults to 1 if a value is not specified.

Note:If the configuration of the Far-end Network Region field changes, the signaling group maynot function correctly for messaging.

Adding a trunk group for direct SIP integration

1. At the SAT command prompt, type add trunk-group n, where n is the trunk groupnumber.

2. In the Group Type field, type SIP.

3. In the TAC field, type the value that you entered in the dial plan analysis.

4. In the Service Type field, type tie.

5. In the Signaling Group field, type the signaling group number used for SIP.

Direct SIP integration between Communication Manager Messaging and Communication Manager


6. In the Number of Members field, type the value supported by the signalinggroup.


Creating a hunt group for messaging

1. At the SAT interface prompt, enter add hunt-group <nnn>, where <nnn>represents the number of a new, unused hunt group.This hunt group should be consistent with your country settings. It is only used formessaging.The system displays the Hunt Group window.

2. Verify that the Group Name field is set to msgserver.

3. Verify that the Group Extension field matches the value used in the Pattern fieldof the dial pattern created for Communication Manager Messaging whileadministering Session Manager. This value must be within the range of extensionsyou defined. Do not use the value as a station or any other entity.This field identifies the default voice mail extension.

4. Verify that the Group Type is set to ucd-mia.

5. Verify that the COR field is set to 1.

Note:The COR for the hunt group must not be outward restricted.

6. Go to page 2.

Important:Set the Message Center to the value sip-adjunct. This value is required forother fields to display on this page.

7. Verify that the Message Center field is set to sip-adjunct.

8. Verify that the Voice Mail Number field is set to the default voice mail extension.

9. Set the value of the Voice Mail Handle field to match the first part of the regularexpression you created while administering Session Manager.For example, if the regular expression is [email protected], use cmm forthe Voice Mail Handle field.



10. Verify that the value of the Routing Digits (e.g. AAR/ARS Access Code) fieldmatches the FAC that you specified for the Auto Alternate Routing (AAR) AccessCode field while setting the FACs for messaging.

11. Press the key combination Control E to save the values in the window.

Changing private numberingThis task is applicable only if you have set the trunk format to private.

1. On the SAT interface enter change private-numbering 1.

2. Enter values for the following fields:

• Ext Len

• Ext Code

• Trk Grp(s)

• Total Len

For example, if an extension and trunk are of the value 90001 and 90 respectively:

• Ext Len: 5

• Ext Code: 9

• Trunk Grp(s): 90

• Total Len: 5

3. Press Control E to save changes.

Changing a route pattern

Important:The route pattern must point to Session Manager.

1. Go to the SAT interface prompt, enter change route-pattern <nnn> , where<nnn> represents the number of the new trunk group that you created while creatinga trunk group for messaging. You must enter this number for messaging to functionproperly.



The system displays the route-pattern window.

2. Verify that the fields on this window are appropriate to change the route pattern.

Change Route-Pattern field descriptions

Field Setting

Pattern Name The route pattern name for the messaging trunk group. For example,msgserver.

Grp No. The number of the trunk group you created while creating a trunk groupfor messaging.

FRL 0

DCS/ QSIG Intw n

IXC user

BCC VALUE0 1 2 3 4 W

y y y y y n

TSC y

CA-TSC Request none

ITC rest

LAR rehu

Note:The CA-TSC Request field cannot contain a value until the TSC field is set to y.

Changing IP network region

1. At the SAT interface prompt, enter change ip-network-region <n>, where <n>represents the value in the Far-end Network Region field.

2. Press Enter.The system displays the IP Network Region page.

3. Set the value of the Authoritative Domain field to the SIP domain name.

4. On Page 4, in the Codec set column, type 1.



5. In the AGL column, type ALL.

6. Save the changes.

Changing the IP Codec Set

1. At the SAT interface prompt, enter change ip-codec-set <n>, where <n>represents the value you recorded for the Codec Set.The system displays the IP Codec Set window.

2. Verify that the Audio Codec field is set to G.711MU.

3. Verify that the Silence Suppression field is set to n.

4. Go to page 2.

5. Perform one of the following:

• If this installation is NOT using Fax, verify that the FAX field is set to relay.

• If this installation is using Fax, verify that the FAX field is set to T.38-standard.

6. Press the key combination Control E to save the values on the window.

Adding a coverage path for messaging

1. At the SAT interface prompt, enter add coverage path <nnn>, where <nnn>represents the number of a new, unused coverage path. You can substitute <nnn>with the first unused coverage path number. For example, if coverage paths 1through 5 are in use, the next parameter creates coverage path 6.The system displays the Coverage Path window.

2. In the Point1 field, enter hxx, where xx is the hunt group you created formessaging.For example, h3 represents hunt group 3.




Important:At this point, an Avaya Technician must be engaged to change the loginpasswords.

Changing AAR analysis

1. Enter change aar analysis <n>, where n represents the first digit of thewelcome to messaging extension.

2. Verify that appropriate values are set on Page 1.

Important:You must use values that are appropriate for your configuration. A system mayuse n–digit extensions. For example, the default messaging voice mail extensionnumber is 30000. This number varies per site. The columns for Total Min andTotal Max refer to the number of digits in the voice mail extension. If you areusing a dial plan with more than five digits, you must adjust this numberaccordingly.


Adding a station

1. On the SAT form, type add station <n>, where <n> is the a number from therange of extension for your enterprise.

2. In the Type field, type the station type.

3. In the Coverage Path 1 field, type the coverage path number that was set whileadding the coverage path.

4. In the Security Code field, type a code that you can use later to retrieve messagesfrom the TUI.

5. Complete the remaining fields.




Saving translationsTranslations refers to the process of configuring the communication server settings throughthe preceding procedures. When you complete the translations, you must save them.

At the SAT interface prompt, enter save translation.The system saves the translations.

Administering the Switch Link

1. Open a Web browser and in the Address field type the IP address of the SystemManagement Interface (SMI).

2. On the Administration menu, click Messaging.

3. Click Switch Link Administration > Switch Link Admin.

4. In the Switch Number field, type 1.

5. In the Extension Length field, enter the appropriate length.

6. In the Switch Integration Type field, enter SIP as the type of integration betweenthe Communication Manager virtual system and the Communication ManagerMessaging virtual system.

7. In the Quality of Service field, type a value for Call Control Per Hop Behavior (PHB)and Audio PHB or accept the default values. The value you enter for both the fieldssets the quality of service level for call control messages and audio streamsrespectively on networks that support this feature. The value for both the fields mustbe in the range 0 to 63. The value must match the corresponding number configuredfor the network region used by the messaging signaling group on the switch.

8. In the Transport Method field, enter either TCP or TLS depending on the methodyou selected while administering the signaling group.

9. In the Far-end Connections field, by default only one procr connection issupported.

10. In the Connection 1 field, enter the IP address of procr. You also need to enter theport number that was administered on procr.

11. The Messaging Address field displays the IP address of Communication ManagerMessaging.



Note:The IP address of procr and Communication Manager Messaging is the same.Hence the port numbers must be different. For example, if the Connection 1 portnumber is set to 5060, you can set the Messaging Address port number to 5061.The port numbers you enter on this Web page must match the values used whileadministering Communication Manager.

12. In the SIP Domain field, enter the domain used for Communication Manager andCommunication Manager Messaging while administering direct SIP integration.

13. In the Messaging Ports field, enter the number of voice ports the CommunicationManager Messaging virtual system uses for mailbox connections to theCommunication Manager virtual system.

14. In the Switch Trunks field, enter the total number of trunks for CommunicationManager.

15. If you have configured SRTP for messaging, in the Media Encryption field, enterthe type of Secure Real-time Transport Protocol (SRTP) encryption formessaging.

Important:You need to enable the SRTP feature in the change customer-options form andset the media encryption type in the change ip-codec-set form on CommunicationManager.

16. Click Save.

Restarting the messaging application

1. Under Utilities, click Stop Messaging.

2. After the application stops, click Start Messaging.



Direct SIP integration between Communication ManagerMessaging Federal and Communication Manager

Setting feature access codes for messagingFor messaging to function, you must create two feature access codes (FACs) and set twofeatures to use these FACs in the System Parameters Features window.

1. Go to the SAT interface prompt and enter change dialplan analysis.The system displays the DIAL PLAN ANALYSIS TABLE window.

2. Create two FACs. The FACs that you use for messaging can be one or moredigits.For example, in the following screen, Dialed Strings 8 and 9 are specified as FACs,and Dialed String 1 is specified as a DAC.

Note:The first FAC Dialed String value is used for the Auto Alternate Routing (AAR)setting. The second FAC Dialed String value is used for the Auto Route Selection(ARS) setting.

3. Press the key combination Control E to save the changes and exit the window.

4. Go to the SAT interface prompt and enter change feature-access-codes.The system displays the FEATURE ACCESS CODE (FAC) window.

5. Verify that the Auto Alternate Routing (AAR) Access Code field is set to the firstFAC Dialed String value you entered for step 2.If you use the example in step 2, the Feature Access Code (FAC) for Auto Alternaterouting (AAR) Access Code would be set to 3.

6. Verify that the Auto Route Selection (ARS) - Access Code 1 field is set to thesecond FAC Dialed String value you entered for step 2.If you use the example in step 2, the Feature Access Code (FAC) for Auto RouteSelection (ARS) - Access Code 1 would be set to 9.

7. Press the key combination Control E to save the changes and exit the window.

Direct SIP integration between Communication Manager Messaging Federal and Communication Manager


Next stepsYou must also create one dial access code (DAC) for later use by the trunk group. The DACis used to create the Trunk Access Code (TAC) while creating a trunk group for messaging.

Adding node names for SIP integration


2. Type change node-names ip.

3. In the Names column, add an entry for SIP.

4. Type procr.

5. In the IP Address column, enter the IP address of the processor Ethernet.

6. Type msgserver.

7. In the IP Address column, enter the IP address of the Communication ManagerMessaging Federal system.


Creating a signaling group

Adding a signaling group for direct SIP integration

1. On the SAT command prompt, type add signaling-group n, where n is thesignaling group used for SIP.

2. On Page 1 in the Group Type field, change the type to SIP.

3. In the Transport Method field, type either tls or tcp as the transport method.

4. In the Near-end Node Name field, type procr.

5. In the Far-end Node Name field, type msgserver.

6. Ensure that the port number is the same in the Far-end Listen Port and Near-endListen Port fields. You can use port 5060 for TCP transport type and port 5061 forTLS transport type.

7. In the Far-end Network Region field, type 1.



8. In the Far-end Domain field, type the SIP domain name.

Note:Ensure that you enter the same values on the Adding signaling group form andthe Switch Link Admin Web page of the Communication Manager MessagingWeb interface.



Field Setting

Group Type SIP

IMS Enabled? n

Transport Method tls or tcp

Near-end Node Name procr (IPv4 IP address) or procr6 (IPv6 IP address)or name of the CLAN, depending on which interfaceconnects to Communication Manager Messaging.

Far-end Node Name Name of the messaging server, in IPv4 or IPv6 IPaddress format, that is resident on the CommunicationManager Messaging server. This name is the samename that appears on the Node Names screen and hasthe Integrated Messaging IP address.

Near-end Listen Port 5061/5060 (TLS/TCP)

Far-end Listen Port 6061/6060 (TLS/TCP)

Far-end Network Region 1 is usually assigned to procr. If this field is left blank,Communication Manager uses the network regionassociated with the near-end node name.

Far-end Domain Name of the SIP domain.



Direct IP-IP AudioConnections?

y





Note:The fields that must be left blank must not have any values entered at this time. The valuesare populated later in the administration process. The fields that need not be left blank cantake default values.



Creating a trunk group

Adding a trunk group for direct SIP integration

1. At the SAT command prompt, type add trunk-group n, where n is the trunk groupnumber.

2. In the Group Type field, type SIP.

3. In the TAC field, type the value that you entered in the dial plan analysis.

4. In the Service Type field, type tie.

5. In the Signaling Group field, type the signaling group number used for SIP.

6. In the Number of Members field, type the value supported by the signalinggroup.


Add Trunk Group Page 1 field descriptions

Field Description

Group Type SIP

Group Name msgserver

COR 1

Dial Access? n

Service Type: tie



Field Description

Outgoing Display? n

Member Assignment Method auto

Signaling Group The number of the signaling group you created in thecreating a signaling group procedure.

1. Enter a value in the TAC field.

2. Enter the number of trunks (ports) in the Number of Members field that isappropriate for the number of messaging mailboxes for your platform.

Note:The TAC must start with the Dialed String value for the DAC you set up while settingthe FACs for messaging, and include the number of the trunk group. If you use the examplewhile setting the FACs for messaging , the TAC value would be 199.

Refer to the Number of Ports to Mailboxes Mapping section to determine the appropriatevalue.


Field Description

Unicode Name auto

Redirect On OPTIM Failure 5000

SCCAN? n

Digital Loss Group 18

Preferred Minimum Session Refresh Interval(sec) 600

XOIP Treatment auto

Delay Call Setup When Accessed Via IGAR? n


Field Setting

ACA Assignment? n

Measured none

Maintenance Tests? y

Numbering Format private



Field Setting

UUI Treatment service-provider

Replace Restricted Numbers? n

Replace Unavailable Numbers? n

Modify Tandem Calling Number no

Show ANSWERED BY on Display? y

Note:The private setting is recommended. If the private setting does not work for your site, usepublic, unknown, or unk-pvt. You must use AAR or ARS digit conversion for pathreplacement to work.


Field Setting

Mark Users as Phone? n

Prepend '+' to Calling Number? n

Send Transferring Party Information? n

Network Call Redirection? n

Send Diversion Header? n

Support Request History? y

Telephone Event Payload Type Leave blank

Convert 180 to 183 for Early Media? n

Always Use re-INVITE for Display Updates? n

Identity for Calling Party Display P-Asserted-Identity

Enable Q-SIP? n

After you submit this form, trunk groups are dynamically assigned for all trunks.


1. At the SAT interface prompt, enter add hunt-group <nnn>, where <nnn>represents the number of a new, unused hunt group.



This hunt group should be consistent with your country settings. It is only used formessaging.The system displays the Hunt Group window.


3. Verify that the Group Extension field matches the value used in the Pattern fieldof the dial pattern created for Communication Manager Messaging whileadministering Session Manager. This value must be within the range of extensionsyou defined. Do not use the value as a station or any other entity.This field identifies the default voice mail extension.




6. Go to page 2.

Important:Set the Message Center to the value sip-adjunct. This value is required forother fields to display on this page.

7. Verify that the Message Center field is set to sip-adjunct.


9. Set the value of the Voice Mail Handle field to match the first part of the regularexpression you created while administering Session Manager.For example, if the regular expression is [email protected], use cmm forthe Voice Mail Handle field.

10. Verify that the value of the Routing Digits (e.g. AAR/ARS Access Code) fieldmatches the FAC that you specified for the Auto Alternate Routing (AAR) AccessCode field while setting the FACs for messaging.







• Ext Len

• Ext Code

• Trk Grp(s)

• Total Len


• Ext Len: 5

• Ext Code: 9


• Total Len: 5



Important:The route pattern must point to Session Manager.

1. Go to the SAT interface prompt, enter change route-pattern <nnn> , where<nnn> represents the number of the new trunk group that you created while creatinga trunk group for messaging. You must enter this number for messaging to functionproperly.The system displays the route-pattern window.



Field Setting



FRL 0

DCS/ QSIG Intw n



Field Setting

IXC user


y y y y y n

TSC y

CA-TSC Request none

ITC rest

LAR rehu


Changing IP network region


2. Press Enter.The system displays the IP Network Region page.

3. Set the value of the Authoritative Domain field to the SIP domain name.

4. On Page 4, in the Codec set column, type 1.

5. In the AGL column, type ALL.

6. Save the changes.





4. Go to page 2.















Important:You must use values that are appropriate for your configuration. A system mayuse n–digit extensions. For example, the default messaging voice mail extensionnumber is 30000. This number varies per site. The columns for Total Min andTotal Max refer to the number of digits in the voice mail extension. If you are



using a dial plan with more than five digits, you must adjust this numberaccordingly.


Adding a station





























16. Click Save.






IPv6 implementation for Communication ManagerMessaging

OverviewWith IPv6 implementation, you can use IPv6 format IP addresses for your enterprise. Toimplement IPv6 capability for your network, administer Communication Manager andCommunication Manager Messaging for your enterprise.

You must administer the gateways registered to Communication Manager to enable IPv6capability.

Important:The system does not support IPv6 implementation for SIP integration using SessionManager. However, you can implement IPv6 for direct SIP integration and H.323 integrationbetween Communication Manager and Communication Manager Messaging.

Adding node names IP


2. In the SAT window, type change node-names IP.In the Name column, by default, the system displays procr6 and its IPv 6 format IPaddress on the form.

3. In the Name column, type mssgserver6.

IPv6 implementation for Communication Manager Messaging


4. In the IP Address column, type the IP address for the message server in IPv6format.


Defining IP interfaces for Processor Ethernet

1. Enter change ip-interfaces procr.The system displays the IP Interfaces window.

2. Enter values for the fields in the window.

IP interfaces field descriptions

Field (Page1) Description

Type The default node name is PROCR.

Node name The unique node name for the IP interface. procr is the default nodename. The node name here must already be administered on the NodeNames screen.

IP Address The IP address (on the customer LAN) of the Processor Ethernet.

Subnet Mask The subnet mask associated with the IP address for this IP interface.For more information on IP addresses and subnets, see Administrationfor Network Connectivity for Avaya Communication Manager,555-233-504.

EnableInterface?

The Ethernet port must be enabled (y) before it can be used. The portmust be disabled (n) before changes can be made to its attributes onthis screen.

Network Region The region number for this IP interface.

Target socketload

The threshold for the number of sockets used by this CLAN within thesame Gatekeeper Priority as that of other IP interfaces. If the targetednumber is exceeded on a CLAN, a warning alarm is generated. If thetargeted percentage is exceeded on an PE interface, a procr error isgenerated.

Allow H.323Endpoints

Enter y to allow H.323 endpoint connectivity on this CLAN. Enter n ifyou do not want H.323 endpoints to connect to this CLAN.

Allow H.248Gateways?

Enter y to allow branch gateways to connect to this CLAN. Enter n ifyou do not want branch gateways to connect to this CLAN.



Field (Page1) Description

GatekeeperPriority

This value is used on the alternate gatekeeper list. The lower thenumber the higher the priority. Valid values for this field are one throughnine with five being the default. This field displays only if the allow H.323endpoints field is set to a yes on this form.

Field (Page 2) DescriptionNode Name The default name is procr6.

IP Address The IP address in IPv6 format of theProcessor Ethernet.

Subnet Mask The subnet mask associated with the IPaddress for this IP interface. For moreinformation on IP addresses and subnets,see Administration for Network Connectivityfor Avaya Communication Manager,555-233-504.

Enable Interface? Enter y to enable Processor Ethernet toaccept IPv6 addresses.

Creating a signaling group

Adding a signaling group for messaging

1. At the SAT interface prompt, enter add signaling-group <nnn>, where <nnn>represents the number of the new signaling group.

2. Press Enter.

Note:The number of this signaling group must not be in use and should also beavailable for the creation of a trunk group. For example, if you create this signalinggroup as 99, the corresponding trunk group should be created as 99. For thisgroup, choose a number that is easily differentiated from other signaling and trunkgroups.

The system displays the Signaling Group window.




You can also set SIP as the group type. However, the fields to add a SIP signaling group aredifferent from an H.323 signaling group.

Field Setting

Group Type h.323

Remote Office? n

Max number of NCA TSC 10

Max number of CA TSC 10

Trunk Group for NCA TSC (Leave blank)

Trunk Group for Channel Selection (Leave blank)

TSC Supplementary ServiceProtocol

b

Near-end Node Name procr (IPv4 IP address) or procr6 (IPv6 IPaddress) or name of the CLAN, depending onwhich interface connects to CommunicationManager Messaging.

Far-end Node Name Name of the messaging server, in IPv4 or IPv6 IPaddress format, that is resident on theCommunication Manager Messaging server. Thisname is the same name that appears on the NodeNames screen and has the Integrated MessagingIP address.

Near-end Listen Port 1720

Far-end Listen Port 1720

Far-end Network Region 1 is usually assigned to procr. If this field is leftblank, Communication Manager uses the networkregion associated with the near-end node name.

Calls Share IP SignalingConnection?

y if the group type is H.323.



Direct IP-IP Audio Connections? y





Note:The fields that must be left blank must not have any values entered at this time. The valuesare populated later in the administration process.


The Calls Share IP Signaling Connection field is set to y so that messaging does not attemptto create a new TCP/IP connection for each call.


Creating a trunk group

Adding a trunk group

1. At the SAT interface prompt, enter add trunk-group <nnn>, where <nnn>represents the number of this new trunk group.

Note:This number must not be in use. For ease of identification, set this number equalto that of the signaling group that you created. For example, if you created asignaling group as 99, create the corresponding trunk group 99.

The system displays page 1 of the Trunk Group window.

2. Verify the fields on page 1, page 2, page 3, and page 4 of the Trunk Groupwindow.


Important:If you do not set the Group Type value to isdn, the system does not display some of thefields of this window.

Important:You can also add a SIP trunk group. However, the fields on the screen are different and youneed to provide values to the fields.



Field Description

Group Type isdn

Group Name msgserver6

Carrier Medium H.323

COR 1

Dial Access? y

Service Type: tie

Outgoing Display? n

Member Assignment Method auto

Signaling Group The number of the signaling group you created in thecreating a signaling group procedure.

1. Enter a value in the TAC field.

2. Enter the number of trunks (ports) in the Number of Members field that isappropriate for the number of messaging mailboxes for your platform.

Note:The TAC must start with the Dialed String value for the DAC you set up while settingthe FACs for messaging, and include the number of the trunk group. If you use the examplewhile setting the FACs for messaging , the TAC value would be 199.

Refer to the Number of Ports to Mailboxes Mapping section to determine the appropriatevalue.


Field Description

Supplementary Service Protocol b

Digit Handling (in/out) enbloc/enbloc

Format pub-unk

Disconnect Supervision - In? y

Out? n




Field Setting

Send Name n

NCA-TSC Trunk Member 1

Send Calling Number y

Format private

Send Called/Busy/Connected Number y

Note:The private setting is recommended. If the private setting does not work for your site, usepublic, unknown, or unk-pvt. You must use AAR or ARS digit conversion for pathreplacement to work.


Field Setting

Path Replacement with Retention? n

Path Replacement Method better-route

QSIG Value-Added? y

After you submit this form, trunk groups are dynamically assigned for all trunks.

Administering gateway

Enabling IPv6 format on the gateway

1. Using PuTTY, log in to the gateway using root credentials.

2. At the prompt, type interface VLAN 1.

3. Press Enter.

4. Type icc-vlan.

5. Press Enter.



6. Type ipv6 admin-state up.

7. Press Enter.

8. Type PMI6.

9. Press Enter.

10. Type exit.

Adding IP address in IPv6 format of Communication Manager

1. At the prompt, type clear mgc list.

2. Press Enter.

3. Type show mgc list.

4. Press Enter.

5. Type set mgc list IPv4 address + IPv6 Address of Communication Manager.

6. Press Enter.

7. Type copy run start. This command copies the configuration to the gateway.

8. Type reset.The gateway is registered to Communication Manager with IPv6 capability.


1. At the SAT interface prompt, enter add hunt-group <nnn>, where <nnn>represents the number of a new, unused hunt group.This hunt group should be consistent with your country settings. It is only used formessaging.The system displays the Hunt Group window.


3. Verify that the Group Extension field is within the range of extensions you defined,and that it is not to be used as a station or any other entity.This field identifies the default voice mail extension.






6. Go to page 2.

Important:Set the Message Center to the value qsig-mwi. This value is required for otherfields to display on this page.

7. Verify that the Message Center field is set to qsig-mwi.

8. Verify that the Send Reroute Request field is set to y.


10. Verify that the value of the Routing Digits (e.g. AAR/ARS Access Code) fieldmatches the FAC that you specified for the Auto Alternate Routing (AAR) AccessCode field while setting the FACs for Communication Manager.





• Ext Len

• Ext Code

• Trk Grp(s)

• Total Len


• Ext Len: 5

• Ext Code: 9




• Total Len: 5



1. Go to the SAT interface prompt, enter change route-pattern <nnn> , where<nnn> represents the number of the new trunk group that you created while creatinga trunk group for messaging. You must enter this number for messaging to functionproperly.The system displays the route-pattern window.



Field Setting



FRL 0

DCS/ QSIG Intw n

IXC user


y y y y y n

TSC y

CA-TSC Request none

ITC rest

LAR rehu




Changing the IP Network Region


2. Press Enter.The system displays the IP Network Region window.

3. Verify that the Intra-region IP-IP Direct Audio field is set to yes.

4. Verify that the Inter-region IP-IP Direct Audio field is set to yes.

5. Verify that the IP Audio Hairpinning? is set to n.

6. Note the value in the Codec Set field for use later in the procedure.

7. Go to page 3. (Key combination Control N)

8. Verify that the value of the src rgn field matches the Far-end Network Regionvalue.

9. Enter the value of the Codec Set field you noted in step 6.

10. Press the key combination Control E to save the values set in the window.





4. Go to page 2.















Important:You must use values that are appropriate for your configuration. A system mayuse n–digit extensions. For example, the default messaging voice mail extensionnumber is 30000. This number varies per site. The columns for Total Min andTotal Max refer to the number of digits in the voice mail extension. If you are



using a dial plan with more than five digits, you must adjust this numberaccordingly.


Adding a station





























16. Click Save.






Subscribers

Subscriber ManagementSystem Manager lets you perform selected messaging system administration activities. Youcan add, view, edit, and delete subscribers through System Manager. Apart from subscribermanagement, you can also administer mailboxes and modify mailbox settings for a messagingsystem.

System Manager supports:

• Communication Manager 5.0 and later

• Avaya Aura® Messaging 6.0

• Avaya Aura® Modular Messaging 5.0 and later

• Communication Manager Messaging 5.2 (with patch having LDAP support) and later

Adding a subscriber

1. On the System Manager console, under Elements, click Messaging.

2. Click Subscriber in the left navigation pane.

3. Select one or more messaging systems from the list of Messaging Systems.

4. Click Show List.

5. Click New.

Subscribers


6. Complete the Basic Information, Subscriber Directory, Mailbox Features,Secondary Extensions, and Miscellaneous sections.

7. Complete the Add Subscriber page and click Commit to add the subscriber.

Note:If you select more than one Messaging, Modular Messaging, or CommunicationManager Messaging from the list of messaging systems, and then click New, thesystem displays the Add Subscriber page with the first Messaging, ModularMessaging, or Communication Manager Messaging in context.

Editing a subscriber



3. Select a messaging system from the list of Messaging Systems.

4. Click Show List.

5. From the Subscriber List, choose the subscriber you want to edit.

6. Click Edit or View > Edit.

7. Edit the required fields in the Edit Subscriber page.

8. Click Commit to save the changes.

Viewing a subscriber




4. Click Show List.

5. Select the subscriber you want to view from the Subscriber List.

6. Click View.



Note:You cannot edit any field on the View Subscriber page.

Deleting a subscriber




4. Click Show List.

5. Select the subscriber you want to delete from the Subscriber List.

6. Click Delete.The system displays a confirmation page for deleting the subscriber.

7. Confirm to delete the subscriber or subscribers.

Note:You cannot delete a subscriber associated with a user through mailboxmanagement. You can delete the user associated subscribers only through UserProfile Management.

Subscriber ListSubscriber List displays all the subscribers under a messaging version (Messaging,Communication Manager Messaging, or Modular Messaging). You can apply filters to eachcolumn in the Subscriber List. You can also sort the subscribers according to each of thecolumn in the Subscriber List. When you click Refresh, you can view the updated informationavailable after the last synchronization operation.

Name Description

Name Specifies the name of the subscriber.

Mailbox Number Specifies the mailbox number of the subscriber.

Email Handle Specifies the e-mail handle of the subscriber.

Telephone Number Specifies the telephone number of the mailbox.

Subscribers


Name Description

Last Modified Specifies the time and date when the subscriber details were lastmodified.

User If a subscriber is associated with a user, then the system displays thename of the user in this column.

System Specifies the messaging system of the subscriber.

Filtering subscribers




4. Click Show List.

5. Click the Filter: Enable option in the Subscriber List.

6. Filter the subscribers according to one or multiple columns.

7. Click Apply.To hide the column filters, click Disable. This does not clear any filter criteria thatyou have set.

Note:The table displays only those subscribers that match the filter criteria.

Subscribers (CMM) field descriptions

Field Description

System Specifies the messaging system of the subscriber you want to add.

Template Specifies the template for this subscriber. You can choose anytemplate from the drop-down box.

Type Specifies the messaging type of your subscriber.

Software Version Specifies the messaging version of the subscriber.

Save as Template Saves your current settings as a template.



Basic Information

Field Description

Last Name Specifies the last name of the subscriber.

First Name Specifies the first name of the subscriber.

Extension Specifies a number that is between 3 to10-digits in length, that thesubscriber will use to log on to the mailbox. Other local subscribers canuse the Mailbox Number to address messages to this subscriber. TheMailbox Number is:

• Within the range of Mailbox Numbers assigned to your system.

• Not assigned to another local subscriber.

• A valid length on the local machine.

Password The default password that a user has to use to login to his/her mailbox.The password you enter can be 1 to 15–digits in length and cannot beblank

COS The class of service for this subscriber. The COS controls subscriberaccess to many features and provides general settings, such as mailboxsize. You can select an option from the drop—down box.

Community ID Specifies the default community ID for the subscriber. Community IDs areused to control message sending and receiving among groups ofsubscribers. The default value is 1.

SwitchNumber

Specifies the number of the switch on which this subscriber's extensionis administered. You can enter 0 through 99, or leave this field blank.

• Leave this field blank if the host switch number should be used.

• Enter 0 if no message waiting indicators should be sent for thissubscriber. You should enter 0 when the subscriber does not have aphone on any switch in the network.

Account Code Specifies the Subscriber Account Code. The Subscriber Account Code isused to create Call Detail Records on the switch for calls placed by thevoice ports. The value you enter in this field can contain a combination ofdigits from 0 to 9. If an account code is not specified, the system will usethe subscriber's mailbox extension as the account code.

Subscriber Directory

Field Description

Email Handle Specifies the name that appears before the machine name and domainin the subscriber's e-mail address.

Common Name Specifies the display name of the subscriber.

Subscribers


Mailbox Features

Field Description

CoveringExtension

Specifies the number to be used as the default destination for theTransfer Out of Messaging feature. You can enter 3 to 10 digits in thisfield depending on the length of the system's extension, or leave this fieldblank.

Secondary Extensions

Field Description

Secondaryextension

Specifies the number assigned to a subscriber for receiving faxmessages. Valid Entries are blank or 3-10 digits (0-9), depending onthe length of the system's extension.

Miscellaneous

Field Description

Misc 1 Specifies additional, useful information about a subscriber. Entries in this field arefor convenience and are not used by the messaging system.




Button Description

Commit Adds the subscriber to the messaging system.

Schedule Adds the subscriber at the specified time.

Save as Template Saves the settings as a template.

Reset Clears all the changes.

Edit Allows you to edit the fields.

Done Completes your action and takes you to the previous page.

Cancel Takes you to the previous page.



Upgrades

Upgrade pathsThe upgrade paths to Communication Manager Messaging Release 6.0.1 are:

• Upgrading IA770 Release 4.0.5 to CMM Release 6.0.1

• Upgrading CMM Release 5.2.1 to CMM Release 6.0.1

Upgrades


Chapter 6: Hardware

This chapter describes the new hardware, including the Avaya Common Severs Dell™ PowerEdge™ R610and HP ProLiant DL360 G7, and new endpoints supported by Communication Manager Release 6.0.1.

Avaya A175 Desktop Video DeviceThe Avaya A175 Desktop Video Device with the Avaya Flare ™ Experience is a high-resolution,touchscreen device that enables you to quickly and easily manage your daily communications(that is, voice calls, video calls, instant messages (IMs), and emails). Running on the Androidoperating system, the Avaya A175 Desktop Video Device can operate on both wired andwireless networks from your desktop.

Using the Avaya A175 Desktop Video Device, you can:

• make and receive voice calls• make and receive video calls• start or join multi-party audio conference calls• start or join multi-party video conference calls• send and receive instant messages• see the availability of contacts that you have identified as buddies• access and manage your Microsoft Exchange account

Once configured, the Avaya A175 Desktop Video Device automatically download yourExchange contacts into the Exchange account and download the events from yourExchange calendar into the Avaya A175 Desktop Video Device calendar. The Avaya A175Desktop Video Device will automatically synchronize with your Exchange account (thatis, contacts, calendar, and email) at regular intervals to ensure you have the most up-to-date information.

• access your Facebook account

Once configured, the Avaya A175 Desktop Video Device automatically download yourFacebook friends into your contacts. The Avaya A175 Desktop Video Device willautomatically synchronize your Facebook information at regular intervals to ensure youhave the most up-to-date information from your Facebook account.

• access and manage your Gmail account

Once configured, the Avaya A175 Desktop Video Device automatically download yourGmail contacts into the Gmail account. The Avaya A175 Desktop Video Device will


automatically synchronize with your Gmail account at regular intervals to ensure you havethe most up-to-date information.

• surf the web

For more information, see Avaya Video Conferencing Solution Release 6.0.

Avaya 1000 Series Video Conferencing endpointAvaya 1000 Series endpoint is a video conferencing system for desktop, office, and small tolarge conference rooms. These endpoints include the video codec, camera, audiocomponents, handheld remote and cables. You must supply HDTVs with built-in speakers andat least one HDMI port. If wall-mounting, you must provide and install the wall mounts.

The Avaya 1000 Series Video Conferencing endpoint has the following characteristics:

• 1080p/720p HD video and wideband audio communications

• Single and dual display configurations

• Embedded MCU options for multipoint calling

• Channel provided accessories and services for HDTV’s, media centers and custominstallation

Avaya 1010 Video Conferencing endpointThe Avaya 1010 Video Conferencing endpoint is primarily for desktop users. This endpointcomes with a fixed focused camera and microphone HDTV speakers primarily for desktopusers.

The Avaya 1010 Video Conferencing endpoint has the following characteristics:

• Supports 1 HD display. The recommended HD display size is 20 to 26 inches

• Does not support optional HD camera

• Single display for viewing participants and content

• Graphical display size is 1024 x 576 pixels

Avaya 1020 Video Conferencing endpointThe Avaya 1020 Video Conferencing endpoint comes with a pan-tilt-zoom camera and micpods. This endpoint is primarily for an office or small conference room. You can locate the 1020system over a credenza or on a wall mount.

Hardware



• Supports 1 HD display. The recommended HD display size is 32 to 42 inches.

• Does not support optional HD camera

• Single display for viewing participants and content


Avaya 1030 Video Conferencing endpointAvaya 1030 Video Conferencing endpoint is for midsize to large conference rooms. You canlocate the 1030 System on a media center or wall mount. The Avaya 1030 Video Conferencingendpoint comes with a pan-tilt-zoom camera, microphone pod, and dual displays for viewingparticipants and content.



• Supports 1 optional HD camera


Avaya 1040 Video Conferencing endpointThe Avaya 1040 Video Conferencing endpoint is for midsize to large conference rooms. Youcan locate it on a media center or wall mount. This endpoint includes a pan-tilt-zoom camera,microphone pod, and dual displays to view participants and content. It also offers an optionalconference room phone and is a 4-port MCU enabling multi-point conferencing.



• 4-port MCU for up to 4 simultaneous users



Avaya 1050 Video Conferencing endpointThe Avaya 1050 Video Conferencing endpoint is primarily for midsize to large conferencerooms. You can locate this endpoint on a media center or wall mount. This endpoint includesa pan-tilt-zoom camera, microphone pod, and dual displays for viewing participants andcontent. This endpoint also offers an optional conference room phone.

Avaya 1000 Series Video Conferencing endpoint



• Supports 2 HD displays. The recommended HD display size is 50 to 65 inches.

• 8-port MCU for up to 8 simultaneous users at 720p resolution, or 6-port MCU for up to 6simultaneous users at 1080p resolution


HP ProLiant DL360 G7 1U server overview

IntroductionThe Avaya Common Servers category includes the HP ProLiant DL360 G7 1U server thatsupports several Avaya software solutions, some requiring additional hardware and memoryrequirements beyond the standard configuration. This book covers the standard configurationonly—consult specific Avaya product documentation for application-specific or solution-specific server configurations.

Front of server

Note:Servers ship with 2–4 hard disk drives, depending upon product requirements.

No. Description

1 Not present

2 Not present

3 DVD-RW

4 HP Systems Insight Display

5 Front USB connector

6 Video connector

Hardware


No. Description

7 Hard drive bay 4

8 Hard drive bay 3

9 Hard drive bay 2

10 Hard drive bay 1

Back of server

Reference Description

1 Slot 1 PCIe2 x8 (8, 4, 2, 1)

Note:Servers might ship with a PCI card installed, depending upon productrequirements.

2 Slot 2 PCIe2 x16 (16, 8, 4, 2, 1), 75W +EXT 75W*


3 Power supply bay 1 (populated)

4 Power supply bay 2

5 iLO 3 connector

6 Serial connector

7 Video connector

8 NIC 4 connector

9 NIC 3 connector

10 NIC 2 connector

11 NIC 1 connector

12 USB connectors (2)



*This expansion slot provides 75 W of power to an adapter, with an additional 75 W of powersupplied by external power.

Server specificationsBaseline configurations and options for the HP DL360 G7 server:

Component Minimum specification Upgrade options basedon product requirements

DL360 G7 1U chassis, dual socket No additional optionssupported.

Processor Simplex configuration: Intel E5620 QuadCore / 2.4 GHz (Westmere), 1 CPU, 3memory channels per CPU with up to 3RDIMMs per channel

Note:Simplex server with the single E56202.4 GHz processor can be used in aduplex server configuration.

Duplex configuration: Intel X5670 sixCore / 2.93 GHz (Westmere), 1 CPU, 3memory channels per CPU with up to 3RDIMMs per channel

N/A

Memory 6 x 2GB DDR3 RDIMMs (1333 MHz) for atotal of 12GB

N/A

HW RAID 1 P410i RAID controller with 256MB cacheand battery backup. Optioned as RAID 5

N/A

Disk drive 146GB SAS 2.5" 10K RPM 6G DP HardDrive. Base configuration:

272 total: RAID 5, 3 x 146GB drives

N/A

NICs 6 NIC ports — HP NC382T PCI ExpressDual Port Gigabit NIC expansion card(Broadcom 5709 silicon) in addition 4integrated ENET Gigabit NIC ports

N/A

PCI slots Two PCI-Express Gen 2 expansion slots:(1) full-length, full-height slot and (1) low-profile slot (1-FL/FH x 16 PCIe & 1-LP x 8PCIe Riser

N/A

Removable media Slim line SATA DVD-RW optical drive(used in all Avaya configurations)

No additional optionssupported.

Hardware



Power supply Single 460 W hotplug AC power supply Redundant 460 W powersupply available.

Fans 3 fan modules (fan redundancy standard) No additional optionssupported.

Additional items 1 front USB, 2 back USB, 1 internal USB

Environmental specificationsThe HP DL360 G7 environmental specifications are listed below:

Specification ValueTemperature range

Note:All temperature ratings shown are for sea level. An altitudederating of 1°C per 300 m (1.8° per 1,000 ft.) to 3048 m(10,000 ft.) is applicable. No direct sunlight allowed.

Operating 10°C to 35°C (50°F to 95°F)

Shipping -40°C to 70°C (-40°F to 158°F)

Maximum wet bulbtemperature

28°C (82.4°F)

Relative humidity(noncondensing) Note:

Storage maximum humidity of 95% is based on a maximumtemperature of 45° C (113°F). Altitude maximum for storagecorresponds to a pressure minimum of 70 kPa.

Operating 10% to 90%

Non-operating 5% to 95%

Physical specificationsThe HP DL360 G7 physical specifications are listed below:

Specification Value

DimensionsHeight: 4.32 cm (1.70 in)

Width: 42.62 cm (16.78 in)



Specification ValueDepth: 69.53 cm (27.38 in)

Weight (maximum; twoprocessors, two powersupplies, eight hard diskdrives)

15.97 kg (35.20 lb)

Weight (minimum; oneprocessor, one powersupply, no hard drives)

14.51 kg (32.00 lb)

Weight (no drivesinstalled)

14.06 kg (31.00 lb)

ReferencesFor more information on HP DL360 G7 server, see the following:

• Installing the HP ProLiant DL360 G7 Server, 03-603799.• Maintaining and Troubleshooting the HP ProLiant DL360 G7 Server, 03-603803.

Dell™ PowerEdge™ R610 1U server overview

IntroductionThe Avaya Common Servers category includes the Dell™ PowerEdge™ R610 1U server thatsupports several Avaya software solutions, some requiring additional hardware and memoryrequirements beyond the standard configuration. This book covers the standard configurationonly—consult specific Avaya product documentation for application-specific or solution-specific server configurations.

Front of server

Hardware


Note:Servers ship with 2–4 hard disk drives, depending upon product requirements.


1 Power-on indicator, power button

2 NMI button


4 Video connector

5 LCD menu buttons

6 LCD panel

7 System identification button

8 Hard drives (maximum 4)

9 DVD-RW

10 System identification panel

Back of server


1 iDRAC6 Enterprise port (optional)

2 VFlash media slot (optional)

3 Serial connector

4 PCIe slot 1





5 Video connector


7 PCIe slot 2


8 Ethernet connectors (4)

9 System status indicator connector

10 System status indicator

11 System identification button

12 Power supply 1 (PS1)

13 Power supply 2 (PS2)

Server specificationsBaseline configurations and options for the Dell R610 server:


R610 1U chassis, dual socket Listed below

Processor Simplex configuration: Intel E5620 QuadCore / 2.4 GHz (Westmere), 1 CPU, 3memory channels per CPU with up to 2RDIMMs per channel

Note:Simplex server with the single E56202.4 GHz processor can be used in aduplex server configuration.

Duplex configuration: Intel X5670 sixCore / 2.93 GHz (Westmere), 1 CPU, 3memory channels per CPU with up to 2RDIMMs per channel

N/A

Memory 6 x 2GB DDR3 RDIMMs (1333 MHz) for atotal of 12GB

N/A

HW RAID 1 H700 RAID controller with 512MB cacheand battery backup. Optioned as RAID 5.

N/A

Hardware



Disk drive 146GB SAS 2.5" 10K RPM 6G DP HardDrive. Base configuration:

272 total: RAID 5, 3 x 146GB drives

N/A

NICs 6 NIC ports — Broadcom 5709 Dual Port1GbE NIC (430-3261) in addition 4integrated ENET gigabit NIC ports

N/A

PCI slots 2 PCIe risers (left and center) provide:

• Two x 8 PCIe Gen2 slots

• One x 4 PCIe Gen 1 slot

• FH/HL PCIe card support

No additional optionssupported.

Removable media DVD+/-RW SATA internal No additional optionssupported.

Power supply Single 502 W Hotplug AC power supply Redundant 502 W powersupply available.

Fans Redundant Speed Adjusting Fansstandard (5 for single processor)

No additional optionssupported. (2nd processorincludes 1 additional fan)

Additional items 2 front USB, 2 back USB, 1 internal USB

Environmental specificationsThe Dell R610 environmental specifications are listed below:

Specification ValueTemperature

Operating 10° to 35°C (50° to 95°F) with a maximum temperature gradation of 10°Cper hour

Note:For altitudes above 2,950 feet, the maximum operating temperature is de-rated 1°F per 550 ft.

Storage -40° to 65°C (-40° to 149°F) with a maximum temperature gradation or20°C per hour

RelativeHumidity



Specification ValueOperating 20% to 80% (non-condensing) with a maximum humidity gradation of

10% per hour

Storage 5% to 95% (non-condensing) with a maximum humidity gradation of 10%per hour

Altitude

Operating -16 to 3,048 m (-50 to 10,000 ft.)

Note:For altitudes above 2,950 ft, the maximum operating temperature is de-rated 1°F per 550 ft.

Storage -16 to 10,600 m (-50 to 35,000 ft.)

Physical specificationsThe Dell R610 physical specifications are listed below:

Specification Value

Dimensions

Height: 4.26 cm (1.68 in)

Width:

• 48.24 cm (18.99 in) with rack latches

• 42.4 cm (16.99 in) without rack latches

Depth:

• 77.2 cm (30.39 in) with power supplies and bezel

• 73.73 cm (29.02 in) without power supplies and bezel

Weight(maximumconfiguration)

17.69 kg (39 lb)

Weight (empty) 13.25 kg (29.2 lb)

ReferencesFor more information on Dell R610 server, see the following:

• Installing the Dell™ PowerEdge™ R610 Server, 03-603793.• Maintaining and Troubleshooting the Dell™ PowerEdge™ R610 Server, 03-603804.

Hardware


Chapter 7: Documentation and procedureupdates

This chapter describes the updates and additions for Communication Manager Release 6.0.1 that are notdocumented elsewhere for this release.

Adding New Hardware for Avaya Servers and GatewaysThe following change applies to the Adding New Hardware for Avaya Servers and MediaGateways, 03-300684:

Downloading Reliable Data Transport Tool

1. Log on to http://support.avaya.com.

2. In the InSite Knowledge Management search box, type “Reliable Data TransportClient/Server Tool” including the quotation marks.

3. Press Enter.

4. In the search results, click the appropriate Communication Manager Downloads linkof 08/26/2010.

5. On the download page, click Reliable Data Transport Client/Server Tool V2.0 of31-Aug-2005.

6. Click RDTT_R2.1.exe.

7. Click Save.

8. Make note of the default download directory.-or-Browse to the appropriate directory.

9. Click Save.

10. Click Run.



Note:To view and save the accompanying ReadMe file, selectRDTT_Readme_2.1.doc.

Administrator guideThe following changes apply to the Administering Avaya Aura™ Communication Manager,03-300509:

PE Interface configurationThe description of PE Interface Acceptance Test is added under the PE Interface configurationsection.

PE Interface acceptance test

If the main servers are duplicated and PE interface is not used (that is, no ESS server isprovided and no IP endpoints are controlled by PE interface), PE interface should not beenabled. The Status Summary page should show that Processor Ethernet connection is notfunctional on both servers, and PE priority is set to IGNORE for both servers.

If the Status Summary page does not provide the information stated above, you should verifythe following:

• For Communication Manager 5.0 and 5.1 releases, the PE Interface should be set toUNUSED on the Set Identities page. The PE Interchange Priority should be set toIGNORE on the Configure Interfaces page.

• For Communication Manager 6.0 and later releases, the Functional Assignment for eth0should not include Processor Ethernet on the Network Configuration page. The PEInterchange Priority should be set to IGNORE on the Duplication Parameters page.

If the main servers are duplicated and PE interface is used (that is, ESS server is provided orIP endpoints are controlled by the PE interface, or both ESS server is provided and IPendpoints are controlled by the PE interface), PE Interface on both the main server and theESS server should be enabled. The Status Summary page should show that ProcessorEthernet connection is functional on both servers, and PE Priority is set to same value (but notIGNORE) on both servers.

Documentation and procedure updates


If the Status Summary page does not provide the information stated above, you should verifythe following:

• For Communication Manager 5.0 and 5.1 releases, PE Interface should be set to one ofthe Ethernet interfaces on the Set Identities page, and PE Interchange Priority should beset to the same value (but not IGNORE) on the Configure Interfaces page on bothservers.

• For Communication Manager 6.0 and later releases, Functional Assignment for eth0should include Processor Ethernet on the Network Configuration page, and the PEInterchange Priority should be set to the same value (but not IGNORE) on the DuplicationParameters page on both servers.

If the main server or ESS server is duplicated, the Current Alarms page or the almdisplay-v shell command should not show any active _PE alarms for up to 15 minutes after bothservers have been running as an active or standby pair.

Administering Network ConnectivityThe following change applies to the Administering Network Connectivity on Avaya Aura™

Communication Manager, 555-233-504:

Reviewing the network region administrationReference 6.0 version – page 172, after step 4, the following steps are added:

1. Enter list ip-network-region igar-dpt to see the IP Network RegionsIGAR-DPT screen, which gives an overview of fields related to the Inter-GatewayAlternate Routing and Dial Plan Transparency features.

2. Ensure that the IGAR and DPT parameters are administered according to yourdesign.

Conversion of servers and gatewaysThe following changes apply to the Converting Avaya Servers and Media Gateways,03-602884:

Administering Network Connectivity


Suppress alarmingReference 5.2 version – pages 217, 220, 227, and 247, step four is removed: Log off and closethe dialog box.

Feature Description and ImplementationThe following changes apply to the Avaya Aura™ Communication Manager FeatureDescription and Implementation, 555-245-205:

Call detail record field descriptionsThe following section provides the description of new condition codes.

Condition Codes

The following condition codes are added to the existing condition codes table:

Conditioncodes

Description

O Identifies CDR records for all calls in which URI was used as dialeddigits.

P Identifies CDR records for all calls in which SA8957 PIN code for PrivateCalls was used.

Call forward overrideIf the Call Forward Override feature is turned on, and a call terminates at an already visitedstation for that call as a part of the call forward chain, the call is not forwarded. Instead, thecall continuously rings at that station to avoid loops while traversing the chained call forwardpath.

For example, Station A has activated call forward feature to Station B, Station B to Station C,and Station C to Station D. In this case, if Station A gets an incoming call and forwards the callto Station B, then Station B forwards the call to Station C, and Station C forwards the call toStation D. Eventually the call is answered by Station D, which transfers the call to Station A.The call continuously rings at Station A and is not forwarded to Station B.



Call ParkIf you enable the Drop Parking User From the Call After Timeout field, the systemautomatically drops the parking user from the call after timeout.

Screens for administering Call Park

Screen name Purpose Fields

Feature-RelatedSystem Parameters

Specifies to the system to automaticallydrop the parking user from the call after thetimeout that is set.

Drop Parking UserFrom the Call AfterTimeout

Considerations for Administrable Language DisplaysThe following list describes the situations when the Display Messages screen is disabled:

• After loading an avaya_user-defined.txt file, Communication Manager disables thefollowing qualifiers for both the change and display display-message commands:

ad-programming, malicious-call-trace, softkey-labels, auto-wakeup-dn-dst,miscellaneous-features, time-of-day-routing, button-labels, transfer-conference, call-identifiers, property-management, view-buttons, date-time, self-administration, vustats,and leave-word-calling.

• After loading an avaya_user-defined.txt file, Communication Manager disables thepage 1 of the Posted Messages screen for both the change and display display-messagecommands. However, you can enter translations for the fixed languages in the PostedMessages screen.

• After loading a custom_user-defined.txt file, Communication Manager disables thelast page of the Posted Messages screen and relates to the user-defined translation forboth the change and display display-message commands. You can, however, entertranslations for the fixed languages in the Posted Messages screen.

• After loading an avaya_user-defined.txt file, Communication Manager does notallow the user-defined keyword for the Label Language field on the Abbreviated Dialingscreen. You can, however, enter translations for the fixed languages in the AbbreviatedDialing screen.

Enhanced Redirection NotificationFor Enhanced Redirection Notification, you must enable at least one of the RedirectionNotification options listed in the Feature-Related System Parameters screen. For example, ifyou disable all the redirection notification options, all the notifications appear on the IP (H.323)

Feature Description and Implementation


telephones. The system does not check the notifications to be displayed when you disable allthe options. However, if you activate Do Not Distrub (DND) notification field, only the DNDnotification appears on the endpoints. This is because the system checks the displayednotifications only when you enable at least one of the options.

Interactions for Station Security CodeThis section provides information about how the Station Security Code feature interacts withthe other features on the system. Use this information to ensure that you receive the maximumbenefits of Station Security Code in any feature configuration.

You may need a Station Security Code to use the following system features and capabilities:

• Call Forwarding

• Demand Printing

• Extended User Administration of Redirected Calls

• Enterprise Mobility User

• Extension to Cellular

• Leave Word Calling (LWC)

• Personal Station Access (PSA)

• Posted Messages

• Station Lock

• Security Violation Notification

• Terminal Self-Administration

• User Change Coverage

• Voice Message Retrieval

System requirements for EMUThe following description is added to the existing System requirements for EMU section:

For optimal performance and feature functionality EMU requires,

• Private numbering administration supporting UDP dialing between enterprise sites.

• The EMU visiting user is able to dial directly the EMU home user using UDP dialing.

• The EMU home user is able to dial directly the EMU visiting user using UDP dialing.

• All locations dialing. If per location dialing or partition group route administration isconfigured, Communication Manager does not support EMU. If an EMU user is assigned



to a location or is reached through partition group routing, EMU registration is notallowed.

Installing and Upgrading the Avaya G450 GatewayThe following change apply to the Installing and Upgrading the Avaya G450 Gateway,03-602054:

Downloading Reliable Data Transport ToolFor information on downloading RDTT, see Downloading Reliable Data Transport Tool onpage 93.

Installing and Upgrading the Avaya S8300 ServerThe following changes apply to the Installing and Upgrading the Avaya S8300 Server,555-234-100:

Downloading Reliable Data Transport ToolFor information on downloading RDTT, see Downloading Reliable Data Transport Tool onpage 93.

Maintenance AlarmsThe following changes apply to the Maintenance Alarms for Avaya Aura™ CommunicationManager, Media Gateways and Servers, 03-300430:

CONFIG (System Configuration)

Error log entries and recommended actions

Reference 6.0 version – page 290, the note about Error Type 257 is modified to 'less than 75%of the overall trunk group capacity is available.'

Installing and Upgrading the Avaya G450 Gateway


disable synchronization-switchThe disable synchronization-switch command is renamed as disablesynchronization.

enable synchronization-switchThe enable synchronization-switch command is renamed as enablesynchronization.

IP Signaling Group Far-End Status Test (#1675)The description of the IP Signaling Group Far-End Status Test is updated as follows:

This test validates that you can use the trunks on this signaling group. If the test fails, theaffected signaling channel is taken out of service and an alarm is raised. Once the test passes,the primary is put back in service and the alarm is retired.

Media Path Status Test (#1374)The Media Path Status test verifies that the VoIP media is available and in-service in the IPstations region or any connected region. If the VoIP media is available in the IP stations regionor any connected region, the test passes. If the VoIP media is not available in the IP stationsregion or any connected region, the test fails.

This test uses the stations mapped region that is also shown in the status stationcommand for the station.

Table 1: Media Path Status Test (#1374)

Error Code Test Result Description / Recommendation1706 ABORT This station is not registered.

Media Path Status test only runs on registered stations.

2100 ABORT Could not locate the necessary system resources to runthis test.

1. Retry the command at 1-minute intervals, up to 5times.

2. Escalate if the problem persists.

2012 ABORT Internal system error.



Error Code Test Result Description / Recommendation



2500 ABORT Internal system error.



ANY FAIL VoIP media is not available in the IP stations region or anyconnected region.

1. Verify that there are VoIP media assigned to thestations region. Valid media are IPMEDRO boards orBranch Gateways.

2. If there are VoIP media assigned to this Stationsregion, verify that the media are in service.

PASS VoIP media is available and in-service in the IP stationsregion.

SIP-SGRP (SIP Signaling Group)Error log entries and recommended action

ErrorType

AuxData

Associated Test AlarmLevel

On/OffBoard

RecommendedAction

258 17 IP Signaling GroupFar-End Status Test(#1675)

MIN OFF

Note:Error Type 258: Primary signaling link is unavailable.

Maintenance CommandsThe following changes apply to the Maintenance Commands for Avaya Aura™ CommunicationManager, Media Gateways and Servers, 03-300431:

Maintenance Commands


AAR and ARS Digit Analysis TableThe following Action/Object is added to the AAR and ARS Digit Analysis Table under theAdministration Screen Reference section.

Action/Object Qualifier

list aar route-chosen dialed number [partition n] [schedule]



list ars route-chosenThe following field description is added in the list ars route-chosen field descriptions table.

Field Description

ActualOutpulsed Digitsby Preference

Digits outpulsed when you choose each of the preferences in the chosenroute pattern.

pingallpingall [-s [ServerID]] [-i [cab#][carrier]] [-c count ][-v ]

Use pingall to verify basic connectivity of all IPSI circuit packs.

-a Ping all network entities on the remote sides, including servers, routers, andIPSI circuit packs.

-s ServerID Ping a specific customer LAN-i cab#[carrier] Ping a specific IPSI



-c count The number of test messages for each network entity-v Turn on verbose mode-? Display a description of command options

Exampleinit@sraydb2-srv1> pingall -aTesting..HostName IPAddress Statusipsi-A02b 172.16.5.54 Passipsi-A02a 172.16.5.53 Passipsi-A01b 172.16.5.52 Passipsi-A01a 172.16.5.51 Passinit@sraydb2-srv1>

ReportsThe following change apply to the Avaya Aura™ Communication Manager Reports,555-233-505:

AAR or ARS Route Chosen reportsReference 6.0 version – pages 55 and 56, the following field description is added in the existingfield description table:

Field Description

ActualOutpulsed Digitsby Preference

Digits outpulsed when you choose each of the preferences in the chosenroute pattern.

Attendant and Maintenance Status reportThe following description is added to the existing Attendant and Maintenance Status reportsection:

To ensure that the authorized users log into the system, you must click Cancel to log off fromthe SAT screen after running the monitor system view1 and monitor system view2commands.

Reports


Screen ReferenceThe following changes apply to the Avaya Aura™ Communication Manager ScreenReference, 03-602878:

Agent LoginIDThe description of the Security Code field on the Agent LoginID screen is modified.

Security Code

The four-digit station security code (password) for the Demand Print messages feature.

Attendant ConsoleThe description of the Security Code field on the Attendant Console screen is modified.

Security Code

The station security code required by the SoftConsole IP attendant.

Dial Plan Analysis TableThe description of the Percent Full field on the Dial Plan Analysis Table screen is modified asfollows:

Percent Full

Valid Entry Usage

0 to 100 The percentage of system memory resources that have been allocatedfor the dial plan currently used. For details on the system memoryresources, see Avaya Aura™ Communication Manager SystemCapacities Table, 03-300511.



Dial Plan ParametersThe following field is added on the Dial Plan Parameters screen.

UDP-ARS Calls Considered Offnet

Valid entry Usage

y If you set the Net field to ARS and the UDP-ARS Calls ConsideredOffnet field to y, the call is considered offnet.If UDP-ARS calls are considered off-net then:

• Users with the COS setting Restrict Call Fwd-Off Net enabled cannotforward calls to a UDP-ARS number.

• Stations that are outward-restricted (through the COR) cannot placecalls to a UDP-ARS number.

• Toll analysis is applied when a call is placed by a toll-restricted user toa UDP-ARS number.

• COR-COR checks are not applied when a user dials a call to a UDP-ARS number.

n If you set the Net field to ARS and the UDP-ARS Calls ConsideredOffnet field to n, the call is considered onnet.

For more information about the Net field, see Uniform Dial Plan Table section of the AvayaAura® Communication Manager Screen Reference, 03-602878.

Feature-Related System ParametersThe following fields are added on the Feature-Related System Parameters screen:

Drop Parking User From the Call After Timeout

Valid Entry Usage

y Drops the parking user from the call automatically after the timeout.

n Does not drop the parking user from the call automatically after thetimeout.

Screen Reference


Restrict Calls

Indicates the type of calls to block first during overload traffic conditions on the system.

Valid Entry Usage

stations-first Deny new traffic generated by internal stations, allowing inbound callsonly. This works best in call center environments.

all-trunks-first Deny all incoming trunk calls and does not block station off-hook.

public-trunks-first

Deny incoming calls on ISDN public trunks and analog CO trunks.

Zip Tone Burst For Call master Endpoints

Valid entry Usage

double When the station set type is a Callmaster series, CommunicationManager retains existing operation which applies the following to ACDagents:

• two bursts of zip tone for auto-answer ACD calls

• two burst of ICI tweedle-dee tone for non-ACD auto-answer calls

This is the default value.

single Communication Manager eliminates the 2nd burst of zip/ICI tonereducing time for agent to start conversation with the caller and possibilityof the agent and the caller hears open mike background noise betweenthe first and second tones. Use with a Callmaster station type when theagent can always hear enough of the single burst auto-answer torecognize that a call is being delivered.

Hunt GroupThe description of the Security Code field on the Hunt Group screen is modified.

Security Code




Incoming Call Handling TreatmentIn addition to predefined Services/Features, any user-defined Facility Type of 0 (feature), 1(service), 2 (incoming), or 3 (outgoing) on the Network Facilities screen is allowed. For aService/Feature defined as Type 2, the Incoming Call Handling Treatment screen determineswhich incoming calls are assigned to this Service/Feature. See the description of the NetworkFacilities screen for details.

Service type 2 is useful when creating a user-defined service on the ISDN Network Facilitiesscreen. A user defined service with Facility Type 2 allows special routing on the Incoming CallHandling Treatment Table as well as Min/Max usage restrictions on the Usage Allocationtable.

Facility type 3 is useful when creating a user-defined service for outgoing calls on ISDN cbctrunk groups. If a user-defined service with Facility Type 3 is used for a route patternpreference, the outgoing SETUP message will not contain an NSF IE, and the call will becounted in the corresponding user-defined service entry in the Usage Allocation table.

IP Network RegionThe valid entries of the WAN-BW limits (Total) field are modified on the IP Network Regionscreen.

WAN-BW limits (Total)

Valid Entry Usage

1 to 9999 The bandwidth limit for direct WAN links. Values for this field can beentered in the number of connections, bandwidth in Kbits or calls, or leftblank for NoLimit.

1 to 65 Values for this field can be entered in the number of connections,bandwidth in Mbits, or left blank for NoLimit.

ISDN Numbering Calling Party Number Conversion for TandemCalls

The following field descriptions on the ISDN Numbering Calling Party Number Conversion forTandem Calls screen are modified.

Screen Reference


CPN Len

Valid Entry Usage

1 to 16 A number between 1 and 16 that indicates the length of calling partynumber (CPN).

blank Leave blank when deleting an entry. This is the default value.

CPN Prefix

Valid Entry Usage

Anycombination ofdigits 0 to 9, upto 16 digits. The'+' sign is alsovalid.

Up to 16 digits to indicate the calling party prefix.

blank Indicates that all trunk groups are valid provided the Modify TandemCalling Party field on the ISDN Trunk Group screen is set to y. A specificCPN digit string match is not required, provided other matching criteriafor tandem CPN modification are met. This is the default value.

Delete

Valid Entry Usage

1 to 16 A valid number of deleted digits up to 16.

all Indicates that all digits are deleted.

blank Indicates that all trunk groups are valid provided the Modify TandemCalling Party field on the ISDN Trunk Group screen is set to y. No digitsare deleted from the received calling party number. This is the defaultvalue.



Insert

Valid Entry Usage

Anycombination ofdigits 0 to 9, upto 16 digits. The'+' sign is alsovalid.

A valid number between 1 and 16 to indicate the number of digits toinsert.

blank Indicates that all trunk groups are valid provided the Modify TandemCalling Party field on the ISDN Trunk Group screen is set to y. Thereceived calling party number is not prefixed with any digits. This is thedefault value.

LocationThe description of the Location field on the AAR and ARS Digit Analysis Table, AAR and ARSDigit Analysis Table, and Dial Plan Analysis Table screens is modified as follows:

Valid Entry Usage

1 to 250 (Depending on your server configuration, see Avaya Aura™

Communication Manager System Capacities Table,03-300511.) The location of the endpoint that is dialing thedigits. See the Location sections in Avaya Aura™

Communication Manager Feature Description andImplementation, 555-245-205, for the other ways to assign alocation, and for a list of features that use location.

all Phones dialing from this location use the entries in the Call TypeDigit Analysis Table. If there are matching entries in thetelephone’s location, those entries are used. If there are nomatching entries in the phone’s location, the CommunicationManager tries the entries in location all. If the MultipleLocations field is disabled, the value of the Location field isall.

Screen Reference


Numbering-Public/Unknown Format and Numbering-PrivateFormat

Overview of Numbering-Public/Unknown Format and Numbering-PrivateFormat screens

In Communication Manager 5.2.1 and later releases, you must administer the extensions ofall calls traversing SIP trunks in the appropriate private and public numbering tables on theNumbering-Public/Unknown Format and Numbering-Private Format screens. You must alsoconfigure the private and public numbering tables in the Numbering-Public/Unknown Formatand Numbering-Private Format screens for all extensions. You must populate the calls toextensions terminating on a SIP integrated Modular Messaging in the appropriate Numbering-Public/Unknown Format or Numbering-Private Format screens, and do not configure a prefixfor the SIP trunk group by which the Modular Messaging is integrated.

Percent FullThe description of the Percent Full field on the AAR and ARS Digit Analysis Table , AAR andARS Digit Conversion Table, Precedence Routing Digit Analysis Table, and Toll Analysisscreens is modified as follows:

Value Comments

0 to 100 The percentage of system memory resources that have been used bythe table. For details on the system memory resources, see Avaya Aura™

Communication Manager System Capacities Table, 03-300511.

Personal CO Line GroupThe description of the Security Code field on the Personal CO Line Group screen ismodified.

Security Code

The station security code that users must dial to retrieve voice messages and to use theDemand Print Message feature. Accepts from three to eight digits.



QSIG to DCS TSC GatewayThe following note is added to the description of the Subscriber Number field on the QSIGto DCS TSC Gateway screen.

Subscriber Number

Note:If the Subscriber Number is local, the form does not send any DCS messages over the listedSig Grp/TSC Index. Therefore, you can put a block entry like '2xxx' with the understandingthat if extension 2001 is local, no DCS message will be sent.

StationThe description of the Security Code field on the Station screen is modified.

Security Code

The security code required by users for specific system features and functions are as follows:

• Extended User Administration of Redirected Calls

• Personal Station Access

• Redirection of Calls Coverage Off-Net

• Leave Word Calling

• Extended Call Forwarding

• Station Lock

• Voice Message Retrieval

• Terminal Self-Administration

• Enterprise Mobility User

• Extension to Cellular

• Call Forwarding

• Posted Messages

• Security Violation Notification

• Demand Printing

The required security code length is administered system wide.

Screen Reference


System parameters customer optionsThe following description of the Usage Allocation Enhancements field on the Systemparameters customer options screen is added.

Usage Allocation Enhancements

Enables the user to use user-defined entries for the incoming and outgoing ISDN callsindependent of the NSF value. The Usage Allocation Enhancements feature lets the useradminister the non-unique Facility Type and Facility Coding combinations. It also enables thecustomer to reserve a minimum number of trunk members for the incoming and outgoing callsat all times.

Note:The Usage Allocation Enhancements feature is helpful outside the US, where the defaultNetwork Facilities available in the system are not very useful.

System Parameters Port NetworksThe following field is renamed on the System Parameters Port Networks screen.

IPSI Connection Up Time

The IPSI Connection Up Time field is renamed as IPSI Connection Up Time (min) on theSystem Parameters Port Networks screen.

Terminating Extension GroupThe description of the Security Code field on the Terminating Extension Group screen ismodified.

Security Code




Trunk Group: Protocol VariationsThe Identity for Calling Party Display field is added on the Trunk Group: Protocol Variationsscreen.

Identity for Calling Party Display

This field appears when the Group Type field is sip.

This field determines which header to retrieve display information for the calling party whenboth the From and P-Asserted-Identity headers are available.

Valid Entry Usage

P-Asserted-Identity

If a call is terminating at SIP, H.323, or DCP stations, or at outgoing H.323or SIP trunk, Communication Manager displays the name and CallingParty number from the PAI header instead of the FROM header. This isthe default value.

From If a call is terminating at SIP, H.323, or DCP stations, or at outgoing H.323or SIP trunk, Communication Manager displays the name and CallingParty number from the FROM header instead of the PAI header.

Uniform Dial Plan TableThe description of the Percent Full field on the Uniform Dial Plan Table screen is modified asfollows:

Percent Full

Displays the percentage (0 to 100) of the memory resources allocated for the uniform dial plandata that are currently being used. For details on the system memory resources, see AvayaAura™ Communication Manager System Capacities Table, 03-300511.

Usage Allocation EnhancementsEnables the user to use user-defined entries for the incoming and outgoing ISDN callsindependent of the NSF value. The Usage Allocation Enhancements feature lets the useradminister the non-unique Facility Type and Facility Coding combinations. It also enables thecustomer to reserve a minimum number of trunk members for the incoming and outgoing callsat all times.

Screen Reference


Note:The Usage Allocation Enhancements feature is helpful outside the US, where the defaultNetwork Facilities available in the system are not very useful.

Vector Directory NumberThe description of the After Xfer or Held Call Drops field on the Vector Directory Numberscreen is added.

After Xfer or Held Call Drops

Use this field to put an auto-in agent into the Timed ACW mode when an ACD or DAC call onhold drops or the call is transferred and the Timed ACW feature is active. This replaces theAvailable mode.

Valid Entry Usage

y Communication Manager places an agent in the Timed ACW state if acaller on hold disconnects or the call is transferred, in addition to theexisting conditions for Timed ACW.

n Communication Manager continues with the existing operation. This isthe default value.

UpgradesThe following changes apply to the Upgrading to Avaya Aura® Communication ManagerRelease 6.0.1, 03-603560.





Index

A

A175 Desktop Video Device .......................................81AAR and ARS Digit Analysis Table ...........................102add media-gateway ....................................................24Add Signaling Group field descriptions .................38, 49Add Signaling Group field descriptions for IPv6 .........62Add Trunk Group Page 1 field descriptions

Communication Manager Messaging Federal .....50Add Trunk Group Page 1 field descriptions for IPv6 . .63Add Trunk Group Page 2 field descriptions ..........51, 64Add Trunk Group Page 3 field descriptions ..........51, 65Add Trunk Group Page 4 field descriptions ..........52, 65Adding a coverage path for messaging ...........43, 56, 70Adding a signaling group for direct SIP integration ....38Adding a signaling group for direct SIP integration for

Communication Manager Messaging Federal 48Adding a signaling group for messaging ....................61Adding a station ..............................................44, 57, 71Adding a trunk group ..................................................63Adding IP address in IPv6 format of Communication

Manager ........................................................66Adding node names for SIP integration ................37, 48Adding node names IP ...............................................59adding subscribers CMM; field description

CMM field descriptionediting subscribers CMM field description .....76viewing subscribers CMM; field description . .76

Adding trunk group for direct SIP integration ........39, 50Administering the Switch Link for direct SIP integration

............................................................45, 57, 71Administrator guide changes ......................................94After Xfer or Held Call Drops ....................................114Agent LoginID ...........................................................104Alarms ........................................................................99Assigning an Analog Trunk Port .................................17Assigning members from more than one signaling group

to one SIP trunk group ..................................21Assigning synchronization reference ..........................14Attendant Console ....................................................104Avaya 1000 Series

Video Conferencing endpoint ...............................82Avaya Branch Gateways changes .............................31

C

Call Admission Control ...............................................34

Call forward override ..................................................96Call Park ...............................................................17, 97

parking call using TAC .........................................17Change Route-Pattern field descriptions ........42, 54, 68change synchronization ..............................................25Changing a route pattern ................................41, 54, 68Changing AAR analysis ..................................44, 56, 70Changing IP network region .................................42, 55Changing private numbering ...........................41, 53, 67Changing the IP Codec Set .............................43, 55, 69Changing the IP Network Region ...............................69Clock Synchronization over IP ........................11, 12, 15

administration .......................................................12detailed description ..............................................11interactions ...........................................................15screens ................................................................12

Communication Manager changes .............................11Communication Manager Messaging R6.0.1 Embedded

direct SIP integration to CommunicationManager R6.0.1 .............................................37

Condition code ...........................................................96Considerations

Administrable Language Displays ........................97CPN Len ...................................................................108CPN Prefix ................................................................108Creating a hunt group for messaging ..............40, 52, 66

D

Defining IP interfaces for Processor Ethernet ............60Delete .......................................................................108Deluxe paging

branch gateways ..................................................16Deluxe paging for analog trunks .................................16disable synchronization ..............................................26disable synchronization-switch ..................100, 102, 114Disabling synchronization ...........................................15Display between Locations with these Display

Parameters ....................................................21display synchronization ..............................................25documentation and procedure updates ......................93download RDTT .........................................................93downloading

Reliable Data Transport Tool ...............................93Drop Parking User From the Call After Timeout .......105


E

enable synchronization ...............................................26enable synchronization-switch ...................100, 102, 114Enabling IPv6 format on the gateway .........................65endpoint

Avaya 1010 Video Conferencing .........................82Avaya 1020 Video Conferencing .........................82Avaya 1030 Video Conferencing .........................83Avaya 1040 Video Conferencing .........................83Avaya 1050 Video Conferencing .........................83

Enhanced Redirection Notification .............................97

F

Feature Description and Implementation changes .....96Feature-related system parameters ...........................16Feature-Related System Parameters .......................105filtering subscribers

using filters; subscribers ......................................76

H

Hardware ....................................................................81Hunt Group ...............................................................106

I

Identity for Calling Party Display ...............................113Incoming Call Handling Treatment ...........................107Insert .........................................................................109interactions, see interactions under individual feature

names ............................................................98interactions, see interactions under individual feature

names\ ...........................................................15introduction ...........................................................84, 88IP interfaces field descriptions ....................................60IP Network Region ..............................................15, 107IP Signaling Group Far-End Status Test ...................100IP Synchronization .....................................................23IP-SYNC .....................................................................23IPSI Connection Up Time .........................................112IPv6 ............................................................................31IPv6 overview for Communication Manager Messaging

.......................................................................59ISDN Numbering Calling Party .................................107

L

legal notice ...................................................................2

list ars route-chosen .................................................102list synchronization .....................................................25listing all administered gateways ................................13Location ....................................................................109

M

mailbox administrationsubscriber management ......................................73

Maintenance CommandsMedia Gateways and Servers ............................101

Media Path Status Test (#1374) ...............................100Multiple signaling groups in one SIP trunk group . 19, 20

Detailed description .............................................19screens ................................................................20

Multiple signaling groups in one SIP trunk groupadministration ................................................19

N

Number display - Short Number Display on Inter LocationCalls ..............................................................21

Numbering-Private Format screen ............................110Numbering-Public/Unknown Format screen .............110

O

Overview of Emergency Calling .................................33

P

Passive Signalling Station ..........................................18PE Interface acceptance test .....................................94PE Interface configuration ..........................................94Percent Full ................................................104, 110, 113Personal CO Line Group ..........................................110pingall

command ...........................................................102Port

Station ..................................................................18provisioning Session Manager and Communication

Manager CAC together .................................35

R

RDTT download .........................................................93Restarting the messaging application .............46, 59, 73Restrict Calls ............................................................106


S

Saving translations ..........................................45, 57, 71Screen Reference changes ......................................104screens, see screens under individual feature names 12Security Code .....................................104, 106, 110–112

Attendant Console ..............................................104see also considerations under individual feature names

..................................................................15, 98server

baseline specifications, configuration, and options . .86, 90

environmental specifications ..........................87, 91front view ........................................................84, 89physical specifications ....................................87, 92rear view .........................................................85, 89

Session Manager .......................................................33Setting feature access codes for messaging ..............47Setting up IP synchronization ...............................13, 14Setting up Passive Signaling Station ..........................17Setting up the BRI trunk board ...................................14Setting up the signaling groups ..................................20signaling group .....................................................38, 48SIP-SGRP (SIP Signaling Group)

Error Type 258 ...................................................101Special applications

features ................................................................29Station .......................................................................111Station Security Code

interactions ...........................................................98status ip-synchronization ............................................27subscriber list .............................................................75subscriber; view

viewing subscribers ..............................................74subscribers; add

adding subscribers ...............................................73subscribers; new ..................................................73

subscribers; deletedeleting subscribers

removing subscribers ....................................75

subscribers; editediting a subscriber ..............................................74editing subscribers ...............................................74

Suppress alarming .....................................................95switch link

administer .................................................45, 57, 71Sync ...........................................................................16synchronization .........................................................114Synchronization over IP .............................................16System parameters customer options

Usage Allocation Enhancements .......................112System Parameters Port Networks ...........................112system requirements for EMU ....................................98

T

Terminating Extension Group ...................................112Trunk Group

Protocol Variations .............................................113trunk group for direct SIP integration ....................39, 50Trunk Side XOIP Modem Support ..............................22

U

UDP-ARS Calls Considered Offnet ..........................105Upgrade paths ......................................................29, 79Usage Allocation Enhancements .......................112, 113Use for IP Sync ..........................................................24

V

Vector Directory Number ..........................................114

W

WAN-BW limits (Total) ..............................................107

X

XOIP Treatment ..........................................................22

Z

Zip Tone Burst For Call master Endpoints ................106


avaya aura communication manager change description release 6.0.1

Documents