Who actually writes to C:\WINDOWS\TAPI\tsec.ini? Unable to assign a user to more than 14 Lines.

[Donald Lee]

We have a customer who needs to be able to assign each User to 30 or
so Tapi Lines (Each user is assigned to the same 30 Tapi lines),
but using "mmc / TAPIMGMT.MSC" we are only able to assign a User to 14
Tapi Lines.
Using "mmc / TAPIMGMT.MSC" on the 15th assignment of a User (Auby
Taylor in this case) to a 15th line (1026 in this case), the "mmc /
TAPIMGMT.MSC" seems to show
that user Auby Taylor is assigned to the 15th Line 1026 ok (as well as
the other 14 lines). But if you exit the "mmc / TAPIMGMT.MSC" and then
run "mmc / TAPIMGMT.MSC" again, the
Gui does not show Auby Taylor assigned to line 1026 anymore (Auby
Taylor is still assigned to the other 14 lines, just not 15th line
1026).

After tracking down what Tapi is doing when Assigning Users to Lines,
I found (using ProcessMonitor) that TAPI is writing to the file
C:\WINDOWS\TAPI\tsec.ini to save all the User to Line assignments.


When we have user Auby Taylor assigned to 13 different lines the
corresponding entries in the tsec.ini file look like this:

[SEDAPPSLAB\ataylor]
FriendlyUserName=Auby Taylor
Lines=5,5,5,6,5,7,5,8,5,9,5,10,5,11,5,12,5,13,5,14,5,15,5,16,5,3

Where apparently the Lines has the format ProviderId,LineId (our Tapi
Provider Id is 5 I assume), so we have SEDAPPSLAB\ataylor assigned to
13 different Lines.

Then thru "mmc / TAPIMGMT.MSC" if I add a 14th Line to user Auby
Taylor the tsec.ini file entry now looks like this

[SEDAPPSLAB\ataylor]
FriendlyUserName=Auby Taylor
Lines=5,5,5,6,5,7,5,8,5,9,5,10,5,11,5,12,5,13,5,14,5,15,5,16,5,3,5,17

And at the end you can see the 14th Line (5,17) added (everything
good).

Now if I run "mmc / TAPIMGMT.MSC" again to add a 15th line (Line 1026)
to Auby Taylor, the Gui acts like it got added and I see Line 1026
associated with
user Auby Taylor, but if I look at the tsec.ini file, it has not
changed, it still has the same 14 Line entries (the 15th Line entry
never got added to the file).

Looking at ProcessMonitor I do see the file being written to, but
apparently its just writing the same data.

If I exit "mmc / TAPIMGMT.MSC" and then re-run "mmc / TAPIMGMT.MSC" it
then shows Auby Taylor only associated with 14 Lines as they are in
the tsec.ini file.

If I manually edit the tsec.ini file add a 15th Line to user Auby
Taylor, and then bring up "mmc / TAPIMGMT.MSC", it properly displays
Auby Taylor associated
to the 15 Lines just fine (don't know yet whether the Service provider
actually works yet, we are in the process of testing that).


The original developer for the Tapi Service provider no longer works
for the company, but looking at the code I do not see anywhere
where tsec.ini file is getting opened/created. This apparently is
something done within the Microsoft Tapi code and not in the service
provider.

If the tsec.ini data is maintained by the service provider, where is
that being done. No where do I see any user information at all. I see
where

TUISPI_providerConfig: allows a PBX to be assigned.

TUISPI_lineConfigDialog: allows a line and the sublines to be assigned
to a PBX

TUISPI_phoneConfigDialog: this is treated the same as a
TUISPI_lineConfigDialog


But no where do I see any API that deals with assigning a user to a
line/address and I don't see the Gui that is displayed from "mmc /
TAPIMGMT.MSC" for
assigning Users to extensions.

Also I do not see a Dialog Box in the code that has Users to Lines
like is displayed by the "mmc / TAPIMGMT.MSC" gui (I wish I could
attach a .PNG file to show the Gui I am talking about).

We also found the "tsecimp" command which allows you to modify/read
the tsec.ini file, and it also only is able to assign a User to 14
lines or less lines.

The customer is saying they were able to do this before when using
W2k3 and our older Tapi service provider, but upgrading to W2k8 and
our latest Tapi service provider is no longer working.

