Guidance on IP Interface Showing Down (AWS)

7. Troubleshooting
1

I recently deployed a new SBC instance on AWS. The installation completed successfully, and both the management interface (mgmt0) and the private interface (voip1) are up and running as expected. However, the public SIP interface (voip0) is showing as down in the SBC’s status view.

I’ve gone through the AWS-side configuration to double-check the setup:

  • The ENI for the public SIP interface is attached to the instance.
  • The subnet, route table, and security groups all appear correct.

Any tips or comments on why voip0 might not be coming up as expected, and what the recommended next steps are to bring this interface online would be appreciated.

Thanks,
Dylan

2

Hello Dylan

Do you see any error on tbrouter or tboamapp logs related to the VoIP0? You can run tbreport and check the tbrouter and tboamapp logs.

Regards

3

We attempted to run tbreport but the command isn’t present on this build.

As a workaround we collected logs manually. tbrouter shows that voip0 gets DHCP OFFER/ACK and is then immediately DHCPRELEASE’d, so it never binds an IPv4, while voip1 binds/renews normally.

Please confirm whether tbreport is delivered via an additional package for this release, or if manual logs are acceptable.

4

Hi

Please check the following link for how to run the tbreport : TBReport | ProSBC Documentation

If there is a problem on the DHCP lease, you need to check the host system messages too. /var/log/messages

5

Hi support,

Thanks for the guidance. I ran tbreport and pulled the relevant section for voip0:

ip_interface_name: voip0
config_failed: true
config_fail_log: “Restore the IP interface on the system or stop using it in the configuration.”
router_tx_unknown_ip_interface_errors: 23
router_rx_dhcp_packets_cnt: 22

tboamapp logs look clean, no related errors.

I also checked /var/log/messages. Both mgmt0 and voip1 successfully receive DHCPACKs and bind IPv4 addresses. However, voip0 only shows DHCPRELEASE events and never completes a DISCOVER/OFFER/ACK handshake, so it never gets an IPv4 lease from the host.

In AWS, I currently have voip0 configured with an Elastic IP and one private address behind it. Should this interface be assigned as a static IP directly on the SBC, or configured with another private address in AWS and left to DHCP?

Just want to confirm the best practice for handling this interface on AWS with ProSBC.

Best regards,

Dylan

6

Hello Dylan,

For AWS installations, you need to select “Use DHCP” in the IP interfaces configuration. Once you are confirmed with the interfaces configuration over AWS, you can do “Change network device role” to see if the VoIPx interfaces can be detected.

Resetting the Network Device Role - TB Wiki

7

Hi Support,

Use DHCP is selected for this IP Interface and it has an IP in AWS Assigned to it already.

Best,

Dylan

8

When you do "Change network device role”, do you see all the desired interfaces?

9

Yes once that is selected, I see all 3 network interfaces Mgmt0 Voip0 Voip1