Avaya Aura Communication Manager Change Description Release 6.0.1

Avaya Aura Communication Manager Change Description for Release 6.0.
Release 6.0.1 03-603723 Issue 1 November 2010
2011 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Documentation means information published by Avaya in varying mediums which may include product information, operating instructions and performance specifications that Avaya generally makes available to users of its products. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of documentation unless such modifications, additions, or deletions were performed by Avaya. End User agrees to indemnify and hold harmless Avaya, 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 Web sites referenced within this site or documentation provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no 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 of the limited warranty. In addition, Avayas standard warranty language, as well as information regarding support for this Product while under warranty is available to Avaya customers and other parties through the Avaya Support Web site: http://support.avaya.com. Please note that if you acquired the Product(s) from an authorized Avaya reseller outside of the United States and Canada, the warranty is provided to you by said Avaya reseller and not by Avaya. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYAAFFILIATE OR AN AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ( AVAYA). Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a
different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. Designated Processor means a single stand-alone computing device. Server means a Designated Processor that hosts a software application to be accessed by multiple users. Software means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone Products or pre-installed on Hardware. Hardware means the standard hardware originally sold by Avaya and ultimately utilized by End User. License types Designated System(s) License (DS). End User may install and use each copy of the Software on only one Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. Avaya may require the Designated Processor(s) to be identified by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A Unit means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Software 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 the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a Server so long as only authorized Named Users access and use the Software. Named User, means a user or device that has been expressly authorized by Avaya to access 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 or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Shrinkwrap License (SR). Customer may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as shrinkwrap or clickthrough license accompanying or applicable to the Software (Shrinkwrap License). (see Third-party Components for more information). Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, or Hardware provided by Avaya. All content on this site, the documentation and the Product provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software unless expressly authorized by Avaya. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law. Third-party components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements (Third Party Components), which may contain terms that expand or limit rights to use certain portions of the Product (Third Party Terms). Information regarding distributed Linux OS source code (for those
Avaya Aura Communication Manager Change Description for Release 6.0.1
November 2010
Products that have distributed the Linux OS source code), and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: http://support.avaya.com/Copyright. Preventing Toll Fraud Toll fraud is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of Toll Fraud associated with your system and that, if Toll Fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya Toll Fraud Intervention If you suspect that you are being victimized by Toll Fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support Web site: http://support.avaya.com. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: securityalerts@avaya.com. Trademarks Avaya and Avaya Aura are trademarks of Avaya Inc. The trademarks, logos and service marks (Marks) displayed in this site, the documentation(s) and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent 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 written permission 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. and other countries. Downloading Documentation For the most current versions of Documentation, see the Avaya Support Web site: http://support.avaya.com. Contact Avaya Support Avaya provides a telephone number for you to use to report problems or to ask questions about your Product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site: http://support.avaya.com.
November 2010
November 2010
Contents Chapter 1: Introduction.............................................................................................................9 Chapter 2: Communication Manager changes.....................................................................11

Clock Synchronization over IP.........................................................................................................................11 Detailed description of Clock Synchronization over IP...........................................................................11 Clock Synchronization over IP administration........................................................................................12 Interactions for Clock Synchronization over IP.......................................................................................15 IP Network Region..................................................................................................................................15 Feature-related system parameters.......................................................................................................16 Deluxe paging support for branch gateways...................................................................................................16 Deluxe paging for analog trunks.............................................................................................................16 Setting up Passive Signaling Station for deluxe paging.........................................................................17 Assigning an Analog Trunk Port.............................................................................................................17 End-user procedure for Call Park...........................................................................................................17 Station....................................................................................................................................................18 Loudspeaker Paging...............................................................................................................................18 Multiple signaling groups in one SIP trunk group............................................................................................19 Detailed description of multiple signaling groups in one SIP trunk group...............................................19 Multiple signaling groups in one SIP trunk group administration............................................................19 Number Display - Short Number Display on Inter Location Calls...................................................................21 Display between Locations with these Display Parameters...................................................................21 Trunk Side XOIP Modem Support...................................................................................................................22 XOIP Treatment......................................................................................................................................22 Maintenance objects.......................................................................................................................................23 IP-SYNC.................................................................................................................................................23 MG-SYNC...............................................................................................................................................23 Maintenance SAT Commands.........................................................................................................................24 add media-gateway................................................................................................................................24 change synchronization..........................................................................................................................25 display synchronization..........................................................................................................................25 list synchronization.................................................................................................................................25 disable synchronization..........................................................................................................................26 enable synchronization...........................................................................................................................26 status ip-synchronization........................................................................................................................27 Installations.....................................................................................................................................................28 Install Communication Manager on the Dell and HP servers.................................................................28 Install System Platform Service Pack 2 on the Dell and HP servers......................................................29 Upgrades.........................................................................................................................................................29 Upgrade paths........................................................................................................................................29 Special applications........................................................................................................................................29
Chapter 3: Avaya Branch Gateways changes.......................................................................31

IPv6.................................................................................................................................................................31
Chapter 4: Communication Manager Session Manager interoperability...........................33

Session Manager............................................................................................................................................33 Desk-level SIP E911 location reporting...........................................................................................................33 Overview.................................................................................................................................................33 Configuring Communication Manager for ELIN Server support.............................................................34
November 2010
Call Admission Control....................................................................................................................................34 Provisioning Session Manager and Communication Manager CAC together........................................35
Chapter 5: Communication Manager Messaging changes..................................................37

Direct SIP integration between Communication Manager Messaging and Communication Manager............37 Overview.................................................................................................................................................37 Adding node names for SIP integration..................................................................................................37 Adding a signaling group for direct SIP integration................................................................................38 Adding a trunk group for direct SIP integration.......................................................................................39 Creating a hunt group for messaging.....................................................................................................40 Changing private numbering..................................................................................................................41 Changing a route pattern........................................................................................................................41 Changing IP network region...................................................................................................................42 Changing the IP Codec Set....................................................................................................................43 Adding a coverage path for messaging..................................................................................................43 Changing AAR analysis..........................................................................................................................44 Adding a station......................................................................................................................................44 Saving translations.................................................................................................................................45 Administering the Switch Link.................................................................................................................45 Restarting the messaging application.....................................................................................................46 Direct SIP integration between Communication Manager Messaging Federal and Communication Manager ........................................................................................................................................................................47 Setting feature access codes for messaging..........................................................................................47 Adding node names for SIP integration..................................................................................................48 Creating a signaling group......................................................................................................................48 Creating a trunk group............................................................................................................................50 Creating a hunt group for messaging.....................................................................................................52 Changing private numbering..................................................................................................................53 Changing a route pattern........................................................................................................................54 Changing IP network region...................................................................................................................55 Changing the IP Codec Set....................................................................................................................55 Adding a coverage path for messaging..................................................................................................56 Changing AAR analysis..........................................................................................................................56 Adding a station......................................................................................................................................57 Saving translations.................................................................................................................................57 Administering the Switch Link.................................................................................................................57 Restarting the messaging application.....................................................................................................59 IPv6 implementation for Communication Manager Messaging.......................................................................59 Overview.................................................................................................................................................59 Adding node names IP...........................................................................................................................59 Defining IP interfaces for Processor Ethernet........................................................................................60 Creating a signaling group......................................................................................................................61 Creating a trunk group............................................................................................................................63 Administering gateway...........................................................................................................................65 Creating a hunt group for messaging.....................................................................................................66 Changing private numbering..................................................................................................................67 Changing a route pattern........................................................................................................................68 Changing the IP Network Region...........................................................................................................69 Changing the IP Codec Set....................................................................................................................69 Adding a coverage path for messaging..................................................................................................70 Changing AAR analysis..........................................................................................................................70 Adding a station......................................................................................................................................71
November 2010
Saving translations.................................................................................................................................71 Administering the Switch Link.................................................................................................................71 Restarting the messaging application.....................................................................................................73 Subscribers.....................................................................................................................................................73 Subscriber Management........................................................................................................................73 Adding a subscriber................................................................................................................................73 Editing a subscriber................................................................................................................................74 Viewing a subscriber..............................................................................................................................74 Deleting a subscriber..............................................................................................................................75 Subscriber List........................................................................................................................................75 Filtering subscribers...............................................................................................................................76 Subscribers (CMM) field descriptions.....................................................................................................76 Upgrades.........................................................................................................................................................79 Upgrade paths........................................................................................................................................79
Chapter 6: Hardware...............................................................................................................81
Avaya A175 Desktop Video Device.................................................................................................................81 Avaya 1000 Series Video Conferencing endpoint...........................................................................................82 Avaya 1010 Video Conferencing endpoint.............................................................................................82 Avaya 1020 Video Conferencing endpoint.............................................................................................82 Avaya 1030 Video Conferencing endpoint.............................................................................................83 Avaya 1040 Video Conferencing endpoint.............................................................................................83 Avaya 1050 Video Conferencing endpoint.............................................................................................83 HP ProLiant DL360 G7 1U server overview....................................................................................................84 Introduction.............................................................................................................................................84 Front of server........................................................................................................................................84 Back of server.........................................................................................................................................85 Server specifications..............................................................................................................................86 Environmental specifications..................................................................................................................87 Physical specifications............................................................................................................................87 References.............................................................................................................................................88 Dell PowerEdge R610 1U server overview..............................................................................................88 Introduction.............................................................................................................................................88 Front of server........................................................................................................................................88 Back of server.........................................................................................................................................89 Server specifications..............................................................................................................................90 Environmental specifications..................................................................................................................91 Physical specifications............................................................................................................................92 References.............................................................................................................................................92
Chapter 7: Documentation and procedure updates.............................................................93

