Re: Third party doubts
From: Andreas Marschall [MVP TAPI] (Andreas.Marschall_at_I-B-A-M.de)
Date: 09/04/04
- Next message: Andreas Marschall [MVP TAPI]: "Re: about TAPI client/server architecture"
- Previous message: Andreas Marschall [MVP TAPI]: "Re: Access to media stream"
- In reply to: Pedro Airo: "Re: Third party doubts"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 4 Sep 2004 15:36:09 +0200
"Pedro Airo" <PedroAiro@discussions.microsoft.com> schrieb im Newsbeitrag
news:4833E4B4-D173-4425-A9EF-0E82D9B0EB66@microsoft.com...
> Hi, i've explain wrong.
>
> From starting, i just want for example, when a phone rings then a window in
> the pc of that user appears with some information there.
> For instance, in the implementation of the 1rst party the phone is
> interacting with the pc by usb, when the phone rings i open an aspx where
the
> information of the person who is contacting me appears.
> now i want the same behavior in a 3rd party model, i just want another
> fucntionalities, but first i want to do the some thing that i have done in a
> 1rst party model.
> i just want to that when a user for example open an aspx that try to call a
> person, then calls that person through the central by a lan cable, and
> associate that information to his phone.
> i guess that the cenario 1 server/central for distribution of incoming calls
> to the users is appropriate.
> i don't understand your question about what tapi apps are involved in my
> cenario.
Pedro,
o.k., here is what you need to port your scenario from 1st to 3rd party using
MS TAPI client/server architecture:
- Domain Controller (all client PCs must be members of this domain)
- Telephony Server (OS: NT4-Srv(PDC) or W2kSrv or WS2k3) needs to be enabled
(NT4: "tcmsetup /S <DomainName\AdminAccountName> <AdminAccountPassword>" ;
W2k/WS2k3: tapimgmt.msc))
- HT170 TSP has to be installed on the Telephony Server
- User/Clients have to be assigned to HT170 line devices on the Telephony
Server (NT4: tcmapp.exe; W2k/WS2k3: tapimgmt.msc)
- Clients need to execute TAPI Client Management setup "tcmsetup /C
<TelephonyServerName>" (this installs RemoteSP.TSP)
- Users can access the new line devices on their Client PCs (each (normal)
user only sees the line device(s) that were assigned to him on the Telephony
Server; administrator will be able to see all lines from the Telephony Server
on each client!). Users can use their existing TAPI app with this new line
instead of the old one (1st party, CallBridge TSP).
- Additionally you can create a new TAPI app (e.g. running on the Telephony
Server) that distributes incoming calls (to an ACD/UCD) to the clients
(agents).
There is a detailed PowerPoint presentation on
"Deploying TAPI-Based Solutions" by David Janson (MS).
The first part is about "Client/Server Telephony".
See "tapi deployment coomsol.ppt" in remotesp.zip on
ftp://ftp.microsoft.com/developr/TAPI/
-- 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.
- Next message: Andreas Marschall [MVP TAPI]: "Re: about TAPI client/server architecture"
- Previous message: Andreas Marschall [MVP TAPI]: "Re: Access to media stream"
- In reply to: Pedro Airo: "Re: Third party doubts"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
