MultiAccess ACS MA420, MultiAccess ACS MA820

1) Introduction:

The MA420 and MA820 are 4 port and 8 port Analog Communication Servers for use with standard POTS lines (PSTN or equivalent). The ACS provides dial in PPP connections for remote nodes that need IP access to the LAN the unit is installed on. The ACS can also provide modem pool functionality for computers on the LAN.

This document compliments the information found in the Quick Start and User guides. It may be to your benefit to re-read this document after using the Quick Start Guide that ships with the product.

Please Note: This document has been updated to address a significant change implemented in version 1.03. Prior to 1.03, the ports of the unit were to be configured for 1 of 2 specific roles (for which they were then dedicated to just that role). Now in 1.03, the ports are configured for both roles (alleviating the need for administrator intervention when either role is needed).

Document Outline

1. Introduction: This document is intended to compliment hands on experience.

2. General Usage: There are two primary ways to use the modems in this unit, RAS and Modem Sharing.

3. Hardware Notes: Physical architecture.

4. Software Notes: Defaults, Misc. Administrative, Version History.

5. Configuration Objectives: General, RAS Role, Modem Sharing Role.

6. Updates: General.

7. Tech Tips: General, Modem Behavior, RAS/PPP, RADIUS Authentication, Modem Sharing, Microsoft DUN and IAS compatibility, Setting Up MCSI200 Com Port Redirector.

8. Known Issues: Default Modem Setup and Modem Sharing, MCSI2000 and Authentication, Extra Sockets and Modem Sharing Calls Not Logged.

 

2) General Usage:

The product has two roles (usage), RAS and Modem Sharing.

RAS solution: The ACS can be used as a dial in PPP Remote Access Server in a LAN to Client environment. The purpose of which is to give remote nodes (i.e. Microsoft Dial-Up Networking clients) TCP/IP access to the same subnet and LAN the ACS is installed on. Masquerading (NAT) and LAN to LAN routing (assignment of an entire subnet) are IP networking techniques not supported by the ACS. The supported PPP security protocol (means of communicating user credentials between PPP end points) is PAP (only).

Modem Sharing solution: The modems in the ACS can be a shared resource on your network, commonly referred to as a network modem pool. Computers with network access to the ACS can use Telnet and get direct AT command access to one of the modems in the ACS (for either outbound or inbound calls). A common way to take advantage of this role is by installing com port redirector software (i.e. Multi-Tech’s MCSI2000 for WindowsXP and Windows 2000) on your workstations. The redirector adds a virtual com port to the workstation and uses Telnet to map (redirect) the com port to a modem in the ACS. The redirector and Telnet session replaces the UART based hardware of a PC and serial cable connection normally found in traditional modem installations. A communication program using this virtual com port will have it’s data redirected to & from the modem within the ACS, making the modem appear as if it were attached directly to a communication port on the workstation.

 

3) Hardware Notes:

The unit consists of one primary server board that runs the ACS firmware, with 4 or 8 MT5634SMI-V92 modems mounted internally.

There are 7 or 11 physical connectors on the unit (depending if the unit is the MA420 or MA820). Power, RJ-45 for Ethernet, RJ-45 for serial port command line and 4 or 8 RJ-11 connectors for analog POTS lines.

The command port operates at 115200 BPS, 8N1 and No Flow Control. The command port pin out configuration is DCE. Count the pins by looking into female RJ-45 connector, pin 1 is on the left with pin 8 on the right. Three pins are used. Pin 4 is TD (input), data from the DTE. Pin 5 is RD (output) data for the DTE. Pin 8 is ground.

The unit does not contain an onboard real time clock. The unit is an SNTP client, used to derive time and date from a network time server.

 

4) Software Notes:

Configuration and management of the unit is web (HTTP) based. The default administrator login username is "admin" with a password of "admin". These credentials also have dial in and dial out access rights. The default IP address is 192.168.2.1 with a 24 bit netmask (a.k.a. subnet mask of 255.255.255.000). The MTS Device Manager software is used to update the ACS firmware and the MT5634SMI-92 Global firmware. Additional updating details are listed below. A developer’s command line interface is accessible via standard telnet and via the command jack on the back of the unit. Command line access should only be used at the direction of engineering.

Version History:

1.03. Released March 2007. Added support for new Day Light Savings dates starting in 2007. Added Non Pool TCP socket number to Modem Sharing. Added new Auto Detect Usage feature. If there is NOT a Telnet session connected to the POTS port, an incoming call will be handled by the ACS as a RAS call. When there IS an active Telnet session connected to the POTS port, the modem’s configuration and behavior is then controlled by the application that opened the Telnet session (be it for outbound or inbound calls). Fixed Call History issue related to call duration of 30 minutes or longer. Fixed Local Authentication issue with Modem Sharing. Fixed the Current Status page, added the status of Modem Sharing for POTS ports used in Modem Sharing connections.

