Support for Avaya one-X® Client Enablement Services

Last Updated : Mar 05, 2021 |
Prolog information
Metadata
Keywords:
Communication Manager uses Avaya one-X® Client Enablement Services (formerly known as Avaya one-X® Server) to configure and control a set of Communication Manager features. Client Enablement Services control alerting of any off-PBX telephones, on-PBX telephones, and the desk set by indicating which particular phone rings when a call is received. Each extension can support four one-X applications. The Client Enablement Services can extract information from Communication Manager. A SIP subscription is used as a transport mechanism between Client Enablement Services and Communication Manager. The SIP trunk is used for signaling and cannot be used to send voice traffic. The application data is passed in the message bodies of the Subscribe, Notify, and associated Response messages.
Communication Manager Release 7.0 and later supports 20 Client Enablement Services servers.
Note:
On-PBX phones require version 6.2 of Client Enablement Services.
You can use Class of Restriction (COR) to control the stations that have Client Enablement Services support. You can see the control status of a station using the status station command.
The Client Enablement Services feature provides a way to control ringing of multiple phones tied to one extension and to provide real time calling information for a synchronized call log. Each Client Enablement Services subscribe to one or more event packages.
The avaya-cm-one-x-call event package is used to convey control information from Client Enablement Services and the status information from Communication Manager. The avaya-cm-one-x-config event package conveys configuration information to a mobile client. The avaya-cm-one-x-call package conveys information in the bodies of SIP Subscribe, Notify, and Response messages. The message information is in XML format. Communication Manager provides administrative capabilities for Client Enablement Services feature. The Client Enablement Services feature supports the following:
Static Call Handling
By using this feature, the server can provide phone numbers from one mobile phone and maximum 3 off-PBX or on-PBX telephones. The server can control alerting of any off-PBX telephones, on-PBX telephones, and desk sets. By using the Static Call Handling feature, the server indicates whether a particular phone must ring or not when an incoming call is received. A static mapping is used when a trigger mapping fails due to loss of connectivity between Communication Manager and Client Enablement Services.
Triggered Call Handling
When this option is active, an incoming call does not alert a desk set or an off-PBX or on-PBX telephone. Communication Manager contacts Client Enablement Services with substantial information to apply pre-screening rules to each incoming call. Client Enablement Services responds to Communication Manager with a list of the phone numbers to alert. The phone numbers can be any combination of a desk set extension, one mobile phone, and maximum 3 other off-PBX or on-PBX phone numbers.
Call Progress Reporting
Client Enablement Services uses this feature to receive a report on calls to and from a station with the one-X application. The report is generated when a station:
  • initiates an outbound call
  • receives a call
  • answers a call
  • ends a call
Note:
The report generated is not a Call detail Recording (CDR) report.
Extended Access
The off-PBX telephones use this feature to invoke a subset of Communication Manager features by dialing a DID number. These numbers are then converted in to Feature Name Extensions.
Note:
Extended access is inapplicable for the on-PBX telephones. The on-PBX telephones invoke features directly by activating relevant feature buttons or by dialing the Feature Access codes.
Autonomous Operation
Autonomous operation occurs when there is a loss of communications between one-X server and Communication Manager. During autonomous operation, Call Handling is active and Triggered Call Handling and Call progress Reporting are inactive. The Static Call Handling profile is used when the Triggered Call Handling fails. When no Static Call Handling profile exists, an incoming call alerts only the desk set.
To ring an on-PBX destination extension, call routing is determined by the following rules:
  • Any extension that represents a group (for example, hunt group.) is not routed.
  • An extension that is under One-X control is routed, but none of the one-X destinations for that extension is routed.
  • An extension that has any OPTIM application is routed, but none of the one-X application numbers for that extension are routed.
    Note:
    The Off-premises station (OPS) SIP phone is also routed.
  • An extension that has any form of call-forwarding or coverage or circular station hunting is routed directly to that extension and ignores the forwarding or coverage or hunting treatment for that extension.
  • Bridged appearances of the on-PBX destination extension are not notified.
  • Call pickup groups or team button members with on-PBX destination extension are not notified about a ringing call, and are unable to pickup that calls.
  • Intercom calls are routed, but not with any automatic answer if enabled.
For more information, see Administration for Avaya one-X® Client Enablement Services.
Related links
Administration for Avaya one-X Client Enablement Services