Klaus Darilion
2008-10-17 15:39:28 UTC
Hi experts!
I have a really strange TAPI problem. On a Windows2003 R2 server a TAPI
service provider is installed which offers 20 lines.
User1 logs on via a terminal session and configures dialer.exe to use
line 1.
User2 logs on via a terminal session and configures dialer.exe to use
line 2.
If those users make phone calls using dialer.exe, everything works fine.
User1 uses line 1 and User2 uses line 2.
Now the User1 starts Lotus Notes. There is a Visual Basic script in
Lotus Notes which allows to dial contacts. The VB script triggers the
call by calling tapiRequestMakeCall(...) (should be handled by the
default dialer application). Now the strange thing is, that sometimes
the call of User1 is performed on line 1, sometimes on line 2. I even
once saw, that while dialing via Lotus Notes in User1's session, the
(currently running) dialer.exe in User2's session popped up and
performed the phone call of User1.
Thus, I suspect there is a bug in TAPI when it tries to locate the
default dialer application - as it does not restrict it on a per user
basis, but uses any dialer application.
Has anybody seen this problem too? Is there a fix or workaround for this
problem?
Thanks
Klaus
I have a really strange TAPI problem. On a Windows2003 R2 server a TAPI
service provider is installed which offers 20 lines.
User1 logs on via a terminal session and configures dialer.exe to use
line 1.
User2 logs on via a terminal session and configures dialer.exe to use
line 2.
If those users make phone calls using dialer.exe, everything works fine.
User1 uses line 1 and User2 uses line 2.
Now the User1 starts Lotus Notes. There is a Visual Basic script in
Lotus Notes which allows to dial contacts. The VB script triggers the
call by calling tapiRequestMakeCall(...) (should be handled by the
default dialer application). Now the strange thing is, that sometimes
the call of User1 is performed on line 1, sometimes on line 2. I even
once saw, that while dialing via Lotus Notes in User1's session, the
(currently running) dialer.exe in User2's session popped up and
performed the phone call of User1.
Thus, I suspect there is a bug in TAPI when it tries to locate the
default dialer application - as it does not restrict it on a per user
basis, but uses any dialer application.
Has anybody seen this problem too? Is there a fix or workaround for this
problem?
Thanks
Klaus