• Created by Unknown User (eleonora), last modified on 2016-12-28

  • Type your task here, using "@" to assign to a user and "//" to select a due date

User Story

Customization of Ringback tone music is a popular feature used by the customers. At the moment a work-around with the Call Queue is used. The drawback of such a work-around is that call queue allows 1 call at a time to a particular extension, and have specific settings for number on hold etc, the ringback tone only replaces a default sound which callee hears, and do not change any distribution logic, which allow any account to receive multiple calls at the same time, right now it is impossible with the queues. Additionally it is not easy to explain how to set this up to end-users.

Implementation of this functionality will give possibility of providing feature that is popular in the market.

Use Cases

Use case #1: Custom Ringback tone setup

Roles: Administrator, User

Preconditions: There is Account 123456.

Account has default (beeps) Ringback tone.

There is Huntgroup 800. It has default (beeps) Ringback tone.

Use scenario #1.1: Administrator enables custom RBT generation for Account

  • User 123456 calls administrator and informs that he wants to play announcement while there is incoming call instead of ringing.

  • Administrator uploads the file "Announcement about new product". He sets this file as a Ringback tone for user 123456.

  • There is a call to 123456. 123456 is ringing. Callee hears "Announcement about new product" file. 123456 picks up the phone. Users talk.

  • There is a second call to 123456. Callee hears "Announcement about new product" file. 


Scenario #1.2: Administrator enables custom RBT generation for huntgroup

  • User of 800 huntgroup contacts Administrator and informs that they want to play file with new products description named "Winter proposition". 

  • Administrator uploads the file "Winter proposition". He sets this file as a Ringback tone for 800 Huntgroup.

  • There is a call to 800 number. Callee hears "Winter proposition" file.

Use case #2: Custom Ringback tone setup via API

Roles: Administrator, User

Preconditions: There is Account 123456.

Account has default (beeps) Ringback tone.

There is Huntgroup 800. It has default (beeps) Ringback tone.

There are API methods in PortaBilling to set up Ringback.

Use scenario #1.1: Administrator enables custom RBT generation for Account via API

  • The API call is performed to upload and change RBT for Account 123456.

  • There is a call to 123456. 123456 is ringing. Callee hears "Announcement about new product" file. 123456 picks up the phone. Users talk.

  • There is a second call to 123456. Callee hears "Announcement about new product" file. 

Scenario #1.2: Administrator enables custom RBT generation for huntgroup via API

  • The API call is performed to upload and change RBT for Huntgroup 800 to "Winter proposition" file.

  • There is a call to 800. UAs of users from 800 huntgroup are ringing . Callee hears "Winter proposition" file.

Other requirements / constraints