1.02. New Product June 2006. First production release, included MT5634SMI modem code 1.32i.

 

5) Configuration Objectives:

Please see the printed Quick Start guide (that ships with the unit) for initial out of the box configuration. The primary purpose of the quick start guide is to get the unit physically installed on your Ethernet network and to get it’s IP network parameters set for your network.

Once logged into the unit via HTTP use the following menus to address specific aspects.

Use the Administration menu to setup the unit for the network it is to be placed in (the IP Configuration section is the required minimum).

The unit needs to be given a static IP address (it does not use DHCP). Define the subnet mask, default gateway (which is the route off the network) and define the IP address of your DNS server. This DNS server will be used by the ACS to resolve names (like when the ACS sends an administrative email notification) and this address will be given to the dial in RAS users as the DNS they can use. Setup administrative email notification. Setup date and time via SNTP. The unit can be restarted from this menu as well.

Use the Modem Setup menu to define Modem Sharing behavior and general modem parameters (country code and number of rings before auto answer).

The Modem Sharing method can be with or without an authentication process. Modem Sharing with authentication means a login prompt will be issued into the socket (to the user) when it is opened. Who (what) ever opened the socket must provide appropriate credentials before access is given to the modem. The database of user’s names and passwords the ACS will check against can be one of two choices. A local database (defined within the ACS) or a RADIUS database (defined in a RADIUS server external to the ACS).

The type of Telnet connection (mode) can be "Raw" (or not raw). A raw Telnet connection is one that does not respond to or use Telnet and RFC 2217 escape sequences (flags). When RAW is not used, packets of FF will be interpreted as escape flags. The escape routine includes a process of removing and replacing escape flags and subsequent characters normally intended for command and control function between Telnet hosts (RFC 2217 com port control via Telnet).

The TCP port (socket) number used by Telnet to access the modem is dependent on how the Modem Sharing Pool option is set. If this option is set to "pool", 6000 is used. All POTS modem ports set to pool (6000) must have the same exact Modem Sharing option (with or without authentication, etc). When a Telnet client on the LAN opens a connection to 6000, it is given the lowest numbered POTS modem port that is not in use. If this option (Modem Sharing Pool) is set to "non pool" then a specific 7000+ number is sequentially associated to each POTS modem (POTS modem 1 is assigned 7000, POTS modem 2 is assigned 7001 and so on incrementally through POTS modem 8 with 7007).

Use the Authentication menu to setup the remote host address and authentication method (RADIUS or Local) for RAS calls. The RADIUS Client details defined here will also be used by Modem Sharing when it is set to use RADIUS Authentication.

For RAS (dial in PPP) a second static IP address is needed. This address is for the dial in user (PPP peer). This address is defined in the Remote Host Address field. This address needs to be on the same subnet (network number) as that of the ACS.

The Authentication Type field in this menu only applies to RAS calls. When the type is set to Local, the ACS will look to match the credentials provided by the caller with credentials listed in the Local Users menu. Additionally, local users can be called back at a fixed pre-defined number that is entered\defined by the "administrator" at the time of setting up the local account or the client (PPP peer) can be called back at a variable (always changing number) that is entered by the "user" at the time of dialing in.

When the type is RADIUS, the ACS will send the credentials to the RADIUS Server that is defined in this menu.

RADIUS Accounting is a process that starts after successful RADIUS authentication. The ACS sends an accounting start packet to the accounting server defined in this menu. When the user disconnects, the ACS sends an accounting stop packet to the accounting server. RADIUS accounting summaries the time and date, duration, POTS port connected on and IP address given to the user, for this particular call. RADIUS Accounting does not track the amount or type of data of the session or the places the user communicates with.

The Secret is an encryption key used by both the RADIUS Server and RADIUS Client and so it must be the same alpha numeric string (including case) defined in both. The ACS implements MD5 encryption.

The RADIUS Server has to be listening on the same set of UDP ports that the RADIUS Client (ACS) is using.

Use the Local Users menu to add users to the local database.

Add local users when the Authentication Menu has the Authentication Type set to "Local" or when Modem Sharing is set with Local Authentication. Local users that are added will have dial in and dial out rights, but they will not have administrator rights.

 

6) Updates:

MT-Device Manager version 1.05.06 or newer is used to update the version of ACS firmware and the version of MT5634SMI modem code. There is a specific ACS firmware file for each model of ACS. However the modem code (file used) is the exact same version in both models. Install the Device Manager on a PC that has full IP access to the ACS. The MT-Device Manager uses Telnet and TFTP to communicate with the ACS, which includes the use of various additional TCP and UDP ports in 1500s,2200s and 3000 ranges. Refer to Appendix A of the MA420 & MA820 User Guide (P/N S000404B Rev C) for a detailed update procedure.

 

