A service-specific congestion overload condition has occurred. Probable Cause: This is the result of an operator-configured congestion overload value reached. This notification indicated a service-specific overload condition, typically the use of the service reaching some fraction of capacity. Once this limit is reached, the configured behavior is taken. This will cause certain older and/or dormant calls to be dropped in favor of newer calls. Note that this is similar to, but different than, the starCongestion notification. Typically the 'overload' condition will be configured to trigger at an earlier point. Since this is a service-specific notification, it is possible to receive multipe notifications for different services. Each Actions to be Taken: Verify that the congestion overload thresholds are correct; if the congested state is seem repeatedly, or for sustained periods of time, additional system capacity may need to be brought online. This system is cleared when the use of the specific resource falls below the configured limit. Condition Clear Alarm: A starOverloadServiceClear notification is sent when the service-specific overload condition is clear.