Справочное Руководство для Netopia 430 s

Netopia can answer calls as well as initiate them. To answer calls, 
Netopia uses an answer profile, just as it uses a connection profile 
to make calls. Netopia’s answer profile controls how incoming calls 
are set up, authenticated, filtered, and more.

The answer profile works like a guard booth at the gate to your 
network: it only scrutinizes incoming calls. Like the guard booth, the 
answer profile allows calls based on a set of criteria that you define.

The main criterion used to check calls is whether they match one of 
the connection profiles already defined. If PAP or CHAP 
authentication is being used, the answer profile checks that the 
incoming call’s name and password/secret match the receive name 
and password/secret of a connection profile. If PAP or CHAP are not 
being used, an incoming call is matched to a connection profile 
using the remote network’s IP address (that is, the caller is defined 
as the destination of a par ticular connection profile).

You could instruct the answer profile to allow calls in even if they fail 
to match a connection profile. Continuing the guard booth analogy, 
this would be like removing the guards or having them wave all calls 
in, regardless of their source.

If an incoming call is matched to an existing connection profile, the 
call is accepted. All of that connection profile’s parameters, except 
for authentication, are adopted for the call.

If an incoming call is not required to match a connection profile, and 
fails to do so, it is accepted as a standard IP connection. Accepted, 
unmatched calls adopt the call parameter values set in the answer 
profile (see below).