Re: client impersonation

Hello Grant

Thanks for your answer and your recommendations. Ok, I'll take back my
statement "it must be possible somehow".
Anyway - we have many different lines (perhaps hundrets or thousands) and
the line filter within the TSP must be somehow auto-selected by the current
applications' user. If we have these problems with the line enumerations
now, then perhaps we could eliminate the enumeration problem this way:
The TSP in TSPI_providerEnumDevices always returns one line called "the
User's own line". Only during the TSPI_lineMakeCall (where I also do
impersonation when starting a thread for doing the call) the correct line
will be selected automatically.
I think this way I can avoid the EnumDevices problem during boot and also
the problem when two users simultanously use the TSP.
What do you think about this solution (implies a lot of code changes)?
Of course this solution has some negative side-effects too (only one line
possible etc.). Or any other ideas of how to solve this problem?

Eric


The remote TSP associates devices with the login specified in the TSP's
configuration. Therefore, when TAPI starts up and initializes the TSP,
the credentials passed by remote TSP to the server are those specified in
the TSP's configuration. It is NOT based on the user application (if any)
which happened to make the first request to TAPI on that machine.

I agree 100% with the advice. Don't attempt to associate lines with the
TAPI application which happens to start first.
--
Grant Schenck


.

Relevant Pages
Loading