Page History

Introduction

RDK Telco Voice Manager is a component that manages the vendor voice stack through TR104 configuration. 
It is responsible for :

• Provisioning voice service via Webconfig
• Managing TR104 data model and persistent storage of the VOIP
• Configuring and managing the life cycle of the vendor voice application through JSON HAL
• Monitoring the network events
• Managing voice firewall rule data via pub/sub events
• Generating diagnostic report using Harvester

Architecture

The RDK Telco Voice Manager consists of

• Data Models : TR104 V1/V2 objects and Custom objects
• Network Monitor : Monitors the network events and manages the lifecycle of vendor voice process
• Persistent storage : Stores the data model object values in JSON format that needs to be persistent across reboot
• JSON HAL : Telco Voice Manager creates JSON HAL client thread and connects with HAL server for exchanging data with vendor stack using JSON RPC messages
• Controller : Subscribe for events to vendor stack
• Diagnostics Report: Generate statistics

Data Model

• RDK Telco Voice Manager owns standard TR-104 DML and additional custom DML objects

<diagram>

• Supports both TR104v1 or TR104v2 version of data model
• By default V1 data model is supported. TR104V2 can be enabled by adding the below distro feature into 
  OEM machine configuration file

DISTRO_FEATURES_append = " rdkb_voice_manager_dmltr104_v2“

Custom Data Models

RDK Telco Voice Manager has a set of custom TR-104 data objects to manage voice service better. Few of them are listed in the below table

• The gateway will be shipped with a default configuration, without enabling voice. Default values are defined based on RDK TR104 standards. The voice flag will be enabled at customer premise
• Post enabling the voice flag, some of the user specific configurations are updated
• Voice profile can be enabled and disabled using below data mode

Device.Services.VoiceService.{i}.VoiceProfile.{i}.Line.{i}.Enable

TR-104-v2 Voice data model list

getv from/to component(eRT.com.cisco.spvtg.ccsp.telcovoicemanager): Device.Services.VoiceService.Execution succeed.

...