So exactly who is writing to this C:\WINDOWS\TAPI\tsec.ini file and
why won't the "mmc / TAPIMGMT.MSC" Gui assign a user to more than 14
Lines.

[Andreas Marschall [exMVP TAPI]]

Am Montag, 30. Juli 2012 23:15:11 UTC+2 schrieb Donald Lee:
> So exactly who is writing to this C:\WINDOWS\TAPI\tsec.ini file and why won't > the "mmc / TAPIMGMT.MSC" Gui assign a user to more than 14 Lines.

Donald,
the TSEC.ini is solely maintained by the OS (i.e. Telephony Service, TAPIMGMT.msc).
A TSP is not involved in handling this INI file, so in a TSP there is no code for accessing this file.

Regarding your issue with adding line #15:
In general a line device is automatically removed by TAPISRV from TSEC.ini if the line is removed or the whole TSP is removed.
Since other line devices from the same TSP (ProviderID 5) are not affected: is it possible that there is something "special" with the line 1026 ?
Out of service / disabled? Removed an re-added?

Another thought: is it actually related to line 1026 or to line #15 ?
I.e. do you encounter the same issue when you try to add a different line as line #15 or when you try to add line 1026 not as #15 but as, let's say, #12, i.e. earlier in the enumeration?
Please clarify.

--
Best Regards
Andreas Marschall
Microsoft MVP for TAPI / Windows SDK
TAPI / TSP Developer and Tester
My TAPI and TSPI FAQ:
http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm
My Toto® Tools (a collection of free, mostly TAPI related tools):
http://www.i-b-a-m.de/Andreas_Marschall's_Toto_Tools.htm
* Please post all messages and replies to the group so all may
* benefit from the discussion. Private mail is usually not replied to.
* This posting is provided "AS IS" with no warranties, and confers no rights.

[dlee...@gmail.com]

On Monday, August 27, 2012 7:44:30 AM UTC-5, Andreas Marschall [exMVP TAPI] wrote:
> Am Montag, 30. Juli 2012 23:15:11 UTC+2 schrieb Donald Lee:
>
> > So exactly who is writing to this C:\WINDOWS\TAPI\tsec.ini file and why won't > the "mmc / TAPIMGMT.MSC" Gui assign a user to more than 14 Lines.
>
>
>
> Donald,
>
> the TSEC.ini is solely maintained by the OS (i.e. Telephony Service, TAPIMGMT.msc).
>
> A TSP is not involved in handling this INI file, so in a TSP there is no code for accessing this file.
>
>
>
> Regarding your issue with adding line #15:
>
> In general a line device is automatically removed by TAPISRV from TSEC.ini if the line is removed or the whole TSP is removed.
>
> Since other line devices from the same TSP (ProviderID 5) are not affected: is it possible that there is something "special" with the line 1026 ?
>
> Out of service / disabled? Removed an re-added?

Nothing special with this line. All the lines are basically identical (more below).

> Another thought: is it actually related to line 1026 or to line #15 ?
>
> I.e. do you encounter the same issue when you try to add a different line as line #15 or when you try to add line 1026 not as #15 but as, let's say, #12, i.e. earlier in the enumeration?
>
> Please clarify.

Doesn't matter what line I use to add the 15th line, they all behave the same.

I had our test guy set the machine back up and I just tried different lines and it always fails to add properly on the 15th no matter what Line I use.

I removed the 1st line which is 1013 (leaving only 13 lines associated with the user), then I can add 1026 to the user it works just fine (which now has 14 lines associated with the user). Then if I try to add back 1013 (which would be the 15th line associated to the user) and it fails to be added to the user which was working fine before.

Then if I remove 1026 (leaving only 13 lines associated to the user) then I can add 1013 to the user just fine (because there are only 14 lines now).

I then repeated this with 1014 and it showed the same thing, as soon as I try to add the 15th line, it fails to be added to the tsec.ini file.

An update to the info from the original post, when we had the customer manually add the entries to the tsec.ini file everything worked fine. So for now at least it appears to be working fine if we manually edit the tsec.ini file with notepad and manually put in the lines, but we cannot get the "mmc / TAPIMGMT.MSC" Gui to do this.

Very much appreciate your response to this and any other info you might have,

-Don