As you wrote, there's a switch inside your router, with the WAP module bridged to it (of course, that module has got a wired port as well). The bridge forwards frames based on the MAC addresses of the connected NICs.
Packets are layer-3 datagrams, so the layer-2 frame encapsulating the layer-3 packet would need to have the host layer-2 address to get into the host network stack, where the packet would be discarded as not matching the layer-3 address configured on the host.
An application/service bound to the localhost loopback 127.0.0.1 can only ever be accessed on the same machine, using said loopback.
If you want the service to be available over the network you need to bind it either to a local interface's IP address or to the unspecified address 0.0.0.0, using all available interfaces.
Literally? No. Unless the devices were very close, it's very unlikely they would ever have been directly connected. Even 20-30 years ago, in the era of T1's, there were repeaters, digital cross-connects, and multiplexing into larger T-carriers.
As Ron has said, today the T1 is a relic. It will be emulated and carried as packets like every thing else "...
No. There may be a dedicated circuit between the routers and the nearest telco central office, but between offices they are switched and multiplexed onto other, higher capacity circuits.
Today, most T1 circuits are emulated over a packet-switched (IP) network. They are rapidly becoming obsolete, and are being replaced by SIP over the IP network.
This is the solution, we need both span and sflow tcam size 256, so i took vPC slice and give it to span region (Notes: following solution only apply for 40G Interface, if you are using 10G for data-source then nothing to do)
hardware access-list tcam region vpc-convergence 0
hardware access-list tcam region sflow 256
hardware access-list tcam region span ...