 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
||||
| APC Errors l NT Controller Errors l Network Errors l WCTP Errors l Other Errors | ||||
| TAPI Errors
TAPI errors report problems setting up and using the Windows telephony interface. These errors should represent problems that are specific to TAPI, and not to the process of sending pages in general. For TAPI errors, unless specified below, check the following:
(1400) TAPI error: TAPI initialization failedTo start up TAPI, the program must load some TAPI / operating system DLLs. If the DLLs cannot be loaded, this error will appear. (1401) TAPI error: Could not negotiate common API versionThere are different versions of TAPI available. Windows 95 shipped with TAPI 1.4 and Windows NT 4.0 shipped with TAPI 2.0. InfoRad Wireless tells the system that it can support TAPI 1.4 and the system responds by enabling only the features available in that version. If there is some problem with this process (for example, if the system only supports TAPI 1.3 or lower), you may see this error. Normally, simply rebooting the computer will fix this problem. (1402) TAPI error: Unable to query TAPI address capabilitiesBefore placing a call on a device, the program queries TAPI about the line’s capabilities. This message shows up when TAPI will not or can not respond to the request. (1405) TAPI error: Selected device does not support data callsTAPI devices include modems, fax boards, ISDN telephones, and other devices, not all of which can transfer data the way modems can. Before sending messages, InfoRad Wireless checks to be sure that the device the user selected is in fact a data modem, and not some other TAPI device. (1410) TAPI error: Could not open line deviceBefore placing a call, InfoRad Wireless checks to be sure that the line is available (and shows error 1105 if it is not), but if there is some problem opening the line (even if TAPI claimed the line was available) this is the error message. (1415) TAPI error: Could not specify status messages to monitorAfter opening a line device, the InfoRad Wireless software informs TAPI which status messages are important for the call. If there is a problem doing this, this error appears. (1425) TAPI error: Could not specify port settings prior to opening portBefore placing a call, the InfoRad Wireless software attempts to set the baud rate, data bits, stop bits, flow control, error correction and data compression settings specified for the modem and messaging service in use. If there is a problem doing this, this error appears.
(1435) TAPI error: Could not create call parametersThis error appears if the data structure containing parameters for TAPI cannot be created. This would only happen if the computer ran out of memory. (1440) TAPI error: Call to lineMakeCall() failedInfoRad wireless uses the lineMakeCall() function of TAPI, which opens the serial port. This error appears when this call fails. (1450) TAPI error: No response to lineMakeCall()After placing a phone call with TAPI, the InfoRad Wireless software expects to get some responses back from TAPI, including an announcement that the modems have either connected or disconnected. If those responses don’t arrive within 60 seconds, this error appears. (1455) TAPI error: Couldn't get port handle from TAPIAfter placing the phone call, the InfoRad Wireless software asks TAPI for direct access to the COM port, through which it can send and receive data. If the port handle is unavailable for some reason, this error appears. (1460) TAPI error: Could not change call parametersAfter dialing a call in Override mode (Modem Configuration), the InfoRad Wireless software attempts to switch back to standard TAPI mode to actually send pages, then hang up. If the switch back to standard TAPI mode does not work, this error appears. (1499) TAPI error: Unexpected TAPI errorThis is error message used in cases where the InfoRad Wireless software is able to detect that something has gone wrong with TAPI, but the error is not one of the above listed errors.
Copyright
© 2000 - 2003 InfoRad, Inc. |
||||