Two PIM sparse-mode domains each keep their own RP: R2 (2.2.2.2) for domain A, where SRC sends, and R3 (3.3.3.3) for domain B, where PC4 has joined 239.1.1.1. RP-B never hears about SRC, so PC4 gets nothing. Peer the two RPs with MSDP so RP-A announces the source in a Source-Active message and RP-B joins it across the border.
The simulator ticks each one as soon as the network meets it.
On R2 (RP-A) configure ip msdp peer 3.3.3.3 connect-source loopback0 remote-as 65002.
On R3 (RP-B) configure ip msdp peer 2.2.2.2 connect-source loopback0 remote-as 65001.
On R2, show ip msdp summary: peer 3.3.3.3 is Up.
From SRC ping 239.1.1.1: PC4 replies.
On R3, show ip msdp sa-cache lists (10.1.1.10, 239.1.1.1) from RP 2.2.2.2, and show ip mroute shows that (S,G) entry with the M flag (created by MSDP).