Instance cleanup¶

SIPIS automatically removes stale device-token pairs and stale SIP client instances. The main cleanup cases are described below.

iOS reinstallation¶

On iOS, app reinstallation may keep the VoIP push token (mIncomingCall) unchanged while the regular remote notifications token (mOther) changes. SIPIS detects this stale token-pair buildup, removes the older pair, and if no device-token pairs remain for the instance, switches the instance to Off and later deletes it once it becomes idle.

Invalid or expired push token reported by PNM as `404 Not Found`¶

A 404 Not Found response from PN Mediator means the reported push token is no longer valid or has expired, typically after app uninstall or reinstall. SIPIS removes the corresponding device-token pair from the affected instance, and if that was the last remaining pair, switches the instance to Off and later deletes it once it becomes idle.

App stopped communicating with SIPIS for too long¶

SIPIS also removes stale instances whose client app has stopped refreshing its state with SIPIS for longer than the configured maximum age. In that case, SIPIS switches the instance to Off and later deletes it once it becomes idle.

Instance remained not registered for too long¶

If an instance stays unregistered for longer than the configured not-registered maximum age, SIPIS switches it to Off and later deletes it once it becomes idle.

MaxAge: 3 days
PremiumMaxAge: 7 days
NotRegisteredMaxAge: 12 hours

Note

SIPIS may also perform additional cleanup in other situations, for example when too many instances with the same selector prefix exist. This can happen during repeated reinstall cycles in development or QA environments.