7) Tech Tips:

Administration

If the IP address of the unit is unknown, from the serial command port on the back of the unit issue the command ifconfig.

If you do not know the HTTP admin account password, from the serial command port on the back of the unit issue the command "cat /var/config/cfgtxtfile" (without the quotes). Look for the "userid" and "password" values for the first entry (index 0) in the "phonebook" section near the top of the file.

Modem Behavior

The ACS system automatically initializes the MT5634SMIV92 Global modem after certain events. The user can also manually invoke the initialization of the modem from the Current Status menu when the modem is idle and there is not an active telnet connection.

The ACS system issues two strings for each initialization event:

AT &F E0 %T19,0,34 &D2 M0 S0=n +FCLASS=0

AT *H4 +VCID=n

The Modem Setup menu allows for the user to control the number of rings to answer on (S0=n), the Country Code (%T19,0,nn) and the displaying of caller id information (+VCID=n) for Modem Sharing applications. The modem initialization events are:

Upon system boot up (power up or unit reset).

After RAS call disconnects.

After Telnet connection is closed\terminated.

When the "Initialize Modem" button is pressed in the Current Status menu.

When the "Update" button is pressed in the Modem Setup menu.

The *Hn command controls the On-Hook Delay feature. This feature keeps the line busy (for the duration specified) after each disconnect event (on hook event). This is a safeguard while the system re-initializes for the next call.

*H0 = Feature Disabled (&f command sets *H0).

*Hn, where n is a value of 0 through 99. Unit value is 10 seconds. So *H4 is a delay of 40 seconds before the modem releases the line.

When the modem is being used via Modem Sharing access, the application using the modem is responsible for the modem’s configuration. Depending on the application, it may be appropriate to disable the *H delay (issue &f or *H0) before establishing calls.

RAS Information

PPP Link: PAP is the only supported PPP authentication protocol. PAP (a sub protocol of PPP) is used to communicate user credentials across the PPP link (between the PPP peer and the ACS). CHAP and MS-CHAP protocols are not supported. PPP session idle time is controlled by the "idle" parameter within the /var/config/options.ttyMU1x files. The default value is 600 seconds. This can only be changed by manually editing these files. The "maxconnect" parameter can also be added to this file in the same fashion (idle and maxconnect values are in seconds). Additionally, if the ACS is to inform the dial in client of a WINS server, add the parameter "ms-wins ipaddress" in the same fashion to the option files. Please Note: any subsequent changes made to the "IP Configuration" section of the Administration menu via the WEB interface will over write manually edited changes to these options files.

IP Networking: The Remote Host IP Addresses (traditionally referred to as the IP Pool) must be on the same network as that of the ACS address (the addresses must use the same network number). The ACS can not; route subnets, masquerade addresses (perform NAT), filter IP packets or implement user defined static routes. The PPP peer (remote host) must be configured to accept a server (ACS) assigned IP address. The ACS implements a "static IP address per POTS port" assignment method. Who ever dials into POTS port 1 will receive the IP address (Remote Host Address field in the Authentication menu) associated with POTS port 1. Whoever dials into POTS port 2 will receive the IP address associated with POTS port 2 and so. The ACS does not support RADIUS assigned IP addresses or DHCP assigned IP Addresses.

RADIUS Authentication problems

General RADIUS Notes: The RADIUS authentication process (protocol) involves Client and Server components. The ACS (be if for Modem Sharing or RAS applications) is a RADIUS Client. For all RADIUS implementations, the RADIUS Server must be configured with (informed of) the IP address of each RADIUS Client (ACS) it is to serve, along with an administrator defined encryption key (Secret password). This secret password is used by both the RADIUS Server and Client and so it must be the same alpha numeric value (including case) in both components. When the RADIUS Client makes an authentication request to the RADIUS Server, it encrypts the "user’s" password with the key (secret). When the RADIUS Server reads the authentication request, it decrypts the password using the secret value. The encryption protocol implemented by the ACS is standard RADIUS encryption MD5.

Trouble shooting an authentication problem solely by what the user encounters can be misleading and inefficient. Determine what the RADIUS Server reports (indicates) for the session.

If the RADIUS server shows the Access Request was Rejected, the ACS was not added to the clients file within the RADIUS server, the user is providing incorrect credentials, or the user doesn’t have appropriate rights (attribute mismatch). Additionally, depending on your RADIUS Server, if the shared secret (key) password is incorrect, the Access Request may be Ignored or Rejected by the RADIUS Server.

If the RADIUS server shows the Access Request was Accepted, but yet the dial up connection was disconnected, most likely then an attribute or attribute value contained within the Access Accept packet is not compatible with the ACS. This is most commonly related to the Framed IP value. The ACS does not support the peer determining it’s own address (RADIUS attribute value of 255.255.255.255)

