Avaya Communication Manager Administrator's Manual page 1665

•
ETSI MCT can not be invoked on an SBS call. This is because end-user activity drives
feature signaling only on the SBS signaling call, not on the SBS bearer call, and an SBS
trunk does not support ETSI protocol.
NOTE:
The normal MCT feature within Communication Manager will record the call as usual.
•
Calling Line ID Prefix information is ignored when transported in conjunction with an
associated bearer trunk.
•
Advice of Charge information received on an SBS bearer call is not displayed to the end
user. However, it is conveyed to the CDR port for the SBS bearer call record. Only SBS
trunk information affects end-user displays.
•
ETSI Network Call Deflection (NCD) will not work with an SBS call. For SBS, the
signaling used to control the call is in the SBS signaling call on the QSIG interface, while
NCD requires an ETSI interface which is only available on SBS bearer calls.
•
ETSI Network Call Transfer (NCT) will not work with an SBS call. For SBS, the
signaling used to control the call is in the SBS Signaling call on a QSIG interface, while
NCT requires an ETSI interface that is only available on the SBS bearer call.
•
Direct SBS calling into Remote Access will not work. Barrier Codes cannot be collected
for SBS calls to Remote Access because the SBS Bearer call has not yet been established
when such tones are prompted for or expected (in-band). However, an SBS call can
invoke Remote Access by means of a vector "collect" or "route-to."
•
SBS does not support Wideband Switching (NxDSO).
•
Russian Incoming ANI via button will not display the ANI received in the SBS bearer call
(only the ANI received on the SBS signaling call will be displayed to the end user).
•
Trunk "Flash" to get recall dial tone from a Central Office will not work because end-user
activity drives signaling on the SBS signaling call only, not the SBS bearer call. QSIG
Call Transfer functionality can be used instead.
•
R2 MultiFrequency Compelled (MFC) Intercept treatment must drop the SBS bearer and
SBS signaling calls, and will do so by applying the appropriate treatment to the call
originator based on what is received on the R2 MFC bearer call.
Networking features or capabilities that will work
•
Authorization codes can be collected when required on an outgoing SBS call (i.e. when
required to access the SBS trunk), since they are collected locally prior to seizing of the
outgoing trunk.
•
Calling Party Number (CPN) restriction may be administered for and/or signaled on both
the SBS signaling and SBS bearer calls. However, end-user displays (including any
restrictions) are populated from information carried in the SBS signaling call, not from
information in the SBS bearer call.
•
At an SBS Interworking node, DCS/DCS+ signaling on the non-SBS leg of the call will be
interworked to/from the SBS signaling call, to the extent that DCS-QSIG interworking
currently applies.
•
A DCS trunk may be used as the bearer trunk on an SBS call. However, any DCS
signaling information received on the Bearer call will be overridden by the QSIG
signaling information received on the SBS signaling call.
Administrator's Guide for Avaya Communication Manager
November 2003
Feature Reference
Separation of Bearer and Signaling
1665