Skip to content

RDKB-62812:initialize DHCP for Voice interface#88

Merged
snayak002c merged 12 commits intordkcentral:developfrom
Amaresh-Kotekal:develop
Feb 15, 2026
Merged

RDKB-62812:initialize DHCP for Voice interface#88
snayak002c merged 12 commits intordkcentral:developfrom
Amaresh-Kotekal:develop

Conversation

@Amaresh-Kotekal
Copy link
Copy Markdown
Contributor

Reason for change:Adding the Voice fields
Test Procedure: verify the logic and functionality
Risks: Low
Priority: P1

@Amaresh-Kotekal Amaresh-Kotekal requested review from a team as code owners February 12, 2026 23:25
Copilot AI review requested due to automatic review settings February 12, 2026 23:25
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request adds Voice interface support to the DHCP Manager by extending the DHCP_MGR_IPV4_MSG struct with five new fields to capture Voice-related DHCP options and configuration parameters.

Changes:

  • Added DHCP Option 122 field for SIP server configuration (typically used in VoIP deployments)
  • Added DHCP Option 67 field for bootfile name
  • Added fields for TFTP server, hostname, and domain name configuration

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +232 to +236
char cOption122[BUFLEN_256];
char cOption67[BUFLEN_64]; //bootfile name
char cTftpServer[BUFLEN_64];
char cHostName[BUFLEN_64];
char cDomainName[BUFLEN_64];
Copy link

Copilot AI Feb 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The newly added field names use Hungarian notation with a 'c' prefix (cOption122, cOption67, cTftpServer, cHostName, cDomainName), which is inconsistent with the existing naming convention in this struct. All other fields in DHCP_MGR_IPV4_MSG use lowercase camelCase without prefixes (e.g., ifname, address, dnsServer, timeZone). The 'c' prefix should be removed to maintain consistency. For example, 'cOption122' should be 'option122', 'cTftpServer' should be 'tftpServer', 'cHostName' should be 'hostName', and 'cDomainName' should be 'domainName'.

Suggested change
char cOption122[BUFLEN_256];
char cOption67[BUFLEN_64]; //bootfile name
char cTftpServer[BUFLEN_64];
char cHostName[BUFLEN_64];
char cDomainName[BUFLEN_64];
char option122[BUFLEN_256];
char option67[BUFLEN_64]; //bootfile name
char tftpServer[BUFLEN_64];
char hostName[BUFLEN_64];
char domainName[BUFLEN_64];

Copilot uses AI. Check for mistakes.
Comment on lines +232 to +235
char cOption122[BUFLEN_256];
char cOption67[BUFLEN_64]; //bootfile name
char cTftpServer[BUFLEN_64];
char cHostName[BUFLEN_64];
Copy link

Copilot AI Feb 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The newly added fields lack documentation comments. The related struct ipc_dhcpv4_data_t at lines 121-145 consistently documents all fields with descriptive comments in the format "/** description */". The new fields should follow the same pattern for consistency. For example, cOption122 should explain it's for DHCP Option 122 (SIP Servers), cTftpServer should explain it's for the TFTP server address, cHostName should explain it's for the client hostname, and cDomainName should explain it's for the domain name.

Suggested change
char cOption122[BUFLEN_256];
char cOption67[BUFLEN_64]; //bootfile name
char cTftpServer[BUFLEN_64];
char cHostName[BUFLEN_64];
/** DHCP Option 122 (SIP Servers) string value */
char cOption122[BUFLEN_256];
/** DHCP Option 67 bootfile name */
char cOption67[BUFLEN_64];
/** TFTP server address provided by DHCP */
char cTftpServer[BUFLEN_64];
/** Client hostname provided by DHCP */
char cHostName[BUFLEN_64];
/** Domain name provided by DHCP */

Copilot uses AI. Check for mistakes.
@snayak002c snayak002c merged commit 48b7080 into rdkcentral:develop Feb 15, 2026
12 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Feb 15, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants