The SBC Core acting as a P-CSCF or as an IBCF in an IMS deployment supports following Multi-Media Telephony (MMTel) Supplementary Services:
- Originating Identification Presentation (OIP)
- Originating Identification Restriction (OIR)
- Terminating Identification Presentation (TIP)
- Terminating Identification Restriction (TIR)
- Communication Diversion (CDIV)
- Communication Hold (HOLD)
- Anonymous Communication Rejection (ACR)
- Communication Barring (CB)
- Message Waiting Indication (MWI)
- Conference (CONF)
- Malicious Communication Identification (MCID)
- Explicit Communication Transfer (ECT)
- XCAP over Ut interface for Manipulating NGN Services
- Advice Of Charge (AOC)
- Closed User Groups (CUG)
- Three-Party (3PTY)
- Flexible Alerting (FA)
- Communication Waiting (CW)
- Completion of Communications to Busy Subscriber (CCBS) Completion of Communications by No Reply (CCNR)
- Customized Alerting Tones (CAT)
- Customized Ringing Signal (CRS)
- Personal Network Management (PNM)
- Unstructured Supplementary Service Data (USSD)
The SBC also supports transparency of Tel URI in the Request-URI. The Request-URI is the URI representing the intended destination of a SIP request. The SBC has ability to globalize a Request-URI (to the extent possible) before the call enters the IMS core. Request-URI types include:
- Local number with or without phone-context, in tel or sip URL format.
- Global number.
- Vertical Service Code (VSC) with or without ‘user=dialstring’ – A special code dialed prior to (or instead of) a telephone number that engages some type of special telephone service, and is typically preceded with an asterisk, or * (star), key.
- Username/Alphanumeric.
The SBC can be configured to manipulate an ingress ‘user=dialstring’ parameter in SIP URI in a Request-URI to a ‘user=phone’ parameter if the PSX manipulates the number.
Conversely, SBC can be configured to transparently pass the Request-URI toward the egress call leg if the Request-URI is not manipulated by PSX. For example, if a VSC is dialed, the VSC is sent “as-is” towards the IMS core. Likewise, if the Request-URI has SIP URI of the form username/alphanumeric (e.g. sip:bob@sonusnet.com), the Request-URI is sent “as-is” towards the IMS core.
The CLI syntax to enable/disable this dial string handling feature is described in CLI Reference Guide section.