Troubleshooting MGC registration problems

Last Updated : Jun 05, 2019 |
Prolog information
Metadata
Keywords:
Digital or analog set requires provisioning in System Manager.
Important:
Troubleshooting MGC registration related problems may require stopping and starting MGC and the dsa service, which might have an impact on endpoint registrations and call handling.
For more information about the impact on endpoint registrations after stopping and starting the dsa service, see Maintenance commands.
Avaya recommends that you stop and start MGC and the dsa service during the maintenance period to minimize endpoint registration and call handling problems.
Before you begin
On System Manager, ensure that the following fields have appropriate values:
  • TN: The loop shelf card unit. Ensure that the loop shelf card unit matches the loop shelf of MGC.
  • SystemId: Ensure that the system ID matches the system ID that is configured in the Avaya Breeze® platform attribute.
  • Type (for digitals): Ensure the type matches the actual set type. For example, if you configure an endpoint type 2616, ensure that the actual physical phone is of type 2616.
  1. If the digital set appears as not registered, run the following command to verify if Device Adapter has detected the digital set:
    ADDITIONAL INFORMATION:
    Note:
    Analog units cannot be detected. Hence, Device Adapter tries to register all 16 units.
    ipeShow
    A message similar to the following appears:
    ipeShow 0-0-3
    The corresponding unit should appear as online.
  2. If the digital set is online, run the following command to verify the registration status:
    ADDITIONAL INFORMATION:
    endpointShow <loop>-<shelf>-<card>-<unit>
    If the output displays that the endpoint is not logged in, go to Step 3.
  3. Run the following command and examine the output to verify if there are any registered and available unallocated VGW channels:
    ADDITIONAL INFORMATION:
    vgwShow <loop>-<shelf>
    The following output appears: 
    [root@breeze5 ~]# vgwShow 0-0
    
 VGW TN      |      IP          | Port  |  Phone TN 
    
 000-00-11-00 |192.168.128.146 |  5392 |000-00-03-00
    
 000-00-11-01 |192.168.128.146 |  5394 |000-00-03-01
    
 000-00-11-02 |192.168.128.146 |  5396 |000-00-03-02
    
 000-00-11-03 |192.168.128.146 |  5398 |000-00-03-03
  4. If the phone does not appear in the Phone TN column and there are no more available channels, verify if more than one VGW channel is assigned to the same phone TN. If yes, then do one of the following:
    • Run the following commands to stop and start the dsa service:
      dasrvstart stop dsa
      dasrvstart start dsa
    • Restart MGC.
    • Report the problem to Avaya Support.
    • Provide more DSPs on the MGC. Upgrade or plug the second DSP DB into MGC to provide more DSPs. Switch from 32 to 96 DSP daughterboard.
  5. If your phone has a linked VGW channel or if there are free channels or if your phone appears in the list after you run the endpointShow command, then do the following:
    1. Unplug the set.
    2. Enable the dsa tDSA tCSDK debug logs.
    3. Run traceSM.
    4. Plug in the set.
    5. Analyze the traceSM output of both SIP and PPM.
    6. Provide the dsa.log and traces logs to Avaya Support.