Occasionally, during an upgrade, the AoIP Audio IP address (the “second” IP address) of the IP-Transceiver may revert to a DHCP connection. To remedy:

1. In EHX, navigate to Hardware > Transceivers and select the settings cog for the unit in question.

   1. Set the AoIP Audio IP for a static IP, and enter the appropriate IP, Subnet Mask, and Gateway.

   2. Apply using the blue check box.

   3. Let the unit reboot, then verify the connection.

2. Using the AoIP Admin (the “first” IP address) of the unit, navigate the CCM and log in.

   1. Navigate to Device > Network

   2. Set the AoIP Audio Address to static, and enter the appropriate IP, Subnet Mask, and Gateway.

   3. Save Changes.

   4. Let the unit reboot, then verify the connection.

If the unit RANDOMLY reverts to DHCP:

1. Navigate the the CCM and login.

2. Navigate to Device > Maintenance > Support Info.

3. Let the logs compile, then save/export.

4. Unzip the logs, and navigate to /var/log/messages

   1. Search for the following entries:
      2022-05-12T01:49:56.872473+00:00 CC-TCVR-46Y50058 avahi-autoipd[605]: Received conflicting normal ARP packet.

      2022-05-12T01:49:56.873360+00:00 CC-TCVR-46Y50058 avahi-autoipd[605]: Trying address 169.254.120.160

      2022-05-12T01:50:02.310859+00:00 CC-TCVR-46Y50058 avahi-autoipd[605]: Callout BIND, address 169.254.120.160 on interface eth0

      2022-05-12T01:50:02.334014+00:00 CC-TCVR-46Y50058 avahi-daemon[754]: Registering new address record for 169.254.120.160 on eth0.IPv4.

      2022-05-12T01:50:06.309707+00:00 CC-TCVR-46Y50058 avahi-autoipd[605]: Successfully claimed IP address 169.254.120.160

*If the above entries are seen, this is internal service/mechanism the IP-Transceiver uses to detect duplicate IPs, and it may be that the unit detected a conflict and tried to change it’s own IP to allow it to re-connect. If a DHCP server is not present, this can land the AoIP Audio IP on a different subnet from the AoIP Audio connection, thus leaving it unusable as they is a protection in place to eliminate it. Additionally, there are some IPs reserved within the units that are not allowed, so if the DHCP lease comes from something within that range, it will also trip into a protection.

See Also: https://clear-com.atlassian.net/wiki/spaces/SF/pages/2077393025/CCM+for+IP+Transceiver+Iris+Panel+or+IPA+Won+t+Allow+172.23.x.x+Subnet