[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]

Configuring ISDN Interfaces and Features with a Configuration Editor

To configure ISDN interfaces on a J-series device, you first configure the basic ISDN interface—either Adding an ISDN BRI Interface (Required) or Configuring Channelized T1/E1/ISDN PRI Interfaces for ISDN PRI Operation. Second, configure the dialer interface by performing Configuring Dialer Interfaces (Required).

To configure ISDN interfaces to back up primary device interfaces, you then configure a backup method—either Configuring Dial Backup, Configuring Dialer Filters for Dial-on-Demand Routing Backup, or Configuring Dialer Watch.

To configure ISDN interfaces for dial-in or callback, configure the basic ISDN BRI or PRI interface and then perform Configuring Dial-In and Callback (Optional).

Perform other tasks as needed on your network.

This section contains the following topics:

Adding an ISDN BRI Interface (Required)

To enable ISDN BRI interfaces installed on your J-series device to work properly, you must configure the interface properties.

To configure an ISDN BRI network interface for the J-series device:

  1. Navigate to the top of the interfaces configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 92.
  3. Go on to Configuring Dialer Interfaces (Required).

Table 92: Adding an ISDN BRI Interface

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Interfaces level in the configuration hierarchy.

  1. In the J-Web interface, select Configuration>View and Edit>Edit Configuration.
  2. Next to Interfaces, click Configure or Edit.

From the [edit] hierarchy level, enter

edit interfaces br-1/0/3

Create the new interface—for example, br-1/0/3.

  1. Next to Interface, click Add new entry.
  2. In the Interface name box, type the name of the new interface, br-1/0/3.
  3. Click OK.
 

Configure dialer options.

  • Name the dialer pool—for example, isdn-dialer-group.
  • Set the dialer pool priority—for example, 255.

Dialer pool priority has a range from 1 to 255, with 1 designating lowest-priority interfaces and 255 designating the highest-priority interfaces.

  1. In the Encapsulation column, next to the new interface, click Edit.
  2. Next to Dialer options, select Yes, and then click Configure.
  3. Next to Pool, click Add new entry.
  4. In the Pool identifier box, type isdn-dialer-group.
  5. In the Priority box, type 255.
  6. Click OK twice.

From the [edit interfaces br-1/0/3] hierarchy, enter

set dialer-options pool isdn-dialer-group priority 255

Configure ISDN BRI properties.

  • Calling number sent to the ISDN switch during the call setup, which represents the caller's number—for example, 18005555555.
  • Service provider ID (SPID)—for example, 00108005555555.
  • Static TEI between 0 and 63 from your service provider—for example, 23. If the field is left blank, the device dynamically acquires a TEI. Also, if you have configured a second SPID, you cannot set a static TEI value.

    If you have a NTDMS-100 or NI1 switch, an additional box for a service provider ID is provided.

    If you are using a service provider that requires SPIDs, you cannot place calls until the interface sends a valid, assigned SPID to the service provider when accessing the ISDN connection.

  • Incoming called number—for example, 18883333456.

    Configure incoming call properties if you have remote locations dialing into the device through the ISDN interface.

  1. Next to Isdn options, click Configure.
  2. In the Calling number box, type 18005555555.
  3. In the Spid1 box, type 00108005555555.
  4. In the Static tei val box, type 23.
  5. Next to Incoming called number, click Add new entry.
  6. In the Called number box, type 18883333456.
  7. Click OK.
  1. To set the ISDN options, enter

    set isdn-options calling-number 18005555555

  2. Enter

    set isdn-options spid1 00108005555555

  3. Enter

    set isdn-options static-tei-val 23

  4. set isdn-options incoming-called-number 18883333456

Select the type of ISDN switch—for example, ATT5E. The following switches are compatible with J-series devices:

  • ATT5E—AT&T 5ESS
  • ETSI—NET3 for the UK and Europe
  • NI1—National ISDN-1
  • NTDMS–100—Northern Telecom DMS-100
  • NTT—NTT Group switch for Japan

From the Switch type list, select att5e.

To select the switch type, enter

set isdn-options switch-type att5e

Configure the Q.931 timer. Q.931 is a Layer 3 protocol for the setup and termination of connections. The default value for the timer is 10 seconds, but can be configured between 1 and 65536 seconds—for example, 15.

In the T310 box, type 15.

set isdn-options t310 15

Configure when the TEI negotiates with the ISDN provider.

  • first-call—Activation does not occur until a call is sent.
  • power-up—Activation occurs when the device is powered on. This is the default value.
  1. From the Tei option list, select power-up.
  2. Click OK to return to the Interfaces page.

To initiate activation at power-up, enter

set isdn-options tei-option power-up

Configuring Dialer Interfaces (Required)

The dialer interface (dl) is a logical interface configured to establish ISDN connectivity. You can configure multiple dialer interfaces for different functions on the J-series device.

