[Contents] [Prev] [Next] [Index] [Report an Error]

Detecting Hanging Terminations

Synchronization of termination information between the PG and the PGC is essential for traffic, maintenance, and charging purposes. If a termination does not exchange messages for a period of time, corresponding data for the termination might be mismatched on the PG and the PGC, and the termination can be hanging. Hanging terminations can consume resources that can be used for chargeable calls.

To detect possible hanging terminations, the PG uses a timer that begins when a message is exchanged for a specific termination. If the termination does not receive a message when the timer expires, the PG notifies the PGC. If the data on the PGC does not match the data on the PG, the PGC returns one of the following error messages to the PG:

Error Code #: 411 Name: The transaction refers to an unknown ContextID
Error Code #: 430 Name: Unknown TerminationID
Error Code #: 435 Name: Termination ID is not in specified Context

The PGC is responsible for correcting mismatches in data. For example, the PGC can subtract the indicated termination and clear associated contexts. The PGC can also audit the termination service state to check its records before taking further action.

[Contents] [Prev] [Next] [Index] [Report an Error]