Configuring RS-DCC

In the RS-DCC approach, physical interface configuration is separated from logical configuration for calls and they can be combined dynamically for each call.

When you configure RS-DCC for on-demand dial, configure RS-DCC sets. Each RS-DCC set is an attribute collection containing a dialer interface, dialer interface attributes, and a dialer bundle.

• For each dialer interface, you can define only one dial string. As this dial string has its own dial attribute set, all calls placed using this dial string use the same DCC attribute parameters (such as dial rate).

• Each dialer interface can use only one dialer bundle. Each dialer bundle can contain multiple physical interfaces with different priorities, but each of these interfaces can belong to multiple dialer bundles. For an ISDN BRI or PRI interface, you can set the number of B channels to be used by configuring the dialer bundle command.

• All calls destined to the same network segment use the same RS-DCC set.

Due to the separation between physical configuration and logical configuration, RS-DCC can accommodate more network topologies and DCC dial demands. For example, it allows multiple interface groups to call multiple remote ends.

In this scenario, a dialer interface is configured only for calling one remote end. On-demand dial, in this case, is implemented by assigning a physical interface to dialer bundles associated with different dialer interfaces.

If RS-DCC sets are used to configure RS-DCC parameters, you only need to configure link layer encapsulation and dialer bundle numbers on physical interfaces.

Before you configure RS-DCC, follow these guidelines:

• In RS-DCC, an R-DCC set is unable to apply the attribute information in it, PPP authentication for example, to the physical interfaces in a dialer bundle. The physical interfaces do not inherit the authentication attribute in the RS-DCC set. Therefore, authentication information must be configured on call-receiving physical interfaces.

• Authentication is mandatory in RS-DCC. You must configure authentication (dialer user and PPP authentication) on both dialer interfaces and their physical interfaces. This is because RS-DCC must conduct PPP negotiation on the physical interface and sends the agreed-upon remote username to DCC. Based on this remote username, DCC decides which dialer interface address is used and then informs PPP. PPP then uses the configuration of the dialer interface to start IPCP negotiation.

Complete these tasks to configure RS-DCC for on-demand calling: