Avaya 9600 Series Configuring
  1. Manuals
  2. Brands
  3. Avaya Manuals
  4. IP Phone
  5. one-X 9600 Series
  6. Configuring
Avaya 9600 Series Configuring

Avaya 9600 Series Configuring

Hide thumbs Also See for 9600 Series:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Instruction Manual, User Manual
Avaya Solution & Interoperability Test Lab
Configuring Avaya 9600 Series IP Deskphones running
Avaya one-X® SIP firmware with Avaya Aura® Session
Manager Release 6.1 and Avaya Aura® Communication
Manager Evolution Server Release 6.0.1 – Issue 1.0
These Application Notes describe the configuration of Avaya 9600 Series IP Deskphones
running Avaya one-X® SIP firmware with Avaya Aura® Session Manager Release 6.1 and
Avaya Aura® Communication Manager Evolution Server Release 6.0.1.
 Avaya Aura® Session Manager provides SIP proxy/routing functionality, routing SIP
sessions across a TCP/IP network with centralized routing policies and registrations for
SIP endpoints.
 Avaya Aura® Communication Manager serves as an Evolution Server within the Avaya
Aura® Session Manager architecture and supports SIP endpoints registered to Avaya
Aura® Session Manager.
These Application Notes provide information for the setup, configuration, and verification of
the call flows tested on this solution.
DJH Reviewed:
SPOC 07/08/2011
Abstract
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
1 of 51
SM6-1_CMES

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the 9600 Series and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Avaya 9600 Series