After configuring the dialer interface, you must configure a backup method—either dial backup, a dialer filter, or dialer watch.

To configure a logical dialer interface for the J-series device:

  1. Navigate to the top of the interfaces configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 93.
  3. To configure a backup method, go on to one of the following tasks:

Table 93: Adding a Dialer Interface to a Device

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Interfaces level in the configuration hierarchy.

  1. In the J-Web interface, select Configuration>View and Edit>Edit Configuration.
  2. Next to Interfaces, click Configure or Edit.

From the [edit] hierarchy level, enter

edit interfaces

Create the new interface—for example, dl0.

Adding a description can differentiate between different dialer interfaces—for example, T1–backup.

  1. Next to Interface, click Add new entry.
  2. In the Interface name box, type dl0.
  3. In the Description box, type T1–backup.
  4. Click OK.

Create and name the interface:

  1. edit dl0
  2. set description T1-backup

Configure encapsulation options—for example, Cisco HDLC.

  • Cisco HDLC—For normal mode (when the device is using only one B-channel). Cisco-compatible High-Level Data Link Control is a group of protocols for transmitting data between network points.
  • PPP—For normal mode (when the device is using only one ISDN B-channel per call). Point-to-Point Protocol is for communication between two computers using a serial interface.
  • Multilink PPP—For multilink mode, when the device is using multiple B-channels per call. Multilink Point-to-Point Protocol (MLPPP) is a protocol for aggregating multiple constituent links into one larger PPP bundle. You can bundle up to eight B-channels.
  1. In the Encapsulation column, next to the new interface, click Edit.
  2. From the Encapsulation list, select cisco-hdlc.

Enter

set encapsulation cisco-hdlc

Enter a hold-time value in milliseconds—for example, 60. The hold-time value is used to damp interface transitions. When an interface goes from up to down, it is not advertised as down to the rest of the system until it remains unavailable for the hold-time period. Similarly, an interface is not advertised as up until it remains operational for the hold-time period. The hold time is three times the interval at which keepalive messages are sent.

  1. In the Hold time section, type 60 in the Down box.
  2. In the Up box, type 60.
  1. Enter

    set hold-time down 60

  2. Enter

    set hold-time up 60

Create the logical unit—for example, 0.

Note: You can set the logical unit to 0 only, unless you are configuring the dialer interface for Multilink PPP encapsulation.

  1. Next to Unit, click Add new entry.
  2. In the Interface unit number box, type 0.
  3. Next to Dialer options, select Yes, and then click Configure.

Enter

set unit 0

Configure dialer options.

  • Activation delay—Time to wait before activating the backup interface once the primary interface is down—for example, 30. Default value is 0 seconds with a maximum value of 60 seconds. Use only for dialer backup and dialer watch.
  • Deactivation delay—Time to wait before deactivating the backup interface once the primary interface is up—for example, 30. Default value is 0 seconds with a maximum value of 60 seconds. Use only for dialer backup and dialer watch.
  • Idle timeout—Time a connection is idle before disconnecting—for example, 30. Default value is 120 seconds with a range from 0 to 4294967295. This option is used only to configure a dialer filter.
  • Initial route check—Time to wait before checking if the primary interface is up—for example, 30. Default value is 120 seconds with a range of 1 to 300 seconds. This option is used only to configure dialer watch.
  • Pool—Name of a group of ISDN interfaces configured to use the dialer interface—for example, isdn-dialer-group.
  • Redial delay—Number of seconds to wait before redialing a failed outgoing ISDN call. Default value is 3 seconds with a range from 2 to 255.
  1. In the Activation delay box, type 60.
  2. In the Deactivation delay box, type 30.
  3. In the Pool box, type isdn-dialer-group.
  4. In the Redial delay box, type 5.
  1. Enter

    edit unit 0 dialer-options

  2. Enter

    set activation-delay 60

  3. Enter

    set deactivation-delay 30

  4. Enter

    set pool isdn-dialer-group

  5. Enter

    set redial-delay 5

Configure the remote destination to call—for example, 5551212.

  1. Next to Dial string, click Add new entry.
  2. In the Value box, type 5551212.
  3. Click OK until you return to the Unit page.

Enter

set dial-string 5551212

Configure source and destination IP addresses for the dialer interface—for example, 172.20.10.2 and 172.20.10.1. (The destination IP address is optional.)

Note: If you configure multiple dialer interfaces, ensure that the same IP subnet address is not configured on different dialer interfaces. Configuring the same IP subnet address on multiple dialer interfaces can result in inconsistency in the route and packet loss. The device might route packets through another dialer interface with the IP subnet address instead of through the dialer interface to which the ISDN modem call is mapped.

  1. Select Inet under Family, and click Edit.
  2. Next to Address, click Add new entry.
  3. In the Source box, type 172.20.10.2.
  4. In the Destination box, type 172.20.10.1.
  5. Click OK.
  1. From the [edit] hierarchy level, enter

    edit interfaces dl0 unit 0

  2. Enter

    set family inet address 172.20.10.2 destination 172.20.10.1

