Configuring Avaya Device Adapter endpoint in System Manager

Last Updated : Jan 03, 2023 |
Prolog information
Metadata
Keywords:
The following procedure is an example of a typical Avaya Device Adapter endpoint configuration. For the full procedure, refer to the respective product specific documentation.
Before you begin
Install and configure the following Avaya Aura® components:
  • System Manager
  • Session Manager
  • Communication Manager
  • Avaya Breeze servers
  • Avaya Device Adapter Snap-in
  • Device Adapter Media Gateways
    Note:
    For information on Device Adapter media gateways, see Device Adapter administration in System Manager.
  1. Log on to System Manager with the appropriate administrative credentials.
  2. Click UsersUser ManagementManage Users.
  3. Click New.
  4. On the User Profile | Add page, click IdentityBasic Info and fill the following mandatory information:
    1. In Last Name, type the last name of the user.
    2. In First Name, type the first name of the user.
    3. In Login Name, type the user's extension number followed by the user's domain.
  5. On the Communication Profile tab, click Communication Profile Password.
    1. In the Comm-Profile Password dialog box, in Comm-Profile Password, type the communication profile password.
    2. In Re-enter Comm-Profile Password, retype the communication profile password.
    3. Click OK.
  6. On the Communication Profile tab, in the left panel, select Communication Address and click New.
    1. In the Communication Address Add/Edit dialog box, in Type, select Avaya SIP.
    2. In Fully Qualified Address, type extension number followed by domain and click OK.
  7. On the Communication profile tab, in PROFILES, click Session Manager Profile toggle button to enable the profile.
    1. In the SIP Registration section, in Primary Session Manager, select a Primary Session Manager.
      ADDITIONAL INFORMATION:
      It is optional to set values for Secondary Session Manager and Survivability Server.
    2. In the Application Sequence section, in Origination Sequence, select the start sequence.
    3. In Termination Sequence, select the stop sequence.
    4. In the Call Routing Settings section, in Home Location, type home location.
    5. In Call History Settings section, select the Enable Centralized Call History checkbox to enable callers lists and redial lists for Unistim phones.
  8. On the Communication profile tab, in PROFILES, click CM Endpoint Profile toggle button to enable profile.
    1. In System, select the appropriate Communication Manager server.
    2. In Template, type the template of the CS1000 phone. Following are the templates of the CS1000 phone.
      ADDITIONAL INFORMATION:
      The Template field identifies the family of the CS1000 phone.
      ADDITIONAL INFORMATION:
      • For all Unistim Phones, select CS1k-IP_DEFAULT_CM_10_1.
      • For Analog Phones hosted by Media Gateway, select CS1k-ana_DEFAULT_CM_10_1.
      • For Aries Digital Phones (2col) (or 1col for phones similar to M2008 - 1 column of keys, 2col for phones similar to 2616 - 2 columns of keys), select CS1k-1col_DEFAULT_CM_10_1.
      • For Taurus Digital Phones (for example M3901-M3905), select CS1k-39xx_DEFAULT_CM_10_1.
      • For Unistim Contact Center agents, select CS1k-IPCC_DEFAULT_CM_10_1.
    3. In Set Type, type the correct model of the phone.
      For example, 2050.
    4. In Terminal number (TN), type the number required for phone registration.
      ADDITIONAL INFORMATION:
      TN is a legacy CS1000 identifier that consists of four numbers:
      • first number (loop) - multiple of 4.
      • second number (shelf) - 0 or 1.
      • third number (card) - in range 0-15.
      • fourth number (unit) - in range 0-31.
      Note:
      • In case of Device Adapter Unistim phones, TN is used only as an identifier and you can choose any free TN.
      • For Digital and Analog phones, TN describes their physical connection.
      • The first two numbers of the TN identify Device Adapter Media Gateway as configured in the System Manager inventory. The third number represents card number in the Media Gateway (position where corresponding DLC or ALC is placed). The fourth number represents Unit number (twisted pair cable in cable pack connected to the corresponding card).
    5. In Extension, do the following to add an extension number:
      ADDITIONAL INFORMATION:
      • In Extension, type the extension number and click editor icon to modify the corresponding CM station.
        Note:
        The extension number should be the same as used in Communication Address and Basic Info in the Identity tab.
      • In the New Endpoint dialog box, ensure that the number in Terminal Number matches with the number in the CM endpoint profile.
      • Click Feature Options, type HFA as a text mnemonic to enable handsfree support.
        Note:
        For all supported options, refer to Appendix A: CS 1000 class of service and Avaya Aura® feature field mapping.
      • Click Button AssignmentMain Buttons and verify the configured buttons.
        Note:
        By default, the Main Buttons tab has three call-appr rows, which are equal to three MCR keys on the CS1000 phone.
      The value of System ID should match with the value configured in Avaya Device Adapter Breeze Attribute, which is blank by default. For more information, see System ID configuration issues.
      Leave the rest of fields with their default values.
  9. Click Commit.
Related links
Manually adding users and endpoints