#4 asTapi does not properly support Microsoft Terminal Services

[djimenez]

Hello,

First off, thanks for astTapi. The bosses will be very happy with
this product if we solve this bug and I've convinced them to give
up a bounty or donation if this issue is resolved.

Most of our ACT! users work out of Terminal Services. The
unfortunate thing is that asTapi configures its settings machine
wide instead of per user account. What this means that even
though Joe and Betty are on the terminal server, when you
configure astTapi for Joe those same settings apply for Betty. If
Betty configures astTapi then the settings change for Joe as well.

We use Terminal Server for all of our users, so this prevents us
from rolling out Terminal Services.

If you have any questions or issues feel free to contact me,

Thanks,
Daniel Jimenez

[djimenez]

Logged In: YES
user_id=1083673

Er,

We use Terminal Server for all of our users, so this prevents us
from rolling out Terminal Services.

I mean that it prevents us from rolling out astTapi...

[Jason Sjöbeck]

Logged In: YES
user_id=641762

I wonder if this is a "hk_local_machine" verus
"hk_current_user issue" registry issue. I ahve found the
answer to a couple of these vexxing ones by using regmon.exe
(free from www.sysinternals.com) to find otu such answers.
Maybe you could do a couple quick tests, record some notes,
if they indicate somehting, pass them on to Nick.

Thanks for taking the time to make this possibly a hugely
important add-in!

Thanks.

[Nick Knight]

Logged In: YES
user_id=644872

I have been thinking about this issue as it is not that
simple! The problem is the dll created for the TAPI driver
is run under svchost and not a user account, so you cannot
create registry in a user area of the registry - becuase it
doesn't exsist when called by svchost under win32 - if that
makes sense.

What i have thought of - and will look into is mutiple
lines, so at the mo where you can create a line - host,
channel etc - have the option to define mutliple and then
create extra lines - so you woule end up with a line called
betty-accounts bob-service or whatever? This is what would
be under an option in outlook - or the TAPI app choose a line.

Would this be suitable?

[Mark Dutton]

Logged In: YES
user_id=564979

Hi Nick

Your idea looks good re:multiple lines. It seems not much
has happened on this project for some time. Has it died? Pity
if it has because Asterisk needs some Win32 integration
apps.

I have worked with a very strong CTI system in past years.
This was not a VOIP system, but the CTI was all IP based. It
worked very well on terminal server. I was involved in the beta
phase, but alas the company went bust.

The way they got TS to work well was to create a
management app that automatically installed when it
detected TS on the computer. It split the tapi settings into
two parts. One part was locked to the terminal and used the
clientname environment variable for this and the other part,
the user extension part was locked to the profile. This was a
TDM system with port assigned handsets, so it was
important to know what computer sat next to what handset.
The clientname/port number mapping worked very well as
this was a reliable mechanism for getting a terminal ID.
Obviously ip address is useless because all terminal
sessionsare coming from the same ip address.

With SIP phones, you could map a SIP address to terminal,
but you could still have the preferences for dialing etc in the
HKCU area of the registry.

Good luck if you persevere with this. I would love to see a
good tapi interface that works on TS. TS is the perfect
companion to IP telephony as it is so often deployed across
a WAN.

Cheers

Mark Dutton