CBOSSvideoRBT Video Ring Back Tone

CBOSSvideoRBT is an innovative and cutting-edge service that allows

subscribers to use their own videos (videoclips, video messages, or video
effects) to replace the standard ring back tones for the calling party when a
video call is set up. Such video files can be selected from the database or
specially recorded by the subscriber.

CBOSSvideoRBT is a perfect tool for making phones more individual and

improving the quality of communications.

CBOSSvideoRBT also serves to expand a carrier’s business and develop

profitable partnerships with content providers. Operators and content providers
get another opportunity to boost their revenue by offering a wide range of video
files, introducing a subscription fee, etc.

The only restriction for applying the CBOSSvideoRBT system is support of video
calls both by a subscriber’s phone (the feature is available on most modern
mobiles) and by a telecom operator’s network (UMTS, LTE, VoIP etc.)

SYSTEM OPERATION

A video ring back media service prescribes to the same usage model with mobile
subscribers as CBOSScrbt either purchasing video ring back content from their
mobile operator, or from a content provider, or creating their own video ring back
media.

Through a service provider portal that is accessible via their handset or on the
web using a computer, mobile subscribers can select from various video content
organized by categories. Personalizing service settings can enable the
subscriber to specify different content based upon who is calling them as
determined by the caller’s number. For instance a short vacation video could be
configured by the mobile subscriber to be used when any one number in a group
of numbers identified as “family members” calls.

KEY FEATURES

 Custom video RBT.

 Capability to assign individual video RBT to different callers.
 Video on:

Call setup

Busy

Unavailable

 Corporate video RBT.

 Advertising and sponsored video RBT.
 Scheduling and filters.

INTEGRATION

CBOSSvideoRBT integrates with any billing system, including CBOSSbcc Billing

& Customer Care. CBOSSvideoRBT’s web-based API ensures seamless
integration with various systems and allows the development of user-defined
client applications for system administration.

CBOSSvideoRBT web interface can integrate with CBOSSics Internet Customer

Service. SMS/Video SMS and USSD interfaces are available in the event of
integration with corresponding systems such as CBOSSsms Short Message
Service Center, CBOSSussd USSD Messaging Center or third-party solutions.
CBOSSvideoRBT also integrates with CBOSSvideoPortal which stores the
required video content.

BENEFITS

 Increased revenue from video content

 Beneficial partnership with content providers
 Additional profit generated by subscription fees and fragment change
fees
 Stronger subscriber loyalty due to the personalized approach and an
enhanced portfolio of services
 Easy integration enabling rapid development of service functionality
and fast time-to-market for videoRBT-based offerings

 mr110
 Admin manuals
 Connection to / interoperability with external systems
 Interoperability with third-party VoIP equipment
 Ringback tone generation and early media relaying

Ringback tone generation and early media

relaying
Link copied to clipboard
 October 25, 2023


When an end user places an outgoing call, they expect to hear a ringback tone in
return, to signify that the call is in progress. If the line is quiet, the end user might think
the call has failed and might hang up although the call is actually ringing at its
destination.

Such situations have been observed when certain VoIP equipment is unable to
generate a ringback tone (for example, due to overload). To ensure that a ringback
tone is delivered to the call originator, PortaSwitch generates a local ringback tone.

Let’s see how this works in SIP. When a caller makes a call from a SIP user agent, an
INVITE request is sent to the called party. When the called party’s phone begins to ring,
it sends back an 18x Ringing response. The 18x Ringing message may or may not
include the Session Description Protocol (SDP) which is used to set up a one-way media
stream for conveying RTP media packets with a ringback tone to the caller.
PortaSwitch analyzes the 18x Ringing message received. If it doesn’t contain the SDP,
PortaSwitch immediately generates its own ringback tone and sends it to the caller. If
the 18x Ringing message is received with the SDP, PortaSwitch waits for the RTP media
packets. If they are not received within a predefined timeout, PortaSwitch generates its
own ringback tone for the caller.

Ringback tone generation is controlled via the call_progress_notification,

call_progress_filter and early_media_ timeout service policy options (you can find
their description in the table below). Besides ringback tone generation, these service
policy options also control early media relaying. Early media is a powerful aspect of SIP
that allows two endpoints (user agents) to communicate before a call is actually
established. In terms of SIP, this means relaying media prior to 200 OK is sent in
response to an INVITE request.

Option Description

 signaling – this is the default value. PortaSwitch just re-sends 18x

call progress responses and media received from the called party.
 audio_rbt – PortaSwitch generates a local ringback tone when:
o An 18x Ringing response is received without the SDP.
o An 18x Ringing response is received with the SDP, but the
RTP media packets are not received within a predefined
timeout.
call_progress_notification
Early media (if provided by the called party) is relayed.

 mow – PortaSwitch plays the Music on Waiting prompt upon

receiving an 182 Queued response without the SDP. The rest of the
18x call progress responses are just re-sent to the called party.

 full_progress – this is the default value. PortaSwitch just re-sends

early media and 18x call progress responses received from the called
party.
call_progress_filter
 ringing_only – PortaSwitch turns all 18x call progress responses and
media from the called party into a 180 Ringing message.

This defines a duration during which PortaSwitch waits for the RTP media
packets upon receiving an 18x Ringing response with the SDP from the
early_media_timeout
called party. If they are not received within the predefined timeout,
PortaSwitch generates its own ringback tone for the caller.
Let’s have a closer look at how a call with ringback tone generation and early media
relaying is established.

1.
a. A caller makes a call from a SIP UA that arrives at the B2BUA. The B2BUA
verifies if there is a service policy dynamically matched by the User-Agent
header field.
b. The B2BUA sends an authorization request to the billing engine. The billing
engine checks if the caller is allowed to send the call to the desired
destination and provides the B2BUA with the routing. The authorization
response also includes information about the service policies configured for
both participants of the call.
c. For each tried route, the B2BUA analyzes the following service policy
options:
 The call_progress_notification option from the dynamically
matched service policy.
 The call_progress_notification option from the service policy
assigned to the Calls from Vendor connection or the authorized
account.
 The call_progress_filter option from the service policy assigned to
the Calls to Vendor connection or the called account.
 The early_media_timeout option from the service policy assigned to
the Calls to Vendor connection or the called account.
d. The B2BUA receives an 18x call progress response from the called party. The
resultant behavior (whether to generate a local ringback tone or just re-send
all 18x call progress responses, relay, or prohibit early media) depends on
the service policy options configured for both participants of the call. For
more detailed information please refer to Service policy
configuration section.

1. The B2BUA starts a new route, without the interruption of the ringback tone
initiated on the previous step.
2. Steps 4 and 5 are repeated for each route tried until 200 OK is received.
3. The B2BUA connects the caller with the called party.

Note that PortaSwitch does not generate ringback tones if a user makes calls through
IVR applications (e.g., in scenarios such as Prepaid card calling, Pass-through-IVR, call
queues, etc.). In these cases, the user hears the media configured within the
corresponding IVR application (ringing tones or music on hold).
For callback calls, however, PortaSwitch generates ringback tones for call leg A – the
initiating call to the access number.