Configuring Dial Backup

Dial backup allows one or more dialer interfaces to be configured as the backup link for a primary interface. The backup dialer interfaces are activated only when the primary interface fails. ISDN backup connectivity is supported on all interfaces except ls-0/0/0.

To configure a primary interface for backup connectivity:

  1. Navigate to the top of the interfaces configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 94.
  3. If you are finished configuring the device, commit the configuration.
  4. Go on to any of the following optional tasks:
  5. To verify that the network interface is configured correctly, see Verifying the ISDN Configuration.

Table 94: Configuring an Interface for ISDN Backup

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Interfaces level in the configuration hierarchy.

  1. In the J-Web interface, select Configuration>View and Edit>Edit Configuration.
  2. Next to Interfaces, click Configure or Edit.

From the [edit] hierarchy level, enter

edit interfaces ge-0/0/0 unit 0

Select the physical interface for backup ISDN connectivity.

  1. In the Interface name column, click the physical interface name.
  1. Under Unit, in the Nested Configuration column, click Edit.
 

Configure the backup dialer interface—for instance, dl0.0.

  1. Next to Backup options, click Configure.
  2. In the Interface box, type dl0.0.
  3. Click OK until you return to the Interfaces page.

Enter

set backup-options interface dl0.0

Configuring Dialer Filters for Dial-on-Demand Routing Backup

This dial-on-demand routing backup method allows an ISDN line to be activated only when network traffic configured as an “interesting packet” arrives on the network. Once the network traffic is sent, an inactivity timer is triggered and the connection is closed after the timer expires.

You define an interesting packet using the dialer filter feature of the device. There are two steps to configuring dial-on-demand routing backup using a dialer filter:

Configuring the Dialer Filter

To configure the dialer filter:

  1. Navigate to the top of the interfaces configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 95.
  3. Go on to Applying the Dial-on-Demand Dialer Filter to the Dialer Interface.

Table 95: Configuring a Dialer Filter for Interesting Packets

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Firewall level in the configuration hierarchy.

  1. In the J-Web interface, select Configuration>View and Edit>Edit Configuration.
  2. Next to Firewall, click Configure or Edit.

From the [edit] hierarchy level, enter

edit firewall

Configure the dialer filter name—for example, int-packet.

  1. Next to Inet, click Configure or Edit.
  2. Next to Dialer filter, click Add new entry.
  3. In the Filter name box, type int-packet.
  1. Enter

    edit family inet

  2. Then enter

    edit dialer-filter int-packet

Configure the dialer filter rule name—for example, term1.

Configure term behavior. For example, you might want to configure your interesting packet as an ICMP packet.

To configure the term completely, include both from and then statements.

  1. Next to Term, click Add new entry.
  2. In the Rule name box, type term1.
  3. Next to From, click Configure.
  4. From the Protocol choice list, select Protocol.
  5. Next to Protocol, click Add new entry.
  6. From the Value keyword list, select icmp.
  7. Click OK twice to return to the Term page.

Enter

set term term1 from protocol icmp

Configure the then part of the dialer filter.

  1. Next to Then, click Configure.
  2. From the Designation list, select Note.
  3. Click OK.

Enter

set term1 then note

Applying the Dial-on-Demand Dialer Filter to the Dialer Interface

To complete dial-on-demand routing with dialer filter configuration:

  1. Navigate to the top of the interfaces configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 96.
  3. When you are finished configuring the device, commit the configuration.
  4. Go on to any of the following optional tasks:
  5. To verify that the network interface is configured correctly, see Verifying the ISDN Configuration.

Table 96: Applying the Dialer Filter to the Dialer Interface

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Interfaces level in the configuration hierarchy.

  1. In the J-Web interface, select Configuration>View and Edit>Edit Configuration.
  2. Next to Interfaces, click Configure or Edit.

From the [edit] hierarchy level, enter

edit interfaces dl0 unit 0

Select the dialer interface to apply the filter—for example, dl0.

  1. In the Interface name column, click dl0.
  2. Under Unit, in the Mtu column, click Edit.
 

Select the dialer filter and apply it to the dialer interface.

  1. In the Family section, next to Inet, click Edit.
  2. Next to Filter, click Configure.
  3. In the Dialer box, type int-packet, the dialer-filter configured in Configuring the Dialer Filter, as the dialer-filter.
  4. Click OK.
  1. Enter

    edit family inet filter

  2. Enter

    set dialer int-packet

Configuring Dialer Watch

