Installation guide

Dial-up and persistent connections 30-3
Chapter 30: Understanding Wave Data Networking
Wave Global Administrator Guide
Note: It is acceptable to configure an Integrated Services Card (ISC1) or VAM with multiple
IP addresses, and for the card to have multiple subnets. While it is sometimes useful to preserve
a pre-Wave configuration, we recommend that you do not do this normally, as it can be
confusing to administer.
Dial-up and persistent connections
The Wave Server supports various kinds of dial-up and persistent connections.
Dial-up connections
A dial-up connection is created and ended on an as-needed basis. A dial-up connection typically
has a phone number associated with it. The connection is made only when a phone call connects
the Wave Server with an ISP or with a corporate headquarters over a WAN. A dial-up
connection (also known as a switched connection) is the RRAS default.
Using ISDN or the modem port(s) on the Integrated Services Card, you can configure the Wave
Server for dial-up connections, routing data using Microsoft RRAS. Both Wave modems and
ISDN serve as system resources for dial-in and dial-out calls.
Dial-in calls come from a remote office over a digital or analog trunk to Wave. Modems and
ISDN are configured so that remote dial-in calls will automatically connect through the Wave
Server.
Dial-out calls are made from Wave over a digital or analog trunk to an Internet Service Provider
or to another site. The type of dial-out calls made when a user requests an Internet connection,
known as dial-on-demand or demand-dial calls, depends on trunk type and protocols in use, as
well as modems, and can be set up through the RRAS administrator application.
Caution: Do not set an interface for dial-on-demand if you intend to use it for
continuous monitoring of the Wave Server. If the monitoring traffic is high, the
connection will never be disconnected. In addition, if you are monitoring the Wave
Server using SNMP over the dial-on-demand connection when the connection is
disconnected, this will generate an SNMP trap causing the connection to be
reconnected. The end result is that the connection will continually be going up and
down.
Release 2.0
September 2010