The x.121 address in the translate command is the in-coming or called address, which is normally the x.121 address of your interface with subaddress appended to the end. The subaddress portion is to distingush different servers/destinations.
I guess the calling or originating address is not used because the calling station could be talking to serveral hosts via the same link/interface and so we still need to know the destination address in order to route the messages correctly, therefore it is more straight forward to use the destination address in the translation command
What you wrote would be correct if the traffic is incoming from the VSAT to the router, whereas here the config is for translation to happen between the router and the IP host. Here the input is the serial interface of the router. Also no translation happens between VSAT and Serial Interface as both are using only X.25. So I think this is the correct config in this scenario.
Right now I have tested only with one VSAT and router. I am wondering what happens when I connect mutiple VSATs to the router. Will the router maintain a separate translation session for the stream coming from each VSAT?
Or in other words, if the router translates all traffic from serial X.121 interface of the router to the Ethernet IP interface, then will be club traffic from all VSATs and create one translation session (in which case I am screwed) or will it maintain a separate translation session for each VSAT-Router-IP Host connection?
Also, lets say I wanted to translate traffic coming from 2 VSATs and not translate traffic coming from other 3 VSATs connected to the same serial X.121 port. How would I do that then?
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...