Are the phones and the 3CX server in the same VLAN? In that case, multicast should just work, unless you intentionally broke it (with ACLs or so).
If phones and server are in different VLANs, you should setup multicast routing in order to get the traffic across a VLAN/subnet boundary.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Aug 02, 2024 02:43 PM
From: Raymond Norton_1
Subject: Assistance with multicasting
I apologize for the very long delay in getting back to you. We found a workaround and got the new phone system up and running, but I am circling back to find a resolution to the issue. Option 132 is unnecessary, as the phones find the VoIP VLAN fine and receive the correct IP. However, in the current setup (Aruba 2930 switches and Hyper-V) the phones do not connect to the multicast address of the 3CX server, as they should for pnp/registration. The VM is setup on Hyper-V with external networking, so multicasting should be available, and the server indicates it is listening for multicast. Haven't discovered the fix yet.
Thanks for your original reply.
Original Message:
Sent: Jul 19, 2024 08:44 PM
From: ariyap
Subject: Assistance with multicasting
are you using VLAN trunking to the IP Phone? if so perhaps you can use DHCP option 132 to assign the VLAN for them and then igmp could kick in.
------------------------------
If my post was useful accept solution and/or give kudos.
Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.