I found there is no issue with NAT and PACKET-TRACERT but my plan.
Originally, I plan to establish 2 outside IPs mapped to 2 inside CCTVs through ASA NAT rules. In my imagination, outside devices can connect CCTVs through the 2 mapped IPs. However, the ASA is not the gateway of outside devices neighter inside CCTVs .The ASA never recieves the icmp request from outside or icmp request-reply inside device. This crux was discovered with "debug icmp trace" command.
debug icmp trace
And previous supplementary notes are misleading, part of ping commands were sent by ASA. Lack of consideration of the status of subnets.
In the end, I made some complex PAT rules. Don't know what to call it? It would be very grateful if someone could answer. It lets both sides, outside devices, and inside CCTVs only need to communicate with the ASA's interface.
object network CCTV1-INSIDE-IP
object network CCTV2-INSIDE-IP
object service CCTV1-OUTSIDE-PORT
service tcp source eq 50001
object service CCTV2-OUTSIDE-PORT
service tcp source eq 50002
object service CCTV-INSIDE-PORT
service tcp source eq 1482
access-list OUTSIDE-TRAFFIC extended permit tcp any object CCTV1-INSIDE-IP eq 1482
access-list OUTSIDE-TRAFFIC extended permit tcp any object CCTV2-INSIDE-IP eq 1482
nat (inside_1,outside) source static CCTV2-INSIDE-IP interface destination static interface any service CCTV-INSIDE-PORT CCTV2-OUTSIDE-PORT
nat (inside_1,outside) source static CCTV1-INSIDE-IP interface destination static interface any service CCTV-INSIDE-PORT CCTV1-OUTSIDE-PORT