Managing registered devices is an important part of maintaining a reliable VoIP environment, especially when an account can be used on multiple devices.
With the latest update, we have added a new Unregister option to the screen displaying users currently registered with the switch. This allows administrators to manually remove a device registration directly from the VSM4 interface without having to wait for the device to unregister itself.

Why is manual unregister useful?

A SIP device normally unregisters from the switch when the user logs out, closes the application correctly, or when the registration expires. However, there are situations where a device can remain registered on the switch even though it is no longer actively being used.
For example, a device may lose its network connection, the application may be terminated unexpectedly, or a test device may be closed without sending a proper SIP REGISTER request with an expiration of 0.
In such cases, the switch may continue to treat the device as registered until the registration expires.
The new Unregister option allows the administrator to immediately remove such a registration.

Prevent unwanted call forking

One common use case is testing an account on multiple devices.
If the same account is registered on two or more devices, an incoming call may be sent to all active registrations. This can result in call forking, where the call is delivered to multiple devices instead of a single intended device.
For example:

• Device A is registered with the account.
• Device B was previously used for testing and is still registered.
• A new call is made to the account.
• The switch sees both registrations and sends the call to both devices.
  If Device B is no longer required, the administrator can simply select its registration and use Unregister.
  This makes it possible to quickly return the account to a single active registration without waiting for the previous registration to expire.

Useful during push notification testing

Manual unregister is also particularly useful when testing push notifications and incoming VoIP calls.
Consider a situation where a mobile application is closed, but the switch still has an active SIP registration for the device. If the registration has not expired or the application did not properly unregister, the switch may continue to consider the device available.
This can interfere with push notification testing because the switch may attempt to use the existing SIP registration instead of triggering the expected push-related flow.
By manually unregistering the device, the administrator can simulate the device no longer being registered and repeat the test from a clean state.

Troubleshooting stale registrations

The feature can also be useful when troubleshooting situations where a user appears to be registered even though the corresponding device is no longer online.
Instead of waiting for the registration to expire, an administrator can remove the stale registration immediately and check whether the problem is resolved.
This can be especially helpful when:

• a device was switched off unexpectedly;
• an application crashed or was force-closed;
• the network connection was lost;
• a device was replaced;
• an account was moved to another device;
• an old test device is still registered;
• multiple registrations are causing unexpected call routing.

A faster way to manage active registrations

Previously, resolving these situations could require waiting for the registration to expire or manually restarting/re-registering the device.
The new Unregister option provides administrators with direct control over individual registrations from the VSM4 interface.
This makes the registered users screen not only a monitoring tool, but also a practical troubleshooting tool for managing active SIP registrations.

In summary

The new Unregister option provides a quick way to:

• remove unwanted or stale device registrations;
• prevent unwanted call forking during testing;
• switch an account between test devices more easily;
• troubleshoot registration-related issues;
• prepare a clean environment for push notification testing;
• avoid waiting for registration expiration.

It is a small addition to the VSM4 interface, but it can significantly simplify day-to-day administration and testing of VoIP and mobile applications.