I was really excited to get this to work, but after a
call a dialog box pops up and says:
"Unable to complete an operation requested by the
automatic phone dialer. Please make sure you modem,
phone and phone line are properly configured."
In Asterisk it says:
"== Manager 'outlook' logged on from 192.168.101.12
-- Lauching Dial(Zap/g1/6**3***) on Zap/1-1
-- Called g1/6**3***
== Manager 'outlook' logged off from 192.168.101.12"
The call then goes through just fine, regardless of the
errors in Windows. However if I try to call again
using AstTapi the following error comes up:
"An internal error occurred in the automatic phone
dialer. Close the Dial Phone dialog box, and then open
it again."
If you have any questions or want some further
clarification, please do not hesitate to contact me.
asttapi at outsidethecube . ca
Logged In: NO
I am also experiencing this problem. Windows XP with Outlook
2003.
Logged In: YES
user_id=1142156
In Outlook 2003:
1. TAPI 0.4 currently reports an exception error when placing
a call: "Unable to complete an operation requested by the
automatic phone dialer. Please make sure your modem,
phone, and phone line are properly configured." The dialog
only offers "OK" as an option. Asterisk behaves as expected
and is able to complete the initial call.
2. After experiencing the first error subsequent call attempts
do not appear to make it to asterisk and the user is presented
with: "An internal error occured with the automatic phone
dailer.l Close the Dial Phone dialog box, and then open it
again." This error is also thrown if you try to adjust the "Line
Properties" for the asterisk TAPI driver. It isn't until you close
Outlook completely and subsequently re-start that another
call is able to be placed giving the error listed in error 1 listed
above.
Logged In: YES
user_id=644872
I have the latest build with debug in it which should be
able to produce some useful info. I have come accross a
build issue with some of the programs at this was resolved
just by the latest version. I will post 0.5 very soon. In
the mean time if anyone wants a copy of the debug build let
me know.
Logged In: YES
user_id=1142156
I'd like a copy of .05 and would be glad to assist in testing.
Logged In: NO
I made the same observation. One Call just works fine.
Logged In: YES
user_id=1147935
I've got a couple of years TAPI programming experience
behind me if you need a hand with anything. Happy to have a
look at the debug build.
Logged In: YES
user_id=1148105
I experienced the exact same problem. I would greatly
appreciate getting the debug build or the 0.5 version. Thanks!
Logged In: NO
Same problem here with XP Pro SP2 and Outlook 2003 SP1.
Please send me a debug version and I will try and help track
this problem down.
Logged In: YES
user_id=43516
I am having the same trouble with the same errors on
Windows XP SP2 and Outlook 2003.
Logged In: YES
user_id=644872
0.05 released can people test it and let me know if it has
improved.
Logged In: YES
user_id=43516
Hi, just tested it under Windows XP, SP2, Outlook 2003.
I am able to place a call, when the call goes on hook or if you
hangup during dialing, the following error occurs:
Runtime Error!
Program c:\WINDOWS\System32\svchost.exe
The application has requested the Runtime to terminate it in
an unusual way.
Please contact the application's support team for more
information.
After this, Windows get unstable and becomes unresponsive.
You can't even soft reboot. A forced power off must be
performed to be able to use windows again.
Logged In: YES
user_id=644872
more bugs found - some unhandled exceptions in the main code
around the mutexes for thread safety. 0.06 released can you
let me know ho wit goes.
Logged In: YES
user_id=43516
I tested the new version.
The first time I tried, the first call went through correctly and
when I tried to place a second call, Outlook hanged. I had to
reboot windows.
I have tested since then, and it is working good. You can
place calls, close the window, place calls again, close in the
middle of the conversation using the End Call button
(although the call keeps going until you physically hang the
phone).
I was able to break the app by closing the window,
reopening, placing a new call on a different contact, calling
again, etc. Outlook remained running alghouth tapi got
unstable. A reboot was required. I even crashed Asterisk
while doing this tests...
I will perform additional tests and let you know if I can
reproduce crashes or strange behavior with instructions.
In the meantime, I think it is enough stable to be used.
Keep up the good work!!
Cheers.
Logged In: NO
I see a similar behaviour. Just downloaded the latest
version. One call works fine. The moment the call is
established, the calling application (Outlook or whatever)
crashes. If I restart the application no calls go out
anymore. I have to reboot the computer to get one call
working again.
Is there really no working version out at the moment? TAPI
is not that unimportant after all.
Logged In: NO
Same Problems here Asttapi (0.08) produces Errors after
serveral calls. Any ideas?
Logged In: YES
user_id=1435310
How does the latest release repond??
With the lastest TSP-driver supporting Asterisk v1.2 from
Kirkham systems http://www.kirkhamsystems.com/asttapi
the problem might be solved.
Let's hope Clint at Kirkham systems uploads his source
codes to this page.