I am using Avaya 3rd Party Tapi on Windows SBS 2003
A Windows 2003 Terminal Server running Database that is using Tapi on SBS to connect to the IP Office.
All works ok until we reboot the IP Office.
After reboot Terminal Server is unable to look up the extensions on the IP Office.
If we go to SBS and try and restart the Telephony service to reload TAPI it will hang and only way to resolve this is to reboot the Windows SBS 2003 server.
I wonder if any one has come across this problem and found the fix.
A Windows 2003 Terminal Server running Database that is using Tapi on SBS to connect to the IP Office.
All works ok until we reboot the IP Office.
After reboot Terminal Server is unable to look up the extensions on the IP Office.
If we go to SBS and try and restart the Telephony service to reload TAPI it will hang and only way to resolve this is to reboot the Windows SBS 2003 server.
I wonder if any one has come across this problem and found the fix.