Can you be more clear regarding what it's actually doing (or not doing)? Do you simply lose connection to it? Does Symposium Agent Launcher stop responding? I'm not trying to be difficult but just need more detail.
I have also had problems with rls. 2.3.1.6. TAPI (and only TAPI) installed on W2K server. Need to reboot server to get TAPI working again. All services seems to be working fine. This problem has not been seeen om TAPI 3.0.0.6 on another site.
We have the same trouble with TAPI service provider 2.3.1. installed on W2k server.
In fact it can’t be put on the production at all – server has to be restarted several times per day because of freezes.
We have already tried everything to make server working properly without any progress.
Could anybody advice some solution (patch, server configuration, or … ) for this issue, or simply TAPI 2.3.1. doesn’t work on W2k server ?
Is here somebody else who could share either negative or positive experience, please?
From our point of view maybe only one solution is possible – upgrade to rel.3.0….
I have the same problem too. We are running TAPI 2.3.1.6 and after several hours server stops responding (the line is not visible on the workstation). We have quite complicated configuration. We have about 250 lines and to each of the lines are asigned hundreds of users!
What is your configuration?
I have not experienced such a problem on small sites with 20 lines (one user per line).
Well , we decided to Upgrade TAPI TSP 2.3.1.6 to TAPI TSP 3.0 and we are having the same problems (Sometimes the Nortel TSP freezes ...). We have more than 100 Outbound Agentes using Predictive Dial , 32 Inbound IVRs , 32 Predictive Dial Outbound IVRs ... The Predictive Dialer makes call using Nortel Phantom Extensions.
You need to make sure that the account that runs the ACDProxy and Telephony services are logged on by the Domain user that you get up. I have installed several TAPI applications on 2000 server and do not have this problem of freezing up. Reply if you still have the problem, I can give you more details.
I have exactly the same problem like [FCVV]. We upgraded from 2.3.1.6 to 3.0.0.6 but it behaves exactly the same way. We have 340 TNs (each has one ACD and one SCR key). Every TN has about 300 users assigned. It means that all users can use all lines. The tsec.ini file has about 1.3MB. Usually the server stops working after several hours. The pop-screens stop working on clients. All lines disappear on clients. When you start Julmar Phone on Server it works very slowly. Usually it is necessary to kill it.
I thing that it is not the problem of the configuration. I made clean installation of the W2k Server SP4. No anti-virus SW or anything else. I installed TAPI under the domain account which is in Local Administrators group. ACDProxy and Telephony services are running under the domain account. The strange thing is that on old server with Windows NT was TAPI running quite well. Since the upgrade it is disaster!!!
Post the server configuration that you are have the probelms with . What is the RAM and CPU speed of the server, stuff like that!!! Let me know what Patches the server is running. Let me know, I will try to help!!
Make sure that you have disabled APIPA. I see that the server has dual NIC's. You are only using the one, correct??
You do not have Symposium Agent Co-res do you???? If so remove it. Agent is not supported on multi-processors! But the APIPA could be the problem. Make sure that that you have the active NIC (CLAN) first in the binding order. Then disable APIPA by doing the following:
1. Use Registry Editor to create the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
2. Add the following value to this key:
Value name: IPAutoconfigurationEnabled (Exact CaSE)
Value type: REG_DWORD
Value in hexadecimal: 0 (A value of 0 disables APIPA support on thiscomputer)
NOTE: If the IPAutoconfigurationEnabled entry is not present, a default value
of 1 is assumed, which indicates that APIPA is enabled.
3. After you make this change, restart your computer.
Try this let me know if this helps. I think it will!
this time we have both NICs connected and teamed together. Previously ot was as you said. We had only one NIC used. However, regardless which configuration of the NICs we used the sever behaved same way. It means that after several hours it failed.
Anyway I will give it a try.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.