RAS and ATS45?

I'm cheating (cut&paste) because I hate typing.....hope this helps. As you didn't specify, I have included articles for both 3.51 and 4.0. The device logging sounds like what you are looking for?

======================================================================
-------------------------------------------------------------------------------
The information in this article applies to:
 
 - Microsoft Windows NT operating system version 3.1
 - Microsoft Windows NT Advanced Server version 3.1
 - Microsoft Windows NT Server versions 3.5, 3.51
 - Microsoft Windows NT Workstation versions 3.5, 3.51
-------------------------------------------------------------------------------
 
For information on Windows NT version 4.0, see the following article in the
Microsoft Knowledge base:
 
   ARTICLE-ID: Q162694
   (http://support.microsoft.com/support/kb/articles/Q162/6/94.ASP)
   TITLE : How to Capture Modem Commands in Windows NT 4.0
 
WARNING: Using Registry Editor incorrectly can cause serious, system-wide
problems that may require you to reinstall Windows NT to correct them.
Microsoft cannot guarantee that any problems resulting from the use of
Registry Editor can be solved. Use this tool at your own risk.
 
If you experience problems connecting to Remote Access Services (RAS),
try to identify the specific problem by doing the following:
 
1. If you are receiving error messages, choose Help and follow the suggested
   steps.
 
2. Check to see if you can access your modem from the Terminal program. If the
   modem works with Terminal, do the following:
 
   a. Make sure your modem is on the list of modems supported by Windows NT
   Remote Access. (See the Windows NT Hardware Compatibility List.)
 
   b. Make sure you have the correct cabling required by Remote Access. For more
   information on RAS cabling requirements, check Remote Access Help. (Search
   on: Cabling Requirements.)
 
3. Enable device logging on Remote Access by doing the following:
 
   a. Start Registry Editor.
 
   b. Go to the following subkey:
 
   hkey_local_machine\system\currentcontrolset \services\rasman\parameters
 
   c. If the value does not exist, choose Add Value from the Edit menu.
 
   d. For the following fields, enter these values:
 
         Value Name: logging<BR/>
         Data Type: REG_DWORD<BR/>
         String: 1
 
   e. Stop and start Remote Access Service and Phone Book to enable the
   DEVICE.LOG file.
 
   The RAS DEVICE.LOG file will be created in the SYSTEM32\RAS subdirectory. See
   the next section for information on using DEVICE.LOG.
 
USING DEVICE.LOG
 
The DEVICE.LOG file contains the strings that are sent to and received
from the serial device (either a modem or an X.25 PAD). DEVICE.LOG is
useful for troubleshooting problems with serial devices, and for
testing new entries added to the MODEM.INF or PAD.INF files.
 
NOTE: You may want to view the DEVICE.LOG file in a text editor that
can display both character and hexadecimal output as some of the
information will not be printable characters. Also, DEVICE.LOG
contains a carriage return (h0D) and line feed (h0A) byte at the end
of each line. These bytes are provided by the program that creates the
DEVICE.LOG file and do not represent information communicated from or
to the device.
 
The DEVICE.LOG file contains:
 
* The command string sent to the device.
 
* The echo of the command.
 
* The response from the device.
 
* The connect and carrier bps (bits per second) (modems only).
 
For each bps pair, there may be several sets of command, echo, and
response data. If the command and echo (on a modem) do not match, a
hardware error message will be generated.
 
The Connect string from the modem (the last response string from the
modem when a connection is established) will normally contain the
connect bps, the carrier bps, or both. If the Connect string contains
both, the connect bps and the carrier bps lines will give the values
from the Connect string. If the Connect string does not have one of
the bps values, a best estimate of the actual bps value is given. Both
of these values are used by RAS; for this reason, RAS initializes the
modem to include both values in its response.
 
NOTE: "Connect bps" refers to the DTE (data terminal equipment) speed
of the modem. This information is required by RAS. The "carrier bps"
refers to the DCE (data communication equipment) or modem-to-modem
speed. This value is not used internally by RAS, but is displayed if
available.
 
If your modem cannot return both the DTE and DCE speeds, configure it
to at least return the DTE speed. Without knowledge of the DTE speed,
RAS cannot reset the port appropriately, thus resulting in
transmission errors.
 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
WINNT:4.0
 

The information in this article applies to:
 
 - Microsoft Windows NT Workstation version 4.0
 - Microsoft Windows NT Server version 4.0
-------------------------------------------------------------------------------
 
SUMMARY
=======
 
Interrogating modem commands sent from the RAS client or server can be useful
troubleshooting tools for diagnosing communications problems.
 
In Windows NT 3.51, the method for capturing modem commands is to enable the
Device.log file. For additional information, please see the following article in
the Microsoft Knowledge Base:
 
   ARTICLE-ID: Q102782
   TITLE : Troubleshooting RAS Problems and Using the Device.log File
 
However, in Windows NT 4.0, when you use UniModem, the Device.log no longer
captures modem commands.
 
MORE INFORMATION
================
 
You can still use the Device.log in Windows NT 4.0 to troubleshoot problems with
Switch.inf and script files. To troubleshoot modem commands in Windows 4.0,
perform the following steps:
 
1. Open Control Panel Modems.
 
2. Select the modem you want to create a log file for.
 
3. Click Properties.
 
4. Click the Connection tab.
 
5. Click Advanced.
 
6. Click to select the "Record a log file" check box. You do not need to restart
   your computer for this setting to take effect.
 
The log file will be created in the %Systemroot% directory, with a name of
Modemlog_<model>.txt, where <model> is your modem's model. For
example, a USR Sportster modem will generate a text file with a name like
ModemLog_Sportster 28800-33600 External.txt.
 

The current theory is that there's a problem with the PABX system at the office, so I might come back after I chased that down.

What to do with the question/points?

You want them, feedback?

Sure, hope you get everthing figured out!