SBS provides a separated trunk call. Many types of trunks can be used to carry the bearer portion of the separated call. Thus, SBS affects many Communication Manager features. Almost any feature that can interact with a trunk call can interact with SBS.
This section describes features that might interact with SBS calls. Other features might also interact with SBS in a minor way.
You must understand how SBS calls are configured internally to understand why certain features can work with SBS calls, and others cannot. This general understanding also helps you to accurately predict whether a feature that is not included in this section can successfully work with an SBS call.
Two important facts about the internal configuration of an SBS call are:
SBS bearer and SBS signaling calls are tracked internally as separate calls for the life of the SBS call. Separate call records are created internally for each call to:
Allow the SBS bearer call to be carried over almost any type of trunk
Use the standard call establishment and tear-down code for that trunk type
The system cannot use the standard code if the bearer trunk is somehow buried as a nonstandard party in a merged signaling and bearer call record.
The endpoint users are parties on the SBS signaling call, and not on the SBS bearer call. In other words, the SBS signaling call controls the call. Endpoint user activity drives QSIG signaling only if a QSIG trunk is a party on the call. Therefore, the SBS signaling call must control the call. A QSIG trunk is guaranteed only if the endpoint user is associated with the SBS trunk. A QSIG trunk is not guaranteed if the endpoint user is associated with the bearer trunk.
