tapi server

[felon]

We are using M1 TAPI with out CTI CRM package. The workstations are WINNT4.0.
We are currently licensed for 10 users, but only have 9 TN's registered in TAPI.
Everything worked great for a few weeks and then all of a sudden (out of the Blue) the dialer on the workstations keeps crashing.
I can not figure out if this is an issue with the local workstation, the tapi server or the switch.
Has anyone experienced this before? Or, does anyone have any suggestions on how I might troubleshoot this problem?

Thanks

 

[ccastillo]

Are you using a seperate TAPI server? If so can your clients see the server and can your server still see the clients?
ex1: (from client)Ping <name of TAPI server>
(from server) ping <name of client workstation>

ex2: (from client)net view <name of TAPI server>
(from server) net view <name of client workstation>
example2 actually tests to see if each machine can see shares on the other

Can you test the basic TAPI app on the clients. In other words. We are using Symposium TAPI with Symposium agent. It has a basic TAPI app. that came with it called Julmar Phone. You can run Julmar Phone and make and receive calls through it without having to use the Symp. Agent piece. It tests completely independent. This tells me if basic TAPI is working or if it's actually the Symp. Agent piece.

Is there some sort of relational database that may have been corrupted? When we implimented TAPI we had to assign TN's to computer names so TAPI knows where to POP the screen. If that table becomes corrupted, we lose the screen pop ability.

Finally, if you are using a seperate TAPI server, have you tried rebooting?



Hope This Helps

 

[felon]

Yes, we are using a seperate tapi server configured and networked exactly to Nortel specs.
In other words, we have configured the clan/elan setup.
In telephony app, we have associated the user to tn, so that the dialer knows what TN to associate with.
The only difference here is that our CRM application is calling the dialer. The dialer seems to crash after a while?
We have rebooted the TAPI server many of times.

Anyone got any other ideas?