The CCBS/NR (Call Completion to Busy Subscriber / on No Reply) feature provides subscribers the capability to activate an automatic callback if the called station is busy or is not answering an alerting call.
The calling to another subscriber wasn't successfully finished. The activated CCBS/NR feature works as follows:
If the called party was busy
Monitoring begins and the calling party hears a confirmation announcement that the request is received. The called party has no notification of the callback request.
As soon as the called party goes onhook, the calling party is notified of the called party's availability and is recalled. When the calling party answers, a new call to the original destination is automatically dialed.
If the called party did not answer the alerting call
Monitoring begins and the calling party hears a confirmation announcement that the request is received. The called party becomes available for callback after initiating some activity on the device, then transitioning to idle state.
As soon as the transition to the idle state occurs, for example, when the called party goes onhook, the calling party is notified of the called party's availability and is recalled. When the calling party answers, a new call to the original destination is automatically dialed.
When the called party becomes available to handle the call, the calling party receives a recall that provides the name and number of the called party. The information displayed is consistent with the settings for other features used to control delivery or suppression of calling and called party numbers, for example, calling name delivery blocking (CNAB). However, the callback must be invoked by a SIP subscriber in order for the displays to be provided.
During these requests, Lotus Sametime Unified Telephony supports service retention, which ensures that the CCBS/NR request continues to be active until the target of the request is alerted. However, for interswitch calls, the originating switch must support this functionality in order for it to operate.
The system administrator can assign one or both of the following to a subscriber:
The ability to activate a CCBS/NR request.
The ability to deny callbacks placed against the subscriber via the Deny Terminating Features attribute.
CCBS/NR is not only supported intraswitch between Lotus Sametime Unified Telephony subscribers, but also for the following interswitch scenarios:
Between subscribers on different Lotus Sametime Unified Telephony systemsNote:
Between a Lotus Sametime Unified Telephony subscriber and a SIP-Q gateway with a QSIG-compliant PBX subscriber.
In transit scenarios comprising Lotus Sametime Unified Telephony systems and SIP-Q gateways.
In version 5 of Lotus Sametime Unified Telephony the SIP-Q interface was enhanced to support incoming CC requests with path reservation signalling. This is required for proper interworking with certain legacy systems such as Hicom 300.
The OpenStage 20/20E/40/60/80, optiPoint 410/420 S, and optiClient 130 S support this feature.
Computer Supported Telecommunications Applications (CSTA) also supports activation of CCBS/NR requests.
This feature is formerly known as automatic callback or auto callback.
How to Enable CCBS (Call Completion to Busy Subscriber)
How to enable CCNR (Call Completion on No Reply)
Parent topic: Calling Services
Deny Terminating Features
RTP System Parameters
Certain aspects of CCBS (Call Completion on Busy Subscriber) and CCNR (Call Completion on No Reply) are controlled on a systemwide basis by RTP (Resilient Telco Platform) system parameters. Any changes made to these parameters affect all business groups and their members. Typically, these parameters are set during initial system configuration, to enforce global system policies and ensure proper feature interworking.