AT+i Programmer's Manual - SE Spezial-Electronic AG

27 iChip RAS Server
27.1 Introduction
iChip RAS Server
iChip features an internal Remote Access Server (RAS) that allows a remote dialer to dial
into iChip using an active modem platform. When configured as RAS, iChip answers the
incoming call and negotiates a PPP connection.
iChip‘s RAS supports acknowledging an IP address request from the remote dialer side,
as well as assigning a default IP address. Once the connection is established, the client
can browse iChip‘s website. (If the AWS parameter is set to a non-zero value.) All other
iChip IP protocol functionality is also enabled, allowing the host to issue Internet
protocol AT+i commands based on the PPP connection. Note, however, that since iChip
is not connected to an actual ISP in this mode, iChip does not have access to the public
Internet and thus only direct connections between iChip and the connected PPP client are
possible.
27.2 RAS Parameters
Three parameters govern the use of iChip‘s RAS server:
RAU RAS Login User Name
The RAU parameter defines the allowable user name for login purposes
when iChip answers an incoming call as a RAS. The remote dialer must
specify the correct user name and matching password in order to
successfully complete the PPP connection. This parameter must have a
non-empty value for the RAS feature to be enabled. Otherwise, when RAU
is empty, iChip‘s RAS is effectively disabled. When RAU contains the
special character (*), RAS is enabled but no authentication is required.
RAP RAS Login Password
The remote dialer must provide the correct password in order to
successfully complete the PPP connection. When the RAP parameter is
empty or contains a (*), any password string is accepted, in effect
nullifying the authentication process.
RAR Number of RINGs before picking up the line.
When the RAS feature is enabled, the RAR parameter defines the number
of RINGs that must arrive before iChip picks up the line and transfers
control to its RAS.