Topology changes like bringing a port up or down could cause flooding. When a port being used for WheatNet IP is flooded, the device connected to that port will most likely miss one or more network packets (potentially hundreds), resulting in loss of control signals and/or audio issues (including but not limited to distortion or dropouts).

Every port in your system should have the no ip igmp snooping tcn flood command applied. But even if this command shows up in your switch configuration, it is ignored in some versions of the Cisco operating system. 

It’s possible you could have a Cisco switch with this issue, and it may not have reared its ugly head yet because you haven’t made any changes. Our tech team suggests you log in and verify your version number with Cisco, and to get the upgrade if necessary. In our support document Cisco 9300 Switch—Multicast is Flooded found in the Wheatstone knowledge base, we discuss this issue and include information on the minimum version you need to resolve or prevent it. If you have older switches, such as the Cisco 3650, you also should review our Technical Advisory—Cisco Catalyst 3650 Memory Leak to ensure everything will work reliably long-term. For more helpful tips, videos, and product information, visit our Support and Knowledge Base Portal.