I would like to know if IOS is capable of using several separate routing tables, automatically associated (maybe using ACLs, calling ID, calling number, etc.) with the relevant "customer ID". The issue naturally appears when implementing telco class access servers with PRI links, and each incoming call needs to be treated according to the settings of its class. For instance, such an access server should route each call to a different RADIUS server for authentication, or each caller should use a certain addressing plan, maybe conflicting with other addresses from another customer. Here, the customers could be ISPs that get dial-up bulk services from the telco access server, or large enterprises, and the telco avoids imposing addresses to the customers.
In a larger context, if we want to service leased-line access, is there any solution (apart from MPLS) to this problem?
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...