Re: TAPI Fails under XP SP2
- From: "Andreas Marschall [MVP TAPI]" <Andreas.Marschall@xxxxxxxxxx>
- Date: Sun, 27 Nov 2005 21:09:30 +0100
"Andreas Marschall [MVP TAPI]" <Andreas.Marschall@xxxxxxxxxx> schrieb im
Newsbeitrag news:%2381dyzi6FHA.3752@xxxxxxxxxxxxxxxxxxxxxxx
> "Danny Connell" <Danny Connell@xxxxxxxxxxxxxxxxxxxxxxxxx> schrieb im
> Newsbeitrag news:35BA07B9-81C9-4628-B6B0-7D24A0953790@xxxxxxxxxxxxxxxx
>> We are upgrading from XP SP1 to SP2. We are currently using Nortel's
>> Symposium Agent as our TAPI client. The server is a Windows NT box
>> running
>> the Symposium TAPI Server.
>>
>> Under SP1 the application works without a problem, but when we test under
>> SP2, we cannot get any TAPI client to working. The first symptom is that
> the
>> device list does not appear. I've tried using Julmar's phone.exe and the
>> enumtapi application. These do not work either. They do not show a
>> device
>> list.
>
> Maybe it is related to the high security setting fix included in XP/SP2
> like
> mentioned in KB 824692 - Client Computer Cannot See or Access the
> Telephony
> Resources on a Server That Is Running Windows Server 2003
>
> I've escalated this question to MS.
Here is the response I got:
KB article 824692 applies to high security setting on the server and was
fixed in XPSP2.
High security requirement was added in XPSP2 to client also for connection
oriented callback(/X option to tcmsetup). But this would have been present
in the remotesp log.
The customer should try and obtain extended error information from RPC.
Since remotesp does not use extended error information, it would require a
network capture or debugger to examine the info.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rpc/rpc/obtaining_extended_rpc_error_information.asp
--
Best Regards
Andreas Marschall
Microsoft MVP for TAPI / Windows SDK
TAPI / TSP Developer and Tester
http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm
* Please post all messages and replies to the newsgroup 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.
.
- References:
- Re: TAPI Fails under XP SP2
- From: Andreas Marschall [MVP TAPI]
- Re: TAPI Fails under XP SP2
- Prev by Date: Re: TSAPI
- Next by Date: register event handler in delphi
- Previous by thread: Re: TAPI Fails under XP SP2
- Next by thread: Re: PBX system recommendation
- Index(es):
Relevant Pages
|