Dialer watch is a backup method that integrates backup dialing with routing capabilities and provides reliable connectivity without relying on a dialer filter to trigger outgoing ISDN connections. With dialer watch, the device monitors the existence of a specified route and if the route disappears, the dialer interface initiates the ISDN connection as a backup connection.

Adding a Dialer Watch Interface on the Device

To configure dialer watch:

  1. Navigate to the top of the interfaces configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 97.
  3. Go on to Configuring the ISDN Interface for Dialer Watch.

Table 97: Adding a Dialer Watch Interface

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Interfaces level in the configuration hierarchy.

  1. In the J-Web interface, select Configuration>View and Edit>Edit Configuration.
  2. Next to Interfaces, click Configure or Edit.

From the [edit] hierarchy level, enter

edit interfaces

Select a dialer interface—for example, dl0.

Adding a description, such as dialer-watch, can help you identify one dialer interface from another.

  1. Under Interface name, select dl0.
  2. In the Description box, type dialer-watch.
  1. Enter

    edit dl0

  2. Enter

    set description dialer-watch

On a logical interface—for example, 0—specify a dial pool—for example, dw-group—to link the dialer interface to at least one ISDN physical interface.

Then configure the list of routes for dialer watch—for example, 172.27.27.0/24.

  1. Under Unit, click the logical unit number 0.
  2. Next to Dialer options, click Edit.
  3. In the Pool box, type dw-group.
  4. Next to Watch list, click Add new entry.
  5. In the Prefix box, type 172.27.27.0/24.
  6. Click OK.
  1. Enter

    edit unit 0 dialer-options

  2. Enter

    set pool dw-group

  3. Enter

    set watch-list 172.27.27.0/24

Configuring the ISDN Interface for Dialer Watch

To configure the ISDN interface to participate as a dialer watch interface:

  1. Navigate to the top of the interfaces configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 98.
  3. If you are finished configuring the device, commit the configuration.
  4. Go on to any of the following optional tasks:
  5. To verify that the network interface is configured correctly, see Verifying the ISDN Configuration.

Table 98: Configuring an ISDN Interface for Dialer Watch

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Interfaces level in the configuration hierarchy, and select an ISDN physical interface—for example, br-1/0/3 for ISDN BRI.

For ISDN PRI, select a channelized T1/E1/ISDN PRI interface—for example, ct1-1/0/1.

  1. In the J-Web interface, select Configuration>View and Edit>Edit Configuration.
  2. Next to Interfaces, click Configure or Edit.
  3. Under Interface name:
    • For ISDN BRI, click br-1/0/3.
    • For ISDN PRI, click ct1-1/0/1.

From the [edit] hierarchy level:

  • For ISDN BRI, enter

    edit interfaces br-1/0/3 dialer-options pool isdn-dialer-group

  • For ISDN PRI, enter

    edit interfaces ct1-1/0/1 dialer-options isdn-dialer-group

Configure dialer watch options for each ISDN interface participating in the dialer watch feature.

Each ISDN interface must have the same pool identifier to participate in dialer watch. Therefore, the dialer pool name isdn-dialer-group, for the dialer watch interface configured in Table 97, is used when configuring the ISDN interface.

  1. Next to Dialer options, click Edit.
  2. Next to Pool, click Add new entry.
  3. In the Pool identifier box, type isdn-dialer-group.
  4. Click OK.
 

Configuring Dial-on-Demand Routing Backup with OSPF Support (Optional)

Two types of routing protocol traffic are used by OSPF to establish and maintain network structure. First, periodic hello packets are sent over each link for neighbor discovery and maintenance. Second, OSPF protocol traffic achieves and maintains link-state database synchronization between devices. The OSPF demand circuit feature removes the periodic nature of both traffic types and reduces the amount of OSPF traffic by removing all OSPF protocol traffic from a demand circuit when the routing domain is in a steady state. This feature allows the underlying data-link connections to be closed when no application traffic is on the network.

You must configure OSPF on the device before configuring on-demand routing backup with OSPF support. For information on configuring OSPF, see Configuring an OSPF Network.

To configure OSPF demand circuits:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 99.
  3. If you are finished configuring the device, commit the configuration.
  4. To verify that the network interface is configured correctly, see Verifying the ISDN Configuration.

Table 99: Configuring OSPF Demand Circuits

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Protocols level in the configuration hierarchy.

  1. In the J-Web interface, select Configuration>View and Edit>Edit Configuration.
  2. Next to Protocols, click Configure or Edit.
  3. Next to Ospf, click Configure.
  4. Next to Area, click Add new entry.
  5. In the Area id box, type 0.0.0.0.

From the [edit] hierarchy level, enter

edit protocols ospf area 0.0.0.0

