Configuring Message Waiting

Last Updated : Jul 23, 2019 |
Prolog information
Metadata
Keywords:
Use this procedure to configure the Message Waiting functionality of Avaya Aura® Messaging (AAM). This configuration may be necessary if you are experiencing issues with connecting to AAM.
  1. Log on to System Manager by using the appropriate credentials.
  2. Navigate to ElementsRouting.
  3. Click SIP Entities.
  4. Add a new SIP Entity with the following information:
    ADDITIONAL INFORMATION:
    • Name — The name of the AAM server.
    • IP Address — The IP address of the AAM server.
    • Location — Select the appropriate location from the list. This was previously configured on the RoutingLocations screen.
    • Time Zone — Select the appropriate time zone.
    • Configure all other attributes as appropriate for your solution configuration.
  5. Add a new Entity Link with the following information:
    ADDITIONAL INFORMATION:
    • SIP Entity 1 — Previously configured Session Manager link.
    • SIP Entity 2 — Messaging link configured in the previous step.
      • Port — 5060 — If TLS is not enabled.
      • Port — 5061 — If TLS is enabled.
    • Protocol — TCP — If TLS is not enabled.
    • Protocol — TLS — If TLS is enabled.
    • Connection Policy — Trusted
  6. Click Commit.
  7. Select RoutingRouting Policy from the menu.
  8. Add a new Routing Policy with the following information:
    ADDITIONAL INFORMATION:
    • Name — Enter an appropriate descriptive name.
    • Click Select in the SIP Entity as Destination section. Select the SIP Entity you created in the previous step.
  9. Click Commit.
  10. Select RoutingDial Patterns from the menu.
  11. Add a new Dial Pattern for the Messaging Access Number with the following information:
    ADDITIONAL INFORMATION:
    Note:
    The Messaging Access Number was previously configured on Avaya Aura® Messaging in AdministrationMessagingSites.
    • Pattern — Dialed number or prefix.
    • Min — The minimum length of dialed number.
    • Max — The maximum length of dialed number.
    • SIP Domain — The solution domain.
  12. Click Add in the Originating Locations and Routing Policies section.
  13. Select the appropriate Location and Routing Policy from the list.
  14. Leave the remaining fields with default values.
  15. Click Commit.
  16. Repeat steps 9 to 14 for the Auto Attendant Number.
    ADDITIONAL INFORMATION:
    Note:
    The Auto Attendant Number was previously configured on Avaya Aura® Messaging in AdministrationMessagingSites.
  17. Select InventoryManage Elements from the menu.
  18. Add a new Managed Element with the following information:
    ADDITIONAL INFORMATION:
    • Name — A descriptive name for the element.
    • Type — Messaging
    • Node — The IP address of the AAM server.
  19. Select the Attributes tab.
  20. Enter the following attributes:
    ADDITIONAL INFORMATION:
    • Login — The System Manager administrative user.
    • Password / Confirm Password — The System Manager administrative password.
    • Messaging Type — AURAMESSAGING
    • Version — 6.3
    • Port — 636
  21. Click Commit.
  22. Log in to the SAT interface using the appropriate credentials.
  23. Enter the following commands:
    ADDITIONAL INFORMATION: > save translation
    > reset system 4
    > add media gateway
  24. Use the command change private-numbering 0 to change the private number configuration.
  25. Add the Ext Code 1100000 to Ext Len 7.
    ADDITIONAL INFORMATION:
    The entry should appear like the example below.
    Ext Len
    Ext Code
    Trk Grp
    Private Prefix
    Total Len
    7
    1100000
    2
     
    7
    Note:
    The trunk group should already be configured. Use the command list trunk-group to view trunk groups.
  26. Use the command change route-pattern 1 to change the route pattern.
  27. Enter the following information:
    ADDITIONAL INFORMATION:
    • Grp No: 2
    • FRL: 0
    • 1: DgtsFormat Subaddress: unk-unk
  28. Use the command change aar analisys 0 to change Automatic Alternate Routing (AAR).
  29. Add Messaging Access Number 1100000.
  30. Use the command add hunt-group 1 to add a hunt group.
  31. Enter the following information:
    ADDITIONAL INFORMATION:
    • Group Name: <A descriptive group name.>
    • Group Extension: 1100000
    • ISDN/SIP Caller Display: mbr-name
    • Coverage Path: 1
      Note:
      This is configured below. Use the command list coverage path command to list all configured coverage paths.
  32. Go to the second page of Hunt Group configuration.
  33. Enter the following information:
    ADDITIONAL INFORMATION:
    • Message Center: sip-adjunct
    • Voice Mail Number: 1100000
    • Voice Mail Handle: 1100000
    • Routing Digits: 8
  34. Use the command change feature-access-code to change the feature access code.
  35. Enter 8 in the Auto Alternate Routing (AAR) Access Code field.
  36. Use the command add coverage path 1 to configure the coverage path.
  37. Enter the following information:
    ADDITIONAL INFORMATION:
    • Point1: Use h1 to indicate hunt-group 1 created above.
    • Rng: 2
  38. Perform the following configuration for each endpoint.
    1. Use the command add station <extension_number>.
    2. Enter the following information:
      ADDITIONAL INFORMATION:
      • Type: <station type as applicable: CS1k-IP/CS1k-39xx/CS1k-1col/CS1k-2col/CS1k-ana>
      • Coverage path: 1
      • Page 6 SIP Trunk: aar
  39. Use the command save translation to save all changes.
  40. Return to System Manager.
  41. Add the same User in AAM User Management.
  42. Select InventorySynchronizationCommunication System from the menu.
  43. Select Incremental Sync data for selected devices.
  44. Click Now.
    ADDITIONAL INFORMATION:
    Important:
    Before adding the mailbox on System Manager it should have already been created on AAM and synchronized.
  45. Select User ManagementManage Users from the menu.
  46. Update the created Identity screen with the following information:
    ADDITIONAL INFORMATION:
    • Login — User login ID.
      Note:
      Check that Session Manager and CM Endpoint Profiles are filled in.
    • Select Messaging Profile.
    • System — The messaging system.
    • Select Use Existing Subscriber on System.
    • Mailbox Number — Enter or select the mailbox number.
    • Template — Use the default template name associated with the Avaya Aura® infrastructure.
    • Password — User password.
  47. Click Commit.