Avaya Communication Manager, Руководство администратора, Страница: 1659 / 1854

Feature Reference
Separation of Bearer and Signaling
Administrator’s Guide for Avaya Communication Manager 1659
November 2003
In the case of an SBS call, the data that is gathered and made available to the adjunct server will not
change. However, since each trunk group involved in an SBS call can be administered for CDR Reports:
y/n, there can be two CDR records for each SBS call. One record is generated for the SBS signaling call
and one record is generated for the SBS bearer call. There is no way to link the separate SBS signaling
and bearer CDR records.
Since there is no way to link the signaling and bearer CDR records, it may be preferable to only measure
the bearer calls, as they are most likely being billed for by a service provider. However, it must be noted
that the SBS bearer call is always answered (by the SBS Extension) even though the real called party
may not answer the SBS call. Also note that the parties on the SBS bearer call are not the actual
originating and terminating parties (they are ’dummy’ users internal to Communication Manager for the
sole purpose of originating and terminating the bearer call).
Call Management System (CMS/BCMS)
Considerations
A trunk group, Vector Directory Number (VDN), and/or hunt group is administrable to be measured for
CMS or Basic Call Management System (BCMS). An SBS call potentially can generate two separate
CMS/BCMS records: one for the SBS signaling call and one for the SBS bearer call.
The SBS bearer call will only be measured if the bearer trunk group is administered to be measured, and
the only events that will be measured on the bearer call will be the trunk (bearer) seize and idle.
The SBS signaling call will be measured if either the SBS signaling group is administered to be
measured, or if an endpoint on the SBS call is a measured object (e.g., an agent in a hunt group that is
administered to be measured). The events that will be measured on the SBS signaling call will include not
only the trunk (signaling) seized and idled events, but also any endpoint events (e.g., agent hold).
The SBS signaling and bearer calls will generate separate CMS/BCMS records with different Universal
Call IDs (UCIDs). There will be no way to link these separate records.
Interactions
Separation of Bearer and Signaling (SBS) provides a new type of trunk call (i.e. separated), and since
numerous types of trunks can be used to carry the bearer portion of the separated call, this feature affects
many Avaya Communication Manager features. Almost any feature that can interact with a trunk call
potentially interacts with SBS.
The following documents features that could interact with SBS calls. There may be still other featurs not
discussed here whose interaction with SBS is relatively minor.
Understanding the way SBS calls are configured internally is critical to understanding why certain
features can work with SBS calls, and others cannot. This general understanding will also help accurately
predict whether or not a feature not discussed here (e.g., a new feature) can successfully work with an
SBS call.