Configure OSPF on-demand circuits for each ISDN dialer interface participating as an on-demand routing interface—for example, dl0.

  1. Next to Interface, click Add new entry.
  2. In the Interface name box, type dl0.0.
  3. Select Demand circuit.
  4. Click OK.
  1. Enter

    edit interface dl0

  2. Enter

    set demand-circuit

Configuring Bandwidth on Demand (Optional)

You can define a threshold for network traffic on the device using the dialer interface and ISDN interfaces. A number of ISDN interfaces are aggregated together into a bundle and assigned a single dialer profile. Initially, only one ISDN link is active and all packets are sent through this interface. When a configured threshold is exceeded, the dialer interface activates another ISDN link and initiates a data connection. The threshold is specified as a percentage of the cumulative load of all UP links that are part of the bundle. When the cumulative load of all UP links, not counting the most recently activated link, is at or below the threshold, the most recently activated link is deactivated.

Configuring Dialer Interfaces for Bandwidth on Demand

To configure a dialer interface for bandwidth-on-demand:

  1. Navigate to the top of the interfaces configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 100.
  3. Go on to Configuring an ISDN Interface for Bandwidth on Demand.

Table 100: Configuring a Dialer Interface for Bandwidth on Demand

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Interfaces level in the configuration hierarchy, and select a dialer interface—for example, dl0.

  1. In the J-Web interface, select Configuration>View and Edit>Edit Configuration.
  2. Next to Interfaces, click Edit.
  3. Next to dl0, click Edit.

From the [edit] hierarchy level, enter

edit interfaces dl0

Configure multilink properties on the dialer interface.

  1. Select multilink-ppp as the encapsulation type.

Enter

set encapsulation multilink-ppp

Configure the dialer options.

  • Dial string—Telephone number for the interface to dial that establishes ISDN connectivity—for example, 4085550115. You can configure a maximum of 15 dial strings per dialer interface.
  • Load interval—Interval of time used to calculate the average load on the dialer interface—for example, 90. Default value is 60 seconds with a range of 20-180 seconds. The value must be a multiple of 10.
  • Load threshold—Threshold above which an additional ISDN interface is activated, specified as a percentage of the cumulative load of all UP links—for example 95. Default value is 100 with a range of 0–100.
  • Pool—Name of a group of ISDN interfaces configured to use the dialer interface—for example, bw-pool.
  1. In the Unit section, click Dialer options under Encapsulation.
  2. Next to Dial string, click Add new entry.
  3. In the Value box, type 4085550115 and click OK.
  4. In the Load interval box, type 90.
  5. In the Load threshold box, type 95.
  6. In the Pool box, type bw-pool.
  7. Click OK.
  1. Enter

    edit unit 0

  2. Enter

    edit dialer-options

  3. Enter

    set dial-string 4085550115

  4. Enter

    set load-interval 90

  5. Enter

    set load-threshold 95

  6. Enter

    set pool bw-pool

Configure unit properties.

To configure multiple dialer interfaces for bandwidth-on-demand, increment the unit number—for example, dl0.1, dl0.2, and so on.

F max period—Maximum number of compressed packets allowed between the transmission of full packets—for example, 100. The value can be between 1 and 65535.

  1. Next to Compression, select Yes, and then click Configure.
  2. Select Rtp, and then click Configure.
  3. In the F max period box, type 100.
  4. Next to Queues, click Add new entry.
  5. From the Value list, select q3.
  6. Click OK until you return to the Unit page.
  1. From the [edit] hierarchy level, enter

    edit interfaces dl0 unit 0

  2. Enter

    set compression rtp f-max-period 500 queues q3

Configure logical properties.

  • Fragment threshold–Maximum size, in bytes, for multilink packet fragments. The value can be between 128 and 16320 bytes, for example, 1024. The default is 0 bytes (no fragmentation). Any nonzero value must be a multiple of 64 bytes.
  • Maximum received reconstructed unit (MRRU)—This value is expressed as a number between 1500 and 4500 bytes—for example, 1500.
  1. In the Fragment threshold box, type 1024.
  2. In the Mrru box, type 1500.
  3. Click OK until you return to the main Configuration page.
  1. Enter

    set fragment-threshold 1024

  2. Enter

    set mrru 1500

Define a CHAP access profile with a client and a secret password. For example, define bw–profile with client 1 and password my-secret.

  1. On the main Configuration page next to Access, click Configure or Edit.
  2. Next to Profile, click Add new entry.
  3. In the Profile name box, type bw-profile.
  4. Next to Client, click Add new entry.
  5. In the Name box, type client1.
  6. In the Chap secret box, type my-secret.
  7. Click OK until you return to the main Configuration page.

From the [edit] hierarchy level, enter

set access profile bw-profile client client1 chap-secret my-secret

