Networking features or capabilities that do not work with SBS

Last Updated : Oct 30, 2012 |
Prolog information
  • Authorization codes cannot be collected on an incoming SBS signaling call or on an SBS bearer call. Such codes might be required to administer of the incoming trunk group or because of insufficient Facilities Restriction Level (FRL) on a tandem call. Authorization codes cannot be collected on incoming SBS signaling calls for two reasons:
    • The SBS bearer call is not established at the time that the system usually prompts for and signals an authorization code.
    • The originating endpoint user is not a party on the SBS bearer call.
  • When the bearer call is transported through Message Oriented Signaling trunks ISDN, information in the SBS bearer call D-channel is not displayed to the end users. The information is not displayed because the signaling in the SBS signaling call overwrites the information.
  • User information in the SBS bearer leg of the call is ignored.
  • Australian Malicious Call Trace (MCT) cannot be invoked on an SBS call because:
    • End-user activity drives feature signaling only on the SBS signaling call, and not on the SBS bearer call
    • An SBS trunk does not support the Australia public network protocol
    The normal MCT feature within Communication Manager records the call as usual.
  • ETSI MCT cannot be invoked on an SBS call because:
    • End-user activity drives feature signaling only on the SBS signaling call, and not on the SBS bearer call
    • An SBS trunk does not support ETSI protocol
      The normal MCT feature within Communication Manager records the call as usual.
  • Calling Line ID Prefix information is ignored when the information is transported in conjunction with an associated bearer trunk.
  • Advice of Charge (AOC) information that is received on an SBS bearer call is not displayed to the end user. However, AOC information 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) does not work with an SBS call. For SBS, the signaling that controls the call is in the SBS signaling call on the QSIG interface. NCD, however, requires an ETSI interface that is available only on SBS bearer calls.
  • ETSI Network Call Transfer (NCT) does not work with an SBS call. For SBS, the signaling that controls the call is in the SBS Signaling call on a QSIG interface. NCT, however, requires an ETSI interface that is available only on the SBS bearer call.
  • Direct SBS calling into Remote Access does 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. However, an SBS call can invoke Remote Access by means of a vector collect or a route-to command.
  • SBS does not support Wideband Switching (NxDSO).
  • Russian Incoming ANI with a button does not display the ANI that is received in the SBS bearer call. The system displays to the end user only the ANI that is received on the SBS signaling call.
  • Trunk Flash to get recall dial tone from a central office (CO) does not work. End-user activity drives signaling on the SBS signaling call only, and not on 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 does so by applying the appropriate treatment to the call originator based on what is received on the R2 MFC bearer call.