Windows Telephony and Converging Communications.ppt

Monday, October 12 Agenda Client/Server Telephony H.323 IP Multicast Conferencing Traditional TAPI Architecture Client/Server Architecture Telephony Server Setup NT 4.0 Server (SP6a) or Windows 2000 Server TCP/IP Install OEM TSP Make sure TSP works on Server Work with OEM Create “Server” user domain acct Enable Telephony Server Set individual line permissions Server Setup – create user create a domain user for the Telephony Server to run under This user account must be in a domain trusted by clients Recommended that it is in the same domain as the client user accounts Recommended that it is named something obvious like “TAPI” or “Telephony” Enable NT 4.0 Telephony Server TCMSetup /s domain/user password TCMSetup.exe is installed with SP6a /q switch available for quiet mode. For automatic ISV setup Enable Windows 2000 Telephony Server MMC – Computer Management “Start” “Programs” “Administrative Tools” “Computer Management” Enable Windows 2000 Telephony Server (cont) NT 4.0 Line Permissions Run TCMApp.exe Windows 2000 permissions Still in Computer Management Select a line and then: “Action” “Edit Users” Client Setup NT 4.0 (SP6a), Windows 9x, Windows 2000 TCP/IP Login via Windows NT user domain account Windows 9x network settings Client for Microsoft Networks Enable File and Print Sharing“ Use “User-Level Access Control Windows 95 “TAPI 2.1 for Windows 95” add-on needed /developr/tapi/tapi2195.zip “tcmsetup /c servername” Again, /q switch available. Perfect for SMS. How remotesp.tsp works How remotesp.tsp works, Step by Step TAPI application on client starts TAPI TAPI loads remotesp.tsp Remotesp.tsp initiates RPC over TCP/IP connection to Server Server validates user Server makes a “Reverse” RPC connection back to client Server assigns lines and completes first remotesp.tsp RPC connection Troubleshooting You know it works when TAPI applications on the client can see their assigned line devices. Problems: Basic Setup Networking Security Client Context