Navigate to the appropriate dialer interface level in the configuration hierarchy—for example, dl0 unit 0.

  1. On the main Configuration page next to Interfaces, click Configure or Edit.
  2. In the interface name box, click dl0.
  3. In the Interface unit number box, click 0.

From the [edit] hierarchy level, enter

edit interfaces dl0 unit 0

Configure CHAP on the dialer interface and specify a unique profile name containing a client list and access parameters—for example, bw-profile.

  1. Next to Ppp options, click Configure.
  2. Next to Chap, click Configure.
  3. Next to Access data, select Access profile.
  4. In the Access profile box, type bw-profile.
  5. Click OK.

Enter

set ppp-options chap access-profile bw-profile

Configure packet compression.

You can configure the following compression types:

  • ACFC (address and control field compression)—Conserves bandwidth by compressing the address and control fields of PPP-encapsulated packets.
  • PFC (protocol field compression)—Conserves bandwidth by compressing the protocol field of a PPP-encapsulated packet.
  1. Under Compression, select Acfc.
  2. Click OK until you return to the Unit page.

Enter

set ppp-options compression acfc

Configure the dialer interface to be assigned an IP address in one of the following ways:

  • Assign source and destination IP addresses as described in Table 93—for example, 172.20.10.2 and 172.20.10.1. (The destination IP address is optional.)
  • Obtain an IP address by negotiation with the remote end. This method might require the access concentrator to use a RADIUS authentication server.
  • Derive the source address from a specified interface—for example, the loopback interface, lo0.0—and assign a destination address—for example, 192.168.1.2. The specified interface must include a logical unit number and have a configured IP address.

Next to Inet, select Yes and click Configure.

Select one of the following IP address configurations:

To assign source and destination IP addresses:

  1. Next to Address, click Add new entry.
  2. In the Source box, type 172.20.10.2.
  3. In the Destination box, type 172.20.10.1.
  4. Click OK.

To obtain an IP address from the remote end:

  1. Next to Negotiate address, select the Yes check box.
  2. Click OK.

To derive the source address and assign the destination address:

  1. Next to Unnumbered address, select the Yes check box and click Configure.
  2. In the Destination box, type 192.168.1.2.
  3. In the Source box, type lo0.0.
  4. Click OK.

Do one of the following:

  • To assign source and destination IP addresses, enter

    set family inet address 172.20.10.2 destination 172.20.10.1

  • To obtain an IP address from the remote end, enter

    set family inet negotiate-address

  • To derive the source address and assign the destination address, enter

    set family inet unnumbered-address lo0.0 destination 192.168.1.2

Configuring an ISDN Interface for Bandwidth on Demand

To configure bandwidth on demand on the ISDN interface:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 101. Repeat these tasks for each ISDN interface participating in the aggregated link.
  3. If you are finished configuring the device, commit the configuration.
  4. To verify that the network interface is configured correctly, see Verifying the ISDN Configuration.

Table 101: Configuring an ISDN Interface for Bandwidth on Demand

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Interfaces level in the configuration hierarchy, and select an ISDN BRI physical interface—for example, br-1/0/3.

For ISDN PRI, select a channelized T1/E1/ISDN PRI interface—for example, ct1-1/0/1.

  1. In the J-Web interface, select Configuration>View and Edit>Edit Configuration.
  2. Next to Interfaces, click Edit.
  3. Under Interface name:
    • For ISDN BRI, click br-1/0/3.
    • For ISDN PRI, click ct1-1/0/1.

From the [edit] hierarchy level:

  • For ISDN BRI, enter

    edit interfaces br-1/0/3

  • For ISDN PRI, enter

    edit interfaces ct1-1/0/1

Because each ISDN interface must have the same pool identifier to participate in bandwidth on demand, use the dialer pool name bw-pool, the dialer interface configured in Table 100, to configure the ISDN interfaces participating in the pool.

For ISDN BRI, you can group up to four ISDN interfaces together when configuring bandwidth on demand, for a total of eight B-channels (two channels per interface) providing connectivity.

For ISDN PRI, the pool limit is eight B-channels per channelized T1/E1/ISDN PRI port.

  1. Next to Dialer options, click Dialer options.
  2. Next to Pool, click Add new entry.
  3. In the Pool identifier box, type the name of the dialer pool—for example, bw-pool.
  4. Click OK.

Enter

set dialer-options pool bw-pool

Configuring Dial-In and Callback (Optional)

If you are a service provider or a corporate data center into which a remote location dials in during an emergency, you can configure your Juniper Networks device to accept incoming ISDN calls originating from the remote location, or reject the incoming calls and call back the remote location. The callback feature lets you control access by allowing only specific remote locations to connect to the device. You can also configure the device to reject all incoming ISDN calls.

Note: Incoming voice calls are currently not supported.

