Remote Access

Last Updated : Sep 16, 2022 |

The system support remote access for incoming data calls on trunks.





To do remote access, an incoming call is passed through the following elements of the system configuration.

  • Incoming Call Route A Incoming Call Route is used to match incoming remote access calls and pass them to a RAS service as the destination.

  • RAS Service The RAS service defines settings relating to the data traffic methods usable with the call.

  • User The user defines the name and password required for the RAS service. The user must have Dial In On enabled. An R setting on the user's Source Numbers tab can be used to define the ICLID from which RAS calls are accepted.  

  • Time Profile The user settings can specify a time profile. The time profile then controls when remote access is allowed.  

  • Firewall Profile The user settings can specify a firewall profile. The firewall profile then controls what traffic is allowed through the remote access connection.

  • Static NAT   The system supports the use of Static NAT records in firewall profiles. These are used to translate external IP addresses to internal IP addresses.

  • System | LAN The system can provide DHCP support for remote access connections when it is set to Server or Dial in modes.  Alternatively the remote access client can use a static IP address on the system's subnet.

  • IP Route If the remote access client uses a IP address that is from a different subnet from the system, then a IP route record is required for returning data. The RAS service is set as the destination.

ISDN Remote Access Example





Create a User   The required details are:

  • In the User tab: Enter a Name and Password. The system is case sensitive. Remember to take care with passwords as this is a remote access link into your network.

  • In the Dial In tab: Ensure that Dial In On is ticked. The Firewall Profile and Time Profile are optional.

Create a RAS Record  

In the RAS tab: Enter the same name as the user that you created earlier. Again, remember this is case sensitive.

Create an Incoming Call Route  

  • Set the Bearer Capability to Any Data.

  • In the Destination drop-down list, select the RAS record created above.

  • The values that you enter for any of the other fields will depend on whether the remote user will be calling in on a particular line, number or from a set ICLID.

  1. Is a Return IP Route Needed ? Go to Step 5.

  2. Create a IP Route (Optional) If the remote user has an IP address that is not in the same domain as the system, then an IP Route is needed for return data. This is not necessary if the remote user's dial-up connection method is set to 'Obtain an IP Address Automatically' and the system's DHCP mode is set to Server or Dial In.

    • Enter the IP Address and IP Mask of the remote system.

    • In the Destination drop-down list select the RAS record created above.

Analog Remote Access Example





Configuration for a connection from an analog modem call is very similar to the ISDN example. However the system must be able to answer modem calls. This can be done in the following ways:

  • Analog Trunk Modem Mode On systems with an analog trunk card in the control unit, the first analog trunk can be set to answer V.32 modem calls. This is done by checking the Modem Enabled option on the analog line settings or using the default short code *9000* to toggle this service on or off.  

  • IP500 ATM4 Uni Trunk Card Modem Support It is not required to switch the card's modem port on/off. The trunk card's V32 modem function can be accessed simply by routing a modem call to the RAS service's extension number. The modem call does not have to use the first analog trunk, instead the port remains available for voice calls.

When using an analog modem, the Bearer Capability of the incoming call route used should be Any Voice.

Related information
Overview of Data Routing