The receiver pipeline needs to be started again, to avoid this issue. Is it
not possible that the receiver pipeline continuously listens to the udp port
and displays video when it receives the data?
Does anyone have any pointers to this issue?

The udpsrc pads are not linked in this case. To create rtp sink pads at
rtpbin, special request using 'rtpbin.recv_rtp_sink_0' has to be made. This
was already done once before, during the initial start of Rx pipeline.

So when the Tx pipeline is stopped(Ctrl+C) and restarted again, does that
mean that the request 'rtpbin.recv_rtp_sink_X' has to be requested again?
Won't the same pads be retained, since the Rx pipeline is never exited?

Can anyone provide some pointers, this is kind of a blocker right now for
me. Else any other suggestions that might avoid this issue altogether.