When it receives an incoming ISDN call, the Juniper Networks device matches the incoming call's caller ID against the caller IDs configured on its dialer interfaces. If an exact match is not found and the incoming call's caller ID has more digits than the configured caller IDs, the device performs a right-to-left match of the incoming call's caller ID with the configured caller IDs and accepts the incoming call if a match is found. For example, if the incoming call's caller ID is 4085550115 and the caller ID configured on a dialer interface is 5550115, the incoming call is accepted. Each dialer interface accepts calls from only callers whose caller IDs are configured on it.

The dialer interface of the device and the dialer interface of the remote device must have the same encapsulation—PPP, Multilink PPP, or Cisco HDLC. If the encapsulation is different, the ISDN call is dropped. Table 102 describes how the device performs encapsulation monitoring.

Table 102: Encapsulation Monitoring by Juniper Networks Devices

Encapsulation on Juniper Networks Device's Interface

Encapsulation on Remote Router's Dialer Interface

Possible Action on Juniper Networks Device's Dialer Interface

Encapsulation Monitoring and Call Status

PPP

PPP

  • Accepts an incoming call
  • Rejects an incoming call and calls back the incoming number when callback is enabled on the dialer interface

Device performs encapsulation monitoring.

ISDN call is successful because encapsulation matches.

Multilink PPP

Multilink PPP

PPP

Multilink PPP or Cisco HDLC

Device performs encapsulation monitoring.

ISDN call is dropped because of encapsulation mismatch.

Multilink PPP

PPP or Cisco HDLC

PPP or Multilink PPP

PPP, Multilink PPP, or Cisco HDLC

  • Dials out
  • Accepts an incoming call as a result of having originally dialed out, because the dialer interface of the remote device has callback enabled

Device does not perform encapsulation monitoring.

Success of the ISDN call depends on the encapsulation monitoring capability of the remote device.

Cisco HDLC

PPP, Multilink PPP, or Cisco HDLC

  • Dials out
  • Accepts an incoming call
  • Accepts an incoming call as a result of having originally dialed out, because the dialer interface of the remote device has callback enabled
  • Rejects an incoming call and calls back the incoming number when callback is enabled on the dialer interface

This section contains the following topics:

Configuring Dialer Interfaces for Dial-In and Callback

To configure a dialer interface for dial-in and callback:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 103.
  3. If you are finished configuring the device, commit the configuration.
  4. To verify that the network interface is configured correctly, see Verifying the ISDN Configuration.

Table 103: Configuring the Dialer Interface for Dial-In and Callback

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Interfaces level in the configuration hierarchy, and select a dialer interface—for example, dl0.

  1. In the J-Web interface, select Configuration>View and Edit>Edit Configuration.
  2. Next to Interfaces, click Configure orEdit.
  3. Next to dl0, click Edit.

From the [edit] hierarchy level, enter

edit interfaces dl0

On a logical interface—for example, 0—configure the incoming map options for the dialer interface. To use dial-in, you must configure an incoming map on the dialer interface.

  • Accept all—Dialer interface accepts all incoming calls.

    You can configure this option for only one of the dialer interfaces associated with an ISDN physical interface. The dialer interface configured to accept all calls is used only if the incoming call's caller ID does not match the caller IDs configured on other dialer interfaces.

  • Caller—Dialer interface accepts calls from a specific caller ID—for example, 4085550115. You can configure a maximum of 15 caller IDs per dialer interface.

    The same caller ID must not be configured on different dialer interfaces. However, you can configure caller IDs with more or fewer digits on different dialer interfaces. For example, you can configure the caller IDs 14085550115, 4085550115, and 5550115 on different dialer interfaces.

  1. In the Unit section, for logical unit number 0, click Dialer options under Encapsulation.
  2. Next to Incoming map, click Configure.
  3. From the Caller type menu, select Caller.

    Next to Caller, click Add new entry.

  4. In the Caller id box, type 4085550115.
  5. Click OK until you return to the Dialer option page.
  1. Enter

    edit unit 0

  2. Enter

    edit dialer-options

  3. Enter

    set incoming-map caller 4085550115

Configure callback options for the dialer interface

  • Callback—Enable this feature to allow the ISDN interface to reject incoming calls, wait for 5 seconds (the default callback wait period), and then call back the incoming number.

    Before configuring callback on a dialer interface, ensure that the following conditions exist:

    • The dialer interface is not configured as a backup for a primary interface.
    • The dialer interface does not have a watch list configured.
    • Only one dial string is configured for the dialer interface.
    • Dial-in is configured on the dialer interface of the remote device that is dialing in.
  • Callback wait period—Number of seconds to wait before redialing an incoming ISDN call.
  1. Select Callback.
  2. In the Callback wait period box, type 5.
  1. Enter

    set callback

  2. Enter

    set callback-wait-period 5

Configuring an ISDN Interface to Screen Incoming Calls

