Feature Reference
Separation of Bearer and Signaling
1664
Administrator’s Guide for Avaya Communication Manager
November 2003
•
When an ACD call is transferred to an agent via an SBS trunk connection on another
system running Communication Manager, all associated call information currently
transported on a QSIG trunk will be sent on the SBS signaling call
•
All types of Service Observing will work on SBS calls as it does on non-SBS calls.
Best Service Routing
•
Polling by Best Service Routing (BSR) can use SBS signaling facilities as long as the
NCA-TSC version of BSR Polling is used and adequate resources are available. The
non-NCA-TSC version of BSR Polling may not work due to the SBS call setup delays.
•
BSR interflow over SBS trunks (including incoming call data forwarding and Enhanced
Information Forwarding) will be supported.
Vectors
•
Routing on Automatic Number Identification (ANI) by a vector can use SBS to route an
outgoing call. For an incoming SBS call, the Routing on ANI functionality will use the
ANI from the SBS signaling call.
•
Correct routing over SBS trunks will work when there is a vector step for routing on ANI
or II digits or a route-to number step and interflow is invoked.
•
Post-Connect in-band DTMF signaling for Call Prompting collect steps and Auto
Attendant functionality will work.
•
When CINFO Digit Routing occurs, and the call is routed over an SBS trunk, the
information will be tandemed with the call.
•
Vector Routing Tables may use SBS trunks for routing calls.
•
Incoming SBS calls will still provide VDN of Origin announcements (VOA) and displays
to the agent answering the call.
•
VDN Return Destination will work with SBS calls.
Networking Related Interactions
Networking features or capabilities that will not work
•
Authorization Codes cannot be collected on incoming SBS signaling or SBS bearer calls
(e.g., when required through administration of the incoming trunk group or when required
due to insufficient FRL on a tandem call). Authorization codes cannot be collected on
incoming SBS signaling calls because the SBS bearer call has not yet been established at
the time when an authorization code would normally be prompted for and signaled
(in-band). Also, authorization codes cannot be collected on incoming SBS bearer calls
because the originating endpoint user is not a party on the SBS bearer call.
•
When the bearer call is transported via Message Oriented Signaling trunks (ISDN),
information in the SBS bearer call "D" channel will not be displayed to the end users as it
is overridden by signaling in the SBS signaling call.
•
User information is ignored when it is in the SBS bearer leg of the call.
•
Australian Malicious Call Trace (MCT) can never 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 the Australia public network
protocol.
NOTE:
The normal MCT feature within Communication Manager will record the call as usual.