Summary of Contents for Avaya 9600 Series

  • Page 1 Manager Evolution Server Release 6.0.1 – Issue 1.0 Abstract These Application Notes describe the configuration of Avaya 9600 Series IP Deskphones running Avaya one-X® SIP firmware with Avaya Aura® Session Manager Release 6.1 and Avaya Aura® Communication Manager Evolution Server Release 6.0.1.

  • Page 2: Table Of Contents

    Define SIP Entities ....................24   4.4.   Define Entity Links ....................25   4.5.   Define Entity Link between Avaya Aura® Session Managers ....... 26   4.6.   Define Routing Policy ................... 27   4.7. Define Dial Pattern ....................28  ...
  • Page 3 4.11.   Synchronize Changes with Avaya Aura® Communication Manager ....35     Manual Configuration of Avaya 9600 Series IP Deskphones ....... 36   5.1.   Configuring IP Addresses ..................36   5.2.   Configure SIP Global and Proxy Settings ............. 38  ...

  • Page 4: Introduction

    Session Managers are deployed so that one Session Manager can serve as backup for the other in case of a network or Session Manager failure. As shown in Figure 1, Avaya 9600 Series IP Deskphones configured as SIP endpoints utilize the Avaya Aura® Session Manager User Registration feature and are supported by Avaya Aura®...
  • Page 5 Figure 1 – Sample Configuration DJH Reviewed: Solution & Interoperability Test Lab Application Notes 5 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 6: Equipment And Software Validated

    Release 6.0.1, SP1 Server Version R16x.00.1.510.1-18777 • Duplicated Avaya S8800 Servers • Avaya G650 Media Gateway Avaya 9600 Series IP Deskphones (with Avaya one-X® Release 2.6.4 SIP firmware) Avaya 9600 Series IP Deskphones (with Avaya one-X® Release 3.1, version 111510 H.323 firmware)

  • Page 7: Configure Avaya Aura® Communication Manager

    This section describes the steps needed to configure SIP trunks between Communication Manager Evolution Server and both Session Managers to support calls between SIP endpoints and other types of stations on Communication Manager. These instructions assume the Avaya G650 Media Server is already configured on Communication Manager Evolution Server. For information on how to administer these other aspects of Communication Manager, see References [6] through [10] in Section 9.

  • Page 8: Verify Off-Pbx Telephones Capacity

    Max Concur Registered Unauthenticated H.323 Stations: 100 … Maximum Video Capable IP Softphones: 0 Maximum Administered SIP Trunks: 4000 … DJH Reviewed: Solution & Interoperability Test Lab Application Notes 8 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 9: Verify Aar/Ars Routing Is Enabled

    Private Networking? y Usage Allocation Enhancements? y Processor and System MSP? y Processor Ethernet? y Wideband Switching? n … DJH Reviewed: Solution & Interoperability Test Lab Application Notes 9 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 10: Configure Trunk-To-Trunk Transfers

    IP Codec Set Codec Set: 2 Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.711MU G.729 Media Encryption none DJH Reviewed: Solution & Interoperability Test Lab Application Notes 10 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 11: Configure Ip Network Region

    Use the change ip-network-region n command where n is an available network region. Enter the following values and use default values for remaining fields.  Authoritative Domain: Enter the correct SIP domain for the configuration. For the sample configuration, “dr.avaya.com” was used.  Name: Enter descriptive name.  Codec Set: Enter the number of the IP codec set configured in Section 3.3.

  • Page 12: Configure Sip Signaling Groups And Trunk Groups

    Alternate Route Timer(sec): 6 Repeat this step to define a second signaling group to connect to the second Session Manager. DJH Reviewed: Solution & Interoperability Test Lab Application Notes 12 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 13: Add Sip Trunk Groups

    Unicode Name: auto Redirect On OPTIM Failure: 5000 SCCAN? n Digital Loss Group: 18 Preferred Minimum Session Refresh Interval(sec): 1200 DJH Reviewed: Solution & Interoperability Test Lab Application Notes 13 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...
  • Page 14 Telephone Event Payload Type: 120 Repeat this step to define a SIP trunk group to connect to the second Session Manager. DJH Reviewed: Solution & Interoperability Test Lab Application Notes 14 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 15: Configure Route Pattern

    4: y y y y y n rest none … DJH Reviewed: Solution & Interoperability Test Lab Application Notes 15 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 16: Administer Private Numbering Plan

    NUMBERING - PRIVATE FORMAT Ext Ext Private Total Len Code Grp(s) Prefix Total Administered: 3 Maximum Entries: 540 … DJH Reviewed: Solution & Interoperability Test Lab Application Notes 16 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 17: Administer Uniform Dial Plan

    SIP stations in the system. In the sample configuration, 5-digit extension numbers starting with “506xx” are used for extensions associated with the 9600 Series SIP Deskphones. Fill in the indicated fields as shown below and use default values for remaining fields.

  • Page 18: Configure Stations

    Hunt-to Station: STATION OPTIONS Time of Day Lock Table: Loss Group: 19 Message Lamp Ext: 50655 … IP Video? n DJH Reviewed: Solution & Interoperability Test Lab Application Notes 18 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...
  • Page 19 Note: Avaya 9601 IP Deskphones display only two local call appearance buttons when idle. So the number of entries shown below is not required to match the number of appearances displayed on the telephone.

  • Page 20: Verify Off-Pbx-Telephone Station-Mapping

    3.12. Verify Off-PBX-Telephone Station-Mapping Use the change off-pbx-telephone station-mapping xxx command where xxx is an extension assigned to a 9600 Series SIP Deskphone to verify an Off-PBX station mapping was automatically created for the SIP station. On Page 1, verify the following fields were correctly populated.

  • Page 21: Configure Avaya Aura® Session Manager

    4. Configure Avaya Aura® Session Manager This section describes the procedures for configuring Avaya Aura® Session Manager to support registrations of SIP endpoints. These instructions assume other administration activities have already been completed such as defining SIP entities for each Session Manager, defining the network connection between System Manager and each Session Manager, and defining Communication Manager as a Managed Element.

  • Page 22: Define Sip Domains

    Click New (not shown). Enter the following values and use default values for remaining fields.  Name Enter the Authoritative Domain Name specified in Section 3.4. For the sample configuration, “dr.avaya.com” was used.  Type Select “sip” from drop-down menu.

  • Page 23: Define Locations

    The screen below shows a Location used for SIP endpoints in the sample configuration. Repeat the steps to define a second location for Communication Manager. DJH Reviewed: Solution & Interoperability Test Lab Application Notes 23 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 24: Define Sip Entities

    The following screen shows the SIP Entity defined for Communication Manager. Note: IP addresses of the “procr” interface and Location fields have been partially hidden for security. DJH Reviewed: Solution & Interoperability Test Lab Application Notes 24 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 25: Define Entity Links

    Evolution Server and one of the Session Managers. Repeat this step to define Entity Link between Communication Manager and the second Session Manager. DJH Reviewed: Solution & Interoperability Test Lab Application Notes 25 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 26: Define Entity Link Between Avaya Aura® Session Managers

    4.5. Define Entity Link between Avaya Aura® Session Managers To provide redundancy and enable sessions to be alternatively routed through the second Session Manager in the case of a network failure, define an Entity Link between Session Managers. Expand Elements  Routing and select Entity Links from the left navigation menu.

  • Page 27: Define Routing Policy

    Other routing policies may be appropriate for different customer networks. The following screen shows the Routing Policy for Communication Manager Evolution Server. DJH Reviewed: Solution & Interoperability Test Lab Application Notes 27 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 28: Define Dial Pattern

    Click Commit to save the new definition. The following screen shows the Dial Pattern defined for routing calls to Communication Manager Evolution Server. DJH Reviewed: Solution & Interoperability Test Lab Application Notes 28 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 29: Define Application

    Leave fields in the Application Attributes (optional) section blank. The screen below shows the Application defined for Communication Manager Evolution Server. DJH Reviewed: Solution & Interoperability Test Lab Application Notes 29 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 30: Define Application Sequence

    Note: The Application Sequence defined for Communication Manager Evolution Server must only contain a single Application. Click Commit to save the new Application Sequence. DJH Reviewed: Solution & Interoperability Test Lab Application Notes 30 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 31: Add Sip Users

    4.10. Add SIP Users Add new SIP users for each 9600 Series SIP station defined in Section 3.11. Alternatively, use the option in Step 5 below to automatically generate the station after adding a new SIP user. To add new SIP users, expand Users  User Management and select Manage Users from left navigation menu.
  • Page 32 New to define a Communication Address for the new user. Enter values for the following required attributes:  Type: Select “Avaya SIP” from drop-down menu.  Fully Qualified Address: Enter same extension number as used for Login Name in Step 1.
  • Page 33 Select “(None)” from drop-down menu.  Home Location Select Location defined in Section 4.2. The screen below shows results from Step 4. DJH Reviewed: Solution & Interoperability Test Lab Application Notes 33 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...
  • Page 34 Communication Profile Password field in Step 2.  Port Select “IP” from drop down menu.  Voice Mail Number Enter Pilot Number for Avaya Modular Messaging or Avaya Aura® Messaging if installed. Else, leave field blank.  Delete Station on Unassign of Endpoint Enter to automatically delete station when Endpoint Profile is un-assigned from user [Optional].

  • Page 35: Synchronize Changes With Avaya Aura® Communication Manager

    4.11. Synchronize Changes with Avaya Aura® Communication Manager After completing these changes in System Manager, perform an on demand synchronization. Navigate to Elements  Inventory  Synchronization  Communication System. On the Synchronize CM Data and Configure Options page, expand the...

  • Page 36: Manual Configuration Of Avaya 9600 Series Ip Deskphones

    Mute c r a f t # (mute 2 7 2 3 8 #). The screen shown below will be displayed on the Deskphone. Note: These screens are from an Avaya 9630 IP Deskphone although all Avaya 9600 Series SIP Deskphones use the same basic settings and procedures.
  • Page 37 Once all fields in this section have been entered, press Save (not shown) to save the new values and return to the main Admin Procedures menu. DJH Reviewed: Solution & Interoperability Test Lab Application Notes 37 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 38: Configure Sip Global And Proxy Settings

    Press Select to edit SIP settings. Step 2: Highlight SIP Global Settings… on the SIP Settings menu and press Select. DJH Reviewed: Solution & Interoperability Test Lab Application Notes 38 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...
  • Page 39 Enter the following values and use defaults for remaining fields:  SIP Mode: Select “Proxied”.  SIP Domain: Enter appropriate domain name. For the sample configuration, “dr.avaya.com” was used.  Avaya Environment: Select “Auto”.  Reg. Policy Select “simultaneous” to support registration to both Session Managers.
  • Page 40 Admin Procedures menu. Step 7: Press Exit to complete the configuration. The phone will reboot. DJH Reviewed: Solution & Interoperability Test Lab Application Notes 40 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 41: Verification Steps

    6. Verification Steps 6.1. Verify Avaya Aura® Session Manager Configuration Step 1: Verify Avaya Aura® Session Manager is Operational Expand Elements  Session Manager and select Dashboard to verify the overall system status for both Session Managers. Specifically, verify the status of the following fields as shown below: ...
  • Page 42 Conn. Status for both links is “Up” as shown below: Click Show to view more information associated with the selected Entity Link. DJH Reviewed: Solution & Interoperability Test Lab Application Notes 42 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...
  • Page 43 SIP endpoints have successfully registered with both Session Managers. For example, the screen below highlights three SIP users who have successfully registered with both Session Managers. DJH Reviewed: Solution & Interoperability Test Lab Application Notes 43 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 44: Verify Avaya Aura® Communication Manager Operational Status

    6.2. Verify Avaya Aura® Communication Manager Operational Status Verify the status of one of SIP trunk groups on Communication Manager Evolution Server by using the status trunk n command, where n is one of the trunk group numbers administered in Section 3.6.2.
  • Page 45 11:37:12 SIP>INVITE sip:50655@135.9.228.230:5060;transport=tcp 11:37:12 SIP>IP/2.0 11:37:12 SIP<SIP/2.0 100 Trying 11:37:12 SIP<SIP/2.0 200 OK 11:37:12 G711MU ss:off ps:20 rgn:1 [135.9.228.217]:5004 rgn:1 [135.9.228.230]:5004 DJH Reviewed: Solution & Interoperability Test Lab Application Notes 45 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...
  • Page 46 11:43:23 SIP>INVITE sip:50655@135.9.228.230:5060;transport=tcp 11:43:23 SIP>IP/2.0 11:43:23 SIP<SIP/2.0 100 Trying 11:43:23 SIP<SIP/2.0 200 OK 11:43:23 G711MU ss:off ps:20 rgn:1 [135.9.228.217]:5004 DJH Reviewed: Solution & Interoperability Test Lab Application Notes 46 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 47: Call Scenarios Verified

     Repeat the above scenarios with calls originating from non-SIP stations on Communication Manager Evolution Server to a SIP endpoint. DJH Reviewed: Solution & Interoperability Test Lab Application Notes 47 of 51 SPOC 07/08/2011 ©2011 Avaya Inc. All Rights Reserved. SM6-1_CMES...

  • Page 48: Acronyms

    Look-ahead Routing Real Time Protocol System Access Terminal (Communication Administration Interface) Session Initiation Protocol SMGR Avaya Aura® System Manager (used to configure Session Manager) Trunk Access Code (Communication Manager Trunk Access) Transmission Control Protocol TCP/IP Transmission Control Protocol/Internet Protocol Transport Layer Security...

  • Page 49: Conclusion

    Finally, testing was performed to verify calls between SIP endpoints and other types of stations on Avaya Aura® Communication Manager Evolution Server were successful even when there were network connectivity issues or when one of the Session Managers was not available.

  • Page 50: Additional References

    Avaya IP Deskphones (SIP) 11) Avaya one-X® Deskphone SIP Administrator Guide. December 6, 2010. 12) Avaya one-X® Deskphone SIP for 9600 Series IP Telephones Administrator Guide, Release 2.6. June 7, 2010. 13) Avaya one-X® Deskphone SIP Installation and Maintenance Guide Release 6.1 for 9601 IP Deskphone, December 6, 2010.
  • Page 51 Application Notes. Please e-mail any questions or comments pertaining to these Application Notes along with the full title name and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at interoplabnotes@list.avaya.com DJH Reviewed: Solution &...

Table of Contents