From the latest attached logs, I saw the statement below and didn't bother to go through the logs.
///////////////care switch seconday///////////////// <---even though this is a layer 3 switch i do not have ip multicast rounting enabled.
Let me explain:
Your topology is described as shown below from your post:
////////////low level of how its source and receivers are///////////////////////
Multicast source-->Core switch1 Main--->Core switch2 secondary--->Hub router--->Internet(DMVPN connecting location)--->Spoke Router--->layer2 switch--->Number of IP phones.
If Core_Switch2, which is between Core_Switch1 and the Hub router, doesn't have multicast routing enabled, how then would multicast packets get to and from the source?
The essence of PIM is to enable Source and Receiver to communicate if they aren't on directly attached LAN. If they're on directly attached LAN, then igmp snooping would suffice.
So for PIM to work, all routing interfaces between the source and the destination must have multicast routing enabled and a PIM mode.
Since debug ip mpacket doesn't work, then use debug ip mfib mpak. That should give same results.
Meanwhile you haven't confirmed what Multicast group you're concerned about. Is it 188.8.131.52?
There is one thing i should mention with the secondary switch, between the core main and the hub vpn is still on the same vlan. while yes the core secondary is in between them its still only a layer2 connection between them, there is no inter-vlan routing going on between the core main and DMVPN hub.
in addition to the other posts, on the spoke router(s), try and replace:
tunnel mode gre multipoint
tunnel destionation x.x.x.x
ip nhrp server-only
to the spoke tunnel(s).
If you apply tunnel destination x.x.x.x, then you effectively are using DMVPN phase 1. As you have 1 tunnel to 2 Hubs, then you need the GRE multipoint. This also ensures that Spoke-to-Spoke communication is supported, if you have Shortcut(Spoke) and Redirect(Hub) configured.