Media Gateway Controller registration of digital and analog stations

Last Updated : Feb 04, 2019 |
Prolog information
Note:
This section is applicable to all endpoints other than the UNIStim IP endpoints.
  • CS 1000 endpoint user experience
    The user is typically unaware that the endpoint is connected to a Media Gateway Controller (MGC) registered to a server providing call processing. All services are carried out invisibly, except under:
    • System fault conditions such as network failures.
    • Maintenance or administration operations that take the endpoint off-line.
    The MGC finds its controlling call server and registers itself. CS 1000 has the underlying software required to map messages to and from the units in the MGC correctly.
  • Device Adapter endpoint user experience
    The MGC finds its controlling call server and registers itself. However, in this case the controlling server is the Device Adapter, which:
    • Maps each device on the MGC by a Terminal Number or TN (legacy Loop, Shelf, Card, and Unit) into information which can be used to retrieve the station identity.
    • Registers the device by its SIP identity with the Session Manager.
    • Acts as a configuration retrieval interface with Session Manager and Communication Manager.
    • Completes any other aspects of the registration of the endpoint.
    Unlike the UNIStim endpoints, the non-IP endpoints historically have not needed to register individually. Doing so allows the endpoints the potential to accept new services and features provided by Communication Manager without reworking the architecture.