nexMatrix is pleased to announce that dual extension registrations are now available on the Protel LTS premise PBX, as well the Protelity Multi-Tenant PBX platform.
This new feature addition allows you to register a second end point to an existing extension seat.  With the growing popularity of SIP apps for smartphones, this gives you the ability to run your mobile extension as a “clone” of your desk handset.  Or, you can designate a secondary desk extension that has full access to inbound calls.  You can manage this functionality from a feature code, which allows you to direct calls to the desk phone, the remote phone (mobile app or secondary phone), or both.  Both end points have complete functionality to place, receive and transfer calls, and they share the same voicemail box.  Deploying this feature does not count against the extension seat licenses that are available.

To activate this feature for a user, navigate to the extension settings pages:  Extensions/Modify Existing Extension and click on the Advanced Tab after you have selected the extension you want.  Check the box marked Enable, next to the Dual Registration label, save the changes, and execute a reload command.  You will now be able to register another phone or app to that same extension number by entering xxxr as the end point’s user name/registration name – just append the letter r to the extension number.  It will use the same SIP registration password as the existing extension.
To toggle call flow, dial the default feature code of 36 from either of the two end points.  The prompts will guide you to press 1 to enable the home extension, press 2 to divert calls to the remote extension, or press 3 to enable both devices to ring simultaneously.
Any call handling behaviors, including group subscriptions, number of rings before voicemail, forwarding, extension feature limits/permissions and concurrent call limit will apply to both end points.  Please note that it is not advisable to set up dual registration for any user that is part of a static ACD queue assignment, or for any user that may log in to an ACD queue as a dynamic agent, as this may cause unexpected queue behavior.  Please check with our support staff before deploying dual registration in combination with ACD queues.