What @mlund is correct, but some additional information. . .
#1 As Mikael notes, often the RP is somewhere near/at the center of your topology, but first, your MC topology might not strictly align with your unicast topology, and if it doesn't, your RP would perhaps be better near/at the center of your MC topology. Second, since an RP, at least initially, creates a shared MC distribution tree, your might have other reason for moving your RP location toward the near/at the center of your heavy MC usage. (BTW, by default [or at least it used to be the default], any one MC flow can switch over from the shared RP distribution tree to a shortest path tree from source to client[s].)
#2 At Mikael also correctly notes, yes you can, but keep in mind all clients of a MC group will then receive all the traffic from all the sources sending to that group. Depending on your applications, this might generate a lot of needless traffic between source(s) and client(s). (BTW, as multicast group will be the same, clients that don't want a particular source's traffic will have their NIC physically accept the unwanted multicast traffic, and then pass it up to the application for the application to discard.)
(Also BTW, even when IP MC groups don't overlap, Ethernet MC can overlap such traffic. In that case, again a client's NIC will physically accept the packet, but the IP layer, on the client, will discard the packet. [Moral of this story, try to avoid needless overlapping usage of IP MC IPs and/or different MC IPs that map to the same Ethernet MC MAC.])
