The Unified Number service features are a group of CSTA (Computer Supported Telecommunications Applications) capabilities that permit CSTA- and ONS-enabled applications to take on the responsibility of routing users' calls. This advanced CSTA service permits ONS-enabled applications to create, route, track, and provide call control for multiple inbound and outbound calls using CSTA Lotus Sametime Unified Telephony call control services for any device, located anywhere, for the entire duration of the call.
unified number functionality is especially suitable for mobile users with multiple associated devices, including external devices such as mobile telephones. It permits the application to hold, consult, transfer during consultation, single-step transfer, alternate, and conference the unified number call, even if one or both of the connected parties are located in the public network. In addition, it enables features such as:
Personalized workflow using rules-based call routing
Single point of contact on inbound and outbound calls
Setting preferred devices on inbound and outbound calls
Examples for CSTA and ONS-enabled applications are Telephony Control Server ComAssistant and UC (Unified Communications) Application.
Unified number should not be used in parallel with Hot Desking!
Supported CSTA Call Control Services
Unified number supports the following standard CSTA call control services:
Single Step Transfer Call
Generate Digits from any associated device
Standard CSTA call control events are sent for unified number calls, including the Offered event on inbound calls. An offered call suspends call processing for two seconds, which gives the CSTA-enabled application time to move the call to a specific associated device.
Each unified number subscriber should be provisioned for the following:
Call Forwarding - Unreachable (in case the link to the ONS-enabled application is not functioning)
Call Transfer (so transfers can be performed)
In addition, all caller ID services should be set properly.
For outbound calls, the subscriber uses the CSTA application interface to originate a call through any associated device, anywhere - for example, a PBX telephone, a mobile telephone, a hotel telephone, or a home telephone. For the called party, the call appears as if it were placed from the subscriber's business phone number.
For inbound calls, the CSTA application provides the functionality to correctly route these calls to any of the subscriber's preferred associated devices, including voice mail. For the calling party, the call appears as if it were answered from the subscriber's business phone number.
When an external associated device is involved in either type of call, Lotus Sametime Unified Telephony processes consultation calls initiated by the CSTA and ONS-enabled application such that a second call leg is not created to the gateway. An external device is any device connected through a SIP- or SIP-Q gateway - for example, a PSTN, another Lotus Sametime Unified Telephony system, or a third-party PBX.
Manually Triggered Consultation Calls for Internal ONDsParent topic: User Mobility
How to Provision a Subscriber for CSTA
Several features that can be manually invoked at an OND (Unified Number service Device) during an active unified number (One Number Service) call, result in establishing an additional call leg to the OND. For some of them - and if the involved OND is internal
(i.e. a registered subscriber device in the Lotus Sametime Unified Telephony) - the second call leg will be identified as a consultation call associated with the active unified number call. This enables subsequent manual feature activations for consultation calls.
The OND (Unified Number Service Device) Consultation feature allow a CSTA/ONS application to initiate a consultation call from an external OND (e.g. cell phone, home phone ...) without creating a second call leg to the OND device.
How to Provision a Subscriber for ONS
This procedure describes how to configure unified number (One Number Service) at the feature profile or subscriber level. Feature profiles, in turn, can be created and configured at the switch level or the BG (Business Group) level. At the subscriber level, the previously assigned feature profile can be overwritten to selectively enable, disable or modify the feature configuration for the particular subscriber. Those subscriber-level modifications effectively disconnect the individual service configuration from the underlying feature profile: a subsequent Reset Subscriber Lines
on the feature profile will not influence a disconnected service configuration.