TAPI - Invalid Error Code

[nytony]

Hello,

When trying to dial out using TAPI, I get an generic Invalid Error Code message. Here are the traceoptions:

SecureCRT - Version 6.5.4 (x64 build 555)
[SERIAL-TRACE] : Starting I/O thread 5068
[SERIAL-TRACE] : Tapi: "Standard 56000 bps Modem" opened
[LOCAL] : Stream has closed [CLOSE_TYPE_NONSPECIFIC] : The operation completed successfully.
[SERIAL-TRACE] : Tapi: "Standard 56000 bps Modem" closed
[SERIAL-TRACE] : Waiting 10 seconds for I/O thread 5068 to exit.
[SERIAL-TRACE] : I/O thread 5068 has exited cleanly.
[LOCAL] : Stream has closed [CLOSE_TYPE_NONSPECIFIC] : The operation completed successfully.


Any suggestions on getting this to complete?

Thanks!

[jdev]

The error you're seeing is one that I haven't seen before with TAPI.

SecureCRT version 6.5.x was first released in 2009. It hasn't been in active development since 6.6.x's release in 2010.

Version 6.5.x was officially available for only these versions of Windows:

• Windows Vista
• Windows XP
• Windows Server 2003
• Windows Server 2000

What version of Windows are you currently using with SecureCRT?

Consider trying out the current version of SecureCRT on your machine and see if it is able to successfully talk to TAPI.

If you're stuck running 6.5.x, the only thing I can suggest is that you use the Serial protocol to talk to the COM port of the modem, and issue your dialing commands manually.

While it may not work with as old a version of SecureCRT as you are running, you might try using the TAPI replacement dialer example script and see if you get any better results using a serial session to connect directly to your modem and do the dialing, rather than farming the job off to TAPI.

--Jake