If the users are going to be using the exact same async interface each time, you can issue the peer default ip-address command. This IP address you configure will need to match the address specified on the remote dial-in client.
You can do this with dialer profiles. Assign the physical interface(s) to dialer pools, and configure them for PPP authentication (PAP or CHAP). Build a unique dialer profile for each user. In the dialer interface configuration, use the "dialer remote-name" command to specify the user, and the "peer default ip address" command to assign the user's address. Each time a user dials in, he or she will be authenticated and the physical router interface will be bound to that user's dialer interface based on the authentication. The dialer interface will assign the specified address to the user. Be sure to assign IP addresses to the dialer interfaces and not to the physical interfaces.
If you aren't familiar with dialer profiles, here is a link to the Configuration Guide for them.
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...