Symposium HDX problem

[mlpress]

Hello All
Currently we have a setup in our company that has 2 SCCS at
separate sites coupled with an HDX at each site. However one site also has a databse that both HDXs point to. When the network goes down briefly or the database is rebooted for maintenance both the symposium and the HDX have to be rebooted for HDX at one site to work properly again. We used to only have to reboot the HDX to sort out this issue. Having to reboot both during business hours is causing major headaches for our call center supervisors. Our Nortel vendor asked us to try to just restart the TFA service on the symposium but it just freezes up when trying to restart so we have to reboot the symposium server anyway. So my question is does anyone know a workaround or what my cause this problem? If we can just get back to rebooting the HDX to sort out this problem that would be fine. Thanks for any feedback concering this is advance
Kind Regards
Mark

 

[rfwhite]

Our software guru says that Symposium was not broadcasting the handle for the HDX object. When we needed to restart we were told to bring TFA_Bridge, TFA, RSM, and Nameserver down and then back up. Even though it causes ACD routing to occur until everything gets happy it seems to fix it.

 

[mlpress]

Thanks for this info. I'll try that next time was there any particular order that you restarted the services? When I stopped the TFA it wouldn't stop but maybe it needed the other service s to stop first. Anyway thanks for this I'll post again as to the outcome.

 

[johnjose]

Sometimes we also have this HDX connection trouble caused by short network outages.
The solution is Symposium Server reboot. When the SCCS reboot is not acceptable for call center managers during the business hours then we use another solution:
We change script variable value for HDX provider ID on Symposium and HDX application ( to the same value of course). Then after only HDX app restart connectivity is restored, everything works fine.
Rem.: We can use our origin provider ID again after the SCCS rebooting.

 

[mlpress]

Thanks John
I'll try this as well. I also think that these problems seemed to have occured after we installed MS and Nortel security patches but I'm not sure it's a good idea to role back on these patches as they covered specific security holes. Thanks again for this info I'll try whatever I can so as to avoid rebooting the Symposium

 

[mlpress]

Hello
Just as an update we are going to upgrade to Symposium 5.0 so that we will no longer need our HDX machine.
Thanks again to all who have given their fedback
Kind Regards
Mark

 

[rfwhite]

Could I have some details on your operation? I don't understand how moving to 5.0 will allow you not to use HDX. What were you using it for originally?

 

[mlpress]

Apparently according to our vendor you can create an ODBC link to a database without going through the HDX anymore as this service is included in the Symposium 5 platform.
Originally we would have our HDX get a request from a database at another site and this request was read by the TFA service in Symposium 4.2. I'm curious myself to see how it will work but if I can avoid rebooting Symposium everytime the network goes down to restore the link that will solve our main problem.

 

[rfwhite]

Right- understood. Our folks are considering the same database change.