Stop Rejected Calls from Ringing Other Endpoints

The same extension can be signed in on more than one place at once. Each of those places is an endpoint: a desk phone, the mobile app, the desktop app, or the web client where your extension is currently registered. When a call comes in, it normally rings every endpoint together.

By default, declining that call on one endpoint does not stop the others: the call keeps ringing everywhere else you are signed in until someone answers or the caller gives up. Turning on the setting below changes that, so a rejection on any single endpoint clears the call from all of them at once.

Note

This is a personal setting on your own extension. It only affects your endpoints, not anyone else’s, and each user turns it on for themselves.

Turn on all-reject mode

1. Sign in to the Cloud Voice App Web Client and open Preferences > Features.

2. Find the Call section and tick All Reject Mode for Endpoints.

   

3. Select Save. The change takes effect on the next incoming call; there is no need to sign the other endpoints out.

What changes

After this is enabled, rejecting an incoming call on one endpoint stops every other endpoint from ringing. The caller is then sent to whatever you have defined as your When Busy destination, found under Preferences > Presence > Call Forwarding.

Caution

With all-reject mode on, a rejection immediately triggers your When Busy forwarding rule. Check that destination before you rely on this feature: if When Busy is set to hang up (or is left unset), rejecting a call ends it for the caller instead of, for example, sending them to voicemail. Set When Busy to the outcome you actually want the caller to hear.

Tip

A common setup is to point When Busy at your voicemail. That way a rejected call is offered a way to leave a message instead of being dropped.