Sidifen Koe
2014-03-17 08:36:05 UTC
Hello,
I'm working with TAPI for some weeks now and sometimes I have a problem concerning TAPI initialization:
First, everything seems to work fine, but later TAPI seems to crash, the events are not recognized, calls are not possible anymore. Then, when I restart my application, it seems that the TAPI initialization command is in an infinite loop, it does not initialize anymore.
After a system reboot everything works fine again. Just logging out and logging on again does not change anything.
The crashing seems to be different from PC to PC. On some PCs it runs perfectly, on some it crashes sometimes and some where it crashes i. e. after half an hour.
On my developing PC I can reproduce it. To test some new features, I start my application, then I test and close it again. After some time, it crashes.
My application is running on Windows 7 x86 and x64 systems with Siemens phones. Programming language: VB.Net with Visual Studio 2010.
I hope you can help me or give me hints how to find a good workaround for this.
Greets, Sidifen.
I'm working with TAPI for some weeks now and sometimes I have a problem concerning TAPI initialization:
First, everything seems to work fine, but later TAPI seems to crash, the events are not recognized, calls are not possible anymore. Then, when I restart my application, it seems that the TAPI initialization command is in an infinite loop, it does not initialize anymore.
After a system reboot everything works fine again. Just logging out and logging on again does not change anything.
The crashing seems to be different from PC to PC. On some PCs it runs perfectly, on some it crashes sometimes and some where it crashes i. e. after half an hour.
On my developing PC I can reproduce it. To test some new features, I start my application, then I test and close it again. After some time, it crashes.
My application is running on Windows 7 x86 and x64 systems with Siemens phones. Programming language: VB.Net with Visual Studio 2010.
I hope you can help me or give me hints how to find a good workaround for this.
Greets, Sidifen.