<Help>
<Connection: PPP Parameters>
<Connection: Special Parameters>

        Connection Folder
        -----------------
        Provide connection information, such as the type of encapsulation
        (PPP versus MP) and Data Compression, on this folder.

        Double click RIGHT mouse button on any
        button or field for help.

<PPP>
<MP>
<Encapsulation>

        This needs to be set to same value, PPP or MP,
        on BOTH ends of your connection.

        This field determines the type of header information
        (regular PPP header, or RFC1717 compliant MultiLink header)
        prepended to data transferred across the connection.

        If you plan to use multiple links, i.e., ISDN
        phone numbers, on this connection, you will probably want
        to select MP, but please check with the administrator at
        the other end of the connection to see if they support RFC1717 MP.

        There are some cases where you may want to use PPP encapsulation
        even though you plan to use multiple links:
        One example: you are interoperating with a Sun system running
        SunISDN 1.0.2, and wish to use Sun's proprietary scheme for
        multilink operation.

<VJ>
<Header Compression>

        Click on VJ to set Van Jacobson compression.

<Data Compression>

        Options are ccp or off. You may use CCP with PPP encapsulation
        on one link only.

        The "ccp" option stands for "Compression Control Protocol (CCP)"
        and it is an Internet Draft(draft-ieft-pppext-compression-04.txt).

<Compression Type>

        This field is only relevant when you have selected CCP
        Data Compression.

        Select stac_ascend when connecting to an Ascend device.
        Select stac otherwise.

        Refer to the Internet-Draft "PPP Stac LZS Compression Protocol"
        (draft-ieft-pppext-stacker-0.6.txt) for Stac compression algorithm.

<STAC Check Mode>

        This field is only relevant when you have selected CCP
        Data Compression, and have selected "stac" Compression Type.

        Options are:
        lcb:       Perform a longitudinal check on a packet.
        crc:       Calculate a complex checksum using crc16 polynomials.
        sequence3: Use "old style" packet sequence number to perform check
        sequence4: Use "new style" packet sequence number to perform check

        Set this to lcb to interoperate with Cisco.
        Set this to seq3 to interoperate with Network Express.
 
<Inactivity Timeout>
 
        This determines the number of seconds the line can remain
        inactive (no data transfer) before the ISDN connection is closed.
 
        The default is set at 120 (2 minutes).
 
        Timing for this parameter is critical.
        If the value is set too small, the pre-connection handshaking
        between systems will take longer than the timeout value and
        no connection will be possible. If the value is set too long,
        the connection may be held open unnecessarily, resulting in charges
        for periods when no communication occurred. Local connections will
        take substantially less time than international calls.
 
<IP Setup Timeout>
 
        This is the time allowed, in seconds, to successfully establish
        the IP connection. The call is disconnected if time runs out.
 
        The default is set at 120 seconds.
        We recommend that you use the default value or a higher value.
 
<Callback>
 
        Click On if and only if this is a callback connection.
        In a telecommuting situation this would often be set to On
        with the central server controlling the bandwidth.  Internet service
        providers do not provide callback and in this case the local
        machine must be set up as a bandwidth controller when using more
        than one channel.  Callback must be correctly set on both ends of
        the connection so if your machine is is being called back by a
        server set this value to ON and leave the new default value -
        "They Will Callback"
 
        The normal default is Off.
 
<We Will Callback>
<They Will Callback>
<Callback Type>
 
        Set this to "We Will Callback" if the local machine will be
        calling back.  Otherwise, set this to "They Will Callback"
        if the remote machine will be calling back.
 
<Reenable Timeout>
 
        This is only relevant on the machine that is being called back.
 
        Further attempts to make calls on this connection are disabled
        for during the callback setup, while we wait for the other
        side to call us back. Timeout period is in units of seconds.
 
        Default value is 30 seconds.
 
<Callback Timeout>
 
        This is only relevant on the machine that does the callback.
 
        The machine waits for this period (in seconds), after receiving
        the call, to initiate the callback.
        
        Default value is 10 seconds.
 
<Bandwidth Controller>
 
        This is only relevant if you have multiple phone lines defined.
        A typical situation would be connecting to a telecommuting server.
        The server would have callback set to On and bandwidth controller
        set to On. The local machine (assuming you are the telecommuter)
        would be able to call in and the server will then call back and
        add additional links if necessary (up to 10 links or 24 B channels).
 
        Only ONE side of the connection can have bandwidth controller
        turned on. The side with this field turned On will control the
        amount of bandwidth (number of ISDN links) used on the connection
        by adding and deleting links, as needed.
        
        Internet service providers do not provide callback and in this case the
        local machine must be set up as a bandwidth controller when using more
        than one channel.
 
        The default is off.

	If this field is turned on, be sure to configure at least two called
        number entries in the Phone Folder. If the "bandwidth controller" is
        on and only one ISDN card is installed in the system, an additional
        called number will be composed implicitly by copying information from an
        existing phone entry if only one called entry is configured by the
        user.
 
<Hunt Mode>
 
        This is only relevant if you have multiple phone lines defined.
 
        Setting this to On simulates the behavior of a hunt-group.
        When attempting to make a connection, or add additional links
        to the connection, the PPP subsystem will sequentially go
        through all defined phone lines, till the desired connection,
        or link, has been established.
 
        Saves all the parameters you have defined to the isppp.cf file.
        If you did not click the OK button in the previous window,
        those parameters will be saved too.
 
	Note that Hunt Mode cannot be set if you have Bandwidth Controller is set.
	Note that Hunt Mode cannot be set if Callback is set and "We Will Callback" is true.

<Dynamic IP Address>
 
        Applies to point-to-point (isptp) interfaces only.
        Allows the other side, usually a server,  to assign an
        IP address to this side of the connection.
 
<Reset>
        Reverts back to the last values applied by doing a Save in any
        of the isdntool windows. All values changed in the window are
        lost.
 
<Defaults>
 
        Restores the default values for the parameters in this window.
        This will override any previously saved values if you Default
        and then OK (save).

<OK>
        Saves all global and specific parameters for all connections
        into the file /etc/opt/SUNWisdn/isppp.cf. The window then
        closes automatically.
 
        Isdntool will make a SINGLE BACKUP COPY ON EACH Save. If you
        make a mistake in applying the configuration, the old configuration
        file can be retrieved from /etc/opt/SUNWisdn/isppp.cf.bak
 
<Save>
        Saves all parameters (including parameters on other pages!)
        associated with this connection to an intermediate file.
 
<Save & Dismiss>
        Saves all parameters associated with this connection.
        Parameters are saved to an intermediate file.
        After saving, this window is closed.
 
        Note that this only saves THIS connection.
        You must again press "Save and Dismiss" on the
        "PPP Configuration Options" window (the one showing the
        Connection Database) in order to save all parameters
        associated with all connections to the PPP configuration
        file /etc/opt/SUNWisdn/isppp.cf.
        
<Dismiss>
        WARNING: this exits the "Connection Settings" window without
        saving any new data you may have entered for this connection.
