The following section is only applicable to the DSC Platform.
The NP Gateway only functions as expected if the appropriate connections and communications have been established between the DSC and the PSX Platforms, which means the following:
DSC must be able to exchange User Datagram Protocol (UDP) packets with the PSX
PSX Host and the underlying PSX Host Connection objects have to be connected (registered with the PSX)
In case of PSX alarms, verify the following:
The Host attribute of the PSX Host object resolves to the correct IP address on the affected DSC routing slot if you are using a hostname for the PSX Host (ping the PSX host from the DSC routing slot)
The NPGWPSXQUEUE_FULL (1625) alarm indicates that the DSC Platform is not processing the NP requests fast enough to keep up with the incoming requests, so some IAM messages are being forwarded without an NP lookup. This scenario can occur because of an unanticipated level of incoming call attempts, or because there is some kind of network or system degradation that is slowing the processing of NP requests. An analysis of the query rate from the NP Gateway statistics files can help narrow down the cause. If this is a capacity issue, consider adding more capacity by adding more PSX or NPGW cards.
For more information about NP Gateway-related alarms, refer to DSC Alarm Definitions.