Page History

...

• JSON HAL Schema should be used as the SLA between RDK and Vendor
• There are 2 versions of hal HAL schema files “telcovoice_hal_schema_v1.json “ and “telcovoice_hal_schema_v2.json “ available in Telco Voice Manager
• Telco Voice Manager picks the right version of schema file based on the selected TR104 data model version

...

{
"hal_schema_path": "/etc/rdk/schemas/telcovoice_hal_schema.json",
"server_port":40104
}

1.What does SLA stand for?

SLA stands for “Service Level Agreement”. JSON HAL schema act as an agreement between the RDK and Vendor on defining the data model object path, data model value patterns , datatype of objects etc. JSON HAL lib validates the parameters exchanged between RDK Manager and Vendor against the respective JSON schema field.

2. How is the JSON HAL conf file provided to the JSON HAL server? Here /opt/secure/telcovoice_config_current.json?

JSON HAL Conf file is maintained by RdkTelcoVoice Manager in the build folder (RdkTelcoVoiceManager/config/telcovoice_manager_conf.json) and is installed as  “/etc/rdk/conf/telcovoice_manager_conf.json”. “opt/secure/telcovoice_config_current.json” is the persistent storage file.

3. Where does the vendor software registration happen?

Vendor Software Registration happens below HAL. Vendor should implement their own JSON HAL server by using JSON HAL Server library package to receive the json messages from TelcoVoiceManager and initiate vendor application registration.

4. How does the Telco manager pick right version of schema file?

TelcoVoiceManager depends on the distro feature flag “rdkb_voice_manager_dmltr104_v2” to pick the right version of schema file. It install V2 schema file if “rdkb_voice_manager_dmltr104_v2” DISTRO feature is enabled in OEM machine configuration file, otherwise v1 schema file is installed.