Avaya Communication Manager Administrator's Manual page 1661

Hide thumbs Also See for Communication Manager:
Table of Contents

Advertisement

Early answer features will not work: Features that require early answer (e.g. to pass tones) will
not work with SBS calls. This is because when the signaling call is answered the bearer call hasn't
been launched yet. When the bearer call is first answered, it is for the SBS extension at the
terminating node. For example, authorization code collection on incoming calls and direct calls to
remote access will not work with SBS calls.
Network features sending tones when the bearer call answers will not work: When the bearer
call is answered it is for the SBS extension. The final endpoint user is not on the call to hear the
tones. For example, the DTMF notification when a network call is eligible to be transferred, such
as with Take-back and Transfer, will not be heard.
General System Feature Interactions
Media processor resources are not used by the SBS trunks, which only carry SBS signaling calls.
SBS bearer calls require media processor resources if IP trunks are used.
NOTE:
Voice quality degradation may be encountered if IP trunks are used for bearer calls.
Shuffling and hairpinning will work with SBS Bearer calls if IP trunks are used. The SBS bearer
call will be originated with the same "shufflable endpoint" characteristics as the real originator.
The contents of the Incoming Call Identification (ICI) display for an SBS call is obtained from the
SBS signaling call, not the bearer call.
The Class of Restriction (COR) of the SBS call originator is used to set up the SBS bearer call.
The SBS signaling and bearer calls are routed separately. Caution must be exercised when
applying Toll Restriction, Toll Analysis and Toll/Code restriction so as to not block calls that
should be allowed.
The Class of Service (COS) Trunk-to-Trunk Transfer permission will affect transfer of SBS trunk
calls just like it currently affects transfer of non-SBS trunk calls.
SBS calls will follow Station Hunting of the originally called party.
When
Tenant Partitioning
endpoints, SBS extensions, SBS trunk groups and the bearer trunk groups involved in any SBS
call.
SBS will work with Dial Plan Expansion (6- or 7-digit stations).
Standard Malicious Call Trace (MCT) on an incoming SBS call will record the bearer trunk call.
Attendant Related Items
Attendant features that will not work
Attendant Control of Trunk Group Access will not work with an SBS Trunk Group, since
it is a QSIG trunk group.
Centralized Attendant Service (CAS) will not work over SBS trunks, since CAS requires
Release Link Trunks (RLT). However, an incoming SBS call can be directed to a
centralized attendant over an RLT using CAS. Likewise, a Centralized Attendant can
extend a call, over an RLT, that then routes to an SBS trunk.
Administrator's Guide for Avaya Communication Manager
November 2003
is active in an enterprise, existing Tenant Partitioning rules apply to
Feature Reference
Separation of Bearer and Signaling
1661

Advertisement

Table of Contents
loading

Table of Contents