MDA limitations for digital and analog endpoints

Last Updated : Sep 23, 2020 |
Prolog information
Metadata
Keywords:
MDA is not supported for analog and digital phones because of the following reasons:
  • For MDA, the TN must be unique in the cluster:
    For digital and analog endpoints, the TN is the physical port ID of the phone. The first half of the TN indicates the MGC and the other half indicates the port ID of the line card on that MGC. Registering two or more Device Adapter digital or analog endpoints with the same TN is not supported because the TN is an identifier for a single, hardwired connection on a line card.
  • A user cannot modify the TN of an analog or digital endpoint:
    Unlike an analog or digital endpoint that have a fixed, physical TN, a UNIStim endpoint has a virtual or logical TN that is used for device tracking. The UNIStim endpoint does not have a physical line card interface point or MGC. This allows a user to modify the TN of a UNIStim endpoint and register as the intended user. Note that after the user modifies the TN, the user must restart the endpoint.
    A system administrator can also modify the station definition for the UNIStim endpoint on Device Adapter and Communication Manager.
    Because the digital and analog endpoints have a fixed TN, a user cannot modify the TN. Hence, there is no mechanism to log in as a different TN or log in again with the same TN.
  • Digital and analog endpoints do not have the ability to block re-registration attempts to re-acquire the TN:
    The Device Adapter core software that is shared by all endpoints can block re-registration attempt of an endpoint until the user re-registers the endpoint by manually logging in the endpoint.
    However, for digital and analog endpoints, there is no mechanism to prevent an MGC from immediately trying to re-register a digital or analog endpoint that gets unregistered. If a 96x1 or other SIP device tries to sequentially register, Session Manager unregisters a currently registered digital or analog endpoint. The MGC of this digital or analog endpoint immediately sends a SIP re-registration request to Session Manager, and repeats the re-registration attempt until the registration succeeds. This process unregisters the 96x1 or other SIP device.