Media processor resources are not used by the SBS trunks. SBS trunks carry only SBS signaling calls. SBS bearer calls require media processor resources if IP trunks are used.

Voice quality can degrade if you use IP trunks for bearer calls.

Shuffling and hairpinning work with SBS bearer calls if you use IP trunks. The SBS bearer call originates with the same shufflable endpoint characteristics as the originator.

The system obtains the contents of the Incoming Call Identification (ICI) display for an SBS call from the SBS signaling call, and not from the bearer call.

The system uses the Class of Restriction (COR) of the SBS call originator to set up the SBS bearer call.

The system routes the SBS signaling and bearer calls separately. Use caution when you administer Toll Restriction, Toll Analysis, and Toll/Code restriction so that you do not block calls that should be allowed.

The Class of Service (COS) Trunk-to-Trunk Transfer permission affects the transfer of SBS trunk calls in the same way as for non-SBS trunk calls.

SBS calls follow the Station Hunting of the originally called party.

When Tenant Partitioning is active in an enterprise, existing Tenant Partitioning rules apply to endpoints, SBS extensions, SBS trunk groups, and the bearer trunk groups that are involved in any SBS call.

SBS works with Dial Plan Expansion of 6-digit or 7-digit extensions.

Standard Malicious Call Trace (MCT) on an incoming SBS call records the bearer trunk call.