Request to Talk (RTT) for 1:1 and Ad hoc Calls

The request to talk (RTT) feature key setting lets a caller send a message requesting a call back when the call recipient is busy on another call.  This option helps users who act as dispatchers to keep track of callers when they receive calls at a very high volume.  The feature key must be enabled for the caller and all recipients and is available for Android users.

Enable Feature Key 

It's best to enable the feature key on a feature key template and add users to the template.  That way, all appropriate users will have this feature key enabled. 

Please note that there is no indication on the client screens that this feature key has been enabled. 

Send an RTT Message

Send an RTT message to an unavailable call recipient. 

When an Android user attempts a PTT call to another user who is on another call, they will see the popup message that the contact(s) are busy along with the option to "Request Call." Selecting "Request Call" sends a message to the intended recipient(s).

Receive an RTT Message While in Call

RTT message delivered to an Android Smartphone

The intended recipient will see a new message notification, as shown.  While in call, they may navigate to the message tab to see

RTT message delivered to a D-Pad Device

D-Pad devices will not receive a notification, but the call back request will appear in the message tab.

RTT message delivered to an iOS device

iOS devices cannot send an RTT but they may receive them while in call.  Just as with the Android devices, they get a notification across the top of the screen and they may see the entire message, along with the time stamp, on the Messages tab.

RTT message delivered to a PC Client

Please note that the PC Client user must navigate back to the contact to call the user who left the request to talk message.  They cannot make a call to the user from the message tab. 

On a PC Client, the message banner appears and the message tab will turn red to indicate that a message is waiting.