If the RADIUS server doesn’t see the authentication request, the RADIUS client is not set to the same set of UDP ports as the RADIUS server, the RADIUS client is pointing to the wrong RADIUS server/IP address, or there is a network problem blocking or dropping the request (RADIUS uses UDP to communicate). No response to an Access Request is the same as receiving an Access Reject - the ACS will disconnect the call.

Microsoft Compatibility and the MultiAccess RAS role

Dial Up Networking on the remote workstation: The properties applet usually has 5 tabs, with the "Security" and "Networking" tabs addressing the parameters of concern. The type of security must be "Typical" with "Allow Unsecured Password". This description of "typical" and "unsecured" refers to the PPP authentication protocol of PAP (which transfers the credentials as clear text). On the Networking tab, the TCP/IP component must be set to Obtain IP Address and DNS Automatically. The remaining TCP/IP parameters can be left at default. However for some of the options (depending on your network variables), if they are set incorrectly communication at a certain level may not work (like name resolution or routing issues).

IAS (Internet Authentication Service): There are many variables to IAS and it’s interaction with a Windows user database (Local Users or Active Directory) that go beyond the scope of this document (and beyond the control of an IAS Client). Additionally, even though IAS may already be installed and working with other clients (applications and appliances), this does not mean it’s settings and policies are appropriate when serving a new client (i.e. additional RAS gear).

IAS Clients Properties

Client-Vendor = Standard RADIUS

Signature Attribute not sent

IAS Policy Properties

Condition to match = Service Type Framed

Grant Access if Condition Matches

Profile Settings:

Advanced

Framed Service value = PPP

Service Type value = Framed

Authentication

PAP

IP = Server Settings Define Policy

Modem Sharing

When access to the modem is granted, an "OK" message is issued to the user/socket.

The ACS can not tell which application (on the workstation) is opening the TCP port/socket. Redirectors, telnet clients, and proprietary programs all appear the same to the ACS because they all need to use/follow TCP/IP to get to the modem in the ACS.

Telnet to the modem and issue AT commands, try to dial out. If responses to AT commands are encountered and the destination rings, the ACS and the phone line connected to it are working and acting appropriately.

When the ACS is configured for Modem Sharing with RADIUS Authentication, the user/s must have outbound rights (defined in your RADIUS server). Normally, the attribute of Service Type would be defined as "outbound".

If, from a Windows based computer the intention is to use the modem in the ACS as a TAPI resource (i.e. Dial Up Networking or other application using a modem listed in the Phone and Modems applet), a com port redirector program needs to be installed on the workstation and configured appropriately. The appropriate Multi-Tech modem choice (MT5634SMI-V92) needs to be manually assigned to the virtual com port created by the redirector. In most cases, the Phone and Modems applet can not auto detect a redirected modem solution, nor will it’s diagnostics feature be able to communicate with the modem. These is due to the behavior of the Phone and Modems applet. The com port created by the redirector will not be listed in the device manager, because it is not actually a piece of hardware within the PC.

Setting Up the MCSI200 Com Port Redirector

Add 1 MCSI com port to your workstation (configure it and reboot the workstation). Multiple com ports can be installed and configured within the workstation, but only one MCSI2000 com port at a time can be active within the workstation. The properties of the MCSI com port should be:

Connect Time = 0

Direct (not MAG)

Use Line Defaults = Yes

Server IP address is that of the ACS

Protocol = Telnet

Port Number = 6000 or 700X depending on how the "pool" option is set in the ACS.

Authentication = No (unchecked).

8) Known Issues:

The default Modem Sharing settings in the "Modem Setup" menu of a new unit (No Authentication and Pool - access via TCP port 6000) do not work until the "Update" button for each POTS port is selected. What is meant by "do not work" is, the network client (application opening the TCP socket or virtual com port) will be able to open\establish a socket to the ACS, but there will be no AT command response from the modem (no response to init strings, dial command, etc). Each POTS port will start to respond after the POTS port settings are updated and the socket connection is then re-established. It is recommended to set the Country Code parameter to match your location and then click on the update button. This issue will come back (be created again) if the "restore" command is issued via the command prompt.

The MCSI2000 com port redirector software when set to use Authentication, and the ACS firmware version 1.03 when set to Modem Sharing with Authentication, are not compatible with each other. The compatibility issue relates to how long MCSI2000 will wait for a login prompt to appear (the login prompt is provided by the ACS modem pool). This timing issue does not exist if the ACS firmware is version 1.02, or when instead using the com port redirector DialOutEZ from Tactical Software.

Avoid opening more telnet sessions to the ACS than there is number of available ports. The results are inconsistent and miss leading. The ACS should reject/drop the socket connection if no ports are available, but it does not. The additional socket connection appears connected but gets no response from the modem.

Modem Sharing calls are not logged within the ACS.

 

Last Updated: February 8th, 2008.