Re: Tapi Setup Windows XP Pro SP2
- From: "Thorsten Hoffmann" <t.hoffmann@xxxxxxxxx>
- Date: 26 Jul 2005 08:01:29 -0700
Andreas Marschall [MVP TAPI] schrieb:
> "hoffi42" <t.hoffmann@xxxxxxxxx> schrieb im Newsbeitrag
> news:1122280996.008486.90270@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > I'm trying to setup CTI on Windows XP Pro SP2. The setup so far was a
> > 3rd Party CTI with a Windows 2000 Pro Server as AD Server and CTI
> > Server and mostly Windows 2000 Pro computers as Clients. This has
> > worked out well so far. However, as Windows XP is becoming more and
> > more of an issue here, this has to work as well.
> >
> > When I install the TAPI client on the client (WinXP pro sp2) I cannot
> > see the user defined line. I have already matched the AD user and the
> > telephone line. The usual setup for Tapi.
> >
> > So. The problem is that I cannot see the line named after the AD user
> > on the client that I would usually use to talk to the PBX. Is there
> > anything extra I have to do to enable this? This computer was freshly
> > installed. No services were touched.
>
> Thorsten,
> please take a look at the discussion "TAPI and Win XP SP2" starting on
> 06/09/05 in this newsgroup,
> and do the same tests/checks I suggested in that case.
>
Excellent. I didnt see that thread. But, that was exactly what I was
looking for. I didnt understand half of what you said there, but the
trace was very informative!
This is what part of my log looked like and what gave me the idea for
the solution to this problem:
[1400] 16:50:46:763: [INFO ] init: Server name='192'
[1400] 16:50:46:763: [INFO ] Creating binding...
[1400] 16:50:49:015: [ERROR] init: 192 is not responding
[1400] 16:50:49:015: [INFO ] Ignoring this server
[2628] 16:50:49:030: [INFO ] NetworkPollThread: enter
It seems as if tcmsetup /c under Windows XP SP2 does not understand IP
addresses. I was always wondering why it would show the named line at
all. If it had at least shown the line and the screwed up I wouldve
looked in my code.. but anyways.. Instead of the IP, I used the name of
the server. The server was found, bound, and was ready to rock! Now I
can finally roll out my CTI app on Win XP SP2.
I wish I could post a reply to the other thread too, but it seems that
one was closed.
Thank you so much!
Thorsten Hoffmann
> --
> 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.
.
- Follow-Ups:
- Re: Tapi Setup Windows XP Pro SP2
- From: Andreas Marschall [MVP TAPI]
- Re: Tapi Setup Windows XP Pro SP2
- References:
- Tapi Setup Windows XP Pro SP2
- From: hoffi42
- Re: Tapi Setup Windows XP Pro SP2
- From: Andreas Marschall [MVP TAPI]
- Tapi Setup Windows XP Pro SP2
- Prev by Date: Re: Alcatel OmniPCX Office - using third-party TAPI
- Next by Date: Re: problem executing ITBasicCallControl::connect
- Previous by thread: Re: Tapi Setup Windows XP Pro SP2
- Next by thread: Re: Tapi Setup Windows XP Pro SP2
- Index(es):
Relevant Pages
|