By default, an ISDN interface is configured to accept all incoming calls. If multiple devices are connected to the same ISDN line, you can configure an ISDN interface to screen incoming calls based on the incoming called number.

You can configure the incoming called numbers that you want an ISDN interface to accept. You can also use the reject option to configure a called number that you want an ISDN interface to ignore because the number belongs to another device connected to the same ISDN line. For example, if another device on the same ISDN line has the called number 4085551091, you can configure the called number 4085551091 with the reject option on the ISDN interface so that it does not accept calls with that number.

When it receives an incoming ISDN call, the device matches the incoming called number against the called numbers configured on its ISDN interfaces. If an exact match is not found, or if the called number is configured with the reject option, the incoming call is ignored. Each ISDN interface accepts only the calls whose called numbers are configured on it.

To configure an ISDN interface to screen incoming ISDN calls:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 104.
  3. If you are finished configuring the device, commit the configuration.
  4. To verify that the network interface is configured correctly, see Verifying the ISDN Configuration.

Table 104: Configuring an ISDN Interface to Screen Incoming ISDN Calls

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Interfaces level in the configuration hierarchy, and select an ISDN physical interface—for example, br-1/0/3.

For ISDN PRI, select a channelized T1/E1/ISDN PRI interface—for example, ct1-1/0/1.

  1. In the J-Web interface, select Configuration>View and Edit>Edit Configuration.
  2. Next to Interfaces, click Configure or Edit.
  3. Under Interface name:
    • For ISDN BRI, click br-1/0/3.
    • For ISDN PRI, click ct1-1/0/1.

From the [edit] hierarchy level:

  • For ISDN BRI, enter

    edit interfaces br-1/0/3

  • For ISDN PRI, enter

    edit interfaces ct1-1/0/1

Configure the incoming called number—for example, 4085550115—for the ISDN interface.

To configure the ISDN interface to ignore the incoming called number, use the reject option.

  1. Next to Isdn options, click Edit.
  2. Next to Incoming called number, click Add new entry.
  3. In the Called number box, type 4085550115.
  4. Click OK.

Enter

set isdn-options incoming-called-number 4085550115

Configuring the Device to Reject Incoming ISDN Calls

By default, the device is configured to accept incoming ISDN calls. The incoming calls are accepted if dial-in is configured on the device. You can configure the device to reject all incoming ISDN calls.

To configure the device to reject incoming ISDN calls:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 105.
  3. If you are finished configuring the device, commit the configuration.
  4. To verify that the network interface is configured correctly, see Verifying the ISDN Configuration.

Table 105: Configuring the Device to Reject Incoming ISDN Calls

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Processes level in the configuration hierarchy.

  1. In the J-Web interface, select Configuration>View and Edit>Edit Configuration.
  2. Next to System, click Configure or Edit.
  3. Next to Processes, click Configure.
  4. Next to Isdn signaling, click Configure.

From the [edit] hierarchy level, enter

set system processes isdn-signaling reject-incoming

Configure the device to reject incoming calls.

  1. Select the Reject Incoming check box.
  2. Click OK.
 

Disabling Dialing Out Through Dialer Interfaces

The JUNOS ISDN dialer services process manages dialing out through dialer interfaces. You can disable dialing out through all dialer interfaces by disabling the dialer services process.

Caution: Never disable a software processes unless instructed to do so by a Customer Support engineer.

To disable dialing out through dialer interfaces:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 106.
  3. If you are finished configuring the device, commit the configuration.

Table 106: Disabling Dialing Out Through Dialer Interfaces

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Processes level in the configuration hierarchy.

  1. In the J-Web interface, select Configuration>View and Edit>Edit Configuration.
  2. Next to System, click Configure or Edit.
  3. Next to Processes, click Configure.
  4. Next to Dialer services, click Configure.

From the [edit] hierarchy level, enter

set system processes dialer-services disable

Disable dialing out through dialer interfaces.

  1. Select the Disable check box.
  2. Click OK.
 

Disabling ISDN Signaling

The JUNOS ISDN signaling process manages ISDN signaling by initializing ISDN connections. You can disable ISDN signaling by disabling the ISDN signaling process.

Caution: Never disable a software processes unless instructed to do so by a Customer Support engineer.

To disable ISDN signaling:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 107.
  3. If you are finished configuring the device, commit the configuration.

Table 107: Disabling ISDN Signaling

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Processes level in the configuration hierarchy.

  1. In the J-Web interface, select Configuration>View and Edit>Edit Configuration.
  2. Next to System, click Configure or Edit.
  3. Next to Processes, click Configure.
  4. Next to Isdn signaling, click Configure.

From the [edit] hierarchy level, enter

set system processes isdn-signaling disable

Disable ISDN signaling on the device.

  1. Select the Disable check box.
  2. Click OK.
 

[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]