Preparing Communication Manager for feature migration

Last Updated : Dec 31, 2020 |
Prolog information
Metadata
Keywords:
Note the following actions and information while preparing Communication Manager for feature migration:
  • Station Migration
    • Ensure there are no conflicts between existing Communication Manager extensions and migrated extensions
    • Administrator should configure Dialplan and Routing so that it satisfies all migrated extensions.
    • Review CS 1000 NARS, BARS, and CDP migration into Communication Manager AAR and ARS.
    • In case the number of migrated sets is less than the number of DNs on these sets, administrators should define an extension pool to be used to assign extensions for sets that does not win any DN as an extension.
  • Multiple Appearance DN
    • In the case that the number of DNs is greater than the number of sets, such a DN is translated as Virtual/XPORT Station type: 9408. See Configuring XPORT 9408 for more information.
  • Short Hunt
    • Short Hunting is generally translated as multiple call appearance buttons on the station.
    • When the short hunt is to a number that is not a call appearance (extension) of any station, the short hunt virtual station XPORT 9408 is created for the purposes of this feature.
      Example
      1. Assume that a user has Short Hunt on their endpoint.  
        User 0 Extensions:
        • on key 0 is 5381234
        • on key 1 is 5385000
        • on key 2 is 5385001
        • on key 3 is 5385002
        If these extra 3 DNs do not exist anywhere else in the CS 1000, then this can be changed to:
        User 0 Extensions:
        • on button 1 is 5381234, appearance 0
        • on button 2 is 5381234, appearance 1
        • on button 3 is 5381234, appearance 2
        • on button 4 is 5381234, appearance 3
        No need for XPort.
      2. Assume that some other user has Short Hunt on their endpoint but hunts to a MADN appearance of 5381234.
        User 0 Extensions:
        • on key 0 is 5381234
        • on key 1 is 5385000
        • on key 2 is 5385001
        • on key 3 is 5385002
        User 1 Extensions:
        • on key 0 is 5384321
        • on key 1 is 5381234
        If these extra 3 DNs do not exist anywhere else in the CS 1000, then this can be changed to:
        User 0 Extensions:
        • on button 1 is 5381234, appearance 0
        • on button 2 is 5381234, appearance 1
        • on button 3 is 5381234, appearance 2
        • on button 4 is 5381234, appearance 3
        User 1 Extensions:
        • on button 1 is 5384321, appearance 0
        • on button 2 is 5381234:
          • bridged appearance to call appearance 0 would be normal
          • bridged appearance to any call appearance is also valid
        No need for XPort. If the map was to a secondary DN, XPort is needed.
      3. Assume that some other user has Short Hunt on their endpoint but hunts to a MADN appearance of 5385000 that has no endpoint where this can be the station extension.
        User 0 Extensions:
        • on key 0 is 5381234
        • on key 1 is 5385000
        • on key 2 is 5385001
        • on key 3 is 5385002
        User 1 Extensions:
        • on key 0 is 5384321
        • on key 1 is 5385000
        If the short hunt DN is not a call appearance anywhere on the CS 1000, then this can be changed to:
        User 0 Extensions:
        • on button 1 is 5381234, appearance 0
        • on button 2 is 5385000, any appearance
        • on button 3 is 5385000, any appearance: it is possible that the button is not needed.
        • on button 4 is 5385000, any appearance: it is possible that the button is not needed.
        • (If the user is to put up to 3 calls on hold to answer a fourth, then all four buttons are needed.)
        User 1 Extensions:
        • on button 1 is 5384321, appearance 0
        • on button 2 is 5385000, any appearance
        XPORT Extensions:
        • on button 1 is 5385000, appearance 0
        • on button 2 is 5385000, appearance 1
        • on button 3 is 5385000, appearance 2
        • on button 4 is 5385000, appearance 3
        XPort is needed.
  • Call Waiting
    • The Call Waiting key is translated as a call appearance button on the station.
  • Privacy Release
    • Administrators should configure Communication Manager/System/System Parameters – Features/AUTOMATIC  EXCLUSION  PARAMETERS: Automatic  Exclusion  by  COS? Y
    • The ProVision/NMT toolsets COS #1 for all migrated stations.
    • Administrators should configure Communication Manager/System/Class Of Service: Number: 1 Automatic Callback: Y
  • Autodial
    • CS 1000 ADL key destination number is not translated to an autodial button during the migration. Phone users should configure it after the migration. These autodial buttons have no administratively configured number.
  • Call Forward Busy/No Answer/Make Set Busy
    • Call Forward Busy/No Answer/MSB features are translated to the Coverage feature.
    • It is represented by coverage path and coverage remote tables.
    • Redirect numbers that do not represent Directory Numbers in migrated extensions are treated as Coverage Remote entries:
      • TNB:
        • FDN
        • HUNT
      • ATT_DATA:
        • ATDN (in case of Customer redirection(RDR_DATA: FNAL/D) configuration is ATT)
    • For Redirect numbers representing Coverage Remote entries, dialplan/routing should be properly configured, and uniform dialplan should be taken into account.
    • The administrator should configure the following system parameters, call coverage/call forwarding and Maintain SBA At Principal: N
    • Short Hunting feature also may use Coverage Path in some special cases.
  • Call Pickup
    • Call Pickup is translated to pickup groups.
    • A pickup group only supports 100 extensions.
    • The administrator should allow Extended; Direct pickup in System Parameters Features.
    • ProVision/NMT toolsets COR #1/2/3/4 for all migrated stations.
    • Administrator should configure Communication Manager/System/Class Of Restriction with the exact correspondence of numbers and parameters:
      COR  Number:  1  Can  Be  Picked  Up  By  Directed  Call  Pickup? N Can  Use  Directed  Call  Pickup? N
      COR  Number:  2  Can  Be  Picked  Up  By  Directed  Call  Pickup? Y Can  Use  Directed  Call  Pickup? N
      COR  Number:  3  Can  Be  Picked  Up  By  Directed  Call  Pickup? N Can  Use  Directed  Call  Pickup? Y
      COR  Number:  4  Can  Be  Picked  Up  By  Directed  Call  Pickup? Y Can  Use  Directed  Call  Pickup? Y
  • Group Call Pickup
    • Group Call Pickup uses Extended Pickup groups.
    • User experience is changed for group call pickup.
    • To access another group, a user should enter Pickup Number from the Extended Pickup Group associated with the Pickup Group Number.
    • Pickup Group Index may not match with Pickup Group Number on CS 1000.
    • Extended pickup group supports only 25 groups within itself.
  • Message Waiting Indicator; Message/Inbox Key; Call Park
    • VoiceMail and Call Park deployment should be preconfigured and integrated with Aura.
    For more information about configuring the Park and Page service for the network, see the Avaya Aura® configuration documentation.
    For more information about deploying and configuring the voice mail system, see the documentation for deploying and configuring the voice mail system used with the Avaya Aura® cloud. The voice mail server used is dependent on interoperability with Communication Manager and not Device Adapter.
  • Message/Inbox Key
    • Fill the voice mail number of the user using ProVision.
    • Fill user communication profile ProVision table column: Endpoint Profile – Voice Mail Number using the voicemail system number with GRID editor after the NMT tool conversion.
  • Speed Dial, Hotline
    • Speed Dial and Hotline translates to abbreviated-dialing group lists.
    • Need to configure Abbreviated Dialing List1/2/3 Access Code.
    • Special hotline virtual station XPORT 9408 is created specifically for this feature.
Related links
Migrating the endpoint and MGC-related data