Difference between revisions of "Cisco dialer profile"
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
*Dialer map-class (optional)—Supply configuration parameters to dialer interfaces (for example, ISDN speed, dialer timers parameters). A map-class can be referenced from multiple dialer interfaces. | *Dialer map-class (optional)—Supply configuration parameters to dialer interfaces (for example, ISDN speed, dialer timers parameters). A map-class can be referenced from multiple dialer interfaces. | ||
=== Configuration overview === | === Configuration overview === | ||
#Define Intresting Traffic | |||
## configure terminal | |||
## dialer-list ip permit | |||
#Create Dialer Interface and associating to dialer pools | |||
## configure terminal | |||
## interface dialer | |||
## ip address | |||
## encapsulation | |||
## dialer remote-name | |||
## dialer string | |||
## dialer-pool | |||
## dialer-group | |||
#Configure and associate physical interface to dialer group | |||
## configure terminal | |||
## interface | |||
## dialer pool-member | |||
=== Reference === | === Reference === | ||
*[http://www.cisco.com/en/US/tech/tk801/tk133/tk159/tsd_technology_support_sub-protocol_home.html Dialer Profiles] | *[http://www.cisco.com/en/US/tech/tk801/tk133/tk159/tsd_technology_support_sub-protocol_home.html Dialer Profiles] | ||
*[http://www.cisco.com/en/US/tech/tk801/tk133/technologies_tech_note09186a0080094e6c.shtml Configuring and Troubleshooting Dialer Profiles] | *[http://www.cisco.com/en/US/tech/tk801/tk133/technologies_tech_note09186a0080094e6c.shtml Configuring and Troubleshooting Dialer Profiles] | ||
Revision as of 23:37, 29 September 2013
Dialer profiles separate logical configurations from the physical interfaces that receive or make calls. Because of this separation, interfaces such as ISDN, asynchronous modems, or synchronous serial connections can be shared by multiple dialer profile configurations. Dialer profiles allow logical and physical configurations to be bound together dynamically on a per call basis, allowing physical interfaces to take on different characteristics based on incoming or outgoing call requirements. They also can define encapsulation, access control lists, minimum or maximum calls, and toggle features on or off.
- The components of a dialer profile include
- Dialer interfaces—Logical entities that use a per-destination dialer profile. Any number of dialer interfaces can be created in a router. All configuration settings specific to the destination go in the dialer interface configuration. Each dialer interface uses a dialer pool, which is a pool of physical interfaces (ISDN BRI and PRI, asynchronous-modem, and synchronous serial).
- Dialer pool—Each interface references a dialer pool, which is a group of physical interfaces associated with a dialer profile. A physical interface can belong to multiple dialer pools. Contention for a specific physical interface is resolved by configuring the optional priority command.
- Physical interfaces—Interfaces in a dialer pool are configured for encapsulation parameters. The interfaces are also configured to identify the dialer pools to which the interface belong. Dialer profiles support PPP and High-Level Data Link Control (HDLC) encapsulation.
- Dialer map-class (optional)—Supply configuration parameters to dialer interfaces (for example, ISDN speed, dialer timers parameters). A map-class can be referenced from multiple dialer interfaces.
Configuration overview
- Define Intresting Traffic
- configure terminal
- dialer-list ip permit
- Create Dialer Interface and associating to dialer pools
- configure terminal
- interface dialer
- ip address
- encapsulation
- dialer remote-name
- dialer string
- dialer-pool
- dialer-group
- Configure and associate physical interface to dialer group
- configure terminal
- interface
- dialer pool-member