DialFire™ Model 2977/B4 RAS Server-Based, Enterprise RAS, BRI RAS, & Fax Patton's DialFire™ Model 2977/B4 DialFire Server-Based, Enterprise RAS, BRI RAS, & Fax ISDN communication module provides connections for four BRI lines allowing up to eight simultaneous digital or analog remote access connections.
Need help? Call Patton at +1 301 975 1000 or email sales@patton.com.
Features & Benefits
Dynamic analog/digital/fax support—On-board DSPs provide advanced modem & fax support and maximize the efficiency of each communication channel
Multi-function ISDN RAS—4 BRI interfaces for up to 8 chassis
Advanced DSP Technology—Supports V.90, K56Flex, ISDN, and Advanced FAX applications
Wide OS and third-party application support—The Model 2977 DialFire RAS integrates with, and take advantage of, the inherent communications capabilities built-into Microsoft, Novell, SCO, and Linux server operating environments
The following operating systems: Novell Netware, SCO OpenServer5, and SCO UnixWare are not supported by Patton's RAS Engineering & Technical Support Teams although legacy Digi International drivers are available from Patton's software Upgrade Site. For additional information, contact marketing@patton.com.
Universal server compliance—The Model 2977/B4 DialFire RAS operates within the PCI 2.1 mechanical and electrical specifications, support 3.3 or 5-volt PCI servers, and share common software architecture
Overview
The Patton DialFire™ Model 2977 BRI RAS is the ultimate WAN adapter card for use with BRI lines. It is designed to work in a standard PCI 2.1 slot (5.0 or 3.3 volts) and can terminate four BRI communication lines. Calls can be originated and answered on all 8 channels (2 each for all 4 BRI connections). All channels can handle modem calls (up to 56 kbps—V.90 and K56flex) and B channel calls (64 kbps).
The Patton Model 2977 DialFire Family of DSP (Digital Signal Processor) based RAS (Remote Access Server) concentrator adapters provides the widest compatibility and most powerful performance available in a PCI slot. For demanding, server-based applications including modem-pooling, remote access, advanced fax, World Wide Web and branch office internetworking, you won't find a better product line than the Patton 2977 DialFire RAS.
Applications
Finding a remote access solution that meets the needs of a small office environment is often a challenge. With Patton's 2977/B4 RAS the solution is easy! It's as simple as adding an adapter to your favorite PC server, installing the device driver and configuring your remote access ports. The users can dial-out of your server while other users are dialing-in. The Patton 2977/B4 is a digital adapter that provides connections to four ISDN BRI (Basic Rate Interface) lines allowing up to eight simultaneous digital or analog connections.
Specifications
Modem Data Modes: V.90, K56Flex, V.34, V.34bis, V.32bis, V.32, V.24bis, V.23, V.22bis, V.22, V.21, Bell 212a, Bell 103, TIA TSB37-A, TIA TSB38 Fax Modes: Group 3, V.17, V.29, V.27,V.21 Channel 2 FAX Command Set: Group 3 FAX Class 1, Group 3 FAX Class 2, Group 3 FAX Class 2.0, Class 2.0 Error Correction, All optional 2.0 Data format conversions are supported including: Normal Image, Fine Image, 1D Image Conversion, 2D—MR Image conversion, Copy Quality Checking & Receiving Thresholds, Adaptive Answering, TSI Banner, Distinctive Ring, Caller ID, and IS-101 Voice Command Set. ISDN Specifications: Basic Rate Interface: ITU-T V.110/I.463 Compression & Error Correction: V.42bis, MNP Class2, MNP Class 4, MNP Class 5, V.42 Error Correction (LAPM & MNP) T1/E1 Specifications: T1 Supervision Modes: Ground Start Signaling, Wink Start Signaling, Immediate Start Signaling, & Loop Start. E1 Supervision Modes: CCS with CRC4 ITU G.704, CAS with CRC4 ITU G.704, CRCA with Remote End Block Error signaling, and R2 Signaling Operating System Support: Microsoft > Windows 2000 Server, Windows XP, Windows NT 4.0 • Novell >Netware4.1, Netware 4.11, & Netware 5.1 • SCO> UnixWare 7 SVR5, Open-Server 5 • Linux Compliance: FCC Part 15A, CE Mark, EMC Directive 89/336/EEC, Low-Voltage Directive 73/23/EEC Op. Temp.: 0–50°C (32–122°F) Humidity: 5–90% non-condensing Air Movement: 30 CFM Forced Altitude: 0–12,000 ft (0–3,660 m) Dimensions: 9.21L x 4.20W in. (23.39L x 23.688W cm) Certifications:Safety: USA: UL Recognized, UL 1950 • Canada: CSA Certified, CSA C22.2 No.950 • Europe: EN60950—CE Mark: Australia: AS3260—Telecom: USA: FCC Part 68 • Canada: CS03 • Europe: I-CTR4 (NET 5) • Australia: TSO38—Emission & Immunity: EN50082 Immunity, FCC Part 15, Subpart B
Go into the GUI. Click on the "Interfaces" tab on the left hand side. Then you will want to click on the first "Details..." tab and there you will see the MAC address listed as the "Physical Address:".
Drivers for Windows 2003 Server for the Dialfire 2977?
For Windows 2003 (server) drivers for the 2977 are included in the OS driver database.
What are the minimum system requirements for a 2977 B4U or B4ST?
Pentium 333 Mhz processor or higher
256 MB RAM for Windows 2000
2MB RAM per 2977 port
What types of High Speed Facilities do the US use?
The US uses a T1 (message oriented or robbed bit) line. A message oriented line is a PRI (Primary RateInterface) ISDN line with 23B channels and 1 D channel. Instead of the phone company sending the ring voltage in-band with the data, the digital packet with the hook status is sent in its own channel (D channel) as an out-of-band signal (Common Channel Signaling). The gain from losing one channel (D channel which happens to be channel 24 on a T1) is that the 23 B channels are full 64K able DS0s and are not interrupted by calls coming in on the line. This is the line you want to use if you have users using a ISDN BRI (Basic Rate Interface) and a Terminal Adapter. This line also will tell you information like who is calling and what number was dialed. Robbed bit signaling is a type of in-band signaling (Channel Associated Signaling) used in T1 when the D channel is buried with the B channels, using the least-significant bits to indicate the hook condition. The least significant bits are "robbed" from each DS0 leaving a throughput of 56kb per second. Robbed bit signaling leaves you with 24 DS0s rather than 23 (remember you can only make ISDN BRI calls on a PRI that's the advantage, because the robbing of the bits only allows each DS0 56K and there is no digital channel to send digital packets on).
How do I configure SYSLOGD in my Linux box to create a debug log?
On the Patton you need to do the following:
Go to System Log->Modify.
Set IP address for Syslog Daemon to the IP address of the machine running syslogd. Select Submit Query
Set minimum priority for syslog daemon to the desired level of logging. The lower the number next to the option the more information you get. Verbose is quite verbose. Debug is also probably more logging than you want. Select submit query.
If you want the messages to go into a separate file called local1-local7 then you set the Unix Facility.
The following instructions are valid for Rehat Linux V6.2. The commands may be slightly different for your version of Unix/Linux.
On the Linux machine, if syslogd is running it will automatically start logging information to the /var/log/messages. If you want that information to go to a separate file as indicated by selecting the Unix facility above then do the following:
Go to /etc and edit syslog.conf.
To log messages to local1.log add the following line:
local1.* /var/log/local1.log
For each of local1-local7 you would need to add a line like the one above.
Stop and start syslogd.
To kill the process type: $ killall syslogd
Restart syslogd by going to /sbin and typing: $ ./syslogd or just $ syslogd from any directory if you have /sbin in your path.
Create an empty file for syslogd to write messages to:
cd /var/log
touch local1.log
You would need to touch each localx file you will have syslogd write messages to.
How is the MTU(maximum tranmission unit) determined on a call?
The remote access server has a default MTU of 1524. This is the maximum The MTU of the ethernet media. We recommend that this not be changed. The MTU will be negotiated during LCP negotation for a dial-in user. During LCP negotiation we will tell the remote end we are capable of 1524.
There are two ways in which a customer can receive an MTU that is lower:
1. The RADIUS software returns a Framed-MTU attribute that specifies a lower value. In releases 2.3.3 and lower, we will change the MTU in response to this attribute. In 2.4.1 and above this RADIUS attribute is ignored.
2. The remote modem indicates that an MTU of 1524 is not acceptable and wants 512. We 'give in' to that request and assign 512 as the MTU.
A lower MTU on a dial-in call is not necessarily a bad thing. Most packets that are larger than the MTU of a connection can be broken down and sent down the connection in smaller chunks.
The problem occurs when the remote access server receives a packet larger than the connection's MTU and the packet has the Do Not Fragment bit set. This bit tells the remote access server that it must not split the packet into smaller chunks. Because the remote access server can not split the packet into smaller chunks AND can not send it as-is over the connection, it drops the packet.
What the dial-in user may see is the inability to load certain web sites.
General 