
Using Shorthold Mode 75
Callback numbers
Regardless of whether the RAS client or the RAS server carries the charges, the server
requires the client’s correct callback number.
Note: If the exchange does not send the client’s call number, the WAN-Miniport driver
will reject the RAS server’s shorthold requests. In this case, it will have no information on
what number it should dial for a callback.
If the RAS client numbers provided by the exchange cannot be called back, for example
because the leading zero for the area code (Euro-ISDN) or the number required for
external calls with PBX systems is not provided, there are two options:
• Call number check (see Number Checking
on page 33):
The correct callback number is preconfigured for every RAS client.
• Callback prefix (see Callback Prefix
on page 32):
One or more digits are placed before the callback numbers of all RAS clients (e.g. for
an external call).
Callback numbers with callback
If the server is being operated in callback mode, the call number or the callback prefix is
not checked when establishing the connection after a shorthold. The WAN-Miniport driver
records all PPP callback queries and the negotiated callback period internally and
compares them with the incoming and outgoing calls. Because the server has already
dialed the right number on callback, it makes no difference if the exchange has provided
an incomplete number. If all calls are made with unique identifiable MSN/EAZs, the
WAN-Miniport driver will recall the right number.
Determining correct callback numbers
The call number provided by the exchange and the actual number called can be displayed
as follows:
Set up a trace file with the Diva Server Diagnostics tool (see Diva Server Diagnostics
on
page 119). The number can be read at the entries ‘Called by xxx’ or ‘Dialing xxx.’
Kommentare zu diesen Handbüchern