Abstract: The invention provides a key system unit comprising a first interface suitable for connection to a plurality of local terminals and a control unit coupled to the first interface. The control unit is operative for receiving a user data signal from the first interface and routing the user data signal toward a selected destination. The control unit has a registry for storing status information, the status information including a local segment and at least one remote segment, the local segment providing a representation of the functional status of the key system unit, the remote segment providing a representation of the functional status of a remote key system unit. The information in the registry can be displayed on a display screen on a local terminal to provide the user with system status information on the local key system unit and the remote key system unit.

Abstract: The invention relates to methods and apparatus for determining whether a CPS should employ a standard interface or an unreliable network for routing telephone calls. The invention includes a telephone call switching apparatus which includes a routing engine configured to receive a telephone call from a terminal connected to the call switching apparatus and a switching matrix connected thereto. The telephone call includes a destination code. The routing engine is configured to receive the telephone call from a terminal or trunk line, determine an unreliable network route for the telephone call based upon the destination code, and provide a message to a call manager associated with the unreliable network route (via the switching matrix). The message includes the destination code. The routing engine is also configured to receive a response from the call manager; and route the call over the unreliable route if the response is affirmative.

Abstract: An OA&M system is provided for a network communication core having a switch, a controller, and a core configuration memory. All configuration information which is static (i.e., information which remains the same regardless of the configuration of the core) is placed off-core in a map file. Because of this, requests for information on the configuration of the core may often be satisfied without the need to query the core, thereby reducing core load. Further, this static information in the map file allows validation of requests for dynamic configuration information as well as requests for reconfiguration of the core. In other words, the static information assists in ensuring that requests are proper. The static information in the map file is presented as "list", "attribute", and "choice" features. This presentation facilitates the making of OA&M requests by a user. The features become arguments of functions in order to generate OA&M requests to the controller.