Adding New Hardware for Avaya Servers and Gateways...............................................................................93 Downloading Reliable Data Transport Tool............................................................................................93 Administrator guide.........................................................................................................................................94 PE Interface configuration......................................................................................................................94 Administering Network Connectivity................................................................................................................95 Reviewing the network region administration.........................................................................................95 Conversion of servers and gateways..............................................................................................................95 Suppress alarming..................................................................................................................................96 Feature Description and Implementation........................................................................................................96 Call detail record field descriptions.........................................................................................................96 Call forward override..............................................................................................................................96
November 2010
Call Park.................................................................................................................................................97 Considerations for Administrable Language Displays............................................................................97 Enhanced Redirection Notification.........................................................................................................97 Interactions for Station Security Code....................................................................................................98 System requirements for EMU...............................................................................................................98 Installing and Upgrading the Avaya G450 Gateway.......................................................................................99 Installing and Upgrading the Avaya S8300 Server.........................................................................................99 Maintenance Alarms.......................................................................................................................................99 CONFIG (System Configuration)............................................................................................................99 disable synchronization-switch.............................................................................................................100 enable synchronization-switch..............................................................................................................100 IP Signaling Group Far-End Status Test (#1675).................................................................................100 Media Path Status Test (#1374)...........................................................................................................100 SIP-SGRP (SIP Signaling Group)........................................................................................................101 Maintenance Commands..............................................................................................................................101 AAR and ARS Digit Analysis Table .......................................................................................................102 disable synchronization-switch.............................................................................................................102 enable synchronization-switch..............................................................................................................102 list ars route-chosen.............................................................................................................................102 pingall...................................................................................................................................................102 Reports..........................................................................................................................................................103 AAR or ARS Route Chosen reports.....................................................................................................103 Attendant and Maintenance Status report............................................................................................103 Screen Reference.........................................................................................................................................104 Agent LoginID.......................................................................................................................................104 Attendant Console................................................................................................................................104 Dial Plan Analysis Table.......................................................................................................................104 Dial Plan Parameters............................................................................................................................105 Feature-Related System Parameters...................................................................................................105 Hunt Group...........................................................................................................................................106 Incoming Call Handling Treatment.......................................................................................................107 IP Network Region................................................................................................................................107 ISDN Numbering Calling Party Number Conversion for Tandem Calls................................................107 Location................................................................................................................................................109 Numbering-Public/Unknown Format and Numbering-Private Format..................................................110 Percent Full...........................................................................................................................................110 Personal CO Line Group......................................................................................................................110 QSIG to DCS TSC Gateway.................................................................................................................111 Station...................................................................................................................................................111 System parameters customer options..................................................................................................112 System Parameters Port Networks.......................................................................................................112 Terminating Extension Group...............................................................................................................112 Trunk Group: Protocol Variations..........................................................................................................113 Uniform Dial Plan Table........................................................................................................................113 Usage Allocation Enhancements..........................................................................................................113 Vector Directory Number......................................................................................................................114 Upgrades.......................................................................................................................................................114 disable synchronization-switch.............................................................................................................114 enable synchronization-switch..............................................................................................................114
Index.......................................................................................................................................115
November 2010
Chapter 1: Introduction
The Avaya Aura Communication Manager Change Description document describes the features and changes that were introduced with release 6.0.1 of Avaya Aura Communication Manager, and Communication 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.
November 2010
Introduction
10
November 2010
Chapter 2: Communication Manager changes

This chapter describes the features and enhancements of Release 6.0.1 of Avaya Aura Communication Manager. The enhancements for Call Center 6.0.1 are provided in Avaya Aura Call Center 6.0 Overview, 07-602633.
Clock Synchronization over IP

Where traditional synchronization is not available, you can use the Clock Synchronization over IP (CSoIP) feature on G450 and G430 Branch Gateways to provide system clocking across IP networks.
Detailed description of Clock Synchronization over IP

Communication 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 transmit within an IP infrastructure. You administer Clock Synchronization over IP through the Communication Manager's SAT Administration forms. Instead of DS1 or BRI interface, you can use a local clock as the clocking source. You can choose a primary and any other backup sources. The Communication Manager maintenance object and connection manager create and maintain the synchronization domains, also known as sync domains. A sync domain is a clock source that emanates IGC streams to clock receivers. All gateways involved with the CSoIP feature are referred to as members. A master domain is a clock source derived from a DS1 or BRI, which is used to emanate IGC streams to clock receivers. Other members that use the incoming IGC stream for internal clocking are known as slave clocks. The receiver is one hop level below the clock source. A secondary clock domain uses the incoming IGC stream, which is 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 the maximum 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.
November 2010
11
Communication Manager changes
When the first IGC source comes into service, it becomes the default system clock source. All other IGC sources become slaves until the fan-out limit is reached. After the fan-out limit is reached, 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 takes place 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 if there is an IGC source board already providing IGC streams. The highest level clock source that was the default system clock source is demoted and becomes a receiver of a master clock source and becomes a tandem clock. There can be as many master clock domains as there are administered sync sources. The CSoIP feature does not attempt to mitigate the reference board outages. If such a board goes out of service, the traditional sync feature raises an alarm and you need to rectify the problem. Removing or adding any reference board from translations causes the CSoIP feature to 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 the PSTN, and each can be used by the CSoIP feature to provide sync to a group of members.
Clock Synchronization over IP administration

The 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 Feature-Related System Parameters Purpose Fields
Set up the Clock Synchronization over IP Synchronization over IP feature.
12
November 2010
Screen name Media Gateway
Purpose Set up IP synchronization on the gateway. Use for IP Sync
Fields
IP Network Region Set up IP synchronization on the network region.
Sync
IP Synchronization Assign synchronization Primary Source Media reference to the primary Secondary Gateway and secondary gateway. DS1 Set up the DS1 board as a Synch Source. For information on fields, see the Configuring a DS1 circuit pack example section of Administering Avaya Aura Communication Manager, 03-300509. Synch Source
ISDN-BRI Trunk Circuit Pack
Set up the BRI trunk board as a Synch Source.
Clock Synchronization over IP administration

Listing all administered gateways
Enter list synchronization media-gateway to display the list of administered gateways. 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.
November 2010
13
Setting up IP synchronization for the gateway
1. Enter change media-gateway n, where n is the number of the gateway in which you want to enable IP synchronization. 2. Set the Use for IP Sync field to y. 3. Select Enter to save your changes. Assigning synchronization reference for the gateway
1. Enter change synchronization media-gateway n, where n is the number of the gateway that requires synchronization. 2. In the Primary field, enter a synchronization-source slot address location. Obtain this location from the Circuit Packs Available for Synchronization list. Ensure that you choose a working synchronization source. 3. (Optional) Add another synchronization-source circuit pack location in the Secondary field. Obtain the location from the Circuit Packs Available for Synchronization lost. 4. Select Enter to save your changes. 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 up as 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 Administering Avaya Aura Communication Manager, 03-300509. 3. Select Enter to save your changes. 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 that you want to set up as a sync source. 2. Set the Synch Source field to y. 3. Select Enter to save your changes.
14
November 2010
Setting up IP synchronization for the network region 1. Enter change ip-network-region n, where n is the network region number in which you want to enable IP synchronization. 2. Click Next until you see the Inter Network Region Connection Management fields. 3. Set the Sync to y. 4. Select Enter to save your changes. Disabling synchronization
Enter disable synchronization media-gateway n, where n is the number of the gateway. The command prevents switching between clock sources.
Interactions for Clock Synchronization over IP

This section provides information about how the Clock Synchronization over IP (CSoIP) feature interacts with other features on the system. Use this information to ensure that you receive the maximum benefits of CSoIP in any feature configuration.
Survivable remote and survivable core servers

If a survivable remote and survivable core servers control the gateways with the primary and secondary synchronization source, the elements under the control of that survivable server have clock synchronization. If the primary and secondary synchronization source is not controlled by the survivable server in a failover fragment: The segment performs as if it had no primary or secondary source for clock synchronization. Any gateways with a DS1 or BRI interface in service takes its clock source from that DS1 or BRI interface.
IP Network Region
Reference Avaya Aura Communication Manager Screen Reference, 03-602878, 6.0 version, a new field is added on the IP Network Region screen.
November 2010
15
Sync
Appears when the Synchronization over IP field is enabled.
Valid Entry y n Usage Timing IGC streams are allowed between the region pair that is being administered. The default value is y. Do not allow timing IGC streams between the region pair that is being administered.
Feature-related system parameters

Reference 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 to a group of members.
Valid entries y n Usage Enables the CSoIP feature. Disables the CSoIP feature. This is the default value.
Deluxe paging support for branch gateways

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

To use the deluxe paging feature with analog trunks, the analog trunk port must be connected to 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. Stations administered as passive signaling stations act as line-end terminations for analog loop start trunk ports.
16
November 2010
Deluxe paging support for branch gateways
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 circuit pack. 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.
November 2010
17
Station
Reference Avaya Aura Communication Manager Screen Reference, 03-602878, Release 6.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 field is available only when you select an analog trunk port as the station type.
Valid Entry y n Usage The analog station port does not process calls when off hook. The analog station port processes and receives calls as an analog station. This is the default value.
Loudspeaker Paging
Reference Avaya Aura Communication Manager Screen Reference, 03-602878, Release 6.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 01 to 64 A to E 01 to 20 01 to 32 x or X Usage The first and second numbers are the cabinet numbers. The third character is the carrier. The fourth and fifth characters are the slot numbers. G650 has 14 slots. The sixth and seventh characters are the port numbers. Indicates that there is no hardware associated with the port assignment since the switch was set up, and the administrator expects that the extension has a non-IP set. Or, the extension had a non-IP set, and it dissociated. Use x for Administered WithOut Hardware (AWOH) and Computer Telephony (CTI) stations, as well as for SBS Extensions. Indicates that there is no hardware associated with the port assignment since the switch was set up, and the administrator expects that the extension would have an IP set. This is automatically entered for certain
IP
18
November 2010
Multiple signaling groups in one SIP trunk group
Valid Entry
Usage IP station set types, but you can enter for a DCP set with softphone permissions. 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 Trunk port
Analog trunk port is available with: MM711 and MM714 media modules TN747 and TN797 circuit packs
Multiple signaling groups in one SIP trunk group

By assigning members from multiple SIP signaling groups to one SIP trunk group, you can directly connect a SIP-integrated Avaya Aura Messaging system with multiple Messaging Application 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 trunk group

To assign members from more than one signaling group to one SIP trunk group, you must first set up the signaling groups. After setting up the signaling groups you must assign members from more than one signaling group to one SIP trunk group. You can have one signaling group per MAS. For example, if you have three MASs within the Messaging system, you must configure three signaling groups, one for each MAS. A single SIP trunk group can then be created with members from the three signaling groups.
Multiple signaling groups in one SIP trunk group administration

The following tasks are part of the administration process for assigning members from more than 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
November 2010
19
Screens for administering multiple signaling groups in one SIP trunk group
Screen name Signaling Group Purpose Set up the signaling group. Fields Group Type IMS Enabled Peer Detection Enabled Peer Server Trunk Group Assign members from one or more signaling groups to one SIP trunk group. Member Assignment Method 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 all signaling 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 group outage and enables trunk group member selection to bypass out-of-service signaling groups. 8. Select Enter to save your changes.
20
November 2010
Number Display - Short Number Display on Inter Location Calls
Assigning members from more than one signaling group to one SIP trunk group
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 subsequent members 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, and so on for the subsequent members of the trunk group. This ensures that load balancing occurs amongst the different signaling groups. 5. Select Enter to save your changes.
Number Display - Short Number Display on Inter Location Calls

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

This field appears when you enable the Multiple Locations field. This field cannot be left blank.
Valid Entry inter-location Usage Communication Manager uses the inter-location display format for calls between designated locations. This is the default value.
November 2010
21
Valid Entry intra-location
Usage Communication Manager uses the intra-location display format for calls within a location. You can use the intra-location format within a branch to display short extensions within that location. This Display Parameter lets you display short extensions between two or more closely associated locations. For example, if you assign display parameter 3 to locations 7 and 17, and set the field to intra-location, Communication Manager uses intra-location format for calls between locations 7 and 17, however uses inter-location calls from 7 to any other location other than 17, and for calls from 17 to any other location other than 7.
Trunk Side XOIP Modem Support

The XOIP Treatment field is added on the Trunk Group screen to use the Trunk Side XOIP Modem Support feature.
XOIP Treatment
Valid Entry auto modem fax tty Usage Identifies treatment of an incoming trunk call. When set to modem, fax, or tty, the serving digital signal processor algorithms is placed in immediate pass-through mode. Use this field when the incoming trunk is transporting the XOIP traffic. By identifying this external equipment through administration, VoIP firmware uses this field to determine if it is necessary to immediately attempt to put a call in pass-through mode so that the DSPs will not miss identification of the initial tone events. Default is 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.
22
November 2010
Maintenance objects
Maintenance objects
IP-SYNC
MO Name in Log IP-SYNC Alarm Level None Initial Command to Run None Full Name of MO IP Synchronization
The IP-SYNC handles the creation and maintenance of the sync domains. This maintenance object runs as a single instance maintenance object when the various IP sync operations are being executed. The IP-SYNC object indicates that gateways are coming in and out of service.
Demand tests descriptions and error codes

There are no demand tests for IP-SYNC.
MG-SYNC
MO Name in Log Alarm Level Initial Command to Full Name of MO Run MG-SYNC None None Branch gateway capable of IP synchronization
The MG-SYNC handles the clock-related messaging to the branch gateways and interfaces with IP Synchronization (IP-SYNC). A branch gateway that is part of a Communication Manager system can use one of three synchronization references: DS1, BRI, and VOIP. These resources derive synchronization reference from a received IGC stream. The MG-SYNC maintenance object implements control of the gateway clock synchronization and synchronization references. The MG-SYNC object configures MG clocks, monitor clock synchronization status, log errors and raise alarms, and reports changes to IP-SYNC distribution for the system.
November 2010
23
Error log entries and recommended actions

Error Type 18 513 (3) Aux Data Associated Test Disable sync Alarm Level WRN MIN On/Off Board OFF OFF Recommended Action
enable synchronizationswitch
None. When the gateway is a master clock member, see DS1 or BRI troubleshooting section of Maintenance Procedures for Avaya Aura Communication Manager, Media Gateways and Servers , 03-300432.
Note: Error Type 18: The Clock Synchronization over IP feature is disabled. The recommended action is to run the enable synchronization-switch command.
Demand tests descriptions and error codes

There are no demand tests for MG-SYNC.
Maintenance SAT Commands

add media-gateway
Reference Maintenance Commands for Avaya Aura Communication Manager, Media Gateways and Servers, 03-300431, 6.0 version, a new field is added to the Media Gateway screen. The field description is as follows:
add media-gateway field descriptions

Field Use for IP Sync Description Appears when the Synchronization over IP field is enabled. Indicates whether or not the G430 and G450 branch gateways are exempted from IP sync. By default, this field is enabled.
24
November 2010
change synchronization
Reference Maintenance Commands for Avaya Aura Communication Manager, Media Gateways and Servers, 03-300431, 6.0 version, a new qualifier is added to the change synchronization command. The description of the qualifier is as follows:
Action/Object change synchronization Qualifier mediagateway n Qualifier Description change the gateway number Login init, inads, craft, cust, rcust, bcms Feature Interaction DS1 interface or BRI trunk is selected as either a primary or secondary sync source cannot be removed from the DS1 circuit pack administration screen or the regular circuit pack administration screen.
display synchronization
Reference Maintenance Commands for Avaya Aura Communication Manager, Media Gateways and Servers, 03-300431, 6.0 version, a new qualifier is added to the display synchronization command. The description of the qualifier is as follows:
Action/Object display synchronization Qualifier mediagateway n Qualifier Description display the gateway number Login init, inads, craft, cust, rcust, bcms Feature Interaction No default. A DS1 interface is selected as a primary or secondary synchronization source cannot be removed from the DS1 circuit pack administration screen or the regular circuit pack administration screen.
list synchronization
Reference Maintenance Commands for Avaya Aura Communication Manager, Media Gateways and Servers, 03-300431, 6.0 version, media-gateway and port-network qualifiers are added to the list synchronization command.
November 2010
25
Use list synchronization media-gateway to see all administered gateway reference boards and the existing reference sources. Use list synchronization port-network to see all administered port network reference boards and the existing reference sources.
Action/Object list synchronization Qualifier mediagateway portnetwork Qualifier Description list the gateway reference boards list the port network reference boards Login init, inads, craft, cust, rcust, bcms Feature Interaction No default. A DS1 interface is selected as a primary or secondary synchronization source cannot be removed from the DS1 circuit pack administration screen or the regular circuit pack administration screen.
disable synchronization
Reference Maintenance Commands for Avaya Aura Communication Manager, Media Gateways and Servers, 03-300431, 6.0 version, a new qualifier is added to the disable synchronization command. The description of the qualifier is as follows:
Action/Object disable synchronization Qualifier media-gateway n Qualifier Description Login disable the gateway number init, inads, craft Default
enable synchronization
Reference Maintenance Commands for Avaya Aura Communication Manager, Media Gateways and Servers, 03-300431, 6.0 version, a new qualifier is added to the enable synchronization command. The description of the qualifier is as follows:
Action/Object enable synchronization Qualifier media-gateway n Qualifier Description Login enable the gateway number init, inads, craft Default
26
November 2010
status ip-synchronization
status ip-synchronization [master | member media-gateway n | oosmembers | source media-gateway n | system-information] Use status ip-synchronization to see the information about the status of the various gateways that are part of IP synchronization.
Action/ Object Qualifier Qualifier Description Login Feature Interactio n
status ipmaster, synchroniza member mediation gateway n, oos-members, source mediagateway n, systeminformation
status of the master sync sources in the system. status of the timing source for a given gateway. status of the members who are not synchronized and their service states. status of the gateways whose sync is sourced by the given gateway. status of the global status of the sync over IP feature.
init, inads, craft, cust, rcust, bcms
status ip-synchronization field descriptions

Field Member Ref Stat DSP Status Input Inp Jit Bad Ord Dup Loss% Description Displays all master sources of the system. Displays the health of the reference board, whether the member is in service and setup to source IGC streams. Displays the status of the DSP. Provides information about the incoming IGC stream. R: Receiving stream, N: No stream detected, D: Stream detected. Jitter detected. Bad packets detected. Out of order packets detected. Duplicated packets detected. Percentage loss of incoming stream.
November 2010
27
Field Output Lock
Description 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 Role Fail Reason Master Domain Count Total Domain Count Member Count Max Level Out of Sync Building domains
Displays whether the clock is synchronized to the synch lead of the PN and MG. Displays the role of the member. Displays why the member is out of synch with other members. Number of master IP sync domain count. Number of overall IP sync system count. Number of gateways in sync domains. Highest hop count by any member. Number of members not in sync. Indicates whether the new sync domains are created after the feature flag is turned on. When the field is set to n, the process is finished. Indicates if the feature is removing the IGC streams and sync domains when the feature is turned off.
Removing Domains
Installations
Install Communication Manager on the Dell and HP servers
For Release 6.0.1, Communication Manager can be installed on the HP ProLiant DL360 G7 and Dell PowerEdge R610 servers. Within Installing and Configuring Avaya Aura Communication Manager, 03-603558, all references to the Avaya S8800 Server apply to these two servers also.
28
November 2010
Upgrades
Install System Platform Service Pack 2 on the Dell and HP servers

For Release 6.0.1, when installing System Platform, ensure that you download and install the Service Pack 2 version. This Service Pack allows System Platform and the Communication Manager templates to be installed on the HP ProLiant DL360 G7 and Dell PowerEdge R610 servers.
Upgrades
Upgrade paths
The 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 Release 6.0.1, 03-603560.
Special applications
Special applications, also known as green features, meet special requirements requested by one or more customer. Customers may activate the special applications by themselves using their own super-user login. Although these special features are available to customers, they may have not gone through extensive testing. So customers must use these features at their own risk. Some of the special features should not be set without the right configurations, and some features should not be set together at the same time. Otherwise, the feature may not operate as expected, the system performance could be affected or both. To avoid users from setting those features accidentally, Communication Manager has identified those features and marked them as restricted. To activate the restricted features, contact Avaya Custom Development team. For a list of unrestricted special features and related information, see Avaya Aura Communication Manager Special Application Features at http://support.avaya.com.
November 2010
29
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
30
November 2010
Chapter 3: Avaya Branch Gateways changes

This chapter summarizes the changes in functionality in Branch Gateways for Communication Manager 6.0.1
IPv6
Internet Protocol version 6 (IPv6) is the successor to IPv4. IPv6 supports 128bit addresses and satisfies the rapidly growing demand for IP addresses. In contrast, IPv4 supported 32bit. IPv6 also improves security, ease of configuration, and routing performance. IPv6 can coexist with IPv4 networks, easing the transition process. The IETF (Internet Engineering Task Force) published RFC 2460, the internet standard specification that defines IPv6, in December 1998.
Addressing
By using 128-bit addresses, IPv6 has about 3.4x1038 unique IP addresses, more than enough for every network device. This eliminates the IPv4 mechanisms, such as NAT (network address transitions), that are used to relieve IP address exhaustion. IPv6 addresses are normally written 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.
Simplicity
IPv6 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. Stateful configuration using DHCPv6 and static configuration are also available.
Deployment and transition

There are several mechanisms that ease the deployment of IPv6 running alongside IPv4. The key to the transition is dual-stack hosts. Dual-stack hosts refers to the presence of two IP software implementations in one operating system, one for IPv4 and one for IPv6. These dual-
November 2010
31
Avaya Branch Gateways changes
stack hosts can run the protocols independently or as a Hybrid. The Hybrid is the common form 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. Tunneling can be either automatic or configured, the latter being more suitable for large, welladministered networks.
Key differences between IPv4 and IPv6

IPv4 Address space Security Configuration 32-bit, about 4.3x109 IPSec support is optional. Requires DHCP or manual configuration. Decimal digits with colon separators, for example: 192.168.1.1 IPv6 128-bit, about 3.4x1038 IPSec support is required. Stateless auto-configuration. Does not require DHCP or manual configuration. Hexadecimal digits with colon separators. For example: 2005:af0c:168d:: 752e:375:4020. The double colon :: represents four zeros 0000 No Broadcast. Various forms of Multicast better network bandwidth efficiency Flow labels and flow classes, more granular approach.
Address format
Broadcast and Multicast support QoS support
Yes
ToS using DIFFServ
Feature Support in Avaya Branch Gateways

Certain 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 Branch Gateway G450
32
November 2010
Chapter 4: Communication Manager Session Manager interoperability
Session Manager
Within an Avaya Aura solution, Session Manager is at the core with one or more installations of Communication Manager. For the Avaya Aura solution to work optimally requires close management of Communication Manager and Session Manager. For whats new for Session Manager in Release 6.1, see Avaya Aura Session Manager Overview, 03-603323.
Desk-level SIP E911 location reporting

Overview
E911 service (such as ELIN Server) enables emergency location lookups for emergency calls and helps in identifying the physical location of the emergency caller (a registered user on Session Manager) in the event of an emergency call. The ELIN is a number which provides specific 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 the emergency call re-establish the emergency call if it gets disconnected for some reason For information on basic concepts, scenario definition, and administration details regarding Emergency Calling, see Avaya Aura Session Manager Case Studies, 03-603478.
November 2010
33
Communication Manager Session Manager interoperability
Configuring Communication Manager for ELIN Server support

Communication Manager should be able to route 911 calls to the PSAP and the required SIP sig groups and trunks needs to be configured for this purpose. 1. For incoming emergency calls to the Communication Manager, if the message signaling has the presence of an ELIN: a. ELIN needs to be mapped to an existing extension via incoming call handling (inc-call-handling-trmt of the SIP trunk group) to get the extension number. b. Each shortened ELIN should be a valid station extension in order to enable callback for the phone making the emergency call. Similar is the case if an unregistered phone makes an emergency call. c. ELIN must be converted back to 10 digits via public-numbering before being sent out to the public network (PSAP). 2. For incoming emergency calls to the Communication Manager, if the message signaling does not have the presence of an ELIN: a. Communication Manager uses the ip-network-region mapping to determine an ELIN based on the users IP address. If it maps the calling user to an ELIN, it uses digit conversion to assign it to some station. After it finds the station, it reapplies the digit conversion to set the ELIN back to 10 digits format before forwarding it to the PSAP. b. In case when the Communication Manager finds no match for the IP address to an ELIN, it includes the actual calling stations extension number as the calling party for the PSAP. Following are some of the essential steps to ensure proper coverage in case of emergency calls: 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 Control

The bandwidth needed for SIP and H.323 audio and video endpoints can be managed within a single logical location. SIP endpoints are managed using Locations administered through
34
November 2010
Call Admission Control
System Manager, and H.323 endpoints are managed using Network Regions administered through Communication Manager. Because Session Manager and Communication Manager are used simultaneously, provisioning them correctly is critical.
Provisioning Session Manager and Communication Manager CAC together

For simultaneous use of Session Manager and Communication Manager CAC, following configurations should be done: 1. Create 1-to-1 mapping of Session Manager Locations to Communication Manager Network Regions, because Communication Manager uses Network Regions for CAC. This is limited by the fact that Communication Manager supports no more than 250 Network Regions, while Session Manager supports thousands of Locations. 2. As Session Manager maps IP addresses to Locations, Communication Manager maps IP addresses to Network Regions. These mappings must be synchronized manually. 3. As part of Communication Manager administration, the SIP trunk to Communication Manager must be placed within a dummy Network Region for which no CAC limits are set. This enables the following changes: Calls terminated to non-SIP destinations (H.323 phones, non-SIP trunks) are counted by Communication Manager CAC for the appropriate Network Regions. All calls terminated to SIP destinations (SIP phones, SIP trunks on Session Manager) are counted by Session Manager CAC for the appropriate Locations. SIP trunks on Communication Manager that do not route to Session Manager (not a recommended configuration) are counted by Communication Manager. Note: Communication Manager performs CAC in terms of bandwidth limits between two specific Network Regions, while Session Manager performs CAC as per limits covering all traffic into or out of a Location, regardless of the far-end location.
November 2010
35
Communication Manager Session Manager interoperability
36
November 2010
Chapter 5: Communication Manager Messaging changes
Direct SIP integration between Communication Manager Messaging and Communication Manager
Overview
Communication Manager Messaging R6.0.1 allows direct SIP integration with Communication Manager R6.0.1. You need to administer Communication Manager screens and Communication Manager Messaging Web pages to implement direct SIP integration between Communication 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 the processor Ethernet. 8. Submit the changes.
November 2010
37
Communication Manager Messaging changes
Adding a signaling group for direct SIP integration

1. On the SAT command prompt, type add signaling-group n, where n is the signaling 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 entered in the Near-end Listen Port field. You can use 5060/6060 (near-end listen port/farend listen port) as the port numbers for TCP transport type and 5061/6061 (nearend 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 and the Switch Link Admin Web page of the Communication Manager Messaging Web interface. 9. Submit the changes.
Add Signaling Group field descriptions

Field Group Type Transport Method Near-end Node Name Setting SIP tls or tcp
procr (IPv4 IP address) or procr6 (IPv6 IP address) or name of the CLAN, depending on which interface
connects to Communication Manager Messaging. Name of the messaging server, in IPv4 or IPv6 IP address format, that is resident on the Communication Manager Messaging server. This name is the same name that appears on the Node Names screen and has the Integrated Messaging IP address.
Far-end Node Name
38
November 2010
Field Near-end Listen Port Far-end Listen Port Far-end Network Region
Setting 5060 (TCP) / 5061(TLS) 6060 (TCP) / 6061(TLS) 1 is usually assigned to procr. If this field is left blank, Communication Manager uses the network region associated with the near-end node name. n Name of the SIP domain. out-of-band y y n PROGress
IMS Enabled? Far-end Domain DTMF over IP Enable Layer 3 Test? Direct IP-IP Audio Connections? IP Audio Hairpinning? Interworking Message
Note: The fields that must be left blank must not have any values entered at this time. The values are populated later in the administration process. The fields that need not be left blank can take 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 may not 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 group number. 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.
November 2010
39
6. In the Number of Members field, type the value supported by the signaling group. 7. Submit the changes.
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 for messaging. 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 field of the dial pattern created for Communication Manager Messaging while administering Session Manager. This value must be within the range of extensions you 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 for other 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 regular expression you created while administering Session Manager. For example, if the regular expression is cmm@domain.avaya.com, use cmm for the Voice Mail Handle field.
40
November 2010
10. Verify that the value of the Routing Digits (e.g. AAR/ARS Access Code) field matches the FAC that you specified for the Auto Alternate Routing (AAR) Access Code field while setting the FACs for messaging. 11. Press the key combination Control E to save the values in the window.
Changing private numbering

This 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 creating a trunk group for messaging. You must enter this number for messaging to function properly.
November 2010
41
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 Pattern Name Grp No. FRL DCS/ QSIG Intw IXC BCC VALUE 0 1234W TSC Setting The route pattern name for the messaging trunk group. For example, msgserver. The number of the trunk group you created while creating a trunk group for messaging. 0 n user yyyyyn y
CA-TSC Request none ITC LAR rest 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.
42
November 2010
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.38standard. 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 1 through 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 for messaging. For example, h3 represents hunt group 3. 3. Press the key combination Control E to save the values in the window.
November 2010
43
Important: At this point, an Avaya Technician must be engaged to change the login passwords.
Changing AAR analysis

1. Enter change aar analysis <n>, where n represents the first digit of the welcome 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 may use ndigit extensions. For example, the default messaging voice mail extension number is 30000. This number varies per site. The columns for Total Min and Total 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 number accordingly. 3. Submit the changes.
Adding a station
1. On the SAT form, type add station <n>, where <n> is the a number from the range 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 while adding the coverage path. 4. In the Security Code field, type a code that you can use later to retrieve messages from the TUI. 5. Complete the remaining fields. 6. Submit the changes.
44
November 2010
Saving translations
Translations refers to the process of configuring the communication server settings through the 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 System Management 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 between the Communication Manager virtual system and the Communication Manager Messaging 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 fields sets the quality of service level for call control messages and audio streams respectively on networks that support this feature. The value for both the fields must be in the range 0 to 63. The value must match the corresponding number configured for 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 method you selected while administering the signaling group. 9. In the Far-end Connections field, by default only one procr connection is supported. 10. In the Connection 1 field, enter the IP address of procr. You also need to enter the port number that was administered on procr. 11. The Messaging Address field displays the IP address of Communication Manager Messaging.
November 2010
45
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 port number 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 while administering Communication Manager. 12. In the SIP Domain field, enter the domain used for Communication Manager and Communication Manager Messaging while administering direct SIP integration. 13. In the Messaging Ports field, enter the number of voice ports the Communication Manager Messaging virtual system uses for mailbox connections to the Communication Manager virtual system. 14. In the Switch Trunks field, enter the total number of trunks for Communication Manager. 15. If you have configured SRTP for messaging, in the Media Encryption field, enter the type of Secure Real-time Transport Protocol (SRTP) encryption for messaging. Important: You need to enable the SRTP feature in the change customer-options form and set the media encryption type in the change ip-codec-set form on Communication Manager. 16. Click Save.
Restarting the messaging application

1. Under Utilities, click Stop Messaging. 2. After the application stops, click Start Messaging.
46
November 2010
Direct SIP integration between Communication Manager Messaging Federal and Communication Manager
Setting feature access codes for messaging
For messaging to function, you must create two feature access codes (FACs) and set two features 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 more digits. 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 first FAC Dialed String value you entered for step 2. If you use the example in step 2, the Feature Access Code (FAC) for Auto Alternate routing (AAR) Access Code would be set to 3. 6. Verify that the Auto Route Selection (ARS) - Access Code 1 field is set to the second FAC Dialed String value you entered for step 2. If you use the example in step 2, the Feature Access Code (FAC) for Auto Route Selection (ARS) - Access Code 1 would be set to 9. 7. Press the key combination Control E to save the changes and exit the window.
November 2010
47
Next steps
You must also create one dial access code (DAC) for later use by the trunk group. The DAC is used to create the Trunk Access Code (TAC) while creating a trunk group for 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 IP address of the Communication Manager Messaging Federal system. 8. Submit the changes.
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 the signaling 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-end Listen Port fields. You can use port 5060 for TCP transport type and port 5061 for TLS transport type. 7. In the Far-end Network Region field, type 1.
48
November 2010
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 and the Switch Link Admin Web page of the Communication Manager Messaging Web interface. 9. Submit the changes.

Field Group Type IMS Enabled? Transport Method Near-end Node Name Setting SIP n tls or tcp
procr (IPv4 IP address) or procr6 (IPv6 IP address) or name of the CLAN, depending on which interface
connects to Communication Manager Messaging. Name of the messaging server, in IPv4 or IPv6 IP address format, that is resident on the Communication Manager Messaging server. This name is the same name that appears on the Node Names screen and has the Integrated Messaging IP address. 5061/5060 (TLS/TCP) 6061/6060 (TLS/TCP) 1 is usually assigned to procr. If this field is left blank, Communication Manager uses the network region associated with the near-end node name. Name of the SIP domain. out-of-band y y n PROGress
Far-end Node Name
Near-end Listen Port Far-end Listen Port Far-end Network Region
Far-end Domain DTMF over IP Enable Layer 3 Test? Direct IP-IP Audio Connections? IP Audio Hairpinning? Interworking Message
November 2010
49
Note: The fields that must be left blank must not have any values entered at this time. The values are populated later in the administration process. The fields that need not be left blank can take default values. 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 may not function correctly for messaging.
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 group number. 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 signaling group. 7. Submit the changes.
Add Trunk Group Page 1 field descriptions

Field Group Type Group Name COR Dial Access? Service Type: Description SIP msgserver 1 n tie
50
November 2010
Field Outgoing Display?
Description n
Member Assignment Method auto Signaling Group The number of the signaling group you created in the creating 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 is appropriate 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 setting the FACs for messaging, and include the number of the trunk group. If you use the example while setting the FACs for messaging , the TAC value would be 199. Refer to the Number of Ports to Mailboxes Mapping section to determine the appropriate value.

Field Unicode Name Redirect On OPTIM Failure SCCAN? Digital Loss Group Preferred Minimum Session Refresh Interval(sec) XOIP Treatment Delay Call Setup When Accessed Via IGAR? Description auto 5000 n 18 600 auto n

Field ACA Assignment? Measured Maintenance Tests? Numbering Format Setting n none y private
November 2010
51
Field UUI Treatment Replace Restricted Numbers? Replace Unavailable Numbers? Modify Tandem Calling Number Show ANSWERED BY on Display?
Setting service-provider n n no y
Note: The private setting is recommended. If the private setting does not work for your site, use public, unknown, or unk-pvt. You must use AAR or ARS digit conversion for path replacement to work.

Field Mark Users as Phone? Prepend '+' to Calling Number? Send Transferring Party Information? Network Call Redirection? Send Diversion Header? Support Request History? Telephone Event Payload Type Convert 180 to 183 for Early Media? Always Use re-INVITE for Display Updates? Identity for Calling Party Display Enable Q-SIP? Setting n n n n n y Leave blank n n P-Asserted-Identity 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.
52
November 2010
This hunt group should be consistent with your country settings. It is only used for messaging. 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 field of the dial pattern created for Communication Manager Messaging while administering Session Manager. This value must be within the range of extensions you 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 for other 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 regular expression you created while administering Session Manager. For example, if the regular expression is cmm@domain.avaya.com, use cmm for the Voice Mail Handle field. 10. Verify that the value of the Routing Digits (e.g. AAR/ARS Access Code) field matches the FAC that you specified for the Auto Alternate Routing (AAR) Access Code field while setting the FACs for messaging. 11. Press the key combination Control E to save the values in the window.

1. On the SAT interface enter change private-numbering 1. 2. Enter values for the following fields:
November 2010
53
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.

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 creating a trunk group for messaging. You must enter this number for messaging to function properly. The system displays the route-pattern window. 2. Verify that the fields on this window are appropriate to change the route pattern.

Field Pattern Name Grp No. FRL DCS/ QSIG Intw Setting The route pattern name for the messaging trunk group. For example, msgserver. The number of the trunk group you created while creating a trunk group for messaging. 0 n
54
November 2010
Field IXC BCC VALUE 0 1234W TSC
Setting user yyyyyn 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.

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.
November 2010
55
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.38standard. 6. Press the key combination Control E to save the values on the window.

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 1 through 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 for messaging. For example, h3 represents hunt group 3. 3. Press the key combination Control E to save the values in the window. Important: At this point, an Avaya Technician must be engaged to change the login passwords.

1. Enter change aar analysis <n>, where n represents the first digit of the welcome 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 may use ndigit extensions. For example, the default messaging voice mail extension number is 30000. This number varies per site. The columns for Total Min and Total Max refer to the number of digits in the voice mail extension. If you are
56
November 2010
using a dial plan with more than five digits, you must adjust this number accordingly. 3. Submit the changes.
Adding a station
Saving translations

1. Open a Web browser and in the Address field type the IP address of the System Management Interface (SMI). 2. On the Administration menu, click Messaging. 3. Click Switch Link Administration > Switch Link Admin.
November 2010
57
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 between the Communication Manager virtual system and the Communication Manager Messaging 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 fields sets the quality of service level for call control messages and audio streams respectively on networks that support this feature. The value for both the fields must be in the range 0 to 63. The value must match the corresponding number configured for 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 method you selected while administering the signaling group. 9. In the Far-end Connections field, by default only one procr connection is supported. 10. In the Connection 1 field, enter the IP address of procr. You also need to enter the port number that was administered on procr. 11. The Messaging Address field displays the IP address of Communication Manager Messaging. 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 port number 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 while administering Communication Manager. 12. In the SIP Domain field, enter the domain used for Communication Manager and Communication Manager Messaging while administering direct SIP integration. 13. In the Messaging Ports field, enter the number of voice ports the Communication Manager Messaging virtual system uses for mailbox connections to the Communication Manager virtual system. 14. In the Switch Trunks field, enter the total number of trunks for Communication Manager. 15. If you have configured SRTP for messaging, in the Media Encryption field, enter the type of Secure Real-time Transport Protocol (SRTP) encryption for messaging. Important: You need to enable the SRTP feature in the change customer-options form and set the media encryption type in the change ip-codec-set form on Communication Manager. 16. Click Save.
58
November 2010
IPv6 implementation for Communication Manager Messaging


Overview
With IPv6 implementation, you can use IPv6 format IP addresses for your enterprise. To implement IPv6 capability for your network, administer Communication Manager and Communication Manager Messaging for your enterprise. You must administer the gateways registered to Communication Manager to enable IPv6 capability. Important: The system does not support IPv6 implementation for SIP integration using Session Manager. However, you can implement IPv6 for direct SIP integration and H.323 integration between Communication Manager and Communication Manager Messaging.
Adding node names IP

1. Using PuTTY, log in to the SAT screen. 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 IP address on the form. 3. In the Name column, type mssgserver6.
November 2010
59
4. In the IP Address column, type the IP address for the message server in IPv6 format. 5. Submit the changes.
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) Type Node name Description The default node name is PROCR. The unique node name for the IP interface. procr is the default node name. The node name here must already be administered on the Node Names screen. The IP address (on the customer LAN) of the Processor Ethernet. The subnet mask associated with the IP address for this IP interface. For more information on IP addresses and subnets, see Administration for Network Connectivity for Avaya Communication Manager, 555-233-504. The Ethernet port must be enabled (y) before it can be used. The port must be disabled (n) before changes can be made to its attributes on this screen. The region number for this IP interface. The threshold for the number of sockets used by this CLAN within the same Gatekeeper Priority as that of other IP interfaces. If the targeted number is exceeded on a CLAN, a warning alarm is generated. If the targeted percentage is exceeded on an PE interface, a procr error is generated. Enter y to allow H.323 endpoint connectivity on this CLAN. Enter n if you do not want H.323 endpoints to connect to this CLAN. Enter y to allow branch gateways to connect to this CLAN. Enter n if you do not want branch gateways to connect to this CLAN.
IP Address Subnet Mask
Enable Interface? Network Region Target socket load
Allow H.323 Endpoints Allow H.248 Gateways?
60
November 2010
Field (Page1) Gatekeeper Priority
Description This value is used on the alternate gatekeeper list. The lower the number the higher the priority. Valid values for this field are one through nine with five being the default. This field displays only if the allow H.323 endpoints field is set to a yes on this form. Field (Page 2) Description The default name is procr6. The IP address in IPv6 format of the Processor Ethernet. The subnet mask associated with the IP address for this IP interface. For more information on IP addresses and subnets, see Administration for Network Connectivity for Avaya Communication Manager, 555-233-504. Enter y to enable Processor Ethernet to accept IPv6 addresses.
Node Name IP Address Subnet Mask
Enable Interface?
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 be available for the creation of a trunk group. For example, if you create this signaling group as 99, the corresponding trunk group should be created as 99. For this group, choose a number that is easily differentiated from other signaling and trunk groups. The system displays the Signaling Group window.
November 2010
61

You can also set SIP as the group type. However, the fields to add a SIP signaling group are different from an H.323 signaling group.
Field Group Type Remote Office? Max number of NCA TSC Max number of CA TSC Trunk Group for NCA TSC Trunk Group for Channel Selection TSC Supplementary Service Protocol Near-end Node Name Setting h.323 n 10 10 (Leave blank) (Leave blank) b
procr (IPv4 IP address) or procr6 (IPv6 IP address) or name of the CLAN, depending on
which interface connects to Communication Manager Messaging.
Far-end Node Name
Name of the messaging server, in IPv4 or IPv6 IP address format, that is resident on the Communication Manager Messaging server. This name is the same name that appears on the Node Names screen and has the Integrated Messaging IP address. 1720 1720 1 is usually assigned to procr. If this field is left blank, Communication Manager uses the network region associated with the near-end node name. y if the group type is H.323. out-of-band y y n PROGress
Near-end Listen Port Far-end Listen Port Far-end Network Region
Calls Share IP Signaling Connection? DTMF over IP Enable Layer 3 Test? Direct IP-IP Audio Connections? IP Audio Hairpinning? Interworking Message
62
November 2010
Note: The fields that must be left blank must not have any values entered at this time. The values are populated later in the administration process. The field, Far-end Network Region, defaults to 1 if a value is not specified. The Calls Share IP Signaling Connection field is set to y so that messaging does not attempt to create a new TCP/IP connection for each call. Note: If the configuration of the Far-end Network Region field changes, the signaling group may not function correctly for messaging.
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 equal to that of the signaling group that you created. For example, if you created a signaling 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 Group window.

Important: If you do not set the Group Type value to isdn, the system does not display some of the fields of this window. Important: You can also add a SIP trunk group. However, the fields on the screen are different and you need to provide values to the fields.
November 2010
63
Field Group Type Group Name Carrier Medium COR Dial Access? Service Type: Outgoing Display?
Description isdn msgserver6 H.323 1 y tie n
Member Assignment Method auto Signaling Group The number of the signaling group you created in the creating 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 is appropriate 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 setting the FACs for messaging, and include the number of the trunk group. If you use the example while setting the FACs for messaging , the TAC value would be 199. Refer to the Number of Ports to Mailboxes Mapping section to determine the appropriate value.

Field Supplementary Service Protocol Digit Handling (in/out) Format Disconnect Supervision - In? Out? Description b enbloc/enbloc pub-unk y n
64
November 2010

Field Send Name NCA-TSC Trunk Member Send Calling Number Format Send Called/Busy/Connected Number Setting n 1 y private y
Note: The private setting is recommended. If the private setting does not work for your site, use public, unknown, or unk-pvt. You must use AAR or ARS digit conversion for path replacement to work.

Field Path Replacement with Retention? Path Replacement Method QSIG Value-Added? Setting n better-route 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.
November 2010
65
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 for messaging. 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 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.
66
November 2010
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 qsig-mwi. This value is required for other fields 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. 9. Verify that the Voice Mail Number field is set to the default voice mail extension. 10. Verify that the value of the Routing Digits (e.g. AAR/ARS Access Code) field matches the FAC that you specified for the Auto Alternate Routing (AAR) Access Code field while setting the FACs for Communication Manager. 11. Press the key combination Control E to save the values in the window.

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
November 2010
67
Total Len: 5 3. Press Control E to save changes.

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 creating a trunk group for messaging. You must enter this number for messaging to function properly. The system displays the route-pattern window. 2. Verify that the fields on this window are appropriate to change the route pattern.

Field Pattern Name Grp No. FRL DCS/ QSIG Intw IXC BCC VALUE 0 1234W TSC Setting The route pattern name for the messaging trunk group. For example, msgserver. The number of the trunk group you created while creating a trunk group for messaging. 0 n user yyyyyn y
68
November 2010
Changing the 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 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 Region value. 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.

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.
November 2010
69
If this installation is using Fax, verify that the FAX field is set to T.38standard. 6. Press the key combination Control E to save the values on the window.

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 1 through 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 for messaging. For example, h3 represents hunt group 3. 3. Press the key combination Control E to save the values in the window. Important: At this point, an Avaya Technician must be engaged to change the login passwords.

1. Enter change aar analysis <n>, where n represents the first digit of the welcome 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 may use ndigit extensions. For example, the default messaging voice mail extension number is 30000. This number varies per site. The columns for Total Min and Total Max refer to the number of digits in the voice mail extension. If you are
70
November 2010
using a dial plan with more than five digits, you must adjust this number accordingly. 3. Submit the changes.
Adding a station
Saving translations

1. Open a Web browser and in the Address field type the IP address of the System Management Interface (SMI). 2. On the Administration menu, click Messaging. 3. Click Switch Link Administration > Switch Link Admin.
November 2010
71
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 between the Communication Manager virtual system and the Communication Manager Messaging 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 fields sets the quality of service level for call control messages and audio streams respectively on networks that support this feature. The value for both the fields must be in the range 0 to 63. The value must match the corresponding number configured for 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 method you selected while administering the signaling group. 9. In the Far-end Connections field, by default only one procr connection is supported. 10. In the Connection 1 field, enter the IP address of procr. You also need to enter the port number that was administered on procr. 11. The Messaging Address field displays the IP address of Communication Manager Messaging. 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 port number 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 while administering Communication Manager. 12. In the SIP Domain field, enter the domain used for Communication Manager and Communication Manager Messaging while administering direct SIP integration. 13. In the Messaging Ports field, enter the number of voice ports the Communication Manager Messaging virtual system uses for mailbox connections to the Communication Manager virtual system. 14. In the Switch Trunks field, enter the total number of trunks for Communication Manager. 15. If you have configured SRTP for messaging, in the Media Encryption field, enter the type of Secure Real-time Transport Protocol (SRTP) encryption for messaging. Important: You need to enable the SRTP feature in the change customer-options form and set the media encryption type in the change ip-codec-set form on Communication Manager. 16. Click Save.
72
November 2010
Subscribers

Subscribers
Subscriber Management
System Manager lets you perform selected messaging system administration activities. You can add, view, edit, and delete subscribers through System Manager. Apart from subscriber management, you can also administer mailboxes and modify mailbox settings for a messaging system. 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.
November 2010
73
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 Communication Manager Messaging from the list of messaging systems, and then click New, the system displays the Add Subscriber page with the first Messaging, Modular Messaging, or Communication Manager Messaging in context.
Editing a subscriber
1. On the System Manager console, under Elements, click Messaging. 2. Click Subscriber in the left navigation pane. 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
1. On the System Manager console, under Elements, click Messaging. 2. Click Subscriber in the left navigation pane. 3. Select a messaging system from the list of Messaging Systems. 4. Click Show List. 5. Select the subscriber you want to view from the Subscriber List. 6. Click View.
74
November 2010
Subscribers
Note: You cannot edit any field on the View Subscriber page.
Deleting a subscriber
1. On the System Manager console, under Elements, click Messaging. 2. Click Subscriber in the left navigation pane. 3. Select a messaging system from the list of Messaging Systems. 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 mailbox management. You can delete the user associated subscribers only through User Profile Management.
Subscriber List
Subscriber List displays all the subscribers under a messaging version (Messaging, Communication Manager Messaging, or Modular Messaging). You can apply filters to each column in the Subscriber List. You can also sort the subscribers according to each of the column in the Subscriber List. When you click Refresh, you can view the updated information available after the last synchronization operation.
Name Name Mailbox Number Email Handle Description Specifies the name of the subscriber. Specifies the mailbox number of the subscriber. Specifies the e-mail handle of the subscriber.
Telephone Number Specifies the telephone number of the mailbox.
November 2010
75
Name Last Modified User System
Description Specifies the time and date when the subscriber details were last modified. If a subscriber is associated with a user, then the system displays the name of the user in this column. Specifies the messaging system of the subscriber.
Filtering subscribers
1. On the System Manager console, under Elements, click Messaging. 2. Click Subscriber in the left navigation pane. 3. Select a messaging system from the list of Messaging Systems. 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 that you have set. Note: The table displays only those subscribers that match the filter criteria.
Subscribers (CMM) field descriptions

Field System Template Type Software Version Description Specifies the messaging system of the subscriber you want to add. Specifies the template for this subscriber. You can choose any template from the drop-down box. Specifies the messaging type of your subscriber. Specifies the messaging version of the subscriber.
Save as Template Saves your current settings as a template.
76
November 2010
Subscribers
Basic Information
Field Last Name First Name Extension Description Specifies the last name of the subscriber. Specifies the first name of the subscriber. Specifies a number that is between 3 to10-digits in length, that the subscriber will use to log on to the mailbox. Other local subscribers can use the Mailbox Number to address messages to this subscriber. The Mailbox 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 15digits in length and cannot be blank The class of service for this subscriber. The COS controls subscriber access to many features and provides general settings, such as mailbox size. You can select an option from the dropdown box. Specifies the default community ID for the subscriber. Community IDs are used to control message sending and receiving among groups of subscribers. The default value is 1. Specifies the number of the switch on which this subscriber's extension is 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 this subscriber. You should enter 0 when the subscriber does not have a phone on any switch in the network. Account Code Specifies the Subscriber Account Code. The Subscriber Account Code is used to create Call Detail Records on the switch for calls placed by the voice ports. The value you enter in this field can contain a combination of digits from 0 to 9. If an account code is not specified, the system will use the subscriber's mailbox extension as the account code.
COS
Community ID
Switch Number
Subscriber Directory
Field Email Handle Description Specifies the name that appears before the machine name and domain in the subscriber's e-mail address.
Common Name Specifies the display name of the subscriber.
November 2010
77
Mailbox Features
Field Covering Extension Description Specifies the number to be used as the default destination for the Transfer Out of Messaging feature. You can enter 3 to 10 digits in this field depending on the length of the system's extension, or leave this field blank.
Secondary Extensions
Field Secondary extension Description Specifies the number assigned to a subscriber for receiving fax messages. Valid Entries are blank or 3-10 digits (0-9), depending on the length of the system's extension.
Miscellaneous
Field Description
Misc 1 Specifies additional, useful information about a subscriber. Entries in this field are for convenience and are not used by the messaging system. Misc 2 Specifies additional, useful information about a subscriber. Entries in this field are for convenience and are not used by the messaging system. Misc 3 Specifies additional, useful information about a subscriber. Entries in this field are for convenience and are not used by the messaging system. Misc 4 Specifies additional, useful information about a subscriber. Entries in this field are for convenience and are not used by the messaging system. Button Commit Schedule Save as Template Reset Edit Done Cancel Description Adds the subscriber to the messaging system. Adds the subscriber at the specified time. Saves the settings as a template. Clears all the changes. Allows you to edit the fields. Completes your action and takes you to the previous page. Takes you to the previous page.
78
November 2010
Upgrades
Upgrades
Upgrade paths
The 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
November 2010
79
80
November 2010
Chapter 6: Hardware
This chapter describes the new hardware, including the Avaya Common Severs Dell PowerEdge R610 and HP ProLiant DL360 G7, and new endpoints supported by Communication Manager Release 6.0.1.
Avaya A175 Desktop Video Device

The 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 Android operating system, the Avaya A175 Desktop Video Device can operate on both wired and wireless 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 your Exchange contacts into the Exchange account and download the events from your Exchange calendar into the Avaya A175 Desktop Video Device calendar. The Avaya A175 Desktop Video Device will automatically synchronize with your Exchange account (that is, contacts, calendar, and email) at regular intervals to ensure you have the most up-todate information. access your Facebook account Once configured, the Avaya A175 Desktop Video Device automatically download your Facebook friends into your contacts. The Avaya A175 Desktop Video Device will automatically synchronize your Facebook information at regular intervals to ensure you have 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 your Gmail contacts into the Gmail account. The Avaya A175 Desktop Video Device will
November 2010
81
Hardware
automatically synchronize with your Gmail account at regular intervals to ensure you have the most up-to-date information. surf the web For more information, see Avaya Video Conferencing Solution Release 6.0.
Avaya 1000 Series Video Conferencing endpoint

Avaya 1000 Series endpoint is a video conferencing system for desktop, office, and small to large conference rooms. These endpoints include the video codec, camera, audio components, handheld remote and cables. You must supply HDTVs with built-in speakers and at 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 HDTVs, media centers and custom installation
Avaya 1010 Video Conferencing endpoint

The Avaya 1010 Video Conferencing endpoint is primarily for desktop users. This endpoint comes with a fixed focused camera and microphone HDTV speakers primarily for desktop users. 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

The Avaya 1020 Video Conferencing endpoint comes with a pan-tilt-zoom camera and mic pods. This endpoint is primarily for an office or small conference room. You can locate the 1020 system over a credenza or on a wall mount.
82
November 2010
Avaya 1000 Series Video Conferencing endpoint
The Avaya 1020 Video Conferencing endpoint has the following characteristics: 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 Graphical display size is 1024 x 576 pixels

Avaya 1030 Video Conferencing endpoint is for midsize to large conference rooms. You can locate the 1030 System on a media center or wall mount. The Avaya 1030 Video Conferencing endpoint comes with a pan-tilt-zoom camera, microphone pod, and dual displays for viewing participants and content. The Avaya 1030 Video Conferencing endpoint has the following characteristics: Supports 2 HD display. The recommended HD display size is 50 to 65 inches. Supports 1 optional HD camera Graphical display size is 1280 x 720 pixels

The Avaya 1040 Video Conferencing endpoint is for midsize to large conference rooms. You can 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 optional conference room phone and is a 4-port MCU enabling multi-point conferencing. The Avaya 1040 Video Conferencing endpoint has the following characteristics: Supports 2 HD display. The recommended HD display size is 50 to 65 inches. 4-port MCU for up to 4 simultaneous users Supports 1 optional HD camera Graphical display size is 1280 x 720 pixels

The Avaya 1050 Video Conferencing endpoint is primarily for midsize to large conference rooms. You can locate this endpoint on a media center or wall mount. This endpoint includes a pan-tilt-zoom camera, microphone pod, and dual displays for viewing participants and content. This endpoint also offers an optional conference room phone.
November 2010
83
Hardware
The Avaya 1050 Video Conferencing endpoint has the following characteristics: 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 6 simultaneous users at 1080p resolution Supports 2 optional HD camera
HP ProLiant DL360 G7 1U server overview

Introduction
The Avaya Common Servers category includes the HP ProLiant DL360 G7 1U server that supports several Avaya software solutions, some requiring additional hardware and memory requirements beyond the standard configuration. This book covers the standard configuration onlyconsult specific Avaya product documentation for application-specific or solutionspecific server configurations.
Front of server
Note: Servers ship with 24 hard disk drives, depending upon product requirements.
No. 1 2 3 4 5 6 Description Not present Not present DVD-RW HP Systems Insight Display Front USB connector Video connector
84
November 2010
No. 7 8 9 10
Description Hard drive bay 4 Hard drive bay 3 Hard drive bay 2 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 product requirements. 2 Slot 2 PCIe2 x16 (16, 8, 4, 2, 1), 75W +EXT 75W* Note: Servers might ship with a PCI card installed, depending upon product requirements. 3 4 5 6 7 8 9 10 11 12 Power supply bay 1 (populated) Power supply bay 2 iLO 3 connector Serial connector Video connector NIC 4 connector NIC 3 connector NIC 2 connector NIC 1 connector USB connectors (2)
November 2010
85
Hardware
*This expansion slot provides 75 W of power to an adapter, with an additional 75 W of power supplied by external power.
Server specifications
Baseline configurations and options for the HP DL360 G7 server:
Component DL360 G7 Processor Minimum specification 1U chassis, dual socket Simplex configuration: Intel E5620 Quad Core / 2.4 GHz (Westmere), 1 CPU, 3 memory channels per CPU with up to 3 RDIMMs per channel Note: Simplex server with the single E5620 2.4 GHz processor can be used in a duplex server configuration. Duplex configuration: Intel X5670 six Core / 2.93 GHz (Westmere), 1 CPU, 3 memory channels per CPU with up to 3 RDIMMs per channel Memory HW RAID 1 Disk drive 6 x 2GB DDR3 RDIMMs (1333 MHz) for a N/A total of 12GB P410i RAID controller with 256MB cache and battery backup. Optioned as RAID 5 146GB SAS 2.5" 10K RPM 6G DP Hard Drive. Base configuration: 272 total: RAID 5, 3 x 146GB drives NICs 6 NIC ports HP NC382T PCI Express Dual Port Gigabit NIC expansion card (Broadcom 5709 silicon) in addition 4 integrated ENET Gigabit NIC ports N/A N/A N/A Upgrade options based on product requirements No additional options supported. N/A
PCI slots
Two PCI-Express Gen 2 expansion slots: N/A (1) full-length, full-height slot and (1) lowprofile slot (1-FL/FH x 16 PCIe & 1-LP x 8 PCIe Riser No additional options supported.
Removable media Slim line SATA DVD-RW optical drive (used in all Avaya configurations)
86
November 2010
Component Power supply Fans Additional items
Minimum specification Single 460 W hotplug AC power supply 3 fan modules (fan redundancy standard) 1 front USB, 2 back USB, 1 internal USB
Upgrade options based on product requirements Redundant 460 W power supply available. No additional options supported.
Environmental specifications
The HP DL360 G7 environmental specifications are listed below:
Specification Temperature range Note: All temperature ratings shown are for sea level. An altitude derating of 1C per 300 m (1.8 per 1,000 ft.) to 3048 m (10,000 ft.) is applicable. No direct sunlight allowed. Operating Shipping Maximum wet bulb temperature Relative humidity (noncondensing) 10C to 35C (50F to 95F) -40C to 70C (-40F to 158F) 28C (82.4F) Value
Note: Storage maximum humidity of 95% is based on a maximum temperature of 45 C (113F). Altitude maximum for storage corresponds to a pressure minimum of 70 kPa. 10% to 90% 5% to 95%
Operating Non-operating
Physical specifications
The HP DL360 G7 physical specifications are listed below:
Specification Dimensions Height: 4.32 cm (1.70 in) Width: 42.62 cm (16.78 in) Value
November 2010
87
Hardware
Specification Depth: 69.53 cm (27.38 in) Weight (maximum; two processors, two power supplies, eight hard disk drives) Weight (minimum; one processor, one power supply, no hard drives) Weight (no drives installed) 15.97 kg (35.20 lb)
Value
14.51 kg (32.00 lb)
14.06 kg (31.00 lb)
References
For 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

Introduction
The Avaya Common Servers category includes the Dell PowerEdge R610 1U server that supports several Avaya software solutions, some requiring additional hardware and memory requirements beyond the standard configuration. This book covers the standard configuration onlyconsult specific Avaya product documentation for application-specific or solutionspecific server configurations.
Front of server
88
November 2010
Note: Servers ship with 24 hard disk drives, depending upon product requirements.
Reference 1 2 3 4 5 6 7 8 9 10 Description Power-on indicator, power button NMI button USB connectors (2) Video connector LCD menu buttons LCD panel System identification button Hard drives (maximum 4) DVD-RW System identification panel
Back of server
Reference Description 1 2 3 4 iDRAC6 Enterprise port (optional) VFlash media slot (optional) Serial connector PCIe slot 1 Note: Servers might ship with a PCI card installed, depending upon product requirements.
November 2010
89
Hardware
Reference Description 5 6 7 Video connector USB connectors (2) PCIe slot 2 Note: Servers might ship with a PCI card installed, depending upon product requirements. 8 9 10 11 12 13 Ethernet connectors (4) System status indicator connector System status indicator System identification button Power supply 1 (PS1) Power supply 2 (PS2)
Server specifications
Baseline configurations and options for the Dell R610 server:
Component R610 Processor Minimum specification 1U chassis, dual socket Simplex configuration: Intel E5620 Quad Core / 2.4 GHz (Westmere), 1 CPU, 3 memory channels per CPU with up to 2 RDIMMs per channel Note: Simplex server with the single E5620 2.4 GHz processor can be used in a duplex server configuration. Duplex configuration: Intel X5670 six Core / 2.93 GHz (Westmere), 1 CPU, 3 memory channels per CPU with up to 2 RDIMMs per channel Memory HW RAID 1 6 x 2GB DDR3 RDIMMs (1333 MHz) for a N/A total of 12GB H700 RAID controller with 512MB cache N/A and battery backup. Optioned as RAID 5. Upgrade options based on product requirements Listed below N/A
90
November 2010
Component Disk drive
Minimum specification 146GB SAS 2.5" 10K RPM 6G DP Hard Drive. Base configuration: 272 total: RAID 5, 3 x 146GB drives
Upgrade options based on product requirements N/A
NICs
6 NIC ports Broadcom 5709 Dual Port 1GbE NIC (430-3261) in addition 4 integrated ENET gigabit NIC ports 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
N/A
PCI slots
No additional options supported.
Removable media DVD+/-RW SATA internal Power supply Fans Single 502 W Hotplug AC power supply Redundant Speed Adjusting Fans standard (5 for single processor) 2 front USB, 2 back USB, 1 internal USB
No additional options supported. Redundant 502 W power supply available. No additional options supported. (2nd processor includes 1 additional fan)
Additional items
Environmental specifications
The Dell R610 environmental specifications are listed below:
Specification Temperature Operating 10 to 35C (50 to 95F) with a maximum temperature gradation of 10C per hour Note: For altitudes above 2,950 feet, the maximum operating temperature is derated 1F per 550 ft. Storage Relative Humidity -40 to 65C (-40 to 149F) with a maximum temperature gradation or 20C per hour Value
November 2010
91
Hardware
Specification Operating Storage Altitude Operating -16 to 3,048 m (-50 to 10,000 ft.) Note:
Value 20% to 80% (non-condensing) with a maximum humidity gradation of 10% per hour 5% to 95% (non-condensing) with a maximum humidity gradation of 10% per hour
For altitudes above 2,950 ft, the maximum operating temperature is derated 1F per 550 ft. Storage -16 to 10,600 m (-50 to 35,000 ft.)
Physical specifications
The Dell R610 physical specifications are listed below:
Specification Height: 4.26 cm (1.68 in) Width: 48.24 cm (18.99 in) with rack latches Dimensions 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 (maximum configuration) 17.69 kg (39 lb) Value
Weight (empty) 13.25 kg (29.2 lb)
References
For 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.
92
November 2010
Chapter 7: Documentation and procedure updates

This chapter describes the updates and additions for Communication Manager Release 6.0.1 that are not documented elsewhere for this release.
Adding New Hardware for Avaya Servers and Gateways

The following change applies to the Adding New Hardware for Avaya Servers and Media Gateways, 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 Transport Client/Server Tool including the quotation marks. 3. Press Enter. 4. In the search results, click the appropriate Communication Manager Downloads link of 08/26/2010. 5. On the download page, click Reliable Data Transport Client/Server Tool V2.0 of 31-Aug-2005. 6. Click RDTT_R2.1.exe. 7. Click Save. 8. Make note of the default download directory. -orBrowse to the appropriate directory. 9. Click Save. 10. Click Run.
November 2010
93
Documentation and procedure updates
Note: To view and save the accompanying ReadMe file, select RDTT_Readme_2.1.doc.
Administrator guide
The following changes apply to the Administering Avaya Aura Communication Manager, 03-300509:
PE Interface configuration
The description of PE Interface Acceptance Test is added under the PE Interface configuration section.
PE Interface acceptance test

If the main servers are duplicated and PE interface is not used (that is, no ESS server is provided and no IP endpoints are controlled by PE interface), PE interface should not be enabled. The Status Summary page should show that Processor Ethernet connection is not functional 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 verify the following: For Communication Manager 5.0 and 5.1 releases, the PE Interface should be set to UNUSED on the Set Identities page. The PE Interchange Priority should be set to IGNORE on the Configure Interfaces page. For Communication Manager 6.0 and later releases, the Functional Assignment for eth0 should not include Processor Ethernet on the Network Configuration page. The PE Interchange 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 or IP endpoints are controlled by the PE interface, or both ESS server is provided and IP endpoints are controlled by the PE interface), PE Interface on both the main server and the ESS server should be enabled. The Status Summary page should show that Processor Ethernet connection is functional on both servers, and PE Priority is set to same value (but not IGNORE) on both servers.
94
November 2010
Administering Network Connectivity
If the Status Summary page does not provide the information stated above, you should verify the following: For Communication Manager 5.0 and 5.1 releases, PE Interface should be set to one of the Ethernet interfaces on the Set Identities page, and PE Interchange Priority should be set to the same value (but not IGNORE) on the Configure Interfaces page on both servers. For Communication Manager 6.0 and later releases, Functional Assignment for eth0 should include Processor Ethernet on the Network Configuration page, and the PE Interchange Priority should be set to the same value (but not IGNORE) on the Duplication Parameters 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 both servers have been running as an active or standby pair.
Administering Network Connectivity

The following change applies to the Administering Network Connectivity on Avaya Aura Communication Manager, 555-233-504:
Reviewing the network region administration

Reference 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 Regions IGAR-DPT screen, which gives an overview of fields related to the Inter-Gateway Alternate Routing and Dial Plan Transparency features. 2. Ensure that the IGAR and DPT parameters are administered according to your design.
Conversion of servers and gateways

The following changes apply to the Converting Avaya Servers and Media Gateways, 03-602884:
November 2010
95
Suppress alarming
Reference 5.2 version pages 217, 220, 227, and 247, step four is removed: Log off and close the dialog box.
Feature Description and Implementation

The following changes apply to the Avaya Aura Communication Manager Feature Description and Implementation, 555-245-205:
Call detail record field descriptions

The following section provides the description of new condition codes.
Condition Codes
The following condition codes are added to the existing condition codes table:
Condition codes O P Description Identifies CDR records for all calls in which URI was used as dialed digits. Identifies CDR records for all calls in which SA8957 PIN code for Private Calls was used.
Call forward override

If the Call Forward Override feature is turned on, and a call terminates at an already visited station for that call as a part of the call forward chain, the call is not forwarded. Instead, the call continuously rings at that station to avoid loops while traversing the chained call forward path. 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 call to Station B, then Station B forwards the call to Station C, and Station C forwards the call to Station 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.
96
November 2010
Feature Description and Implementation
Call Park
If you enable the Drop Parking User From the Call After Timeout field, the system automatically drops the parking user from the call after timeout.
Screens for administering Call Park

Screen name Feature-Related System Parameters Purpose Fields
Specifies to the system to automatically Drop Parking User drop the parking user from the call after the From the Call After timeout that is set. Timeout
Considerations for Administrable Language Displays

The following list describes the situations when the Display Messages screen is disabled: After loading an avaya_user-defined.txt file, Communication Manager disables the following 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, callidentifiers, property-management, view-buttons, date-time, self-administration, vustats, and leave-word-calling. After loading an avaya_user-defined.txt file, Communication Manager disables the page 1 of the Posted Messages screen for both the change and display display-message commands. However, you can enter translations for the fixed languages in the Posted Messages screen. After loading a custom_user-defined.txt file, Communication Manager disables the last page of the Posted Messages screen and relates to the user-defined translation for both the change and display display-message commands. You can, however, enter translations for the fixed languages in the Posted Messages screen. After loading an avaya_user-defined.txt file, Communication Manager does not allow the user-defined keyword for the Label Language field on the Abbreviated Dialing screen. You can, however, enter translations for the fixed languages in the Abbreviated Dialing screen.
Enhanced Redirection Notification

For Enhanced Redirection Notification, you must enable at least one of the Redirection Notification options listed in the Feature-Related System Parameters screen. For example, if you disable all the redirection notification options, all the notifications appear on the IP (H.323)
November 2010
97
telephones. The system does not check the notifications to be displayed when you disable all the options. However, if you activate Do Not Distrub (DND) notification field, only the DND notification appears on the endpoints. This is because the system checks the displayed notifications only when you enable at least one of the options.
Interactions for Station Security Code

This section provides information about how the Station Security Code feature interacts with the other features on the system. Use this information to ensure that you receive the maximum benefits 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 EMU

The 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 is configured, Communication Manager does not support EMU. If an EMU user is assigned
98
November 2010
Installing and Upgrading the Avaya G450 Gateway
to a location or is reached through partition group routing, EMU registration is not allowed.
Installing and Upgrading the Avaya G450 Gateway

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

For information on downloading RDTT, see Downloading Reliable Data Transport Tool on page 93.
Installing and Upgrading the Avaya S8300 Server

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

For information on downloading RDTT, see Downloading Reliable Data Transport Tool on page 93.
Maintenance Alarms
The following changes apply to the Maintenance Alarms for Avaya Aura Communication Manager, 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.'
November 2010
99
disable synchronization-switch
The disable synchronization-switch command is renamed as disable synchronization.
enable synchronization-switch
The enable synchronization-switch command is renamed as enable synchronization.
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, the affected 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 IP stations region or any connected region. If the VoIP media is available in the IP stations region or any connected region, the test passes. If the VoIP media is not available in the IP stations region or any connected region, the test fails. This test uses the stations mapped region that is also shown in the status station command for the station. Table 1: Media Path Status Test (#1374)
Error Code 1706 2100 Test Result ABORT ABORT Description / Recommendation This station is not registered. Media Path Status test only runs on registered stations. Could not locate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals, up to 5 times. 2. Escalate if the problem persists. 2012 ABORT Internal system error.
100
November 2010
Maintenance Commands
Error Code
Test Result
Description / Recommendation 1. Retry the command at 1-minute intervals, up to 3 times. 2. Escalate if the problem persists.
2500
ABORT
Internal system error. 1. Retry the command at 1-minute intervals, up to 3 times. 2. Escalate if the problem persists.
ANY
FAIL
VoIP media is not available in the IP stations region or any connected region. 1. Verify that there are VoIP media assigned to the stations region. Valid media are IPMEDRO boards or Branch Gateways. 2. If there are VoIP media assigned to this Stations region, verify that the media are in service.
PASS
VoIP media is available and in-service in the IP stations region.
SIP-SGRP (SIP Signaling Group)

Error log entries and recommended action
Error Type 258 Aux Data 17 Associated Test IP Signaling Group Far-End Status Test (#1675) Alarm Level MIN On/Off Board OFF Recommended Action
Note: Error Type 258: Primary signaling link is unavailable.
Maintenance Commands
The following changes apply to the Maintenance Commands for Avaya Aura Communication Manager, Media Gateways and Servers, 03-300431:
November 2010
101
AAR and ARS Digit Analysis Table

The following Action/Object is added to the AAR and ARS Digit Analysis Table under the Administration Screen Reference section.
Action/Object list aar route-chosen Qualifier dialed number [partition n] [schedule]
list ars route-chosen

The following field description is added in the list ars route-chosen field descriptions table.
Field Description
Actual Digits outpulsed when you choose each of the preferences in the chosen Outpulsed Digits route pattern. by Preference
pingall
pingall [-s [ServerID]] [-i [cab#][carrier]] [-c count ][-v ]
Use pingall to verify basic connectivity of all IPSI circuit packs. -a -s ServerID Ping all network entities on the remote sides, including servers, routers, and IPSI circuit packs. Ping a specific customer LAN
-i cab#[carrier] Ping a specific IPSI
102
November 2010
Reports
-c count -v -?
The number of test messages for each network entity Turn on verbose mode Display a description of command options
Example
init@sraydb2-srv1> pingall -a Testing.. HostName IPAddress ipsi-A02b 172.16.5.54 ipsi-A02a 172.16.5.53 ipsi-A01b 172.16.5.52 ipsi-A01a 172.16.5.51 init@sraydb2-srv1> Status Pass Pass Pass Pass
Reports
The following change apply to the Avaya Aura Communication Manager Reports, 555-233-505:
AAR or ARS Route Chosen reports

Reference 6.0 version pages 55 and 56, the following field description is added in the existing field description table:
Field Description
Actual Digits outpulsed when you choose each of the preferences in the chosen Outpulsed Digits route pattern. by Preference
Attendant and Maintenance Status report

The following description is added to the existing Attendant and Maintenance Status report section: To ensure that the authorized users log into the system, you must click Cancel to log off from the SAT screen after running the monitor system view1 and monitor system view2 commands.
November 2010
103
Screen Reference
The following changes apply to the Avaya Aura Communication Manager Screen Reference, 03-602878:
Agent LoginID
The 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 Console
The 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 Table

The description of the Percent Full field on the Dial Plan Analysis Table screen is modified as follows:
Percent Full
Valid Entry 0 to 100 Usage The percentage of system memory resources that have been allocated for the dial plan currently used. For details on the system memory resources, see Avaya Aura Communication Manager System Capacities Table, 03-300511.
104
November 2010
Screen Reference
Dial Plan Parameters

The following field is added on the Dial Plan Parameters screen.
UDP-ARS Calls Considered Offnet

Valid entry y Usage If you set the Net field to ARS and the UDP-ARS Calls Considered Offnet 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 cannot forward calls to a UDP-ARS number. Stations that are outward-restricted (through the COR) cannot place calls to a UDP-ARS number. Toll analysis is applied when a call is placed by a toll-restricted user to a UDP-ARS number. COR-COR checks are not applied when a user dials a call to a UDPARS number. n If you set the Net field to ARS and the UDP-ARS Calls Considered Offnet field to n, the call is considered onnet.
For more information about the Net field, see Uniform Dial Plan Table section of the Avaya Aura Communication Manager Screen Reference, 03-602878.
Feature-Related System Parameters

The following fields are added on the Feature-Related System Parameters screen:
Drop Parking User From the Call After Timeout

Valid Entry y n Usage Drops the parking user from the call automatically after the timeout. Does not drop the parking user from the call automatically after the timeout.
November 2010
105
Restrict Calls
Indicates the type of calls to block first during overload traffic conditions on the system.
Valid Entry stations-first all-trunks-first public-trunksfirst Usage Deny new traffic generated by internal stations, allowing inbound calls only. This works best in call center environments. Deny all incoming trunk calls and does not block station off-hook. Deny incoming calls on ISDN public trunks and analog CO trunks.
Zip Tone Burst For Call master Endpoints

Valid entry double Usage When the station set type is a Callmaster series, Communication Manager retains existing operation which applies the following to ACD agents: 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 tone reducing time for agent to start conversation with the caller and possibility of the agent and the caller hears open mike background noise between the first and second tones. Use with a Callmaster station type when the agent can always hear enough of the single burst auto-answer to recognize that a call is being delivered.
Hunt Group
The description of the Security Code field on the Hunt Group screen is modified.
Security Code
106
November 2010
Screen Reference
Incoming Call Handling Treatment

In 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 a Service/Feature defined as Type 2, the Incoming Call Handling Treatment screen determines which incoming calls are assigned to this Service/Feature. See the description of the Network Facilities screen for details. Service type 2 is useful when creating a user-defined service on the ISDN Network Facilities screen. A user defined service with Facility Type 2 allows special routing on the Incoming Call Handling Treatment Table as well as Min/Max usage restrictions on the Usage Allocation table. Facility type 3 is useful when creating a user-defined service for outgoing calls on ISDN cbc trunk groups. If a user-defined service with Facility Type 3 is used for a route pattern preference, the outgoing SETUP message will not contain an NSF IE, and the call will be counted in the corresponding user-defined service entry in the Usage Allocation table.
IP Network Region
The valid entries of the WAN-BW limits (Total) field are modified on the IP Network Region screen.
WAN-BW limits (Total)

Valid Entry 1 to 9999 Usage The bandwidth limit for direct WAN links. Values for this field can be entered in the number of connections, bandwidth in Kbits or calls, or left blank for NoLimit. Values for this field can be entered in the number of connections, bandwidth in Mbits, or left blank for NoLimit.
1 to 65
ISDN Numbering Calling Party Number Conversion for Tandem Calls

The following field descriptions on the ISDN Numbering Calling Party Number Conversion for Tandem Calls screen are modified.
November 2010
107
CPN Len
Valid Entry 1 to 16 blank Usage A number between 1 and 16 that indicates the length of calling party number (CPN). Leave blank when deleting an entry. This is the default value.
CPN Prefix
Valid Entry Any combination of digits 0 to 9, up to 16 digits. The '+' sign is also valid. blank Usage Up to 16 digits to indicate the calling party prefix.
Indicates that all trunk groups are valid provided the Modify Tandem Calling Party field on the ISDN Trunk Group screen is set to y. A specific CPN digit string match is not required, provided other matching criteria for tandem CPN modification are met. This is the default value.
Delete
Valid Entry 1 to 16 all blank Usage A valid number of deleted digits up to 16. Indicates that all digits are deleted. Indicates that all trunk groups are valid provided the Modify Tandem Calling Party field on the ISDN Trunk Group screen is set to y. No digits are deleted from the received calling party number. This is the default value.
108
November 2010
Screen Reference
Insert
Valid Entry Any combination of digits 0 to 9, up to 16 digits. The '+' sign is also valid. blank Usage A valid number between 1 and 16 to indicate the number of digits to insert.
Indicates that all trunk groups are valid provided the Modify Tandem Calling Party field on the ISDN Trunk Group screen is set to y. The received calling party number is not prefixed with any digits. This is the default value.
Location
The description of the Location field on the AAR and ARS Digit Analysis Table, AAR and ARS Digit Analysis Table, and Dial Plan Analysis Table screens is modified as follows:
Valid Entry 1 to 250 Usage (Depending on your server configuration, see Avaya Aura Communication Manager System Capacities Table, 03-300511.) The location of the endpoint that is dialing the digits. See the Location sections in Avaya Aura Communication Manager Feature Description and Implementation, 555-245-205, for the other ways to assign a location, and for a list of features that use location. Phones dialing from this location use the entries in the Call Type Digit Analysis Table. If there are matching entries in the telephones location, those entries are used. If there are no matching entries in the phones location, the Communication Manager tries the entries in location all. If the Multiple Locations field is disabled, the value of the Location field is all.
all
November 2010
109
Numbering-Public/Unknown Format and Numbering-Private Format

Overview of Numbering-Public/Unknown Format and Numbering-Private Format screens
In Communication Manager 5.2.1 and later releases, you must administer the extensions of all calls traversing SIP trunks in the appropriate private and public numbering tables on the Numbering-Public/Unknown Format and Numbering-Private Format screens. You must also configure the private and public numbering tables in the Numbering-Public/Unknown Format and Numbering-Private Format screens for all extensions. You must populate the calls to extensions terminating on a SIP integrated Modular Messaging in the appropriate NumberingPublic/Unknown Format or Numbering-Private Format screens, and do not configure a prefix for the SIP trunk group by which the Modular Messaging is integrated.
Percent Full
The description of the Percent Full field on the AAR and ARS Digit Analysis Table , AAR and ARS Digit Conversion Table, Precedence Routing Digit Analysis Table, and Toll Analysis screens is modified as follows:
Value 0 to 100 Comments The percentage of system memory resources that have been used by the table. For details on the system memory resources, see Avaya Aura Communication Manager System Capacities Table, 03-300511.
Personal CO Line Group

The description of the Security Code field on the Personal CO Line Group screen is modified.
Security Code
The station security code that users must dial to retrieve voice messages and to use the Demand Print Message feature. Accepts from three to eight digits.
110
November 2010
Screen Reference
QSIG to DCS TSC Gateway

The following note is added to the description of the Subscriber Number field on the QSIG to DCS TSC Gateway screen.
Subscriber Number
Note: If the Subscriber Number is local, the form does not send any DCS messages over the listed Sig Grp/TSC Index. Therefore, you can put a block entry like '2xxx' with the understanding that if extension 2001 is local, no DCS message will be sent.
Station
The 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.
November 2010
111
System parameters customer options

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

Enables the user to use user-defined entries for the incoming and outgoing ISDN calls independent of the NSF value. The Usage Allocation Enhancements feature lets the user administer the non-unique Facility Type and Facility Coding combinations. It also enables the customer to reserve a minimum number of trunk members for the incoming and outgoing calls at all times. Note: The Usage Allocation Enhancements feature is helpful outside the US, where the default Network Facilities available in the system are not very useful.
System Parameters Port Networks

The 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 the System Parameters Port Networks screen.
Terminating Extension Group

The description of the Security Code field on the Terminating Extension Group screen is modified.
Security Code
112
November 2010
Screen Reference
Trunk Group: Protocol Variations

The Identity for Calling Party Display field is added on the Trunk Group: Protocol Variations screen.
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 when both the From and P-Asserted-Identity headers are available.
Valid Entry P-AssertedIdentity Usage If a call is terminating at SIP, H.323, or DCP stations, or at outgoing H.323 or SIP trunk, Communication Manager displays the name and Calling Party number from the PAI header instead of the FROM header. This is the default value. If a call is terminating at SIP, H.323, or DCP stations, or at outgoing H.323 or SIP trunk, Communication Manager displays the name and Calling Party number from the FROM header instead of the PAI header.
From
Uniform Dial Plan Table

The description of the Percent Full field on the Uniform Dial Plan Table screen is modified as follows:
Percent Full
Displays the percentage (0 to 100) of the memory resources allocated for the uniform dial plan data that are currently being used. For details on the system memory resources, see Avaya Aura Communication Manager System Capacities Table, 03-300511.
Usage Allocation Enhancements

Enables the user to use user-defined entries for the incoming and outgoing ISDN calls independent of the NSF value. The Usage Allocation Enhancements feature lets the user administer the non-unique Facility Type and Facility Coding combinations. It also enables the customer to reserve a minimum number of trunk members for the incoming and outgoing calls at all times.
November 2010
113
Note: The Usage Allocation Enhancements feature is helpful outside the US, where the default Network Facilities available in the system are not very useful.
Vector Directory Number

The description of the After Xfer or Held Call Drops field on the Vector Directory Number screen 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 on hold drops or the call is transferred and the Timed ACW feature is active. This replaces the Available mode.
Valid Entry y Usage Communication Manager places an agent in the Timed ACW state if a caller on hold disconnects or the call is transferred, in addition to the existing conditions for Timed ACW. Communication Manager continues with the existing operation. This is the default value.
Upgrades
The following changes apply to the Upgrading to Avaya Aura Communication Manager Release 6.0.1, 03-603560.
114
November 2010
Index A
A175 Desktop Video Device .......................................81 AAR and ARS Digit Analysis Table ...........................102 add media-gateway ....................................................24 Add Signaling Group field descriptions .................38, 49 Add Signaling Group field descriptions for IPv6 .........62 Add Trunk Group Page 1 field descriptions Communication Manager Messaging Federal .....50 Add Trunk Group Page 1 field descriptions for IPv6 . .63 Add Trunk Group Page 2 field descriptions ..........51, 64 Add Trunk Group Page 3 field descriptions ..........51, 65 Add Trunk Group Page 4 field descriptions ..........52, 65 Adding a coverage path for messaging ...........43, 56, 70 Adding a signaling group for direct SIP integration .... 38 Adding a signaling group for direct SIP integration for Communication Manager Messaging Federal 48 Adding a signaling group for messaging ....................61 Adding a station ..............................................44, 57, 71 Adding a trunk group ..................................................63 Adding IP address in IPv6 format of Communication Manager ........................................................66 Adding node names for SIP integration ................37, 48 Adding node names IP ...............................................59 adding subscribers CMM; field description CMM field description editing subscribers CMM field description .....76 viewing subscribers CMM; field description . .76 Adding trunk group for direct SIP integration ........39, 50 Administering the Switch Link for direct SIP integration ............................................................45, 57, 71 Administrator guide changes ......................................94 After Xfer or Held Call Drops ....................................114 Agent LoginID ...........................................................104 Alarms ........................................................................99 Assigning an Analog Trunk Port .................................17 Assigning members from more than one signaling group to one SIP trunk group ..................................21 Assigning synchronization reference ..........................14 Attendant Console ....................................................104 Avaya 1000 Series Video Conferencing endpoint ...............................82 Avaya Branch Gateways changes .............................31 Call forward override ..................................................96 Call Park ...............................................................17, 97 parking call using TAC .........................................17 Change Route-Pattern field descriptions ........42, 54, 68 change synchronization ..............................................25 Changing a route pattern ................................41, 54, 68 Changing AAR analysis ..................................44, 56, 70 Changing IP network region .................................42, 55 Changing private numbering ...........................41, 53, 67 Changing the IP Codec Set .............................43, 55, 69 Changing the IP Network Region ...............................69 Clock Synchronization over IP ........................11, 12, 15 administration .......................................................12 detailed description ..............................................11 interactions ...........................................................15 screens ................................................................12 Communication Manager changes .............................11 Communication Manager Messaging R6.0.1 Embedded direct SIP integration to Communication Manager R6.0.1 .............................................37 Condition code ...........................................................96 Considerations Administrable Language Displays ........................97 CPN Len ...................................................................108 CPN Prefix ................................................................108 Creating a hunt group for messaging ..............40, 52, 66
D
Defining IP interfaces for Processor Ethernet ............60 Delete .......................................................................108 Deluxe paging branch gateways ..................................................16 Deluxe paging for analog trunks .................................16 disable synchronization ..............................................26 disable synchronization-switch ..................100, 102, 114 Disabling synchronization ...........................................15 Display between Locations with these Display Parameters ....................................................21 display synchronization ..............................................25 documentation and procedure updates ......................93 download RDTT .........................................................93 downloading Reliable Data Transport Tool ...............................93 Drop Parking User From the Call After Timeout .......105
C
Call Admission Control ...............................................34
November 2010
115
E
enable synchronization ...............................................26 enable synchronization-switch ...................100, 102, 114 Enabling IPv6 format on the gateway .........................65 endpoint Avaya 1010 Video Conferencing .........................82 Avaya 1020 Video Conferencing .........................82 Avaya 1030 Video Conferencing .........................83 Avaya 1040 Video Conferencing .........................83 Avaya 1050 Video Conferencing .........................83 Enhanced Redirection Notification .............................97
list ars route-chosen .................................................102 list synchronization .....................................................25 listing all administered gateways ................................13 Location ....................................................................109
M
mailbox administration subscriber management ......................................73 Maintenance Commands Media Gateways and Servers ............................101 Media Path Status Test (#1374) ...............................100 Multiple signaling groups in one SIP trunk group . 19, 20 Detailed description .............................................19 screens ................................................................20 Multiple signaling groups in one SIP trunk group administration ................................................19
F
Feature Description and Implementation changes .....96 Feature-related system parameters ...........................16 Feature-Related System Parameters .......................105 filtering subscribers using filters; subscribers ......................................76
N
Number display - Short Number Display on Inter Location Calls ..............................................................21 Numbering-Private Format screen ............................110 Numbering-Public/Unknown Format screen .............110
H
Hardware ....................................................................81 Hunt Group ...............................................................106
I
Identity for Calling Party Display ...............................113 Incoming Call Handling Treatment ...........................107 Insert .........................................................................109 interactions, see interactions under individual feature names ............................................................98 interactions, see interactions under individual feature names\ ...........................................................15 introduction ...........................................................84, 88 IP interfaces field descriptions ....................................60 IP Network Region ..............................................15, 107 IP Signaling Group Far-End Status Test ...................100 IP Synchronization .....................................................23 IP-SYNC .....................................................................23 IPSI Connection Up Time .........................................112 IPv6 ............................................................................31 IPv6 overview for Communication Manager Messaging .......................................................................59 ISDN Numbering Calling Party .................................107
O
Overview of Emergency Calling .................................33
P
Passive Signalling Station ..........................................18 PE Interface acceptance test .....................................94 PE Interface configuration ..........................................94 Percent Full ................................................104, 110, 113 Personal CO Line Group ..........................................110 pingall command ...........................................................102 Port Station ..................................................................18 provisioning Session Manager and Communication Manager CAC together .................................35
R
RDTT download .........................................................93 Restarting the messaging application .............46, 59, 73 Restrict Calls ............................................................106
L
legal notice ...................................................................2
116
November 2010
S
Saving translations ..........................................45, 57, 71 Screen Reference changes ......................................104 screens, see screens under individual feature names 12 Security Code .....................................104, 106, 110112 Attendant Console ..............................................104 see also considerations under individual feature names ..................................................................15, 98 server baseline specifications, configuration, and options . . 86, 90 environmental specifications ..........................87, 91 front view ........................................................84, 89 physical specifications ....................................87, 92 rear view .........................................................85, 89 Session Manager .......................................................33 Setting feature access codes for messaging ..............47 Setting up IP synchronization ...............................13, 14 Setting up Passive Signaling Station ..........................17 Setting up the BRI trunk board ...................................14 Setting up the signaling groups ..................................20 signaling group .....................................................38, 48 SIP-SGRP (SIP Signaling Group) Error Type 258 ...................................................101 Special applications features ................................................................29 Station .......................................................................111 Station Security Code interactions ...........................................................98 status ip-synchronization ............................................27 subscriber list .............................................................75 subscriber; view viewing subscribers ..............................................74 subscribers; add adding subscribers ...............................................73 subscribers; new ..................................................73 subscribers; delete deleting subscribers removing subscribers ....................................75
subscribers; edit editing a subscriber ..............................................74 editing subscribers ...............................................74 Suppress alarming .....................................................95 switch link administer .................................................45, 57, 71 Sync ...........................................................................16 synchronization .........................................................114 Synchronization over IP .............................................16 System parameters customer options Usage Allocation Enhancements .......................112 System Parameters Port Networks ...........................112 system requirements for EMU ....................................98
T
Terminating Extension Group ...................................112 Trunk Group Protocol Variations .............................................113 trunk group for direct SIP integration ....................39, 50 Trunk Side XOIP Modem Support ..............................22
U
UDP-ARS Calls Considered Offnet ..........................105 Upgrade paths ......................................................29, 79 Usage Allocation Enhancements .......................112, 113 Use 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
November 2010
117

Avaya Aura Communication Manager Change Description Release 6.0.1

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Avaya Aura Communication Manager Change Description Release 6.0.1

Hochgeladen von

Copyright:

Verfügbare Formate

Avaya Aura Communication Manager Change Description for Release 6.0.

Release 6.0.1 03-603723 Issue 1 November 2010

Avaya Aura Communication Manager Change Description for Release 6.0.1

Avaya Aura Communication Manager Change Description for Release 6.0.1

Avaya Aura Communication Manager Change Description for Release 6.0.1

Contents Chapter 1: Introduction.............................................................................................................9 Chapter 2: Communication Manager changes.....................................................................11

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

Chapter 4: Communication Manager Session Manager interoperability...........................33

Avaya Aura Communication Manager Change Description for Release 6.0.1

Chapter 5: Communication Manager Messaging changes..................................................37

Avaya Aura Communication Manager Change Description for Release 6.0.1

Chapter 7: Documentation and procedure updates.............................................................93

Avaya Aura Communication Manager Change Description for Release 6.0.1

Avaya Aura Communication Manager Change Description for Release 6.0.1

Avaya Aura Communication Manager Change Description for Release 6.0.1

Avaya Aura Communication Manager Change Description for Release 6.0.1

Chapter 2: Communication Manager changes

Clock Synchronization over IP

Detailed description of Clock Synchronization over IP

Avaya Aura Communication Manager Change Description for Release 6.0.1

Communication Manager changes

Clock Synchronization over IP administration

Screens for administering Clock Synchronization over IP

Set up the Clock Synchronization over IP Synchronization over IP feature.

Avaya Aura Communication Manager Change Description for Release 6.0.1

Clock Synchronization over IP

Screen name Media Gateway

Purpose Set up IP synchronization on the gateway. Use for IP Sync

IP Network Region Set up IP synchronization on the network region.

ISDN-BRI Trunk Circuit Pack

Set up the BRI trunk board as a Synch Source.

Clock Synchronization over IP administration

Avaya Aura Communication Manager Change Description for Release 6.0.1

Communication Manager changes

Setting up IP synchronization for the gateway

Avaya Aura Communication Manager Change Description for Release 6.0.1

Clock Synchronization over IP

Interactions for Clock Synchronization over IP

Survivable remote and survivable core servers

Avaya Aura Communication Manager Change Description for Release 6.0.1

Communication Manager changes

Feature-related system parameters

Deluxe paging support for branch gateways

Deluxe paging for analog trunks

Avaya Aura Communication Manager Change Description for Release 6.0.1

Deluxe paging support for branch gateways

Setting up Passive Signaling Station for deluxe paging

Assigning an Analog Trunk Port

End-user procedure for Call Park

Avaya Aura Communication Manager Change Description for Release 6.0.1

Communication Manager changes

Passive Signalling Station

Avaya Aura Communication Manager Change Description for Release 6.0.1

Multiple signaling groups in one SIP trunk group

Analog Trunk port

Multiple signaling groups in one SIP trunk group

Detailed description of multiple signaling groups in one SIP trunk group

Multiple signaling groups in one SIP trunk group administration

Avaya Aura Communication Manager Change Description for Release 6.0.1

Communication Manager changes

Setting up the signaling groups

Avaya Aura Communication Manager Change Description for Release 6.0.1

Number Display - Short Number Display on Inter Location Calls